Boundaries of new communes as of 01/01/2016Périmètres des communes nouvelles à compter du 01/01/2016
Périmètres des communes nouvelles à compter du 01/01/2016Boundaries of new communes as of 01/01/2016
This dataset provides a geographic layer showing only the boundaries of the newly created French communes (municipalities formed through mergers of former communes) that took effect on 1 January 2016. It is published via the Brittany regional open-data portal and is intended for mapping and administrative-boundary analysis, allowing users to identify the updated territorial divisions resulting from the municipal merger process in France.Couche contenant uniquement les périmètres des communes nouvelles à partir du 01/01/2016.
Trust score
How is this computed?Weighted across five axes. Tap a ring for what it measures.
Data schema (7 fields)
Click a field to see example values.
| Field | Type | Description |
|---|---|---|
| geo_point_2dGeo Point | geo_point_2d | Geographic centroid coordinates of the new commune.Geographic centroid coordinates of the new commune. |
| geo_shapeShape | geo_shape | Geometric boundary shape of the new commune.Geometric boundary shape of the new commune. |
| gml_idGml id | text | Unique GML identifier of the geometry record.Unique GML identifier of the geometry record. |
| code_inseeINSEE commune code | text | INSEE code identifying the new commune.INSEE code identifying the new commune. |
| nom | text | Name of the new commune.Name of the new commune. |
| date_fusionDate fusion | datetime | Date on which the commune merger took effect.Date on which the commune merger took effect. |
| date_majDate maj | text | Date when the record was last updated.Date when the record was last updated. |
Schema captured from opendatasoft 3 days ago.
Query the data
Pick columns and a sort, then fetch a live preview straight from the source. Choose an API-filterable column (marked ▾) under “Where” to pick from its list of values.
Sample data (5 records)
Record 1nom: Luitré-Dompierre · gml_id: commune_nouvelle_geom.35163
{
"nom": "Luitré-Dompierre",
"gml_id": "commune_nouvelle_geom.35163",
"date_maj": "20250106",
"geo_shape": "[large value omitted]",
"code_insee": "35163",
"date_fusion": null,
"geo_point_2d": {
"lat": 48.28680970229555,
"lon": -1.1340326414536066
}
}Record 2nom: La Roche-Jaudy · gml_id: commune_nouvelle_geom.22264
{
"nom": "La Roche-Jaudy",
"gml_id": "commune_nouvelle_geom.22264",
"date_maj": "20250106",
"geo_shape": "[large value omitted]",
"code_insee": "22264",
"date_fusion": null,
"geo_point_2d": {
"lat": 48.73157855919999,
"lon": -3.2332167931714366
}
}Record 3nom: Saint-Gérand-Croixanvec · gml_id: commune_nouvelle_geom.56213
{
"nom": "Saint-Gérand-Croixanvec",
"gml_id": "commune_nouvelle_geom.56213",
"date_maj": "20250106",
"geo_shape": "[large value omitted]",
"code_insee": "56213",
"date_fusion": null,
"geo_point_2d": {
"lat": 48.10894466746018,
"lon": -2.8860783525284184
}
}Record 4nom: Forges de Lanouée · gml_id: commune_nouvelle_geom.56102
{
"nom": "Forges de Lanouée",
"gml_id": "commune_nouvelle_geom.56102",
"date_maj": "20250106",
"geo_shape": "[large value omitted]",
"code_insee": "56102",
"date_fusion": null,
"geo_point_2d": {
"lat": 48.0106784084489,
"lon": -2.5806937577539664
}
}Record 5nom: Plumieux · gml_id: commune_nouvelle_geom.22241
{
"nom": "Plumieux",
"gml_id": "commune_nouvelle_geom.22241",
"date_maj": "20250106",
"geo_shape": "[large value omitted]",
"code_insee": "22241",
"date_fusion": null,
"geo_point_2d": {
"lat": 48.10054198092998,
"lon": -2.5877276770235658
}
}Live sample captured at profiling time — values may have changed upstream.
Verification Status
Using the API
Configuration
- Base URL
- https://data.bretagne.bzh/api/explore/v2.1/catalog/datasets/perimetres-des-communes-nouvelles-a-compter-du-01012016
License
- ✓ Redistributable
- ✓ Attribution required
Query examples
curl -s 'https://data.bretagne.bzh/api/explore/v2.1/catalog/datasets/perimetres-des-communes-nouvelles-a-compter-du-01012016/records?limit=20' -H 'Accept: application/json'First 20 records of the dataset as JSON.
Uses the Opendatasoft Explore v2.1 syntax — supports select, where, group_by and order_by.
Rate limits
Dataset
Volume & freshness
License
No license declared upstream.
Source: opendatasoft
Machine-readable & source
Embed this badge in a README or wiki — it always shows the latest verification state and quality tier.