Electromagnetic wave sensors - daily historyCapteur d'ondes électromagnétiques - historique journalier

Name: Electromagnetic wave sensors - daily history
Creator: opendatasoft

Capteur d'ondes électromagnétiques - historique journalierElectromagnetic wave sensors - daily history

APIDiscovered1/7blocked by verifiedQuery nowOpen workbench Subscribe🇫🇷France

This dataset provides the historical daily average measurements recorded by the various electromagnetic wave sensors deployed across Bordeaux Métropole, in France. It is built from the data-aggregation webservice supplied by Bordeaux Métropole and is joined with the related dataset describing the electromagnetic wave sensors themselves, adding location and technical context to the daily readings. It is published as open data and can be used to track electromagnetic exposure levels over time within the metropolitan area.Le jeu de données présente l'historique des mesures journalières moyennes pour les différents capteurs d'ondes électromagnétiques. Il est construit à partir du webservice d'agrégation proposé par Bordeaux Métropole. Une jointure a été effectuée avec le jeu de données Capteur d'ondes électromagnét...

⬇ Export CSV List records Select & filter Run verified request Read the docs

Trust score

How is this computed?

poor

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

Data schema (10 fields)

Filterable via the API (8)

timegidcdatenometaturlimageidentmesure

Click a field to see example values.

Field	Type	Description
timeDate des mesures	date	—
gid	int	—
geo_point_2dGeo Point	geo_point_2d	—
cdate	datetime	Date de création
geo_shapeShape	geo_shape	—
nom	text	—
etat	text	—
urlimage	text	—
ident	text	—
mesure	double	—

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.

Where=

Sort by

Sample data (5 records)

Record 1gid: 1 · nom: Le-Haillan_01

{
  "gid": 1,
  "nom": "Le-Haillan_01",
  "etat": "EN_LIGNE",
  "time": "2023-01-13",
  "cdate": "2021-08-13T13:32:39+00:00",
  "ident": "01767c5a-9f3e-49f1-868e-7d6a4807d6d1",
  "mesure": 0.49447916666666664,
  "urlimage": "https://storage.googleapis.com/odo-prod-sites/site_01767c5a-9f3e-49f1-868e-7d6a4807d6d1/Le_Haillan_01_1000x1000.webp",
  "geo_shape": {
    "type": "Feature",
    "geometry": {
      "type": "Point",
      "coordinates": [
        -0.678703,
        44.879311
      ]
    },
    "properties": {}
  },
  "geo_point_2d": {
    "lat": 44.879311,
    "lon": -0.678703
  }
}

Record 2gid: 1 · nom: Le-Haillan_01

{
  "gid": 1,
  "nom": "Le-Haillan_01",
  "etat": "EN_LIGNE",
  "time": "2023-01-14",
  "cdate": "2021-08-13T13:32:39+00:00",
  "ident": "01767c5a-9f3e-49f1-868e-7d6a4807d6d1",
  "mesure": 0.04635416666666667,
  "urlimage": "https://storage.googleapis.com/odo-prod-sites/site_01767c5a-9f3e-49f1-868e-7d6a4807d6d1/Le_Haillan_01_1000x1000.webp",
  "geo_shape": {
    "type": "Feature",
    "geometry": {
      "type": "Point",
      "coordinates": [
        -0.678703,
        44.879311
      ]
    },
    "properties": {}
  },
  "geo_point_2d": {
    "lat": 44.879311,
    "lon": -0.678703
  }
}

Record 3gid: 1 · nom: Le-Haillan_01

{
  "gid": 1,
  "nom": "Le-Haillan_01",
  "etat": "EN_LIGNE",
  "time": "2023-01-15",
  "cdate": "2021-08-13T13:32:39+00:00",
  "ident": "01767c5a-9f3e-49f1-868e-7d6a4807d6d1",
  "mesure": 0.49197916666666663,
  "urlimage": "https://storage.googleapis.com/odo-prod-sites/site_01767c5a-9f3e-49f1-868e-7d6a4807d6d1/Le_Haillan_01_1000x1000.webp",
  "geo_shape": {
    "type": "Feature",
    "geometry": {
      "type": "Point",
      "coordinates": [
        -0.678703,
        44.879311
      ]
    },
    "properties": {}
  },
  "geo_point_2d": {
    "lat": 44.879311,
    "lon": -0.678703
  }
}

Record 4gid: 1 · nom: Le-Haillan_01

{
  "gid": 1,
  "nom": "Le-Haillan_01",
  "etat": "EN_LIGNE",
  "time": "2023-01-18",
  "cdate": "2021-08-13T13:32:39+00:00",
  "ident": "01767c5a-9f3e-49f1-868e-7d6a4807d6d1",
  "mesure": 0.5116666666666666,
  "urlimage": "https://storage.googleapis.com/odo-prod-sites/site_01767c5a-9f3e-49f1-868e-7d6a4807d6d1/Le_Haillan_01_1000x1000.webp",
  "geo_shape": {
    "type": "Feature",
    "geometry": {
      "type": "Point",
      "coordinates": [
        -0.678703,
        44.879311
      ]
    },
    "properties": {}
  },
  "geo_point_2d": {
    "lat": 44.879311,
    "lon": -0.678703
  }
}

Record 5gid: 1 · nom: Le-Haillan_01

{
  "gid": 1,
  "nom": "Le-Haillan_01",
  "etat": "EN_LIGNE",
  "time": "2023-01-19",
  "cdate": "2021-08-13T13:32:39+00:00",
  "ident": "01767c5a-9f3e-49f1-868e-7d6a4807d6d1",
  "mesure": 0.48041666666666666,
  "urlimage": "https://storage.googleapis.com/odo-prod-sites/site_01767c5a-9f3e-49f1-868e-7d6a4807d6d1/Le_Haillan_01_1000x1000.webp",
  "geo_shape": {
    "type": "Feature",
    "geometry": {
      "type": "Point",
      "coordinates": [
        -0.678703,
        44.879311
      ]
    },
    "properties": {}
  },
  "geo_point_2d": {
    "lat": 44.879311,
    "lon": -0.678703
  }
}

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/rt_ondeelectro_p_histo_jour

License

Licence Ouverte 2.0 (France / Etalab)Open

✓ Redistributable
✓ Attribution required

Query examples

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

32k

32472

Last upstream update

5 months ago

2026-04-20

License

No license declared upstream.

○ Documentation○ Data dictionary○ Versioning

Source: opendatasoft

Machine-readable & source

JSON

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