c0mm0.com — the continuously verified register of European data

Register record·API·FR·AGENCYVERIFIED · checked 2d ago
I

Inventory of Ground MovementsInventaire des mouvements de terrain

Inventaire des mouvements de terrainInventory of Ground Movements

APIExecutable4/7Query nowOpen workbenchSubscribe🇫🇷France

This dataset provides point locations of ground movements (landslides and similar terrain instabilities) recorded across the Gironde department in France. It is published as open data, with an additional download option available in AutoCAD DWG format. The dataset is maintained in connection with the Bureau de recherches géologiques et minières (BRGM), the French geological survey, and can be used for geological risk assessment, land-use planning, and hazard mapping in the covered territory.Dictionnaire Public Ce jeu de données localise par un ponctuel les mouvements de terrain recensés sur le territoire Girondin. Ce jeu de données est disponible dans un format additionnel : Téléchargement au format AutoCAD DWG

44
fair

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

Data schema (12 fields)

Filterable via the API (10)
gidgeom_ogeom_errtypecdatemdatefiabilitedate_debut_mvtprecision_planialtitude

Click a field to see example values.

FillFieldTypeDescription
geo_point_2dGeo Pointgeo_point_2dGeographic point coordinates (latitude and longitude) of the ground movement.Geographic point coordinates (latitude and longitude) of the ground movement.
geo_shapeShapegeo_shapeGeoJSON geometry representing the location of the ground movement.GeoJSON geometry representing the location of the ground movement.
gidFilterable via the APIintPrimary key identifier of the record.Clé primaire
geom_oFilterable via the APIGeom odoubleOrientation angle of the point geometry.Orientation du point
geom_errFilterable via the APIGeom errtextError code indicating a geometry validity issue, if any.Code d'erreur géométrique : Liste des valeurs possibles : 9999 : Polygone compose et / ou à sections multiples 9998 : Linéaire compose et / ou à sections multiples 9996 : La géométrie contient des informations LRS 9995 : Nombre de dimensions différent de 2 ou 3 9994 : Présence d'un arc de cercle 9000 : Erreur autre 13343 : Polygone de moins de 4 points 13349 : Polygone papillon 13350 : Deux éléments d'un polygone archipel se touchent 13351 : Deux éléments d'un polygone archipel se touchent 13356 : Point double 13366 : Combinaison invalide d'intérieur / extérieur d'un polygone 13367 : Orientation invalide d'intérieur / extérieur d'un polygone
typeFilterable via the APItextType of ground movement recorded (e.g. landslide, rockfall, mudflow, collapse, bank erosion).Type de mouvement de terrain : Liste des valeurs possibles : GLISSEMENT : Glissement de terrain CHUTE_BLOC_EBOULEMENT : Chute de bloc ou éboulement COULEE : Coulée de boue EFFONDREMENT_AFFAIBLISSEMENT : Effondrement ou affaiblissement EROSION_BERGES : Erosion des berges
cdateFilterable via the APIdatetimeDate the record was created.Date de création
mdateFilterable via the APIdatetimeDate the record was last modified.Date de modification
fiabiliteFilterable via the APItextReliability level of the survey (low, medium, high).Fiabilité du relevé : Liste des valeurs possibles : FAIBLE : Faible MOYENNE : Moyenne FORTE : Forte
date_debut_mvtFilterable via the APIDate debut mvtdatetimeDate when the ground movement started.Date de début du mouvement de terrain
100%precision_planiFilterable via the APIPrecision planitextPlanimetric precision of the location (metric, decametric, hectometric, kilometric, or communal).Précision planimétrique : Liste des valeurs possibles : METRIQUE : Métrique DECAMETRIQUE : Décamétrique HECTOMETRIQUE : Hectométrique KILOMETRIQUE : Kilométrique COMMUNALE : Communale
52.7%altitudeFilterable via the APIintAltitude of the location, in meters.Altitude (en mètre)

