c0mm0.com — the continuously verified register of European data

Register record·API·FR·MUNICIPALITYVERIFIED · checked 31h ago
N

Negative Layer of Geographic Blocks in Rennes MétropoleNégatif des îlots géographiques sur Rennes Métropole

Négatif des îlots géographiques sur Rennes MétropoleNegative Layer of Geographic Blocks in Rennes Métropole

APIJoinable5/7Query nowOpen workbenchSubscribe🇫🇷France

This dataset provides the inverse (negative) footprint of the geographic blocks (îlots géographiques) defined across the territory of Rennes Métropole, France. It is published as an API by Rennes Métropole and forms part of its geographic information system data. Further technical details on the underlying geographic blocks are available through the associated metadata record in the Rennes Métropole GeoNetwork catalog. The layer is intended for use in spatial analysis and mapping applications requiring the complement of the standard block delineation across the metropolitan area.rennesCette couche contient l'emprise inverse des ilots géographiques constitués sur le territoire de Rennes Métropole. Plus d'info sur les îlots géographiques en consultant la métadonnée suivante : https://portail.sig.rennesmetropole.fr/geonetwork/srv/fre/catalog.search#/metadata/187ce493-e778-4adc-ac...

geospatial
57
fair

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

Data schema (7 fields)

Filterable via the API (5)
gml_idobjectidsecteurcommune_agglocode_insee

Click a field to see example values.

FieldTypeDescription
geo_point_2dGeo Pointgeo_point_2dGeographic center point (latitude/longitude) of the feature.Geographic center point (latitude/longitude) of the feature.
geo_shapeShapegeo_shapeGeometry of the inverse geographic block (negative footprint area).Geometry of the inverse geographic block (negative footprint area).
gml_idFilterable via the APIGml idtextUnique GML identifier of the geographic block feature.Unique GML identifier of the geographic block feature.
objectidFilterable via the APIintInternal numeric identifier of the record.Internal numeric identifier of the record.
secteurFilterable via the APIintSector code to which the geographic block belongs.Sector code to which the geographic block belongs.
commune_aggloFilterable via the APICommune agglointIndicator of whether the commune belongs to the agglomeration.Indicator of whether the commune belongs to the agglomeration.
code_inseeFilterable via the APIINSEE commune codetextINSEE code identifying the commune.INSEE code identifying the commune.

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 1gml_id: ilot_topo_negatif.95 · secteur: 2
{
  "gml_id": "ilot_topo_negatif.95",
  "secteur": 2,
  "objectid": 95,
  "geo_shape": "[large value omitted]",
  "code_insee": "35080",
  "geo_point_2d": {
    "lat": 48.10681569568011,
    "lon": -1.881678785536766
  },
  "commune_agglo": 1
}
Record 2gml_id: ilot_topo_negatif.42 · secteur: 2
{
  "gml_id": "ilot_topo_negatif.42",
  "secteur": 2,
  "objectid": 42,
  "geo_shape": "[large value omitted]",
  "code_insee": "35180",
  "geo_point_2d": {
    "lat": 48.281734354347584,
    "lon": -1.929039830350153
  },
  "commune_agglo": 1
}
Record 3gml_id: ilot_topo_negatif.58 · secteur: 2
{
  "gml_id": "ilot_topo_negatif.58",
  "secteur": 2,
  "objectid": 58,
  "geo_shape": "[large value omitted]",
  "code_insee": "35343",
  "geo_point_2d": {
    "lat": 47.885599241226295,
    "lon": -1.5481016417672173
  },
  "commune_agglo": 0
}
Record 4gml_id: ilot_topo_negatif.148 · secteur: 2
{
  "gml_id": "ilot_topo_negatif.148",
  "secteur": 2,
  "objectid": 148,
  "geo_shape": "[large value omitted]",
  "code_insee": "35242",
  "geo_point_2d": {
    "lat": 48.38414083480915,
    "lon": -1.5276922426109083
  },
  "commune_agglo": 0
}
Record 5gml_id: ilot_topo_negatif.155 · secteur: 2
{
  "gml_id": "ilot_topo_negatif.155",
  "secteur": 2,
  "objectid": 155,
  "geo_shape": "[large value omitted]",
  "code_insee": "35334",
  "geo_point_2d": {
    "lat": 48.15468694198403,
    "lon": -1.5832552133802982
  },
  "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/negatif-des-ilots-geographiques-sur-rennes-metropole

Query examples

curl -s 'https://data.rennesmetropole.fr/api/explore/v2.1/catalog/datasets/negatif-des-ilots-geographiques-sur-rennes-metropole/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
155
Last upstream update
3 days ago
2026-10-20

License

No license declared upstream.

○ Documentation○ Data dictionary○ Versioning

Source: opendatasoft

Machine-readable & source

Négatif des îlots géographiques sur Rennes Métropole — live verification badge

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