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
- Creative Commons Attribution 4.0 International 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-be-sample
| Field | Type | Description | Constraints | Title |
|---|---|---|---|---|
| country_code | string | ISO 3166-1 alpha-2 -- always BE | Country Code | |
| postal_code | string | Belgian postal code (4 digits) | { "pattern": "^\\d{4}$" } | Postal Code |
| place_name | string | Commune/locality name | Place Name | |
| admin_name1 | string | Region (Bruxelles-Capitale/Vlaanderen/Wallonie) -- 3/3 covered | Administrative Name 1 | |
| admin_code1 | string | ISO 3166-2:BE region code | Administrative Code 1 | |
| admin_name2 | string | Province -- 11 distinct values (Brussels has no province, treated as province-equivalent) | Administrative Name 2 | |
| admin_code2 | string | ISO 3166-2:BE province code | Administrative Code 2 | |
| admin_name3 | string | Arrondissement -- 43 distinct values, globally unique code | Administrative Name 3 | |
| admin_code3 | string | GeoNames' own 2-digit arrondissement code (not an ISO code) | Administrative Code 3 | |
| latitude | number | GeoNames latitude (WGS84) | Latitude | |
| longitude | number | GeoNames longitude (WGS84) | Longitude | |
| accuracy | string | GeoNames accuracy of latitude/longitude. GeoNames documents 1=estimated, 4=geonameid, 6=centroid of addresses or shape; other values (e.g. 3) occur upstream without documentation. Empty where GeoNames gives none. | Accuracy | |
| alternative_city_name | string | Not populated in this release | Alternative City Name |
Download
Download sample CSVAbout
- Last updated
- 6 October 2026
- Total rows
- 100
- Format
- CSV
- File size
- 9.24 kB
About this dataset
Belgium (BE): migration notes
Internal record of the P5 migration from the old scripts to the producer: the discrepancies found, their causes, and who decided what. This is a dated record, so the numbers are as of the migration and not kept current. It is not shipped in the zip.
- Issue: pc-28e.7.6 (closed 2026-10-02)
- Commit:
e7df6fb(worktree commitf1b4656, same content), landed in batch 1 - Parity verdict:
explained(row_orderonly); user signed off 2026-10-02 - Producer:
custom, refresh disabled
Sources
| Input | URL | Notes |
|---|---|---|
| GeoNames postal export | https://download.geonames.org/export/zip/BE.zip | The only input |
Parity against the live zip (2026-10-02)
Rows: 2,781 live and 2,781 fresh, none only on one side. 0 changed cells. One class: row_order ×1, about 885 rows moved (1,770 diff lines).
| Change | Example | Cause |
|---|---|---|
| Rows reordered within postal codes | 2040 Zandvliet is line 29 in fresh, 31 in live; 2220 Hallaar and 2222 Itegem swapped neighbours | Attributed to GeoNames reordering its export. Not traced to a specific earlier GeoNames file |
The public sample at postal.datahub.io/be/be.csv came out unexplained (informational only); it is the old sample.
Decisions
| Decision | By | Basis |
|---|---|---|
Accept row_order | User, 2026-10-02 (session 2479b1c9) | "I sign off on the row order"; recorded in the sign-off section of docs/parity/p5.md |
| New check: a province must belong to its region | Agent | Structural check added while porting the asserts |
Drop the exact EXPECTED_ROWS == 2781 assert | Orchestrator instruction | Batch brief |
| Remove row, distinct-code and "2726 distinct communes/localities" counts from README and descriptor; keep 3 / 11 / 43 admin-unit counts | Orchestrator instruction; the agent judged 2726 volatile (it counts place names, not communes) | README counts rule (user, 2026-10-02, session 068ca403) |
| README "0 collisions" → the producer checks the key is unique; accuracy description replaced with the shared GeoNames wording | Orchestrator, after the user's "fix the small doc problems" (session 2479b1c9) | b7fb93b, 5311ad3 |
Transforms carried over
From build_postal_codes_product.py:
admin_code1→ ISO 3166-2:BE region code,admin_code2→ ISO province code, by addingBE-(checked against Wikipedia 2026-09-03). Brussels has no province, so its province code repeats the region: BE-BRU.admin_code3kept as GeoNames' 2-digit arrondissement code.alternative_city_nameempty.- Old asserts are
ProducerErrors: unknown region or province, a province with no rows, duplicate (postal_code, place_name), literal "nan", float accuracy, malformed or non-BE row.
Open questions
ATTRIBUTION.txtstill says "2,781 rows"; left for the end-of-epic sweep (pc-hfz).
Provenance
Reconstructed 2026-10-05 from the agent transcript 2479b1c9-c4dd-47e5-be82-34ccf8d49a80/subagents/agent-a5717e75363982765.jsonl, the orchestrator sessions 2479b1c9-… (batch 1, sign-off) and 068ca403-… (README counts rule), the commit message and the bd close reason.