Schema captured from opendatasoft 6 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: 1601 · type: EFFONDREMENT_AFFAIBLISSEMENT
{
  "gid": 1601,
  "type": "EFFONDREMENT_AFFAIBLISSEMENT",
  "cdate": "2003-05-20T22:00:00+00:00",
  "mdate": "2024-09-03T22:00:00+00:00",
  "geom_o": 0,
  "altitude": 43,
  "geom_err": null,
  "fiabilite": "FORTE",
  "geo_shape": {
    "type": "Feature",
    "geometry": {
      "type": "Point",
      "coordinates": [
        -0.093327,
        44.5427319
      ]
    },
    "properties": {}
  },
  "geo_point_2d": {
    "lat": 44.5427319,
    "lon": -0.093327
  },
  "date_debut_mvt": "1990-12-31T23:00:00+00:00",
  "precision_plani": "HECTOMETRIQUE"
}
Record 2gid: 1602 · type: EFFONDREMENT_AFFAIBLISSEMENT
{
  "gid": 1602,
  "type": "EFFONDREMENT_AFFAIBLISSEMENT",
  "cdate": "2003-05-20T22:00:00+00:00",
  "mdate": "2024-09-03T22:00:00+00:00",
  "geom_o": 0,
  "altitude": 16,
  "geom_err": null,
  "fiabilite": "FORTE",
  "geo_shape": {
    "type": "Feature",
    "geometry": {
      "type": "Point",
      "coordinates": [
        -0.4148959,
        44.6866459
      ]
    },
    "properties": {}
  },
  "geo_point_2d": {
    "lat": 44.6866459,
    "lon": -0.4148959
  },
  "date_debut_mvt": "2003-03-20T23:00:00+00:00",
  "precision_plani": "DECAMETRIQUE"
}
Record 3gid: 1603 · type: EFFONDREMENT_AFFAIBLISSEMENT
{
  "gid": 1603,
  "type": "EFFONDREMENT_AFFAIBLISSEMENT",
  "cdate": "2003-05-20T22:00:00+00:00",
  "mdate": "2024-09-03T22:00:00+00:00",
  "geom_o": 0,
  "altitude": null,
  "geom_err": null,
  "fiabilite": "FORTE",
  "geo_shape": {
    "type": "Feature",
    "geometry": {
      "type": "Point",
      "coordinates": [
        -0.3041669,
        44.5681339
      ]
    },
    "properties": {}
  },
  "geo_point_2d": {
    "lat": 44.5681339,
    "lon": -0.3041669
  },
  "date_debut_mvt": "1986-09-30T23:00:00+00:00",
  "precision_plani": "HECTOMETRIQUE"
}
Record 4gid: 1604 · type: EFFONDREMENT_AFFAIBLISSEMENT
{
  "gid": 1604,
  "type": "EFFONDREMENT_AFFAIBLISSEMENT",
  "cdate": "2003-05-20T22:00:00+00:00",
  "mdate": "2024-09-03T22:00:00+00:00",
  "geom_o": 0,
  "altitude": null,
  "geom_err": null,
  "fiabilite": "FORTE",
  "geo_shape": {
    "type": "Feature",
    "geometry": {
      "type": "Point",
      "coordinates": [
        -0.3163079,
        44.5735999
      ]
    },
    "properties": {}
  },
  "geo_point_2d": {
    "lat": 44.5735999,
    "lon": -0.3163079
  },
  "date_debut_mvt": "1988-06-12T22:00:00+00:00",
  "precision_plani": "HECTOMETRIQUE"
}
Record 5gid: 1607 · type: EFFONDREMENT_AFFAIBLISSEMENT
{
  "gid": 1607,
  "type": "EFFONDREMENT_AFFAIBLISSEMENT",
  "cdate": "2003-05-20T22:00:00+00:00",
  "mdate": "2024-09-03T22:00:00+00:00",
  "geom_o": 0,
  "altitude": null,
  "geom_err": null,
  "fiabilite": "FORTE",
  "geo_shape": {
    "type": "Feature",
    "geometry": {
      "type": "Point",
      "coordinates": [
        -0.486754,
        45.0327219
      ]
    },
    "properties": {}
  },
  "geo_point_2d": {
    "lat": 45.0327219,
    "lon": -0.486754
  },
  "date_debut_mvt": "1999-11-08T23:00:00+00:00",
  "precision_plani": "HECTOMETRIQUE"
}

Live sample captured at profiling time — values may have changed upstream.

Verification Status

Using the API

Configuration

Base URL
https://opendata.bordeaux-metropole.fr/api/explore/v2.1/catalog/datasets/ri_mvt_terrain_p

License

  • Redistributable
  • Attribution required

Query examples

curl -s 'https://opendata.bordeaux-metropole.fr/api/explore/v2.1/catalog/datasets/ri_mvt_terrain_p/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

50 000 req/day
per ipmeasured
observed 6 days ago

Dataset

Volume & freshness

Records
827
Last upstream update
7 days ago
2026-09-02

License

No license declared upstream.

Documentation Data dictionary Versioning

Source: opendatasoft

Machine-readable & source

Inventaire des mouvements de terrain — live verification badge

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