Anchor step2 step2
Enabling Geocoding Feature
| step2 | |
| step2 |
Geocoding feature is used to convert customer/supplier address data into geographical coordinates that can later be used for data visualization on a Map chart. This feature can be used in any Hansaworld data cube for which customer (CUVc) register is imported.
1. Create a TomTom Account
...
Add the following code to your config/eazybi.toml file:
Anchor step2 step2 Code Block [[regular_jobs]] job = "Geocoding.perform" every = "24h"
Specify a new regular job Geocoding.perform and the frequency for execution of this job. In the code example below, a frequency of 24h is set. You can specify a value that corresponds to your needs.
Add the following code to the [general] section of your config/eazybi.toml file:
Code Block tomtom_api_key = "<your_tomtom_api_key>" tomtom_base_URL = "api.tomtom.com" tomtom_version_number = "2"
In the code block above, you have to replace <your_tomtom_api_key> with your actual TomTom API key. Also you have to check if the defined version is the current version of the API.Define the following plan parameters in the Update Account section's Plan parameters box of your flex.bi account:
Code Block enable_geocoding = true min_address_precision = 8 min_address_similarity = 0.85
You can also use the following plan parameter, to enable debugging mode and log geocoding errors:
Code Block debug_geocoding = "error"
...
If you haven't imported any data yet, proceed with data import.
If you had some data imported, you have already imported data, make sure that you have imported the customer register (CUVc). If you haven't done that, import this register. After importing customer register, geocoding will be run automatically according to the schedule you set in the step 2.
you don't to need to empty the cube. Geocoding process will begin next time, when customer (CUVc) file is imported. To start it right away, just upload or delete data from existing customer (CUVc) file and import application.
...
| Anchor | ||||
|---|---|---|---|---|
|
Troubleshooting
...
If no geocoding results are returned for a customer/supplier or the results are below the minimum precision and similarity limits:
- no geocoding data is stored for this customer/supplier in properties ;
- and it is marked using Geocoding needed property value -1 which means that geocoding has failed for this customer/supplier. In this case, there are a couple things you can try, to get the geocoding data for such customers/suppliers.