Postal Codes Dataset for Malaysia, MY

362
0
Updated:
Files:1
Size:6.26 kB
Formats:csv
License:CC-BY-4.0

Postal Codes Dataset for Malaysia, MY 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-my/
https://datahub.io/logistics/postal-codes-my/_r/-/.licensing-notes.md
https://datahub.io/logistics/postal-codes-my/_r/-/README.md
https://datahub.io/logistics/postal-codes-my/_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-my/_r/-/datapackage.yml
README.mddocumentation
https://datahub.io/logistics/postal-codes-my/_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 Malaysia, MY


About this dataset

Malaysia (MY) — internal licensing notes

Not mentioned in datahub-next#941 — no known licensing flag on this country. Sources: MCMC Postcode Dataset via data.gov.my (CC BY 4.0 — postal code, state, city) + GeoNames MY (CC BY 4.0 — coordinates, joined by postal code only; no admin2/admin3 data of its own).

Session finding, 2026-08-19

Fixed my/scripts/ from hardcoded other-repo paths to self-contained. Two real gaps closed, not just paths — this pipeline never had these steps, it always assumed pre-fetched/pre-packaged files existed on disk:

  • Wrote fetch_source.py (didn't exist) to download both sources fresh.
  • run_qa.py now builds my.zip and writes validation_report.json into the delivery folder — publish_r2.py requires both, nothing produced them before.
  • Added the buyer-facing README as a committed static template.

Verified end-to-end from a fresh fetch: 2,931 rows, 16/16 states (exact match). Final my.csv MD5-identical to live R2 (8819f4853269ae71df5204b7771db78d, 158,936 bytes).

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

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

Added standalone my/ATTRIBUTION.txt (MCMC/data.gov.my CC BY 4.0 + GeoNames CC BY 4.0, explicit no-share-alike-sources note) — now in R2 and inside my.zip. build_deliverable.py updated to write it, run_qa.py updated to zip it, on every run. _meta/catalog.json's MY entry rebuilt to include it. No pre-existing defect found.