Geocoding & Reverse Geocoding API — Introduction

This page introduces the DQE Geocoding and Reverse Geocoding APIs used to retrieve coordinates from postal addresses, or address information from coordinates.

DQE offers two sets of API endpoints with equivalent functionality:

• Legacy WS — the original WS-style endpoints, still fully supported.
• RESTful — the newer REST endpoints, recommended for new integrations.

Related Geocoding documentation:

• Geocoding — LATLG endpoint
• Reverse Geocoding — SINGLE endpoint
• Geocoding and Reverse Geocoding Swagger documentation

Geocoding and reverse geocoding overview

Description

The Geocoding and Reverse Geocoding services enrich postal address data with geographical coordinates, or retrieve address information from latitude and longitude coordinates.

Geocoding addresses

Geocoding locates the geographical coordinates (latitude and longitude) of a postal address.

Input data can come from:

• SINGLE: single, precise address input for targeted geolocation.
• FUNNEL: multiple address entries or partial address data used to determine the most accurate geolocation.

This functionality is useful for mapping services, location-based analytics, and applications requiring address-to-coordinate translation.

Reverse geocoding

Reverse geocoding retrieves address information from geographical coordinates and a defined radius.

• Latitude and longitude input: precise coordinates used as the starting point.
• Radius-based search: returns potential addresses within the defined radius.

This service is useful for logistics, real-time location tracking, and localized service delivery.