New version of Geocoding Augmentation Extractor

Geocoding Augmentation Extractor has been rewritten as Docker component and the old version will be switched off by the end of June. Till then its users are kindly requested to migrate their configuration to the new version. Here is how to do it:

  1.  Choose Geocoding v2 from list of extractors
  2. Create new configuration and give it some name as usual
  3. Add extraction configuration
    1. Add one or more input tables to input mapping. Please note that the table must have exactly one column with locations (or two columns with latitudes and longitudes in case of reverse geocoding) or you have to map the one (or two) columns in the input mapping.
    2. Add exactly one table to output mapping which will be filled with result of geocoding.
    3. Fill parameters configuration. It is in json format and must contain method of geocoding, data provider and other optional parameters like api key or locale. See for more details

Geocoding Augmentation component update

Geocoding component now allows to configure which data provider will be used and in which locale the data will be processed. You can choose from Google Maps, Google Maps for Business, Bing Maps, Yandex, MapQuest, TomTom, OpenCage and OpenStreetMap. See Apiary documentation for more details about configuration. Notice that you need to obtain API key for most services first.

Original mode of the component which used mixed providers with our own API keys still works (for configuration tables without attribute provider) but is only temporary to allow you to migrate and will be removed after few weeks.