When the Geolocation process is enabled, DQE adds geolocation output columns to the processed file.
These columns help you understand whether geolocation was performed and read the latitude and longitude coordinates returned by DQE.
Who should read this article
Use this article if your file-based batch processing includes Geolocation and you need to understand the DQE geolocation columns added to your output file.
This article applies to file-based batch processing via SFTP. It does not apply to real-time API responses.
Geolocation columns
| Column | Description |
|---|---|
DQE_GEOLOCALISATION_ERROR_CODE |
Return code after Geolocation processing. |
DQE_GEOLOCALISATION_ERROR |
Return code label after Geolocation processing. |
DQE_LATITUDE |
Latitude geographic coordinate. |
DQE_LONGITUDE |
Longitude geographic coordinate. |
Geolocation error code values
The DQE_GEOLOCALISATION_ERROR_CODE column indicates whether geolocation was performed.
| Value | Description |
|---|---|
00 |
Geolocation has been performed. |
03 |
The Hexavia code is missing, and geolocation has not been performed. |
92 |
No geolocation information. |
Geolocation error label values
The DQE_GEOLOCALISATION_ERROR column provides a readable label for the geolocation result.
| Value | Description |
|---|---|
Geolocation is ok |
Geolocation has been performed. |
Hexavia number empty |
The Hexavia code is missing, and geolocation has not been performed. |
No geolocation information |
No geolocation information. |
Best practices
- Use
DQE_GEOLOCALISATION_ERROR_CODEto identify whether geolocation was performed. - Use
DQE_LATITUDEandDQE_LONGITUDEonly when the geolocation status confirms that geolocation was performed. - Review records with missing Hexavia code when geolocation is expected but not returned.
- Keep the original address fields so that you can compare them with the geolocation result.