Operation

This operation is licensed separately and then only available in the cloud service.

Returns point geometries for each address in a table, i.e. geocoding. Addresses that could not be found for any reason is not returned in the result. Specify either an address string in the Search Text property or structured parts in the corresponding properties, such as Country, Street etc. Combinations are also allowed. A recommendation is to not specify redundant parts which might confuse more than they help. If you for instance have both postal code and postal city and you trust that postal code is correct, then it is best to not specify postal city. It is recommended to always specify country.

Note: To geocode English or Pinyin addresses in China, the Contry parameter must be set to "CHN".

The returned table contains the fields for (values can be empty where data is not available or not applicable):

• Key field - same as the key field for the name table
• Address - The found address, formatted to address standards of the country
• Geometry - The point for the found item
• HouseNumber - The house number for the found item
• Street - The street for the found item
• PostalCode - The postal code for the found item
• City - The name of the city-level administrative division for the found item
• Adm1 - The name or abbreviated name for the first order administrative division (state) for the found item
• CountryIso2 - The country code for the found item
• Match - A value between 0 and 1 that tells how good the match was. 1 means perfect.

Generates rectangular or hexagonal bins for a point dataset. Generates a table with the bin geometries with a field that is an association to the original dataset.

Deprecated. Use closest instead with high closest count.

Returns relations and distances between objects in one dataset and the closest n objects in another, if any is closer than the maximum distance. Adds a field called <dataset1 name>_<dataset2 name>_Distance with the distance in the specified cost unit (default meters) between the objects. The cost may also be calculated along roads and in that case optionally use travel time. This operation is useful in many cases, not only for getting the relations to the closest but also for getting distance matrices between a set of points.

Produces clusters from a point dataset. Returns a table with relations between points and clusters. Also returns a table named Clusters with cluster geometries. It contains the fields ClusterID, ClusterCenter (point geometry) and PointCount. The count field contains the number of points in the cluster.

Dissolves and simplifies areas to form larger areas based on a mapping between old area identities (or geometries) and new area identities. This is typically used for building custom areas that are build up by smaller well defined areas, such as postal areas of administrative areas. Returns a table with the fields:

• <Dissolve Field> - association via the dissolve field
• <Dissolve Field>_Geometry - the geometries of the dissolved areas.

The geometry dataset is optional. If not provided, geometries are supposed to be available in the dissolve definition dataset.

Note that overlaps of polygons are removed in all resolutions except Source.

Returns a table that maps between the key in dataset1 and the key in dataset2 for all objects that intersects. The field names in the returned table will be the same as for the key field in dataset1 and dataset2 respectively. If both datasets contain polygons, the relative overlap area compared to the areas of the original areas are returned in <Dataset1>_RelativeOverlap and <Dataset2>_RelativeOverlap.

The operation is symmetric.

Same as Intersects but only returns the relation to the area in Dataset2 each area in Dataset1 overlaps the most. This operation is useful when you want to build a hierarchy and relate smaller areas to larger areas but the smaller areas might overlap some borders of the larger ones.

Returns location information and point geometries for IP-addresses in a table. This is useful when you are analyzing access data to web services. The returned table contains the following fields:

• <Address Table Ip Field> - same as the ip field that was looked up
• <IP Table name>_Geomety - The point for the found item
• CountryIso2 - The country code for the found item
• <IP Table name>_Adm1Code - The code for the first order administrative area for the found item. Note that this code is not always compatible with the code returned by the location service.
• <IP Table name>_City - The city for the found item

If you have many rows in your loaded data and the field with IP address is the same in many cases, it improves performance to set "Only load distinct" to "Yes" in the properties for the loaded table.

IP geolocation is inherently imprecise. For many IP-addresses it is possible to pinpoint a city but for others only country can be resolved.

This product includes GeoLite2 data created by MaxMind, available from http://www.maxmind.com.

Just loads the dataset, no operation applied. This makes it possible to load all the formats that GeoAnalytics supports.

Returns area geometries for each name in a table by looking them up in the location service. In the location service names for things like countries, administrative areas, airports, postal codes etc are available. The returned table contains the following fields:

