About v1
What v1 is, what it cannot do yet — and what it is meant to become.
/v1 is in beta, and it does not cover all of DAWA's dataset.
If you need address data in production today, use [/dawa](?fane=dawa&v=v1&side=introduktion) — it is 1:1 with the official DAWA and fully covered.
What v1 is
/v1 is our own surface on top of the same data as /dawa. It is written from scratch with structured JSON, one consistent error format, ETag caching and enrichments DAWA never had.
/dawa is, and will remain, a faithful copy of the official DAWA. /v1 is what we think a modern version of that same data model ought to look like.
What v1 does NOT cover yet
MEASURED against /dawa: /v1 covers 27 path areas, /dawa 35. These exist today only on /dawa:
- DAGI areas — regions, municipalities, parishes, police districts, judicial districts, nomination districts, multi-member constituencies, electoral provinces, provinces and polling districts
- Place names and places
- Buildings, BBR light and OIS
- History for addresses and access addresses
- Street name/postcode relations
If you need any of those, /dawa is the answer — not because /v1 is worse, but because it has not got there yet.
What v1 can do that /dawa cannot
The other way round, /v1 has fourteen areas the official DAWA never had:
- Soil contamination (V1/V2 mapping), traffic noise and air quality
- Foreclosure auctions from Statstidende
- Public property assessments and listed buildings
- Validation of an address written as free text
- Reverse geocoding with combined enrichment in a single call
What v1 is meant to become
The goal is for /v1 to one day cover everything /dawa does — but in the shape we would have chosen had we built DAWA today: consistent responses, predictable errors, one call where DAWA needs three, and enrichments that otherwise have to be fetched from five different places.
Until then the recommendation is simple:
Building something that has to work now? Use /dawa.
Want to help shape /v1? Use it — and tell us when something is missing.