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.yml to inspect schema and resources
- 2. Download data resources listed in datapackage.yml
- 3. Read README.md for full context
Data Files
Postal Codes Data Resource for Argentina, AR
| Field | Description | Title |
|---|---|---|
| country_code | ISO 3166-1 alpha-2 code for the country. | Country Code |
| postal_code | Postal code for the location. | Postal Code |
| place_name | Name of the city, town, or place. | Place Name |
| admin_name1 | Primary administrative division (e.g., state, region). | Administrative Name 1 |
| admin_code1 | Code for the primary administrative division. | Administrative Code 1 |
| admin_name2 | Secondary administrative division (e.g., county, district). | Administrative Name 2 |
| admin_code2 | Code for the secondary administrative division. | Administrative Code 2 |
| admin_name3 | Tertiary administrative division (e.g., municipality, borough). | Administrative Name 3 |
| admin_code3 | Code for the tertiary administrative division. | Administrative Code 3 |
| latitude | Latitude coordinate of the place. | Latitude |
| longitude | Longitude coordinate of the place. | Longitude |
| accuracy | Accuracy level of the latitude and longitude coordinates. | Accuracy |
| alternative_city_name | Alternative name(s) for the city or place. | Alternative City Name |
Download
Download sample CSVAbout
- Last updated
- 30 August 2026
- Total rows
- ...
- Format
- CSV
- File size
- 1.35 MB
About this dataset
Argentina (AR) — licensing trace
Checked 2026-08-29. Starting from zero — no prior work anywhere for this
country code (no .licensing-notes.md, no scripts, no countries/ARG/ in
the sibling fedex-agents-prototype repo).
Postal system
Argentina's current system is the CPA (Código Postal Argentino), an
8-character alphanumeric code (1 letter + 4 digits + 3 letters, e.g.
C1425DJP) in effect since 1998-2000. The legacy 4-digit numeric code
(pre-1999) was never officially retired for general use but is not the
current standard.
Source checked — GeoNames AR
https://download.geonames.org/export/zip/AR.zip # 20,260 rows
GeoNames' own export/zip/readme.txt flags Argentina specifically: "The
Argentina data file contains the first 5 positions of the postal code."
Read the exact text directly (not assumed) — unlike Chile/Ireland/Malta,
which are each flagged "for copyright reasons," Argentina's note states a
plain data-limitation, not an explicit rights restriction. The general CC
BY 4.0 licence statement at the top of the same readme applies to every
country subset, AR included.
Verified directly against the raw file: 20,260 rows, legacy-format 4-digit
numeric codes (e.g. 3636, 4123), not the modern 8-char CPA — 1,976
distinct codes. admin_name1 (province, e.g. "Salta") is populated on
100% of rows; admin_name2 (department/partido) is empty on all 20,260
rows — same one-tier-only shape as the postal export originally found for
South Africa, except here the coordinate/gazetteer-join fix used for ZA was
not attempted in this pass (out of scope for a research-only pass; flagged
as a viable follow-up given the ZA precedent in this catalogue).
Official source — checked, does not exist as a bulk export
Correo Argentino does not publish a bulk CPA file. Its site
(correoargentino.com.ar/secciones/cpa) offers only a single-address
lookup form, no download. Confirmed via direct search — no official portal,
API, or open-data catalogue entry from Correo Argentino or AFIP was found.
Third-party alternatives — checked, none better than GeoNames
| Candidate | Verdict | Why |
|---|---|---|
dat.ar (datar.info/dataset/codigo-postal-argentino) | ❌ unresolved | Community open-data portal entry, explicitly "License not specified." Data vintage May 2010 (a 2016 refresh also referenced) — stale and licence-unresolved, same bucket as Mauritius/Vietnam/Tanzania. |
| cataromap.com.ar | ❌ not sellable | Commercial product (2M+ georeferenced records) — no indication of an open licence; a paid competitor dataset, not a source to build from. |
| jcodagnone/localidades-ar (GitHub) | not checked in depth | Surfaced in search as a scraper against Correo Argentino's own lookup site, not a static open dataset — same shape of concern as scraping a lookup-only official site (no bulk grant from Correo Argentino to begin with). Not pursued further given GeoNames already covers the same ground under a clean licence. |
Decision
{
"channel": "postal-codes-r2",
"source_url": "https://download.geonames.org/export/zip/AR.zip",
"licence_id": "CC-BY-4.0",
"collected_at": "2026-08-29",
"decision": "compatible",
"decided_by": "claude-session-2026-08-29",
"decided_at": "2026-08-29",
"note": "GeoNames' AR export truncates to the legacy 4-digit postal code and carries admin_name1 (province) only, no admin_name2 -- both must be disclosed, not silently shipped as if it were the modern 8-char CPA with full department coverage."
}
Proposed tier
B ($49). Single source normalised in place, real derivation work (ISO 3166-2:AR crosswalk would be needed for admin_code1), but the source itself is thin (province tier only) and no second authoritative source was found to consolidate onto it. Not A.
Verdict
Buildable as GeoNames-only, disclosed as legacy-format/province-only. Do not market this as the modern CPA or as carrying department-level admin data — it is neither. Not yet built; this is the research/decision record only.
Build — 2026-08-30 (local only, not published)
Built via datasets/ar/scripts/build_postal_codes_product.py. Found a
real primary-key defect not caught in the research pass (which only
checked distinct postal-code counts, not the full key): 14
(postal_code, place_name) pairs repeat across two or three DIFFERENT
provinces — e.g. postal code 8138 "LA ADELA" is a real, distinct place in
Buenos Aires, La Pampa AND Rio Negro. Same shape as Bulgaria's 20-row
collision found in this same research batch. Fixed by keying the dataset's
real primary key as (postal_code, place_name, admin_code1), disclosed in
README/ATTRIBUTION/datapackage rather than silently deduplicated (which
would have dropped real places).
admin_code1: confirmed GeoNames' own internal single-letter code for
Argentina already equals the real ISO 3166-2:AR letter (verified against
Wikipedia — e.g. GeoNames "B" = Buenos Aires = ISO AR-B), so only the
"AR-" prefix was added, no renaming crosswalk needed. Confirmed AR-C
(Ciudad Autonoma de Buenos Aires) has zero rows — 23/24 provinces covered,
disclosed as a real gap tied to the legacy numbering, not a build defect.
Frictionless validation: valid: True.
Status: built and validated locally only. Nothing published to R2,
nothing committed to git. datasets/ar/README.md and datapackage.yml
updated in place (tier B, premium_source_key: ar/ar.zip, real
sources/licenses, replacing the "Multiple sources" placeholder).