• <name table key field> - same as the key field for the name table
• <name table name>_Geomety - the polygon for the found item
• <nameField> - same as the input name field for all successful lookups, only available if the name field is not same as the key field in the name table
• <name table name>_Name - the name from the location database
• CountryIso2 - The country code for the found item
• <name table name>_Adm1Code - The code for the first order administrative area for the found item
• <name table name>_Adm2Code - The code for the second order administrative area for the found item
• LocationDbType - The type code of the found item, see the Location Service Description

The names can be specified as described in the Location Service Description. In that case the type should be set to Any and no country specified. No rows are returned for names not found or when ambiguous.

Returns point geometries for each name in a table by looking them up in the location service. In the location service names for things like countries, administrative areas, airports, postal codes etc are available. The returned table contains the following fields:

• <name table key field> - same as the key field for the name table
• <name table name>_Geomety - the point for the found item
• <nameField> - same as the input name field for all successful lookups, only available if the name field is not same as the key field in the name table
• <name table name>_Name - the name from the location database
• CountryIso2 - The country code for the found item
• <name table name>_Adm1Code - The code for the first order administrative area for the found item
• <name table name>_Adm2Code - The code for the second order administrative area for the found item
• LocationDbType - The type code of the found item, see the Location Service Description

The names can be specified as described in the Location Service Description. In that case the type should be set to Any and no country specified. No rows are returned for names not found or when ambiguous.

This operation is licensed separately and then only available in the GeoAnalytics cloud service.

Returns closest address for points in the list, also known as reverse geocoding. Points that are close to streets will get street level adresses, otherwise it will fall back to return postal area or city level hits. For points too far away, no data is returned. The returned table contains fields for:

• Key field - same as the key field for the name table
• Address - The found address, formatted to the address standard of the country
• Geometry - The point for the found item
• HouseNumber - The house number for the found item
• Street - The street for the found item
• PostalCode - The postal code for the found item
• City - The name of the city-level administrative division for the found item
• Adm1 - The name or abbreviated name for the first order administrative division (state) for the found item
• CountryIso2 - The country code for the found item
• Distance - Distance in meters to the found address.

Calculates routes including length and duration, between two locations in a table. Returns a table with key, length (in meters), duration (in seconds), status (OK or no route found) and a low resolution route line.

Note that the origin is the geometry column in the dataset. The destination column is specified in operation parameters since datasets only know of one geometry column.

If you use "bird" as transportation type it generates great circle arcs between origins and destinations.

There are limitations on the size of non "bird" routes based on number of steps needed to take in the routing graph.

Simplifies the line and area geometries in the dataset. Returns a table with one field that is the key to the dataset to simplify and one with simplified geometries.

The degree of simplification is calculated automatically based on area, number of objects and size of objects. It is then possible to adjust that to a higher or lower resolution with the Resolution parameter.

Area simplification is done with an advanced algorithm that handles topologies and can remove gaps and join islands.

Line simplification is done with a breakpoint reduction algorithm.

Note that overlaps of polygons are removed. There will be no overlapping polygons in the output.

Generates a spatial index for a dataset that is needed for the "Select Visible" feature in the Qlik GeoAnalytics extension. All generated index tables should be included (the ones starting with "IdevioSIndex"). Normally the operation parameters need not be changed from the default values.

Note that the "Select Visible" feature in the Qlik GeoAnalytics extension depends on the variable _IdevioSIndexFields that the load script sets. This means that if you generate the index in advance and load that into your app, make sure to set the variable also. Copy the generated line that looks something like this:

Calculates travel time iso areas. All locations within the returned area can be reached within a certain time or is closer than a certain distance along roads. Returns a table with id, travel area geometry, center point, cost, cost unit and status (OK or failed).

If you use "bird" as transportation type it generates geographically correct circles around the origins.

There are limitations on the size of non "bird" travel areas based on number of steps needed to take in the routing graph.

There is a relation between enclosed and enclosing if enclosed is completely inside the enclosing area. Returns a table which maps between the key in enclosed and the key in enclosing for all found relations. The field names in the returned table will be the same as for the key field in enclosed and enclosing datasets respectively.

Use within typically for finding which areas the data is in. For example to test GPS-position for which administrative area they are in. This is a kind of reverse geocoding.