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

Download sample · CSV · 5.38 kB Report an Issue

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-ie/

├ .licensing-notes.md

https://datahub.io/logistics/postal-codes-ie/_r/-/.licensing-notes.md

├ .migration-notes.md

https://datahub.io/logistics/postal-codes-ie/_r/-/.migration-notes.md

├ ATTRIBUTION.txt

https://datahub.io/logistics/postal-codes-ie/_r/-/ATTRIBUTION.txt

├ README.md

https://datahub.io/logistics/postal-codes-ie/_r/-/README.md

└ datapackage.yaml

https://datahub.io/logistics/postal-codes-ie/_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-ie/_r/-/datapackage.yaml

README.md— documentation

https://datahub.io/logistics/postal-codes-ie/_r/-/README.md

Typical Usage

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-ie-sample

Field	Type	Description	Constraints	Title
country_code	string	ISO 3166-1 alpha-2 -- always IE		Country Code
postal_code	string	Eircode routing key (3 characters) -- NOT the full per-address Eircode	{ "pattern": "^[A-Z0-9]{3}$" }	Postal Code
place_name	string	Principal post town for the routing key		Place Name
admin_name1	string	Province -- 4/4 covered		Administrative Name 1
admin_code1	string	ISO 3166-2:IE code		Administrative Code 1
admin_name2	string	Not populated -- GeoNames carries no routing-key-to-county join for Ireland		Administrative Name 2
admin_code2	string	Not populated		Administrative Code 2
admin_name3	string	Not populated		Administrative Name 3
admin_code3	string	Not populated		Administrative Code 3
latitude	number	GeoNames-estimated latitude (WGS84)		Latitude
longitude	number	GeoNames-estimated 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 CSV

About

Last updated: 2 October 2026
Total rows: 100
Format: CSV
File size: 5.38 kB
Source: GeoNames postal code database -- Ireland (IE)
License: Creative Commons Attribution 4.0 International

About this dataset

Ireland (IE): 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.26 (closed 2026-10-02)
Commit: 75d6657 (worktree commit 7596c5d, identical diff), landed in batch 2; accuracy wording later changed in 5311ad3
Parity verdict: format-only (gate pass)
Producer: custom, refresh disabled

Sources

Input	URL	Notes
GeoNames postal export	https://download.geonames.org/export/zip/IE.zip	Eircode routing keys only (3-character prefix); GeoNames truncates it "for copyright reasons"

The only input the old builder used. The full per-address Eircode database (ECAD) is licensed and out of scope.

Parity against the live zip (2026-10-02)

Rows: 139 live and 139 fresh, none only on one side, 0 changed cells. The only difference is line endings (CRLF→LF): cmp first differs at byte 158, the end of the header. No row_order class.

The informational check against the public sample (postal.datahub.io/ie/ie.csv) came out unexplained; it doesn't affect the gate.

Decisions

Decision	By	Basis
Land with CRLF→LF as the only difference	Gate (`format-only` passes without sign-off)	Recorded under batch 2 in `docs/parity/p5.md`
Drop the old exact-139-rows assert	Orchestrator instruction (P5 brief: no row-count asserts)
Remove row and routing-key counts from README and descriptor; reword the stale `licence_status.decision` sentence; standard accuracy description	Orchestrator instruction (P5 brief)	Kept "all 4 provinces" and the ~2.2M ECAD figure, which isn't a count of this dataset
Accuracy description says GeoNames documents 1/4/6 and other values (e.g. 3) occur upstream	Orchestrator (`5311ad3`, all batch-2 descriptors)	Reported to the user with batch 2; the user replied "agree to all" (session 2479b1c9)

Transforms carried over

From build_postal_codes_product.py:

admin_code1: province letters C/L/M/U → ISO 3166-2:IE (IE-C, IE-L, IE-M, IE-U).
admin_name2 / admin_code2 / admin_name3 / admin_code3 emptied: GeoNames has no routing-key-to-county join for Ireland.
alternative_city_name empty; every other cell verbatim.
The old asserts are ProducerErrors: known province letter, all 4 provinces present, 3-character routing key, unique (postal_code, place_name).
build_postal_codes_product.py and publish_r2.py removed.

Open questions

ATTRIBUTION.txt ("139 rows") and .licensing-notes.md still carry counts; left for the end-of-epic sweep (pc-hfz, which subsumes pc-3d2).

Provenance

Reconstructed 2026-10-05 from the agent transcript 2479b1c9-c4dd-47e5-be82-34ccf8d49a80/subagents/agent-a1eacc948202892db.jsonl, the orchestrator session 2479b1c9-…, the commit messages (75d6657, 5311ad3), the bd close reason and docs/parity/p5.md.