Reference municipal boundaries of Rennes Métropole (polylines)Limites communales référentielles de Rennes Métropole (polylignes)
Limites communales référentielles de Rennes Métropole (polylignes)Reference municipal boundaries of Rennes Métropole (polylines)
This API provides one of the two reference layers of municipal boundaries for Rennes Métropole, France. The polyline layer is derived from the corresponding polygon layer and has been topologically processed so that only a single line represents the shared boundary between two neighboring municipalities. It is published and maintained by Rennes Métropole and is intended for use in geographic information systems requiring precise, non-duplicated municipal boundary lines within the metropolitan area.Il s'agit d'une des deux couches de référence des limites communales de Rennes Métropole. Cette couche de polylignes est dérivée de la couche polygonale. Elle a été traitée de façon topologique afin qu'il n'existe qu'une seule ligne comme limite commune entre deux communes voisines. Cette couche...
Trust score
How is this computed?Weighted across five axes. Tap a ring for what it measures.
Data schema (11 fields)
Click a field to see example values.
| Fill | Field | Type | Description |
|---|---|---|---|
| — | geo_point_2dGeo Point | geo_point_2d | Geographic centroid coordinates of the boundary line.Geographic centroid coordinates of the boundary line. |
| — | geo_shapeShape | geo_shape | Geometry of the municipal boundary line as GeoJSON.Geometry of the municipal boundary line as GeoJSON. |
| — | gml_idGml id | text | Unique GML identifier of the boundary line feature.Unique GML identifier of the boundary line feature. |
| — | objectid | int | Internal record identifier.Internal record identifier. |
| — | commune_aggloCommune agglo | int | Flag indicating whether the boundary belongs to Rennes Métropole.Flag indicating whether the boundary belongs to Rennes Métropole. |
| — | code_insee_dCode insee d | text | INSEE code of the municipality on the right side of the line.INSEE code of the municipality on the right side of the line. |
| — | nom_min_dNom min d | text | Lowercase name of the municipality on the right side.Lowercase name of the municipality on the right side. |
| — | nom_maj_dNom maj d | text | Uppercase name of the municipality on the right side.Uppercase name of the municipality on the right side. |
| — | code_insee_gCode insee g | text | INSEE code of the municipality on the left side of the line.INSEE code of the municipality on the left side of the line. |
| — | nom_min_gNom min g | text | Lowercase name of the municipality on the left side.Lowercase name of the municipality on the left side. |
| 100% | nom_maj_gNom maj g | text | Uppercase name of the municipality on the left side.Uppercase name of the municipality on the left side. |
Schema captured from opendatasoft 2 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)
These rows are ODbL-1.0: share-alike. Reusing them obliges you to license any derived database on the same terms.
Record 1gml_id: commune_contour.360 · objectid: 360
{
"gml_id": "commune_contour.360",
"objectid": 360,
"geo_shape": "[large value omitted]",
"nom_maj_d": "ACIGNE",
"nom_maj_g": "THORIGNE-FOUILLARD",
"nom_min_d": "Acigné",
"nom_min_g": "Thorigné-Fouillard",
"code_insee_d": "35001",
"code_insee_g": "35334",
"geo_point_2d": {
"lat": 48.14471443768399,
"lon": -1.5616952697919002
},
"commune_agglo": 1
}Record 2gml_id: commune_contour.370 · objectid: 370
{
"gml_id": "commune_contour.370",
"objectid": 370,
"geo_shape": "[large value omitted]",
"nom_maj_d": "BETTON",
"nom_maj_g": "THORIGNE-FOUILLARD",
"nom_min_d": "Betton",
"nom_min_g": "Thorigné-Fouillard",
"code_insee_d": "35024",
"code_insee_g": "35334",
"geo_point_2d": {
"lat": 48.1684112372446,
"lon": -1.618875320845957
},
"commune_agglo": 1
}Record 3gml_id: commune_contour.404 · objectid: 404
{
"gml_id": "commune_contour.404",
"objectid": 404,
"geo_shape": "[large value omitted]",
"nom_maj_d": "GEVEZE",
"nom_maj_g": "LANGOUET",
"nom_min_d": "Gévezé",
"nom_min_g": "Langouët",
"code_insee_d": "35120",
"code_insee_g": "35146",
"geo_point_2d": {
"lat": 48.24550059745745,
"lon": -1.8139931712767672
},
"commune_agglo": 1
}Record 4gml_id: commune_contour.276 · objectid: 276
{
"gml_id": "commune_contour.276",
"objectid": 276,
"geo_shape": "[large value omitted]",
"nom_maj_d": "LAILLE",
"nom_maj_g": "ORGERES",
"nom_min_d": "Laillé",
"nom_min_g": "Orgères",
"code_insee_d": "35139",
"code_insee_g": "35208",
"geo_point_2d": {
"lat": 47.97133555462204,
"lon": -1.6885326519969475
},
"commune_agglo": 1
}Record 5gml_id: commune_contour.296 · objectid: 296
{
"gml_id": "commune_contour.296",
"objectid": 296,
"geo_shape": "[large value omitted]",
"nom_maj_d": "NOYAL-CHATILLON-SUR-SEICHE",
"nom_maj_g": "PONT-PEAN",
"nom_min_d": "Noyal-Châtillon-sur-Seiche",
"nom_min_g": "Pont-Péan",
"code_insee_d": "35206",
"code_insee_g": "35363",
"geo_point_2d": {
"lat": 48.02866331942208,
"lon": -1.6856166112300617
},
"commune_agglo": 1
}Live sample captured at profiling time — values may have changed upstream.
Verification Status
Using the API
Configuration
- Base URL
- https://data.rennesmetropole.fr/api/explore/v2.1/catalog/datasets/limites-communales-referentielles-de-rennes-metropole-polylignes
License
- ✓ Redistributable
- ✓ Attribution required
Query examples
curl -s 'https://data.rennesmetropole.fr/api/explore/v2.1/catalog/datasets/limites-communales-referentielles-de-rennes-metropole-polylignes/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.