Part of a Data Solution
- Explore →
Postal Codes Solution
Every worldwide postal-code dataset in one bundle — the ultimate global reference for precise postal codes.
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
API Access
Access dataset files directly from scripts, code, or AI agents.
Browse dataset files
API Access
Access dataset files directly from scripts, code, or AI agents.
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.
Start with these files — they give you everything you need to understand and access the dataset.
- 1. Fetch datapackage.yaml to inspect schema and resources
- 2. Download data resources listed in datapackage.yaml
- 3. Read README.md for full context
Data Files
postal-codes-nl-sample
| Field | Type | Description | Constraints | Title |
|---|---|---|---|---|
| country_code | string | ISO 3166-1 alpha-2 country code — always NL | { "pattern": "^NL$", "required": true } | Country Code |
| postal_code | string | Dutch postal code, format 'NNNNAA' (4 digits + 2 letters) | { "pattern": "^[0-9]{4}[A-Z]{2}$", "required": true } | Postal Code |
| place_name | string | Locality (woonplaats) served by the postal code | Place Name | |
| admin_name1 | string | Province (provincie) | Administrative Name 1 | |
| admin_code1 | string | ISO 3166-2:NL province code, prefix stripped (e.g. NH, ZH) | Administrative Code 1 | |
| admin_name2 | string | Municipality (gemeente) | Administrative Name 2 | |
| admin_code2 | string | Reserved — no municipality code in the source; always blank | Administrative Code 2 | |
| admin_name3 | string | Locality (woonplaats) — the third administrative tier | Administrative Name 3 | |
| admin_code3 | string | Reserved — always blank | Administrative Code 3 | |
| latitude | number | Latitude, decimal degrees (WGS84) | Latitude | |
| longitude | number | Longitude, decimal degrees (WGS84) | Longitude | |
| accuracy | string | Coordinate precision tier — BLOCK (postcode-block level) | Accuracy | |
| alternative_city_name | string | Not available for this dataset — always blank | Alternative City Name |
Download
Download sample CSVAbout
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: customwith refresh disabled, and the data stays as harvested from the live zip in09d7c89. - 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
| Decision | By | Basis |
|---|---|---|
| Defer: stay on live data | User, 2026-10-03 | Plan 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
sourcesis now absent. The upstream behind the FedEx delivery isn't identified anywhere (.licensing-notes.mdonly says its base source is CC0), so nothing was invented. Identify it when nl gets a producer (pc-5kk).