DSS provides a variety of processors to work with geographic information
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:
It produces two kinds of information:
- Administrative data (country, region, city, …)
- Geographic data (latitude, longitude)
The output GeoPoint can be used for /visualization/geo_charts
To use this processor, you must first install the DSS plugin called “Reverse Geocoding”. Please see Installing a DSS plugin.
This processor provides “Geographic coordinates” –> “Administrative data” resolution, at the city-level resolution.
- You need a column containing a Geo Point or a Geometry as input
- The processor outputs city, region, country, … columns
To use this processor, you must first install the DSS plugin called “Zipcode geocoding”. Please see Installing a DSS plugin.
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
The Geo-join processor performs a geographic nearest-neighbour join between two datasets with geo coordinates.
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.
API calls can be expensive, depending on your API key usage terms
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.