c0mm0.com — the continuously verified register of European data

Register record·API·FR·MUNICIPALITYVERIFIED · checked 21h ago
C

Cadastre: SectionsCadastre : Sections

Cadastre : SectionsCadastre: Sections

APIExecutable4/7Query nowOpen workbenchSubscribe🇫🇷France

This API provides the polygon layer of cadastral sections within Rennes Métropole, France. A section is the basic unit of cadastral subdivision, representing a portion of a municipal territory delimited to facilitate the creation, consultation, and maintenance of cadastral records. The dataset defines the boundaries of these sections, which typically follow physical or administrative features. It is published by Rennes Métropole and is useful for land administration, urban planning, property identification, and geographic information system applications requiring precise cadastral boundaries at the local level.Cette couche de polygones contient les sections du plan cadastral. La section est l'unité de découpage cadastral. C'est une partie du territoire communal déterminée dans le but de faciliter l'établissement, la consultation et la tenue des documents cadastraux. Son périmètre est constitué dans la...

54
fair

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

Data schema (8 fields)

Filterable via the API (6)
gml_idogc_fidlotsectioncommunesection_txt

Click a field to see example values.

FieldTypeDescription
geo_point_2dGeo Pointgeo_point_2dGeographic coordinates of the section's centroid.Geographic coordinates of the section's centroid.
geo_shapeShapegeo_shapePolygon geometry outlining the cadastral section boundary.Polygon geometry outlining the cadastral section boundary.
gml_idFilterable via the APIGml idtextUnique GML identifier of the geometry record.Unique GML identifier of the geometry record.
ogc_fidFilterable via the APIOgc fidintInternal numeric feature identifier.Internal numeric feature identifier.
lotFilterable via the APItextData batch or update version identifier.Data batch or update version identifier.
sectionFilterable via the APItextFull cadastral section code including commune identifier.Full cadastral section code including commune identifier.
communeFilterable via the APICommunetextINSEE code of the commune the section belongs to.INSEE code of the commune the section belongs to.
section_txtFilterable via the APISection txttextShort alphabetic code identifying the cadastral section.Short alphabetic code identifying the cadastral section.

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)

Record 1lot: 2026-03 · gml_id: section.fid--2fb12420_1a15842043d_-39da
{
  "lot": "2026-03",
  "gml_id": "section.fid--2fb12420_1a15842043d_-39da",
  "commune": "350189",
  "ogc_fid": 344,
  "section": "350189000AN",
  "geo_shape": "[large value omitted]",
  "section_txt": "AN",
  "geo_point_2d": {
    "lat": 48.15884768317979,
    "lon": -1.7075949640463095
  }
}
Record 2lot: 2026-03 · gml_id: section.fid--2fb12420_1a15842043d_-3b08
{
  "lot": "2026-03",
  "gml_id": "section.fid--2fb12420_1a15842043d_-3b08",
  "commune": "350032",
  "ogc_fid": 50,
  "section": "350032000ZE",
  "geo_shape": "[large value omitted]",
  "section_txt": "ZE",
  "geo_point_2d": {
    "lat": 48.006280609256315,
    "lon": -1.6045253636899284
  }
}
Record 3lot: 2026-03 · gml_id: section.fid--2fb12420_1a15842043d_-3960
{
  "lot": "2026-03",
  "gml_id": "section.fid--2fb12420_1a15842043d_-3960",
  "commune": "350210",
  "ogc_fid": 461,
  "section": "350210000AI",
  "geo_shape": "[large value omitted]",
  "section_txt": "AI",
  "geo_point_2d": {
    "lat": 48.15875647156547,
    "lon": -1.7826723257457007
  }
}
Record 4lot: 2026-03 · gml_id: section.fid--2fb12420_1a15842043d_-3a50
{
  "lot": "2026-03",
  "gml_id": "section.fid--2fb12420_1a15842043d_-3a50",
  "commune": "350076",
  "ogc_fid": 231,
  "section": "350076000ZA",
  "geo_shape": "[large value omitted]",
  "section_txt": "ZA",
  "geo_point_2d": {
    "lat": 48.075203407997954,
    "lon": -1.7866719648345888
  }
}
Record 5lot: 2026-03 · gml_id: section.fid--2fb12420_1a15842043d_-3997
{
  "lot": "2026-03",
  "gml_id": "section.fid--2fb12420_1a15842043d_-3997",
  "commune": "350206",
  "ogc_fid": 411,
  "section": "350206000AK",
  "geo_shape": "[large value omitted]",
  "section_txt": "AK",
  "geo_point_2d": {
    "lat": 48.053761018971755,
    "lon": -1.6355732166418242
  }
}

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/cadastre-sections

Query examples

curl -s 'https://data.rennesmetropole.fr/api/explore/v2.1/catalog/datasets/cadastre-sections/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
837
Last upstream update
3 days ago
2026-10-20

License

No license declared upstream.

○ Documentation○ Data dictionary○ Versioning

Source: opendatasoft

Machine-readable & source

Cadastre : Sections — live verification badge

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