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
- custom:open-government-licence-oman 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-om-sample
| Field | Type | Description | Constraints | Title |
|---|---|---|---|---|
| country_code | string | ISO 3166-1 alpha-2 code for the country. | { "pattern": "^OM$", "required": true } | Country Code |
| postal_code | string | Postal code for the location. | { "pattern": "^\\d{3}$", "required": true } | Postal Code |
| place_name | string | Name of the city, town, or place. | Place Name | |
| admin_name1 | string | Governorate (Muhafazah) — ISO 3166-2:OM alpha code, OM- prefix stripped | Administrative Name 1 | |
| admin_code1 | string | Code for the primary administrative division. | Administrative Code 1 | |
| admin_name2 | string | Wilayat (province) — 63 units | Administrative Name 2 | |
| admin_code2 | string | Code for the secondary administrative division. | Administrative Code 2 | |
| admin_name3 | string | Locality / post-office town served by the code | Administrative Name 3 | |
| admin_code3 | string | Code for the tertiary administrative division. | Administrative Code 3 | |
| latitude | number | Latitude coordinate of the place. | Latitude | |
| longitude | number | Longitude coordinate of the place. | Longitude | |
| accuracy | string | Accuracy level of the latitude and longitude coordinates. | Accuracy | |
| alternative_city_name | string | Alternative name(s) for the city or place. | Alternative City Name |
About this dataset
Oman (OM) — licensing trace
Built 2026-08-27 per human instruction: "resource oman and rebuild and run qa
and if all good push to postal-codes and r2." Full trace lives in the
originating project's countries/OMN/research.json (fedex-agents-prototype
repo); this is the summary for this repo.
Layer-by-layer
| Layer | Source | Licence | Status |
|---|---|---|---|
| admin1/admin2 (governorate + wilayat) | NCSI Statistical Year Book 2026, Issue 54 | Open Government License — Sultanate of Oman (attribution-only, no share-alike) | compatible |
| latitude/longitude (111/223 rows) | GeoNames OM dump | CC BY 4.0 | compatible |
| postal codes (213 distinct 3-digit PO Box codes) | UNRECORDED — inherited file, origin never documented | none | residual risk, not cleared |
The unresolved part — read before treating this as a clean "compatible" ship
The postal codes are the actual product being sold, and their origin could not be traced on 2026-08-27: Oman Post (omanpost.om) 404s post-Asyad-rebrand, and neither GeoNames nor Wikipedia carries an Oman postal file. No primary or secondary corroboration exists. The codes are 3-digit PO Box identifiers — facts assigned by a postal authority, likely low originality — but there is no chain of title.
datapackage.json's top-level licence_status.decision is recorded as
"compatible" on the strength of the admin+coordinate layers and an explicit
human risk-acceptance for the postal-code layer specifically. That risk
acceptance is not the same as a verified-clean chain of title. Per this
project's Provenance & Licence Gate (see fedex-agents-prototype/CLAUDE.md
§"Provenance & Licence Gate"), only a genuinely compatible decision should
reach a paid shipping path — a "residual risk, accepted by the human" label
on the core content is functionally closer to unresolved, which the gate
reserves for free/disclosed distribution, not premium sale.
This was flagged back to the human on 2026-08-27 at the same time this was
committed. The is_premium: true / premium_tier: B flags currently in
datapackage.yml were set before this residual risk was surfaced this
clearly — treat them as provisional until the human confirms selling with the
gap disclosed, or the postal-code source is actually re-traced (Asyad/Oman
Post, when reachable).
What ships
om.csv— 218 rows, 13-column postal-codes schema.- Attribution required in README (NCSI + GeoNames) per this repo's licensing convention (opposite of the FedEx-delivery no-sourcing rule).