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-cz-sample
| Field | Type | Description | Constraints | Title |
|---|---|---|---|---|
| country_code | string | ISO 3166-1 alpha-2 -- always CZ | Country Code | |
| postal_code | string | Czech postal code (PSC, 5 digits with a space, NNN NN) | { "pattern": "^\\d{3} \\d{2}$" } | Postal Code |
| place_name | string | Locality/place name | Place Name | |
| admin_name1 | string | Kraj (region) -- 14/14 covered | Administrative Name 1 | |
| admin_code1 | string | ISO 3166-2:CZ code | Administrative Code 1 | |
| admin_name2 | string | Okres (district) -- 77 distinct values (76 real okresy plus Prague, a district-equivalent statutory city) | Administrative Name 2 | |
| admin_code2 | string | GeoNames' own internal district code -- not an official ISO code | Administrative Code 2 | |
| admin_name3 | string | Not populated -- no third admin tier in this source | Administrative Name 3 | |
| admin_code3 | string | Not populated | 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.97 kB
About this dataset
Czechia (CZ): 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.14 (closed 2026-10-02)
- Commit:
9149b8c(worktree commit5c19d40, same content), landed in batch 1 - Parity verdict:
explained(row_orderonly); signed off by the user - Producer:
custom, refresh disabled
Sources
| Input | URL | Notes |
|---|---|---|
| GeoNames postal export | https://download.geonames.org/export/zip/CZ.zip | The only input, as in the old builder. ČÚZK's RÚIAN is stronger but needs a much bigger build |
Parity against the live zip (2026-10-02)
Rows: 15,507 live and 15,507 fresh, none only on one side. 0 changed cells. The only class is row_order ×1: rows within a postal code are reordered. For example, under 100 00 live lists Strašnice, Malešice, Praha 10-Žižkov, …, Vršovice, while fresh puts Vršovice first and moves Strašnice down. No values differ. Consistent with GeoNames reordering its export.
Decisions
| Decision | By | Basis |
|---|---|---|
Accept the row_order difference | User (session 2479b1c9-…, 2026-10-02: "I sign off on the row order") | Batch 1 sign-off, recorded in docs/parity/p5.md |
| Remove "15,507 rows" and "2,694 distinct postal codes" from README and descriptor; keep 14 kraje and 77 okresy | Orchestrator instruction (the README counts rule, user 2026-10-02) | Counts change whenever the data does |
README "0 collisions" → "the producer checks it is unique"; drop the licence_status.decision sentence; standard GeoNames accuracy wording | Orchestrator (batch 1 doc fixes b7fb93b, then 5311ad3), after the user said "Fix the small doc problems you've noticed" | The agent flagged "0 collisions" as a data claim that could go stale |
Leave the row counts in ATTRIBUTION.txt for now | User (session 2479b1c9-…, 2026-10-02: "file a bead to fix it later") | Filed as pc-3d2, folded into pc-hfz |
Transforms carried over
Folded from build_postal_codes_product.py:
admin_code1→ ISO 3166-2:CZ by a name crosswalk of the 14 kraje (Wikipedia, 2026-09-03), not a prefix. GeoNames' own code is a false friend: its 52 is Praha, but ISO CZ-52 is Královéhradecký kraj.- A literal "nan" field becomes empty (the old builder only asserted none were present; upstream currently has none).
alternative_city_nameis empty.admin_name2is kept as-is (76 okresy plus Prague).- The old asserts are now
ProducerErrors: column count and country code, unmapped region name, float accuracy, duplicate (postal_code, place_name), all 14 kraje present. The oldEXPECTED_ROWS == 15507assert is gone.
Open questions
ATTRIBUTION.txtstill says "15,507 rows";.licensing-notes.mdhas historical counts. Both are for pc-3d2 / pc-hfz.
Provenance
Reconstructed 2026-10-05 from the agent transcript 2479b1c9-c4dd-47e5-be82-34ccf8d49a80/subagents/agent-a3f25eea47fd498e5.jsonl, the orchestrator session 2479b1c9-…, the commit messages (9149b8c, b7fb93b, 5311ad3), the bd close reason and docs/parity/p5.md.