Cross-source linking
Linking identifiers
The shared keys that let data be joined across French public sources — a parcel number, an INSEE commune code, an IRIS zone, a BAN address id, an RNB building id, a SIREN/SIRET. For each, this catalog shows how many sources expose it, under which raw field names, and whether it can be used as a filter in API requests (useful for sequential, drill-down calls). It's the map we'll link data with.
Based on 8,218 French sources with a classified field, out of 12,424 currently profiled. Updated 2026-08-16 13:45 UTC.
Territorial — administrative geography
INSEE COG codes that pin data to a commune, département, région or EPCI.
EPCI / intercommunalité (SIREN)
163sources · 9 field names
INSEE / DGCL (BANATIC)
Code commune INSEE (COG)
1067sources · 33 field names
INSEE (Code Officiel Géographique)
Code département
575sources · 15 field names
INSEE (Code Officiel Géographique)
Code région
273sources · 10 field names
INSEE (Code Officiel Géographique)
NUTS code
1source · 1 field name
Eurostat (NUTS)
LAU code
16sources · 5 field names
Eurostat (LAU)
GSS code (UK ONS)
13sources · 5 field names
Office for National Statistics (GSS)
Regionalschlüssel (DE ARS)
4sources · 1 field name
Statistisches Bundesamt (Destatis)
Gemeindeschlüssel (DE AGS)
26sources · 3 field names
Statistisches Bundesamt (Destatis)
Country code (ISO 3166-1)
59sources · 5 field names
ISO 3166 / Eurostat
Code postal
515sources · 9 field names
La Poste
Statistical zoning
Fine-grained census geography (IRIS).
Cadastre
Land parcels and their components.
Buildings
Building-level pivot keys (RNB, BD TOPO).
Addresses
Postal/address references (BAN, FANTOIR).
Organisations
Legal units and establishments (SIREN/SIRET).
Coordinates & geometry
Spatial linking via points or geometry.
How to read this
- Joinable counts sources whose real sample values match the key's expected format (e.g. genuine 5-char INSEE codes) — those are directly joinable today; the higher source count is the candidate pool.
- Coverage is limited to French sources we've already profiled — others appear as they get profiled.
- “Filterable” is authoritative for Opendatasoft/DataFair facets and inferred structurally for feature services (WFS/OGC API Features/ArcGIS). For plain OpenAPI REST APIs it's unknown, because query parameters aren't captured yet.
- Field→identifier matching is alias/pattern-based — it may miss exotic spellings; composite keys (parcel, IRIS, lat+lon) are flagged but not auto-assembled.