Postal Codes Dataset for Philippines, PH

194
0
Updated:
Files:1
Size:8.55 kB
Formats:csv
License:CC-BY-4.0

Postal Codes Dataset for Philippines, PH 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
  • Creative Commons Attribution 4.0 license
10% off
$49.90$44.91
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-ph/
https://datahub.io/logistics/postal-codes-ph/_r/-/.licensing-notes.md
https://datahub.io/logistics/postal-codes-ph/_r/-/README.md
https://datahub.io/logistics/postal-codes-ph/_r/-/datapackage.yml
Key Files

Start with these files — they give you everything you need to understand and access the dataset.

datapackage.ymlmetadata & schema
https://datahub.io/logistics/postal-codes-ph/_r/-/datapackage.yml
README.mddocumentation
https://datahub.io/logistics/postal-codes-ph/_r/-/README.md
Typical Usage
  1. 1. Fetch datapackage.yml to inspect schema and resources
  2. 2. Download data resources listed in datapackage.yml
  3. 3. Read README.md for full context

Data Files

Postal Codes Data Resource for Philippines, PH


About this dataset

Philippines (PH) — internal licensing notes

Not mentioned in datahub-next#941 — no known licensing flag on this country. Source: GeoNames PH postal export, CC BY 4.0, refreshed daily. Single-source rebuild — matches docs/PRICING_TIERS.md's own description of PH as Tier B, "no second source is consolidated onto it." (Do not confuse with the separate FedEx-schema PHL build elsewhere, which does consolidate GeoNames + PSGC admin + PSA district membership for a different product with a different pricing model.)

Session finding, 2026-08-19 — a real bug fixed, not just paths

ph/scripts/build_base.py's SOURCE used to point at a snapshot of data already live in R2 (ph_r2_snapshot_2026-08-18.csv) — genuinely circular: if R2 ever lost that data, this script reproduced nothing, because its own input already depended on the thing it was supposed to independently regenerate. It only cleaned known serialization bugs (literal "nan" strings, "4.0"-style accuracy floats, an inconsistent NCR region code).

Fixed: wrote fetch_source.py to download GeoNames PH directly, repointed build_base.py at its output. Verified: exactly 2,317 rows (matches both live R2 and the script's own hard-coded expectation). Cross-checked every row against live R2: all 2,317 postal codes present in both, zero missing/extra. 403 rows show a place_name text difference from the old snapshot — sampled 5/5, all the same benign pattern (GeoNames appended historical-name parentheticals to some Ilocos Norte municipalities since). Known, deliberate gap: alternative_city_name ships empty for every row — it would require GeoNames' separate alternate-names gazetteer dump, not fetched here; documented rather than faked.

No further licensing review — this was a code-reproducibility audit.

CLOSED — 2026-08-24 (datahub-next#941 §4)

Added standalone ph/ATTRIBUTION.txt (GeoNames CC BY 4.0 notice + warranty disclaimer) — now in R2 and inside ph.zip. package.py updated to write and zip it on every run. _meta/catalog.json's PH entry rebuilt to include it. No pre-existing defect found — README and datapackage.json were already correct.