Input and output mapping for reverse geocoding

Learn more about the input and output mapping attributes for reverse geocoding.

The following table lists the 3 attributes you need to input for the reverse geocode process. The platform selects the nearest address based on the geodistance from these input coordinates.

Table 1. Input mapping
Cleanse attribute	Required?	Description
Latitude	Yes	The latitude coordinate of the location for which you want to locate the address.
Longitude	Yes	The latitude coordinate of the location for which you want to locate the address.
Country	Yes	The 3 character country code of the address.

Here is a sample L3 configuration:

{
  "cleanseFunction": "Loqate",
  "resultingValuesSourceTypeUri": "configuration/sources/ReltioCleanser",
  "proceedOnSuccess": false,
  "proceedOnFailure": true,
  "mapping": {
    "inputMapping": [
      {
        "attribute": "configuration/entityTypes/Location/attributes/Country",
        "mandatory": true,
        "allValues": false,
        "cleanseAttribute": "Country"
      },
      {
        "attribute": "configuration/entityTypes/Location/attributes/GeoLocation/attributes/Latitude",
        "mandatory": true,
        "allValues": false,
        "cleanseAttribute": "Latitude"
      },
      {
        "attribute": "configuration/entityTypes/Location/attributes/GeoLocation/attributes/Longitude",
        "mandatory": true,
        "allValues": false,
        "cleanseAttribute": "Longitude"
      }
    ],
    "outputMappingRef": "configuration/entityTypes/Location/cleanse/mappings/address/outputMapping"
  },
  "params": {
    "radiusFilter": 40
  }
}

Radius filter

Even though you do get an address as a final output, it may not be the exact address you're expecting. It may be the nearest correct address. For instance, it may show the address of one of the houses in a community or one of the shops in a mall, and not the exact house or shop you are looking for. To help you further determine your correct address, use the radiusFilter option in your address cleanser to specify the radius in meters within which the address must be searched. See the example above.

The radiusFilter option determines the radius within which the addresses are to be found, and it is in meters. You can specify a maximum of 300 meters here, which is also the default value. If you want to receive an exact address match, specify this option as 0.

Note: You may raise a Support request to define the radiusFilter option in the tenant physical configuration but the value in the L3 configuration overrides the value provided in the physical configuration.

Output mapping

In the response section, the following 2 fields are added for the reverse geocode service:


Cleanse attribute	Required?	Description
`ReverseGeoStatus`	No	Denotes the status of the address that is matched, which can be any one of the following: `ExactMatch` - when the coordinates of the selected address exactly matches the input coordinates. `RadiusMatch` - when the selected address is not an exact match, but the address falls within the radiusFilter defined in the input or configuration. `NoMatch` - when no addresses are found within the defined radiusFilter. In case a radiusFilter is not defined in the configuration, the default value of 300 meters is considered.
`ReverseGeoDistance`	No	Denotes the distance between the coordinates given as input and the generated address. This is displayed in meters.

A sample is given below:

{
  "uri": "configuration/entityTypes/Location/cleanse/mappings/address",
  "outputMapping": [
    {
      "attribute": "configuration/entityTypes/Location/attributes/VerificationStatus",
      "mandatory": false,
      "allValues": false,
      "cleanseAttribute": "VerificationStatus"
    },
    {
      "attribute": "configuration/entityTypes/Location/attributes/VerificationStatusDetails",
      "mandatory": false,
      "allValues": false,
      "cleanseAttribute": "VerificationStatusDetails"
    },
    :
    :
    {
      "attribute": "configuration/entityTypes/Location/attributes/GeoLocation/attributes/Latitude",
      "mandatory": false,
      "allValues": false,
      "cleanseAttribute": "Latitude"
    },
    {
      "attribute": "configuration/entityTypes/Location/attributes/GeoLocation/attributes/Longitude",
      "mandatory": false,
      "allValues": false,
      "cleanseAttribute": "Longitude"
    },
    {
      "attribute": "configuration/entityTypes/Location/attributes/GeoLocation/attributes/GeoAccuracy",
      "mandatory": false,
      "allValues": false,
      "cleanseAttribute": "GeoAccuracy"
    },
    {
      "attribute": "configuration/entityTypes/Location/attributes/GeoLocation/attributes/GeoDistance",
      "mandatory": false,
      "allValues": false,
      "cleanseAttribute": "GeoDistance"
    },
    {
      "attribute": "configuration/entityTypes/Location/attributes/ReverseGeoDistance",
      "mandatory": false,
      "allValues": false,
      "cleanseAttribute": "ReverseGeoDistance"
    },
    {
      "attribute": "configuration/entityTypes/Location/attributes/ReverseGeoStatus",
      "mandatory": false,
      "allValues": false,
      "cleanseAttribute": "ReverseGeoStatus"
    },
    {
      "attribute": "configuration/entityTypes/Location/attributes/POBox",
      "mandatory": false,
      "allValues": false,
      "cleanseAttribute": "PostBox"
    },
    :
    :
  ]
}

You've found your way to a temporary environment. Content is not complete or final. Looking for Reltio documentation? Go to docs.reltio.com.

Unify and manage your data

Input and output mapping for reverse geocoding

Radius filter

Output mapping

Footer