Qlik Geocoding Geocoding Template, Data and presentation

[Patric_Nordstrom]

Qlik Geocoding is a subscription service for address to coordinate lookups and vice versa. The service is hosted, address and key get sent to remote servers for lookup. The subscription has a limited amount of lookups and is valid for one year. Qlik Geocoding is an add-on service to Qlik GeoAnalytics Base and Qlik GeoAnalytics Enterprise Server. The service is provided through the Qlik GeoAnalytics Connector using the operations “AddressPointLookup” and “PointToAddressLookup”. Forward geocoding is address to point conversion. The result includes information about match level and location structure. Reverse geocoding is point to address conversion. Useful for example converting GPS coordinates to an location.

To get started

1. Please contact your Qlik sales rep for pricing and license key.
2. Watch the Qlik Geocoding Presentation
3. Download the Qlik Geocoding Template
4. Start converting addresses!

Below you will find templates for use together with the Qlik GeoAnalytics connector for Qlik Sense and QlikView. And also a template for GeoOperations : "Qlik Geocoding Template for GeoOperations.qvf"

[pwagner]

Hello Patric,

thank you. 

The template works for a part of our adresses fine. After some lines we receive following error and we cannot continue the script:

Custom connector error

Connector reply error: QVX_SYNTAX_ERROR: Failed to process query: Failed to create dataset adr: Invalid number of columns at row 43 in CSV data. Make sure to check the quoting.

Do you have an idea what here the issue(s) can be? 

Best regards, Patrick

[Patric_Nordstrom]

Most likely due to odd characters in the indata fields. Run a small sample and try to identify the character.

Thanks,

Patric

[pwagner]

Thanks.

Do you have an idea how I can check the adresses before running the AdressLookUp script?

Best regards, Patrick

[Patric_Nordstrom]

Can be difficult to spot if there are many rows and fields.

I would modify the script to store the result after each lookup call and to narrow down the search, until I find the row with the problem.

[pwagner]

I found one adress which creates the error:

id	street	isocode	city	zip
827	Schönbrunnerstraße 222-228 Stiege 1, 7. Stock	AT	Wien	1100

Do you have an idea what the reason for the error can be?

EDIT: The error was an enter (newline character) in field street. Solved with purgechar(street,CHR(10))

EDIT2: An additional error was caused by ´ within the field street. Solved with replace(street,'´','')

[Patric_Nordstrom]

Ok, great to hear, thanks for posting the solution.

[craigleach]

Patric,

I have a customer with on-prem Geoanalytics. They also have QSE Windows on-prem and QCS/SAAS for consumption. Is using the on-prem Geoanalytics with QCS supported / possible?

Thanks,

Craig Leach

[Patric_Nordstrom]

In QCS the maps and geo calculations are served by maps.qlikcloud.com, no other option.

If you are running a client managed cloud with QSEoK it is possible to connect to an on-prem geo server. It's yaml parameter that is set like this

It is a yaml-parmeter, see https://github.com/qlik-trial/elastic-charts/blob/master/charts/geo-operations/README.md.

config.serverUrl

GeoAnalytics server URL (for routing, location lookups)

https://ga.qlikcloud.com

[julian_rodriguez]

Hello Patric,

Good examples, however, I'd like to test the cluster operation with my own data. ¿Could you provide me an example, please?

thanks

Julian

[pwagner]

Hello @Patric_Nordstrom 

Is it possible to add Adm2Code and the Adm3Code at the lookup? In your template only the Adm1Code is included.

Thank you.

Best regards,

Patrick