2022 Traffic Counts – Bordeaux MétropoleComptage du trafic 2022 Bordeaux Métropole
Comptage du trafic 2022 Bordeaux Métropole2022 Traffic Counts – Bordeaux Métropole
This dataset is published by Bordeaux Métropole, which operates a network of sensors to monitor traffic conditions across its territory. While live traffic data can be consulted via the sedeplacer.bordeaux-metropole.fr platform, this specific dataset provides alphanumeric records summarizing annual average traffic values at peak hours for the year 2022. It is intended to support analysis of traffic flow patterns on the metropolitan road network, and can be used for urban planning, mobility studies, and infrastructure assessment within the Bordeaux Métropole area. Access to the data is free and does not require authentication.Bordeaux Métropole a installé un réseau de capteurs pour évaluer l'état de la circulation sur son territoire. Ce trafic peut être consulté en temps réel sur http://sedeplacer.bordeaux-metropole.fr/ Ce jeu présente des données alphanumériques qui informent sur les valeurs moyennes annuelles à l'he...
Trust score
How is this computed?Weighted across five axes. Tap a ring for what it measures.
Data schema (16 fields)
Click a field to see example values.
| Fill | Field | Type | Description |
|---|---|---|---|
| 100% | ident | text | Unique identifier of the traffic sensor or counting point.Unique identifier of the traffic sensor or counting point. |
| 100% | hpm_valHpm val | int | Traffic volume during the morning peak hour.Traffic volume during the morning peak hour. |
| 100% | hps_valHps val | int | Traffic volume during the evening peak hour.Traffic volume during the evening peak hour. |
| 100% | mjo_valMjo val | int | Average daily traffic on working days.Average daily traffic on working days. |
| 94.6% | hpm | double | Year-on-year evolution rate of morning peak hour traffic, in percent.Year-on-year evolution rate of morning peak hour traffic, in percent. |
| 95.1% | hps | double | Year-on-year evolution rate of evening peak hour traffic, in percent.Year-on-year evolution rate of evening peak hour traffic, in percent. |
| 95.1% | mjo | double | Year-on-year evolution rate of average daily working-day traffic, in percent.Year-on-year evolution rate of average daily working-day traffic, in percent. |
| 15% | pl_valPl val | int | Number or share of heavy goods vehicles counted.Number or share of heavy goods vehicles counted. |
| 13.7% | pl | double | Year-on-year evolution rate of heavy goods vehicle traffic, in percent.Year-on-year evolution rate of heavy goods vehicle traffic, in percent. |
| 14.7% | vit_valVit val | int | Average vehicle speed recorded at the sensor.Average vehicle speed recorded at the sensor. |
| 14.2% | vit_evoVit evo | double | Year-on-year evolution rate of average vehicle speed, in percent.Year-on-year evolution rate of average vehicle speed, in percent. |
| 0% | comment | text | Free-text comment or remark about the counting point.Free-text comment or remark about the counting point. |
| 100% | nom_voieNom voie | text | Name and location of the road where the sensor is installed.Name and location of the road where the sensor is installed. |
| 99% | sens_cirSens cir | text | Direction of traffic flow monitored by the sensor.Direction of traffic flow monitored by the sensor. |
| 0% | v85_vlV85 vl | double | 85th percentile speed of light vehicles.85th percentile speed of light vehicles. |
| 0% | v85_plV85 pl | double | 85th percentile speed of heavy goods vehicles.85th percentile speed of heavy goods vehicles. |
Schema captured from opendatasoft 3 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 1pl: — · hpm: 9.1
{
"pl": null,
"hpm": 9.1,
"hps": -18.1,
"mjo": -6,
"ident": "Z25CT17",
"pl_val": null,
"v85_pl": null,
"v85_vl": null,
"comment": null,
"hpm_val": 80,
"hps_val": 186,
"mjo_val": 1990,
"vit_evo": null,
"vit_val": null,
"nom_voie": "Bordeaux Quebec avant Royer",
"sens_cir": "Nord > Sud"
}Record 2pl: — · hpm: -14.6
{
"pl": null,
"hpm": -14.6,
"hps": -11,
"mjo": -12,
"ident": "Z4CT19",
"pl_val": null,
"v85_pl": null,
"v85_vl": null,
"comment": null,
"hpm_val": 263,
"hps_val": 279,
"mjo_val": 4548,
"vit_evo": null,
"vit_val": null,
"nom_voie": "Bordeaux Rue N.-Pénard après Michelet",
"sens_cir": "Nord > Sud"
}Record 3pl: — · hpm: -9.1
{
"pl": null,
"hpm": -9.1,
"hps": -3.5,
"mjo": -4.9,
"ident": "Z13CT9",
"pl_val": null,
"v85_pl": null,
"v85_vl": null,
"comment": null,
"hpm_val": 398,
"hps_val": 349,
"mjo_val": 4931,
"vit_evo": null,
"vit_val": null,
"nom_voie": "Bordeaux Rue Johnston avant Arsenal",
"sens_cir": "Sens Entrant"
}Record 4pl: — · hpm: -12.9
{
"pl": null,
"hpm": -12.9,
"hps": -6.9,
"mjo": -9,
"ident": "Z15CT2",
"pl_val": null,
"v85_pl": null,
"v85_vl": null,
"comment": null,
"hpm_val": 260,
"hps_val": 363,
"mjo_val": 4593,
"vit_evo": null,
"vit_val": null,
"nom_voie": "Bordeaux Cours Portal après Doumer",
"sens_cir": "Sens Sortant"
}Record 5pl: — · hpm: 4.4
{
"pl": null,
"hpm": 4.4,
"hps": 1.2,
"mjo": 10.2,
"ident": "Z7CT8",
"pl_val": null,
"v85_pl": null,
"v85_vl": null,
"comment": null,
"hpm_val": 164,
"hps_val": 305,
"mjo_val": 3120,
"vit_evo": null,
"vit_val": null,
"nom_voie": "Mérignac Av. Leclerc après V. Eglise",
"sens_cir": "Sud > Nord"
}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/comptage_trafic_2022
License
- ✓ Redistributable
- ✓ Attribution required
Query examples
curl -s 'https://opendata.bordeaux-metropole.fr/api/explore/v2.1/catalog/datasets/comptage_trafic_2022/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.
Rate limits
Dataset
Volume & freshness
License
No license declared upstream.
Source: opendatasoft
Machine-readable & source
Embed this badge in a README or wiki — it always shows the latest verification state and quality tier.