Geographic processing

DSS provides a variety of processors to work with geographic information.

Geopoint converters

Most geographic processors in DSS are based on the Geopoint meaning.

DSS provides two processors to convert between a Geopoint column and latitude/longitude columns:

Resolve GeoIP

The Resolve GeoIP processor uses the GeoIP database (https://www.maxmind.com) to resolve an IP address to the associated geographic coordinates.

../_images/geoip-processor.png

It produces two kinds of information:

  • Administrative data (country, region, city, …)

  • Geographic data (latitude, longitude)

The output GeoPoint can be used for Map Charts.

Reverse geocoding

Note

To use this processor, you must first install the DSS plugin called “Reverse Geocoding”. Please see Installing plugins.

The reverse geocoding processor takes geographic coordinates as input and extracts the different levels of administrative boundary to which it belongs (country, region, city …). The administrative boundaries we use are the ones defined in Open Street Map. The type of administrative boundary for each level depends on the country. For more information please refer to the Open Street Map documentation.

  • You need a column containing a Geo Point or a Geometry as input.

  • The processor outputs two columns per administrative level for which you provide a column name: one with the local name of the administrative entity and one with the English name.

Zipcode geocoding

Note

To use this processor, you must first install the DSS plugin called “Zipcode geocoding”. Please see Installing plugins.

This processor provides “Country + zipcode” –> “Geographic coordinates” resolution, at the city-level resolution.

  • You need a column containing the country (name or ISO code) and a column containing the zipcode

  • The processor outputs a Geo Point column

Geo-join

The Geo-join processor performs a geographic nearest-neighbor join between two datasets with geo coordinates.

Geocoding

This processor performs the geocoding of an address using either the MapQuest or Bing API.

For details on which kind of addresses are handled, please see the doc of the associated API.

Warning

This processor requires the use of an API key for the external services. You must comply to the terms of use of these services

API calls can be expensive, depending on your API key usage terms

Warning

This processor (with both API) is extremely slow. Once you are happy with the result, you should export to another dataset so that the processor does not make API call every time you restart the studio.