Early Access: The content on this website is provided for informational purposes only in connection with pre-General Availability Qlik Products.
All content is subject to change and is provided without warranty.
Skip to main content Skip to complementary content

Configuring Qlik GeoCoding

Download the template app

Either Qlik GeoAnalytics Base or Qlik GeoAnalytics Enterprise Server, and Qlik GeoCoding installed is required in order to run.

Download the template app from the Qlik GeoAnalytics Qlik Community site. For QlikView only, during configuration, ensure you insert your QGA connection key.

Information noteUse connector type "Cloud".
Information noteUse your normal LEF key, the Geocoding attribute will be added to your QGA key.

Load the addresses

Replace the example addresses in the “Load Addresses” section of the load script.

Start with a small list, loading only 10-20 test addresses, making sure to use the same names for fields, remapping if necessary.

For example (test addresses_400.xlsx):

addresses:

First 10

LOAD

id,

street,

city,

state,

zip,

country

FROM [lib://ctemp/test_addresses.xlsx]

(ooxml, embedded labels, table is addresses);

Modify paths (if needed)

Modify the paths Qlik GeoCoding uses to locate c:\temp and QGA, if necessary.

Run the load script

Run the script. The results will be saved to a file “AddressPointLookupResult.qvd” in the temp folder.

The QVD file can be imported into other apps, using the “id” field as the key.

Further documentation

Qlik GeoCoding operates using two Qlik GeoAnalytics operations, AddressPointLookup and PointToAddressLookup. The Qlik GeoCoding connector can be used directly in apps, but it’s strongly recommended to build your data set using the template apps, to use the optimal workflow and not overuse the limited number of address lookups. The template app is written for Qlik Sense, but can also be used for QlikView, as the load script is identical.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!