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
- Turkmenpochta public branch locator -- factual directory data (branch name, postal code, public address); no licence or terms of use published by the source 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-tm-sample
| Field | Type | Description | Constraints | Title |
|---|---|---|---|---|
| country_code | string | ISO 3166-1 alpha-2 -- always TM | Country Code | |
| postal_code | string | Turkmen 6-digit postal code | { "pattern": "^\\d{6}$" } | Postal Code |
| place_name | string | Post office branch name (this source is a branch locator, not a settlement gazetteer) | Place Name | |
| admin_name1 | string | Region -- 7/7 regions covered (5 welayat + Ashgabat + Arkadag) | Administrative Name 1 | |
| admin_code1 | string | ISO 3166-2:TM region code -- blank for Arkadag, which has no ISO code assigned (a 2023-created 'city of state importance') | Administrative Code 1 | |
| admin_name2 | string | Not populated -- no second admin tier in this source | Administrative Name 2 | |
| admin_code2 | string | Not populated | Administrative Code 2 | |
| admin_name3 | string | Street address of the branch (the finest location detail this source provides) | Administrative Name 3 | |
| admin_code3 | string | Not populated | Administrative Code 3 | |
| latitude | number | Not populated -- this source carries no coordinates | Latitude | |
| longitude | number | Not populated -- this source carries no coordinates | Longitude | |
| accuracy | string | Not populated | Accuracy | |
| alternative_city_name | string | Not populated in this release | Alternative City Name |
About this dataset
Turkmenistan (TM): migration notes
Internal record of the P5 migration. This is a dated record (2026-10-05) and is not shipped in the zip.
- Issue: pc-28e.7.54 (open, deferred)
- Producer: none written. The descriptor keeps
pipeline: producer: customwith refresh disabled, and the data stays as harvested from the live zip in09d7c89. - Parity: not run (no producer).
Why it stays on live data
post.tm/departmentsis an SPA. The data is only available from/api/departments, which robots.txt disallows..licensing-notes.mdrelies on not touching/api/.- Options: (1) call
/api/departmentsdirectly throughhttp_get; (2) render headless with Playwright (a new dependency, and the browser still hits/api/). Either one means revisiting the licensing notes. - If approved, the producer would map the 7 regions to ISO, leave Arkadag blank, use PK (postal_code, place_name), and have no coordinates.
Decisions
| Decision | By | Basis |
|---|---|---|
| Live data unchanged meanwhile | Orchestrator, 2026-10-03 | Plan D1 |
Defer under D1: stay on live data; don't call /api/ | User, 2026-10-05 | robots.txt disallows /api/, and .licensing-notes.md relies on not touching it |
Open questions
- Revisit only if post.tm publishes the data outside
/api/or relaxes robots.txt.
Provenance
Written 2026-10-05 from docs/parity/p5.md and the bd notes on pc-28e.7.54.