Postal Codes Dataset for Netherlands, NL

563
Files:1
Formats:csv

Postal Codes Dataset for Netherlands, NL 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
  • CC0 1.0 Universal (public domain) — LJPc-solutions postal codes and coordinates license
20% off
$99.90$79.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-nl/
https://datahub.io/logistics/postal-codes-nl/_r/-/.licensing-notes.md
https://datahub.io/logistics/postal-codes-nl/_r/-/.migration-notes.md
https://datahub.io/logistics/postal-codes-nl/_r/-/ATTRIBUTION.txt
https://datahub.io/logistics/postal-codes-nl/_r/-/README.md
https://datahub.io/logistics/postal-codes-nl/_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-nl/_r/-/datapackage.yaml
README.md— documentation
https://datahub.io/logistics/postal-codes-nl/_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-nl-sample


About this dataset

Netherlands (NL): 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.38 (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 old builder (scripts/convert_from_fedex.py) read a manually staged FedEx export. That file was local and no longer exists, so the build can't be rerun.
  • Its upstream, the LJPc-solutions address files, would need a new pipeline, not a port.

Decisions

DecisionByBasis
Defer: stay on live dataUser, 2026-10-03Plan D1; no rerunnable source

Open questions

  • Revisit once there's a decision on a new pipeline from the LJPc-solutions upstream.

Provenance

Written 2026-10-05 from docs/parity/p5.md (batch sign-offs) and the bd notes on pc-28e.7.38.

2026-10-06: sources placeholder dropped (pc-dky)

  • The 'Multiple sources' placeholder is gone and sources is now absent. The upstream behind the FedEx delivery isn't identified anywhere (.licensing-notes.md only says its base source is CC0), so nothing was invented. Identify it when nl gets a producer (pc-5kk).