Geocoding and reverse — WGS84 & ETRS89/UTM32N

Convert addresses to coordinates and back — in WGS84 (4326) and ETRS89/UTM32N (EPSG:25832). 2.4M access addresses.

Status: Live · all 2.4M coordinates indexed.

What you get

Forward — address → coordinate

From street + house number + postcode, or a single text string.

Reverse — coordinate → address

<10 ms · finds the nearest address from a GPS pin.

Two coordinate systems

Ask for WGS84 for map pins, ETRS89 for surveying.

Pre-calculated lookups

Spatial index on lat/lon — no on-the-fly transformation.

Spatial filters

Bbox, polygon and radius searches (Pro+).

Batch geocoding

1M addresses in batch · async job with a download URL.

Example

# Reverse — coordinate → address
curl 'https://api.danadresse.dk/adgangsadresser/reverse?x=12.5683&y=55.6761'

# Forward — address → coordinate (autocomplete + struktur=full)
curl 'https://api.danadresse.dk/autocomplete?q=R%C3%A5dhuspladsen+1&struktur=full'

How it's used

Map pins & markers

Plot customers, orders, deliveries on a map with precision.

Route planning

Driver app: drive from GPS to address · ETA per pin.

GPS → address

Field service: technician triangulates position to an address ID.

Spatial analysis

Density per postcode, radius stats, choropleth maps.

Drop-in DAWA-compatible

The slug /geokodning follows DAWA's conventions — same paths, same JSON shape, same UUIDs. See the migration guide for the full picture.

Ready to integrate?

Free key, no credit card, 1,000 calls/day.

Start free → Read the API docs →