New Communes in Brittany: Tracking Changes Since 01/01/2016Communes nouvelles en Bretagne : suivi des évolutions depuis le 01/01/2016
Communes nouvelles en Bretagne : suivi des évolutions depuis le 01/01/2016New Communes in Brittany: Tracking Changes Since 01/01/2016
This API tracks the evolution of newly merged communes ('communes nouvelles') in Brittany since 1 January 2016. For each commune that has undergone a merger, it provides an attribute indicating the name of the resulting new commune along with its new INSEE code. The dataset is published via the Brittany regional open-data portal and is useful for monitoring administrative territorial changes and updating commune-level references in France's Brittany region.Suivi de l'évolution des communes nouvelles. Pour chaque commune ayant fusionné, un attribut décrira le nom de la nouvelle commune ainsi que le nouveau code INSEE.
Trust score
How is this computed?Weighted across five axes. Tap a ring for what it measures.
Data schema (9 fields)
Click a field to see example values.
| Field | Type | Description |
|---|---|---|
| geo_point_2dGeo Point | geo_point_2d | — |
| geo_shapeShape | geo_shape | — |
| gml_idGml id | text | — |
| code_insee_2015Code insee 2015 | text | — |
| nom_2015Nom 2015 | text | — |
| code_inseeINSEE commune code | text | — |
| nom | text | — |
| date_majDate maj | text | — |
| date_fusionDate fusion | datetime | — |
Schema captured from opendatasoft 7 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: Berrien · gml_id: commune_nouvelle_suivi_geom.29007
{
"nom": "Berrien",
"gml_id": "commune_nouvelle_suivi_geom.29007",
"date_maj": "20250106",
"nom_2015": "Berrien",
"geo_shape": "[large value omitted]",
"code_insee": "29007",
"date_fusion": null,
"geo_point_2d": {
"lat": 48.40299160048062,
"lon": -3.7656324800139958
},
"code_insee_2015": "29007"
}Record 2nom: Plouzané · gml_id: commune_nouvelle_suivi_geom.29212
{
"nom": "Plouzané",
"gml_id": "commune_nouvelle_suivi_geom.29212",
"date_maj": "20250106",
"nom_2015": "Plouzané",
"geo_shape": "[large value omitted]",
"code_insee": "29212",
"date_fusion": null,
"geo_point_2d": {
"lat": 48.37741942926512,
"lon": -4.598919192806079
},
"code_insee_2015": "29212"
}Record 3nom: Coat-Méal · gml_id: commune_nouvelle_suivi_geom.29035
{
"nom": "Coat-Méal",
"gml_id": "commune_nouvelle_suivi_geom.29035",
"date_maj": "20250106",
"nom_2015": "Coat-Méal",
"geo_shape": "[large value omitted]",
"code_insee": "29035",
"date_fusion": null,
"geo_point_2d": {
"lat": 48.50603449339907,
"lon": -4.539704926526276
},
"code_insee_2015": "29035"
}Record 4nom: Dol-de-Bretagne · gml_id: commune_nouvelle_suivi_geom.35095
{
"nom": "Dol-de-Bretagne",
"gml_id": "commune_nouvelle_suivi_geom.35095",
"date_maj": "20250106",
"nom_2015": "Dol-de-Bretagne",
"geo_shape": "[large value omitted]",
"code_insee": "35095",
"date_fusion": null,
"geo_point_2d": {
"lat": 48.53660463752554,
"lon": -1.7420769496474322
},
"code_insee_2015": "35095"
}Record 5nom: Saint-Onen-la-Chapelle · gml_id: commune_nouvelle_suivi_geom.35302
{
"nom": "Saint-Onen-la-Chapelle",
"gml_id": "commune_nouvelle_suivi_geom.35302",
"date_maj": "20250106",
"nom_2015": "Saint-Onen-la-Chapelle",
"geo_shape": "[large value omitted]",
"code_insee": "35302",
"date_fusion": null,
"geo_point_2d": {
"lat": 48.169524437090764,
"lon": -2.1557357391975525
},
"code_insee_2015": "35302"
}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/communes-nouvelles-en-bretagne-suivi-des-evolutions-depuis-le-01012016
License
- ✓ Redistributable
- ✓ Attribution required
Query examples
curl -s 'https://data.bretagne.bzh/api/explore/v2.1/catalog/datasets/communes-nouvelles-en-bretagne-suivi-des-evolutions-depuis-le-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.