Municipal boundaries - archives - Angers Loire MétropoleLimites communales - archives - Angers Loire Métropole
Limites communales - archives - Angers Loire MétropoleMunicipal boundaries - archives - Angers Loire Métropole
This API provides archived municipal boundary data for the municipalities of Angers Loire Métropole, France, as they existed prior to the creation of the new merged municipalities of Longuenée-en-Anjou and Verrières-en-Anjou on 1 January 2016. It is published and maintained by Angers Loire Métropole and offers free access without authentication. The dataset is useful for historical or comparative geographic analysis of municipal territorial divisions within the metropolitan area before the administrative reorganization took effect.Limites communales des communes d'Angers Loire Métropole avant la création des communes nouvelles de Longuenée-en-Anjou et de Verrières-en-Anjou au 1er janvier 2016.
Trust score
How is this computed?Weighted across five axes. Tap a ring for what it measures.
Data schema (10 fields)
Click a field to see example values.
| Field | Type | Description |
|---|---|---|
| geo_point_2dGeo Point | geo_point_2d | — |
| geo_shapeShape | geo_shape | — |
| name | text | — |
| description | text | — |
| gid | text | — |
| ccocom | text | — |
| nom_comNom com | text | — |
| canton | text | — |
| nom_com_2Nom com 2 | text | — |
| cpostal | text | — |
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 1gid: 47 · name: kml_5
{
"gid": "47",
"name": "kml_5",
"canton": "ST GEORGES SUR LOIRE",
"ccocom": "49329",
"cpostal": "49170",
"nom_com": "SAVENNIERES",
"geo_shape": "[large value omitted]",
"nom_com_2": "Savennieres",
"description": "<center><table><tr><th colspan='2' align='center'><em>Attributes</em></th></tr><tr bgcolor=\"#E3E3F3\">\n<th>GID</th>\n<td>47</td>\n</tr><tr bgcolor=\"\">\n<th>CCOCOM</th>\n<td>329</td>\n</tr><tr bgcolor=\"#E3E3F3\">\n<th>NOM_COM</th>\n<td>SAVENNIERES</td>\n</tr><tr bgcolor=\"\">\n<th>CANTON</th>\n<td>ST GEORGES SUR LOIRE</td>\n</tr><tr bgcolor=\"#E3E3F3\">\n<th>NOM_COM_2</th>\n<td>Savennieres</td>\n</tr><tr bgcolor=\"\">\n<th>CPOSTAL</th>\n<td>49170</td>\n</tr></table></center>",
"geo_point_2d": {
"lat": 47.405632874748136,
"lon": -0.6674199426993742
}
}Record 2gid: 49 · name: kml_6
{
"gid": "49",
"name": "kml_6",
"canton": "LOUROUX BECONNAIS",
"ccocom": "49271",
"cpostal": "49370",
"nom_com": "SAINT-CLEMENT DE LA PLACE",
"geo_shape": "[large value omitted]",
"nom_com_2": "Saint-Clement-De-La-Place",
"description": "<center><table><tr><th colspan='2' align='center'><em>Attributes</em></th></tr><tr bgcolor=\"#E3E3F3\">\n<th>GID</th>\n<td>49</td>\n</tr><tr bgcolor=\"\">\n<th>CCOCOM</th>\n<td>271</td>\n</tr><tr bgcolor=\"#E3E3F3\">\n<th>NOM_COM</th>\n<td>SAINT-CLEMENT DE LA PLACE</td>\n</tr><tr bgcolor=\"\">\n<th>CANTON</th>\n<td>LOUROUX BECONNAIS</td>\n</tr><tr bgcolor=\"#E3E3F3\">\n<th>NOM_COM_2</th>\n<td>Saint-Clement-De-La-Place</td>\n</tr><tr bgcolor=\"\">\n<th>CPOSTAL</th>\n<td>49370</td>\n</tr></table></center>",
"geo_point_2d": {
"lat": 47.526599599851195,
"lon": -0.7342562771582263
}
}Record 3gid: 135 · name: kml_24
{
"gid": "135",
"name": "kml_24",
"canton": null,
"ccocom": "49339",
"cpostal": "49460",
"nom_com": "SOULAIRE-ET-BOURG",
"geo_shape": "[large value omitted]",
"nom_com_2": "Soulaire-Et-Bourg",
"description": "<center><table><tr><th colspan='2' align='center'><em>Attributes</em></th></tr><tr bgcolor=\"#E3E3F3\">\n<th>GID</th>\n<td>135</td>\n</tr><tr bgcolor=\"\">\n<th>CCOCOM</th>\n<td>339</td>\n</tr><tr bgcolor=\"#E3E3F3\">\n<th>NOM_COM</th>\n<td>SOULAIRE-ET-BOURG</td>\n</tr><tr bgcolor=\"\">\n<th>NOM_COM_2</th>\n<td>Soulaire-Et-Bourg</td>\n</tr><tr bgcolor=\"#E3E3F3\">\n<th>CPOSTAL</th>\n<td>49460</td>\n</tr></table></center>",
"geo_point_2d": {
"lat": 47.57989208375813,
"lon": -0.5425436672074657
}
}Record 4gid: 247 · name: kml_26
{
"gid": "247",
"name": "kml_26",
"canton": "ANGERS NORD EST",
"ccocom": "49238",
"cpostal": "49112",
"nom_com": "PELLOUAILLES\\n-LES-VIGNES",
"geo_shape": "[large value omitted]",
"nom_com_2": "Pellouailles-Les-Vignes",
"description": "<center><table><tr><th colspan='2' align='center'><em>Attributes</em></th></tr><tr bgcolor=\"#E3E3F3\">\n<th>GID</th>\n<td>247</td>\n</tr><tr bgcolor=\"\">\n<th>CCOCOM</th>\n<td>238</td>\n</tr><tr bgcolor=\"#E3E3F3\">\n<th>NOM_COM</th>\n<td>PELLOUAILLES\\n-LES-VIGNES</td>\n</tr><tr bgcolor=\"\">\n<th>CANTON</th>\n<td>ANGERS NORD EST</td>\n</tr><tr bgcolor=\"#E3E3F3\">\n<th>NOM_COM_2</th>\n<td>Pellouailles-Les-Vignes</td>\n</tr><tr bgcolor=\"\">\n<th>CPOSTAL</th>\n<td>49112</td>\n</tr></table></center>",
"geo_point_2d": {
"lat": 47.53282564765505,
"lon": -0.4494693003324295
}
}Record 5gid: 324 · name: kml_32
{
"gid": "324",
"name": "kml_32",
"canton": "PONTS DE CE",
"ccocom": "49246",
"cpostal": "49130",
"nom_com": "LES PONTS-DE-CE",
"geo_shape": "[large value omitted]",
"nom_com_2": "Les Ponts-De-Ce",
"description": "<center><table><tr><th colspan='2' align='center'><em>Attributes</em></th></tr><tr bgcolor=\"#E3E3F3\">\n<th>GID</th>\n<td>324</td>\n</tr><tr bgcolor=\"\">\n<th>CCOCOM</th>\n<td>246</td>\n</tr><tr bgcolor=\"#E3E3F3\">\n<th>NOM_COM</th>\n<td>LES PONTS-DE-CE</td>\n</tr><tr bgcolor=\"\">\n<th>CANTON</th>\n<td>PONTS DE CE</td>\n</tr><tr bgcolor=\"#E3E3F3\">\n<th>NOM_COM_2</th>\n<td>Les Ponts-De-Ce</td>\n</tr><tr bgcolor=\"\">\n<th>CPOSTAL</th>\n<td>49130</td>\n</tr></table></center>",
"geo_point_2d": {
"lat": 47.427276397518774,
"lon": -0.5125971677264338
}
}Live sample captured at profiling time — values may have changed upstream.
Verification Status
Using the API
Configuration
- Base URL
- https://data.angers.fr/api/explore/v2.1/catalog/datasets/alm-boundary
License
- ✓ Redistributable
- ✓ Attribution required
Query examples
curl -s 'https://data.angers.fr/api/explore/v2.1/catalog/datasets/alm-boundary/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.