c0mm0.com — the continuously verified register of European data

Register record·API·FR·MUNICIPALITYVERIFIED · checked 2d ago
L

Reference Communal Boundaries of Rennes Métropole (polygons)Limites communales référentielles de Rennes Métropole (polygones)

Limites communales référentielles de Rennes Métropole (polygones)Reference Communal Boundaries of Rennes Métropole (polygons)

APIJoinable5/7Query nowOpen workbenchSubscribe🇫🇷France

This dataset provides one of the two reference layers of communal boundaries for Rennes Métropole, France. The polygon layer is derived from the 2013 cadastral boundary layer, with corrections applied in sectors where the cadastral map showed geometric issues, such as overlapping parcels. Published by Rennes Métropole, it offers an authoritative geometric representation of municipal boundaries within the metropolitan area, useful for mapping, spatial analysis, and administrative applications requiring accurate delineation of communes.”Il s'agit d'une des deux couches de référence des limites communales de Rennes Métropole. Cette couche de polygones est dérivée de la couche cadastrale des limites communales (version 2013). Sur les secteurs où le plan cadastral présentait des problèmes géométriques (superposition de parcelles, t...

geospatial
57
fair

Weighted across five axes. Tap a ring for what it measures.

Data schema (11 fields)

Filterable via the API (9)
gml_idobjectidcode_inseenomcommune_agglox_centrbrgy_centrbrgcode_postalid_ban_commune

Click a field to see example values.

FillFieldTypeDescription
—geo_point_2dGeo Pointgeo_point_2dGeographic centroid coordinates (latitude, longitude) of the commune.Geographic centroid coordinates (latitude, longitude) of the commune.
—geo_shapeShapegeo_shapePolygon geometry outlining the commune's boundary.Polygon geometry outlining the commune's boundary.
—gml_idFilterable via the APIGml idtextUnique GML identifier for the commune boundary feature.Unique GML identifier for the commune boundary feature.
—objectidFilterable via the APIintInternal record identifier for the boundary feature.Internal record identifier for the boundary feature.
—code_inseeFilterable via the APIINSEE commune codedoubleINSEE code identifying the commune.INSEE code identifying the commune.
—nomFilterable via the APItextName of the commune.Name of the commune.
—commune_aggloFilterable via the APICommune agglointFlag indicating whether the commune belongs to Rennes Métropole.Flag indicating whether the commune belongs to Rennes Métropole.
—x_centrbrgFilterable via the APIX centrbrgdoubleX coordinate of the commune's town centre point.X coordinate of the commune's town centre point.
—y_centrbrgFilterable via the APIY centrbrgdoubleY coordinate of the commune's town centre point.Y coordinate of the commune's town centre point.
—code_postalFilterable via the APIPostal codetextPostal code of the commune.Postal code of the commune.
100%id_ban_communeFilterable via the APIId ban communetextUnique identifier of the commune in the BAN address database.Unique identifier of the commune in the BAN address database.

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 1nom: Bovel · gml_id: commune_emprise.106
{
  "nom": "Bovel",
  "gml_id": "commune_emprise.106",
  "objectid": 106,
  "geo_shape": "[large value omitted]",
  "code_insee": 35035,
  "x_centrbrg": 1328520,
  "y_centrbrg": 7206453,
  "code_postal": "35330",
  "geo_point_2d": {
    "lat": 47.95684548584906,
    "lon": -1.9597535677580373
  },
  "commune_agglo": 0,
  "id_ban_commune": "f2e46ae3-b3fe-474c-a94d-f17eef8c26be"
}
Record 2nom: l'Hermitage · gml_id: commune_emprise.90
{
  "nom": "l'Hermitage",
  "gml_id": "commune_emprise.90",
  "objectid": 90,
  "geo_shape": "[large value omitted]",
  "code_insee": 35131,
  "x_centrbrg": 1341750,
  "y_centrbrg": 7225171,
  "code_postal": "35590",
  "geo_point_2d": {
    "lat": 48.12203802772909,
    "lon": -1.8163064816481886
  },
  "commune_agglo": 1,
  "id_ban_commune": "262199aa-5cbc-414c-8604-2714017117e8"
}
Record 3nom: Saint-Sulpice-la-Forêt · gml_id: commune_emprise.35
{
  "nom": "Saint-Sulpice-la-Forêt",
  "gml_id": "commune_emprise.35",
  "objectid": 35,
  "geo_shape": "[large value omitted]",
  "code_insee": 35315,
  "x_centrbrg": 1359936,
  "y_centrbrg": 7234339,
  "code_postal": "35250",
  "geo_point_2d": {
    "lat": 48.21238377442801,
    "lon": -1.5759336638175796
  },
  "commune_agglo": 1,
  "id_ban_commune": "2c997c6b-04df-4dc0-bb9c-e34947996b4a"
}
Record 4nom: Monterfil · gml_id: commune_emprise.134
{
  "nom": "Monterfil",
  "gml_id": "commune_emprise.134",
  "objectid": 134,
  "geo_shape": "[large value omitted]",
  "code_insee": 35187,
  "x_centrbrg": 1329223,
  "y_centrbrg": 7219290,
  "code_postal": "35160",
  "geo_point_2d": {
    "lat": 48.06003584941625,
    "lon": -1.9903593525192416
  },
  "commune_agglo": 0,
  "id_ban_commune": "13cc825c-4488-4470-93b6-ec09afa709ce"
}
Record 5nom: Baulon · gml_id: commune_emprise.13
{
  "nom": "Baulon",
  "gml_id": "commune_emprise.13",
  "objectid": 13,
  "geo_shape": "[large value omitted]",
  "code_insee": 35016,
  "x_centrbrg": 1332156,
  "y_centrbrg": 7210130,
  "code_postal": "35580",
  "geo_point_2d": {
    "lat": 47.99499297325172,
    "lon": -1.9294499511974932
  },
  "commune_agglo": 0,
  "id_ban_commune": "2936147f-f8b5-4d5f-ae63-5b2707a99c13"
}

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-polygones

License

  • ✓ Redistributable
  • ✓ Attribution required

Query examples

curl -s 'https://data.rennesmetropole.fr/api/explore/v2.1/catalog/datasets/limites-communales-referentielles-de-rennes-metropole-polygones/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.

Full API documentation ↗

Rate limits

7 000 req/day
per ipmeasured
observed 2 days ago

Dataset

Volume & freshness

Records
147
Last upstream update
3 days ago
2026-10-20

License

No license declared upstream.

○ Documentation○ Data dictionary○ Versioning

Source: opendatasoft

Machine-readable & source

Limites communales référentielles de Rennes Métropole (polygones) — live verification badge

Embed this badge in a README or wiki — it always shows the latest verification state and quality tier.