Postal Codes Dataset for Moldova, Republic of, MD

285
Updated:
Files:1
Size:106 kB
Rows:1,753
Formats:csv
License:CC-BY-4.0

Postal Codes Dataset for Moldova, Republic of, MD 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 International 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-md/
https://datahub.io/logistics/postal-codes-md/_r/-/.licensing-notes.md
https://datahub.io/logistics/postal-codes-md/_r/-/.migration-notes.md
https://datahub.io/logistics/postal-codes-md/_r/-/ATTRIBUTION.txt
https://datahub.io/logistics/postal-codes-md/_r/-/README.md
https://datahub.io/logistics/postal-codes-md/_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-md/_r/-/datapackage.yaml
README.md— documentation
https://datahub.io/logistics/postal-codes-md/_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-md-sample

About

Last updated
6 October 2026
Total rows
100
Format
CSV
File size
6.05 kB

About this dataset

Moldova (MD): 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.34 (closed 2026-10-02)
  • Commit: a7ad9eb (worktree commit 011fe18), landed in batch 2
  • Parity verdict: explained (row_order only); signed off by the user
  • Producer: custom, refresh disabled

Sources

InputURLNotes
GeoNames postal exporthttps://download.geonames.org/export/zip/MD.zipThe only input; same URL as the old builder

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

Rows: 1,753 live and 1,753 fresh, none only on one side, 0 changed cells. Line endings went from CRLF to LF.

Cause: GeoNames reordered its export (upstream drift). Sorted, the two files are identical, and the postal-code sequence is the same. 539 row positions differ across 234 postal codes, always within one postal code.

Postal codeLive orderFresh order
MD-6537Balmaz, MirnoeMirnoe, Balmaz
MD-6511Botnaresti one row higherBotnaresti one row lower

The informational 100-row sample check reported unexplained against postal.datahub.io/md/md.csv. It doesn't feed the gate, and the cause was not traced.

Decisions

DecisionByBasis
Accept row_orderUser, 2026-10-02 (session 2479b1c9-…, "agree to all" to the batch-2 sign-off question)Recorded in the sign-off section of docs/parity/p5.md
Map every "Tr." label, including "Bender Tr.", to MD-SN rather than Bender's own de jure code MD-BDAgent: a faithful portThe old builder did this; disclosed in ATTRIBUTION.txt
Keep "Lazo" with a blank admin_code1Agent: a faithful portIts unit can't be resolved; the old builder left it blank rather than guess
Reword the accuracy description to admit undocumented valuesOrchestrator (commit 5311ad3, batch 2); reported to the user with the batch-2 resultsThe agent found accuracy 3 on 69 rows (live and fresh). The standard text said "GeoNames documents no other values"
Remove row and distinct-code counts from README and description; keep "35/37 units"Orchestrator instruction (README counts rule, plan §4 P5)Counts drift; admin-unit counts are fixed

Transforms carried over

From build_postal_codes_product.py (now removed, with publish_r2.py):

  • admin_name1 labels → ISO 3166-2:MD admin_code1 plus a clean display name, via a name crosswalk. GeoNames' own admin_code1 is dropped.
  • Typo and variant labels merged: Cantrmir → Cantemir, Canul → Cahul, Uhnheni → Ungheni, Mun.Balti → Balti, Mun.Chisinau → Chisinau, Comrat → Gagauzia, the three "Criuleni-Dub." spellings and "Dubasari Cr." → Dubasari (MD-DU).
  • Every "Tr." label → MD-SN "Stinga Nistrului (Transnistria)".
  • alternative_city_name is empty.
  • The old asserts are now ProducerErrors: unknown admin_name1 label, literal "nan", float-formatted accuracy, duplicate (postal_code, place_name). Added: postal codes match MD-NNNN, and every crosswalk unit has rows. Basarabeasca has no rows in GeoNames and isn't in the crosswalk.

Open questions

  • Resolved (2026-10-05, pc-28e.7.60): README now says "GeoNames accuracy code" with no code list. Was: README.md still lists the accuracy codes as "(1/4/6)", though the data has 3s. Only the descriptor was reworded.
  • ATTRIBUTION.txt ("1,753 rows") and .licensing-notes.md still contain counts; they are left for the end-of-epic sweep (pc-hfz).

Provenance

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