Postal Codes Dataset for Oman, OM

420
Updated:
Files:1
Size:16.7 kB
Rows:218
Formats:csv

Postal Codes Dataset for Oman, OM including name of the city, town, or place, various administrative divisions and alternative city names.

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
  • custom:open-government-licence-oman license
20% off
$49.90$39.92
one-time payment

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-om/
https://datahub.io/logistics/postal-codes-om/_r/-/.licensing-notes.md
https://datahub.io/logistics/postal-codes-om/_r/-/.migration-notes.md
https://datahub.io/logistics/postal-codes-om/_r/-/ATTRIBUTION.txt
https://datahub.io/logistics/postal-codes-om/_r/-/README.md
https://datahub.io/logistics/postal-codes-om/_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-om/_r/-/datapackage.yaml
README.md— documentation
https://datahub.io/logistics/postal-codes-om/_r/-/README.md
Typical Usage
  1. 1. Fetch datapackage.yaml to inspect schema and resources
  2. 2. Download data resources listed in datapackage.yaml
  3. 3. Read README.md for full context

Data Files

postal-codes-om-sample


About this dataset

Oman (OM): migration notes

Internal record of the P5 migration. This is a dated record (2026-10-11) and is not shipped in the zip.

  • Issue: datopian/postal-codes#41 (pc-28e.7.41)
  • Producer: scripts/produce.py (+ test_produce.py), pipeline: producer: custom, refresh disabled
  • Parity: unexplained: 7 of 218 rows (3.2%) have different coordinates, all traced to GeoNames having changed since the live build. Same 218 keys, 0 other changed cells

What the producer does and does not fetch

Oman has no open postal source (Oman Post 404s; GeoNames has no Oman postal file), so the producer is a port of the fedex-agents-prototype chain (countries/OMN: scrape_postal phase 2, rebuild_qa, FedEx→postal-codes conversion) with three curated inputs committed beside it and one fetched:

InputWhereNotes
scripts/stations.csvcommittedThe 220 post-office rows (3-digit PO-Box codes). Origin undocumented (inherited file, git HEAD Oman.csv of the prototype). Residual risk accepted by the owner 2026-08-27
scripts/wilayats.csvcommitted63 wilayats / 11 governorates from the NCSI Statistical Year Book 2026 (Open Government Licence, attribution only). Transcribed from the PDF; not refreshed automatically
scripts/wilayat_corrections.csvcommitted44 rules, each with its own evidence. 3 rules match no row today; harmless
GeoNames OM.zipfetchedCoordinates (AREA) and Arabic names. CC BY 4.0

So the postal codes themselves do not refresh from anywhere; only the coordinates and Arabic names track GeoNames.

Verification

  • Fed the prototype's saved July GeoNames snapshot, the producer logic returns the same 218 rows in the same order as the live om.csv (differs only in CSV quoting bytes, which write_outputs normalises).
  • Fed today's GeoNames dump: 7 rows differ, all in latitude/longitude (one also in the Arabic name).
PostcodePlaceLive pointNew pointJudgement
414, 436, 441Masirah23.194, 57.21220.651, 58.873 (331 km away)New is right: Masirah is an island at about 20.6N 58.9E; the live point is on the mainland
700, 716Al Duqm17.007, 54.12619.662, 57.704 (479 km)New is right: Duqm is at about 19.7N 57.7E; the live point is in Dhofar
146Al Ghubra23.274, 57.70023.589, 58.396 (79 km)New is right: Ghubrah is in Muscat
713Al Kahal17.089, 54.56824.450, 55.910 (830 km)Neither is verified. Both are fuzzy matches (the live one to "Arkāḩāl", the new one to "Kaḩal"); the new point is near the UAE border, far from Al Wusta. Not safe to publish as is

Six of the seven changes fix real errors in the live file. The seventh swaps one doubtful point for another.

Not ready for R2

The 1% bound agreed for this batch is exceeded (3.2%), and 713 is doubtful. Options for the owner:

  1. Accept the 6 corrections and blank the 713 coordinate (a rule "no fuzzy coordinate match is accepted below an exact one", or a one-row exception).
  2. Keep live as is and park this producer.

Decisions

DecisionByBasis
Build a producer despite the 2026-10-03 "no producer without a builder" ruleUser, 2026-10-11The builder chain exists in fedex-agents-prototype; ported rather than invented
Commit stations.csv despite the unknown originCarried overlicence_status residual-risk acceptance 2026-08-27
FedEx "00000" backfill rows not producedAgentThe postal-codes product is a list of postal codes; same as the live file

Other records, unchanged

  • README.md and ATTRIBUTION.txt already credit NCSI (Open Government Licence) and GeoNames (CC BY 4.0) and disclose the unverified postal-code origin. Attribution is mandatory in this product, so nothing is stripped here (unlike the FedEx delivery packager, which removes it).
  • Licence channel for the decision above is postal-codes-r2; it does not cover a FedEx delivery.