...
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 the 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"
min_address_precision is the minimum geocoding result precision that is required to save the latitude and longitude values. The recommended value is 8, but you can increase it, to make the rules for result acceptance more strict, or decrease it, to make the rules less strict. The precision is a value returned by the TomTom service together with the geocoding results, which specifies how precise are the returned results based on the TomTom algorithm.
- min_address_similarity is the minimum similarity between the original address and the address returned from the geocoding service. The recommended value is 0.85, but you can increase it, to make the similarity rules more strict, or decrease it, to make the rules less strict. The similarity is a value calculated by comparing the address saved in flex.bi and the results returned from the TomTom geocoding service.
If one of the mentioned minimal values are not met by the result received from the TomTom geocoding service, it is deemed to be too imprecise and is not saved in flex.bi. The affected customer/supplier record is assigned a value of -1 for the property Geocoding needed and is skipped during the next geocoding runs, until the customer/supplier information is altered, providing more address details. Also the address and precision returned from the geocoding service is saved in Address Precision and Geocoding address properties, respectively, to help you determine if you should adjust the address information in flex.bi or the minimum precision or similarity parameters, to get better geocoding results. The calculated similarity is saved in the Address similarity property. To learn more about these limits and adjusting your address data for better geocoding results, see Troubleshooting section below.
...