Postal Codes Dataset for Denmark, DK

458
Files:1
Formats:csv
License:CC-BY-4.0

Postal Codes Dataset for Denmark, DK including name of the city, town, or place, various administrative divisions and alternative city names.

Part of a Data Solution

  • Postal Codes Solution

    Every worldwide postal-code dataset in one bundle — the ultimate global reference for precise postal codes.

    Explore →

Premium

You're viewing a free sample

Get the complete dataset — all rows and files — delivered instantly after checkout, with lifetime access to the latest version.

  • Secure checkout via Stripe
  • Instant download after payment
  • Lifetime access to the latest version
  • Creative Commons Attribution 4.0 International license
20% off
$49.90$39.92
one-time payment

API Access

Access dataset files directly from scripts, code, or AI agents.

Browse dataset files
Dataset Files

Each file has a stable URL (r-link) that you can use directly in scripts, apps, or AI agents. These URLs are permanent and safe to hardcode.

/logistics/postal-codes-dk/
https://datahub.io/logistics/postal-codes-dk/_r/-/.licensing-notes.md
https://datahub.io/logistics/postal-codes-dk/_r/-/.migration-notes.md
https://datahub.io/logistics/postal-codes-dk/_r/-/ATTRIBUTION.txt
https://datahub.io/logistics/postal-codes-dk/_r/-/README.md
https://datahub.io/logistics/postal-codes-dk/_r/-/datapackage.yaml
Key Files

Start with these files — they give you everything you need to understand and access the dataset.

datapackage.yaml— metadata & schema
https://datahub.io/logistics/postal-codes-dk/_r/-/datapackage.yaml
README.md— documentation
https://datahub.io/logistics/postal-codes-dk/_r/-/README.md
Typical Usage
  1. 1. Fetch datapackage.yaml to inspect schema and resources
  2. 2. Download data resources listed in datapackage.yaml
  3. 3. Read README.md for full context

Data Files

postal-codes-dk-sample


About this dataset

Denmark (DK): migration notes

Internal record of the P5 migration. This is a dated record (2026-10-05) and is not shipped in the zip.

  • Issue: pc-28e.7.16 (open, deferred)
  • Producer: none written. The descriptor keeps pipeline: producer: custom with refresh disabled, and the data stays as harvested from the live zip in 09d7c89.
  • Parity: not run (no producer).

Why it stays on live data

  • The DAWA API (api.dataforsyningen.dk, dawa.aws.dk) permanently returns 410 Gone for postnumre, kommuner and regioner, so the old scripts/build_postal_codes_product.py can't fetch.
  • Successor: the Datafordeler DAR REST postnummer endpoint (services.datafordeler.dk/DAR/DAR/1/rest/postnummer, 200, no auth) has only postnr and navn. Municipality, region and geometry need other registers, and graphql.datafordeler.dk is 401 (needs credentials).
  • For a producer, the old builder's behaviour to keep: rows sorted by postal_code, CRLF in live, coordinates to 5 dp, accuracy AREA, and 8 municipality overrides (2770 3760 2610 2650 2605 2730 8970 4291).

Decisions

DecisionByBasis
Live data unchanged meanwhileOrchestrator, 2026-10-03Plan D1
Defer under D1: stay on live data, no Datafordeler move for nowUser, 2026-10-05DAWA is gone; Datafordeler needs credentials plus a new licence check

Open questions

  • Revisit if Datafordeler credentials are obtained. That needs a new licence check for the Datafordeler registers (DAR plus whichever registers provide municipality, region and geometry).

Provenance

Written 2026-10-05 from docs/parity/p5.md and the bd notes on pc-28e.7.16.