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
- Creative Commons Attribution 4.0 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-cl-sample
| Field | Type | Description | Constraints | Title |
|---|---|---|---|---|
| country_code | string | ISO 3166-1 alpha-2 country code — always CL | { "pattern": "^CL$", "required": true } | Country Code |
| postal_code | string | 7-digit Chilean postal code, comuna-level (last 4 digits are always 0000) | { "pattern": "^\\d{7}$", "required": true } | Postal Code |
| place_name | string | Comuna name as supplied by the source | Place Name | |
| admin_name1 | string | Region name (Región) | Administrative Name 1 | |
| admin_code1 | string | Official INE/SUBDERE region code (01-15), zero-padded — see derivation note | { "pattern": "^\\d{2}$" } | Administrative Code 1 |
| admin_name2 | string | Province name (Provincia) | Administrative Name 2 | |
| admin_code2 | string | Province code as supplied by the source | Administrative Code 2 | |
| admin_name3 | string | Comuna name | Administrative Name 3 | |
| admin_code3 | string | Official 5-digit comuna code | { "pattern": "^\\d{5}$" } | Administrative Code 3 |
| latitude | number | Latitude, decimal degrees (WGS84) | Latitude | |
| longitude | number | Longitude, decimal degrees (WGS84) | Longitude | |
| accuracy | string | Coordinate accuracy indicator as supplied by GeoNames | Accuracy | |
| alternative_city_name | string | Alternative or historic name for the place where known | Alternative City Name |
Download
Download sample CSVAbout
- Last updated
- 11 October 2026
- Total rows
- 100
- Format
- CSV
- File size
- 11.7 kB
About this dataset
Chile (CL) — internal licensing notes
Status: rebuilt and resolved, per datahub-next#941 §1.2 and the 2026-08-13 comment on that issue (not done in this session — recorded here for institutional memory since I did not do this rebuild myself).
The problem that triggered it (issue #941 §1.2)
"GeoNames deliberately truncates Chilean codes: 'For Chile we have only
the first digits (for copyright reasons)'. Correos de Chile returned 403,
and the workaround was an unattributed GitHub repo found via local-language
search. At our highest price point."
What was done (per the issue comment, 2026-08-13)
Rebuilt from GeoNames' raw CL export to replace an unpackaged, buggy legacy copy:
- Fixed leading-zero stripping on
admin_code1/admin_code3 - Corrected GeoNames' non-official region numbering — derived from the comuna-code prefix instead, verified 100% self-consistent against Chile's real INE codes
- Added CC BY 4.0 attribution and a proper
datapackage.json/README/zipbundle where none existed before
One known, disclosed-not-fixed gap remains: ~21 Ñuble-region comunas are still coded under the pre-2018 Biobío split, because no current comuna→region reference was available to correct it at the time.
Open questions the issue itself flagged, still unanswered
- Correos de Chile's terms of use (their legal pages did not render during the review)
- Chilean statutory position on compilation/database protection is unconfirmed — do not rely on a "facts aren't protected" argument without local counsel
Source: datahub-next#941 (opened by @anuveyatsu, 2026-08-08), comment by @amautadev, 2026-08-13.