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 →

Download · CSV · 264 kB Explore with AI Report an Issue

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-sn/

├ .licensing-notes.md

https://datahub.io/logistics/postal-codes-sn/_r/-/.licensing-notes.md

├ README.md

https://datahub.io/logistics/postal-codes-sn/_r/-/README.md

└ datapackage.yml

https://datahub.io/logistics/postal-codes-sn/_r/-/datapackage.yml

Key Files

Start with these files — they give you everything you need to understand and access the dataset.

datapackage.yml— metadata & schema

https://datahub.io/logistics/postal-codes-sn/_r/-/datapackage.yml

README.md— documentation

https://datahub.io/logistics/postal-codes-sn/_r/-/README.md

Typical Usage

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

Explore with AI

Postal Codes Data Resource for Senegal, SN

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 CSV

About

Last updated: 25 August 2026
Total rows: ...
Format: CSV
File size: 264 kB
Sources: La Poste Senegal — postal codes (posteasy widget asset, publicly served, no restriction found; no explicit redistribution licence confirmed — see ATTRIBUTION.txt); Wikipedia — ISO 3166-2:SN region codes (administrative layer, factual extraction only)

About this dataset

Senegal (SN) — internal licensing notes

Status: NOT live, correctly gated. Lower risk than most items in this review, but no path to resolution exists without contacting the source — and the human has instructed not to. Reviewed 2026-08-24 under datahub-next#941 §2.

Product identity

R2 sn/sn.csv is a 159-byte, 0-row placeholder. No is_premium. Nothing on sale.
The real content (4,110 rows, QA-passed, Frictionless-valid) is in fedex-agents-prototype/countries/SEN/. No Senegal_Delivery/ folder exists — never sold to a customer.

The upstream origin, confirmed (the issue flagged this as unexamined)

datahub-next#941 §2 said the origin "has never been examined" and guessed "likely La Poste Sénégal." Confirmed, not a guess: the tier-1 source in research.json is https://www.laposte.sn/wp-content/plugins/posteasy/assets/js/postal-data.js — that domain is La Poste Sénégal's own official website, not a third-party vendor. This is a materially different starting posture than Guinea's mapanet.eu (a for-profit EU aggregator with explicit no-resale terms) — here the data comes directly from the postal authority itself.

Checked directly, all public, nothing circumvented:

robots.txt: Allow: / — no crawl restriction (contrast: mapanet 403s its own robots.txt).
The JS asset: HTTP 200, no auth, no rate-limiting hit. Its own embedded French comment: "Fichier généré automatiquement depuis la base des divisions admin du Senegal" — auto-generated to power a form widget (address/postal-code autocomplete) on their own site.
No terms of service or mentions-légales page found anywhere on the site (checked the homepage and common French ToS paths — all 404).
No bot-evasion tooling used, no auth bypass, no rate-limit circumvention — a plain HTTP GET of a public static asset.

Why this is genuinely lower risk, and why it still can't ship

No explicit prohibition exists — but no explicit grant exists either. That is a real gap, not a green light. The closest doctrinal parallel elsewhere in this review is the EU sui generis database right (which bit hard on Canada's PCCF and Sweden's PostNord) — but Senegal is not an EU/EEA jurisdiction, so that specific doctrine does not transplant cleanly. What actually governs is Senegalese law, which this review has no basis to characterise.

GeoNames has no Senegal export — reconfirmed 2026-08-24 (download.geonames.org/export/zip/SN.zip → HTTP 404, same signature as Saudi Arabia and Guinea). No free rebuild alternative exists.

Recommendation

No action possible under the current constraint (no contact). Keep data_available: false. Of everything reviewed under §2, this is the single most tractable "just ask" case in the whole catalogue if the no-contact rule is ever relaxed — the data is literally La Poste Sénégal's own, served openly, with no restriction found and no third-party rights to untangle. Contrast with Jersey (datasets/je/.licensing-notes.md), which stacks three separate problems even before a contact question arises.

Not legal advice — a research summary of published terms and verified source availability, not a characterisation of Senegalese law.

Source: datahub-next#941 (opened by @anuveyatsu, 2026-08-08); review 2026-08-24.

GENERATED AND PUBLISHED — 2026-08-25

Human decision, overriding the "no action possible without contact" hold above: generate and publish now, resolve licensing after, rather than wait indefinitely on a contact that may never happen. sn.csv (4,110 rows) built from the FedEx-schema QA-passed dataset via datasets/sn/scripts/build_postal_codes_product.py. licence_status.decision is explicitly "unresolved" (not "compatible") — this is a deliberate, disclosed exception to the provenance gate's normal hard-block rule, not a gate failure. data_available: true should be flipped once this is on R2 (see datapackage.yml). Full disclosure ships in ATTRIBUTION.txt and the README.

Still true: no contact has been made with La Poste Senegal. This publish does not resolve the underlying licence question — it makes an informed decision to sell into that gap, disclosed, rather than wait on it.