Postal Codes Dataset for Ecuador, EC

143
Updated:
Files:1
Size:106 kB
Formats:csv
License:CC-BY-4.0

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

About

Last updated
30 August 2026
Total rows
...
Format
CSV
File size
106 kB

About this dataset

Ecuador (EC) — licensing trace

Checked 2026-08-29. Starting from zero — no prior work anywhere for this country code.

Postal system

Ecuador uses a 6-digit numeric postal code system ("CORREOSCODIGO"), administered through the Ministerio de Telecomunicaciones y de la Sociedad de la Informacion (MINTEL) via its postal regulator ARCOTEL/ARCPostal.

Source checked — GeoNames EC

https://download.geonames.org/export/zip/EC.zip   # 1,225 rows

No per-country caveat for Ecuador in GeoNames' export/zip/readme.txt — general CC BY 4.0 applies without restriction.

Verified directly against the raw file: 1,225 rows, all 1,225 distinct 6-digit codes, matching the real CORREOSCODIGO format (e.g. 200101). admin_name1 (Provincia, e.g. "Galapagos") and admin_name2 (Canton, e.g. "Canton San Cristobal") are both populated on 1,221/1,225 rows (99.7%) — no gazetteer join needed, only 4 rows have a gap. No admin_name3 (parroquia) in the postal export itself.

Official source — a real candidate exists, but could not be verified this pass

Ecuador is the strongest official-source lead of this batch of three: a government (.gob.ec) system exists specifically for this — codigopostal.gob.ec (MINTEL's "Codigo Postal Ecuador" portal) and its postal regulator ARCPostal reportedly publish a downloadable Excel file with the full national postal-code list, referenced from regulacion.mintel.gob.ec/descargue-productos-del-sistema-codigo-postal-ecuatoriano/.

Both government URLs returned connect ECONNREFUSED on direct fetch today (2026-08-29) — same failure class already logged elsewhere in this catalogue for other government sites (Oman Post 404, PostNord Denmark 403). Could not verify the actual download link, file format, or licence terms this pass. This is a real, promising lead for a future pass — not ruled out, just unreachable today — rather than something to build against blind.

Decision

{
  "channel": "postal-codes-r2",
  "source_url": "https://download.geonames.org/export/zip/EC.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": "MINTEL/ARCPostal's own codigopostal.gob.ec and regulacion.mintel.gob.ec were identified as a likely stronger official source (a named Excel export exists per search results) but were unreachable (ECONNREFUSED) during this research pass -- re-check before assuming GeoNames is the ceiling for this country."
}

Proposed tier

B ($49). Single source normalised in place, real derivation work (ISO 3166-2:EC crosswalk for admin_code1), no second source consolidated in this pass. Would move toward A if the MINTEL official export is later confirmed reachable and consolidated on top (definitive code list + admin_name3 parroquia tier neither GeoNames row currently carries).

Verdict

Buildable now on GeoNames alone (clean, near-complete 2-tier admin coverage), with a real official upgrade path still open. Re-attempt the MINTEL/ARCPostal fetch in a future pass — a working .gob.ec source would likely add both a name-verified code list and a third admin tier. Not yet built; this is the research/decision record only.

Build — 2026-08-30 (local only, not published)

Retried MINTEL/ARCPostal (codigopostal.gob.ec, regulacion.mintel.gob.ec/descargue-productos-del-sistema-codigo-postal-ecuatoriano/) once before building — both timed out again (connection timeout, not a 404 or explicit block). Proceeded on GeoNames as the research already concluded; not retried further per this project's tunnel-vision rule.

Built via datasets/ec/scripts/build_postal_codes_product.py, straight from the raw GeoNames source via csv (no pandas). Derived ISO 3166-2:EC codes for all 24 provinces via a verified Wikipedia crosswalk — every one of GeoNames' 24 admin1 codes matched a real ISO province by name, zero ambiguity.

value
Final rows1,225
Distinct postal codes1,225 (all unique — no primary-key collisions)
Provinces covered24/24
Cantons220 distinct
Rows with no province (disclosed, not guessed)4 (900001–900004, disputed "Manga del Cura" territory)

admin_name3/admin_code3 ship empty — source carries no parroquia tier. alternative_city_name ships empty — single-source build, no gazetteer enrichment attempted.

Frictionless validation: valid: True.

Status: built and validated locally only. Nothing published to R2, nothing committed to git. datasets/ec/README.md and datapackage.yml updated in place (tier B, premium_source_key: ec/ec.zip, real sources/licenses, replacing the "Multiple sources" placeholder).