2019 Traffic Counting – Bordeaux MétropoleComptage du trafic 2019 Bordeaux Métropole
Comptage du trafic 2019 Bordeaux Métropole2019 Traffic Counting – Bordeaux Métropole
This dataset provides 2019 road traffic counting data collected by a network of sensors installed by Bordeaux Métropole across its territory to monitor traffic conditions. Real-time traffic can also be consulted via the metropolitan area's dedicated traffic website. The dataset can be cross-referenced with the location of traffic counters to analyze traffic flow and volume at specific points within the Bordeaux metropolitan area, supporting mobility studies and urban planning.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 de données peut être mis en relation avec la localisation des compteurs de trafic à partir d...
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 counting sensor.Unique identifier of the traffic counting sensor. |
| 99.6% | hpm_valHpm val | double | Traffic volume measured during the morning peak hour.Traffic volume measured during the morning peak hour. |
| 99.8% | hps_valHps val | double | Traffic volume measured during the evening peak hour.Traffic volume measured during the evening peak hour. |
| 99.8% | mjo_valMjo val | double | Average daily traffic volume on a working day.Average daily traffic volume on a working day. |
| 97.2% | hpm | double | Percentage change in morning peak hour traffic compared to previous period.Percentage change in morning peak hour traffic compared to previous period. |
| 97.4% | hps | double | Percentage change in evening peak hour traffic compared to previous period.Percentage change in evening peak hour traffic compared to previous period. |
| 97.4% | mjo | double | Percentage change in average daily traffic compared to previous period.Percentage change in average daily traffic compared to previous period. |
| 20.4% | pl_valPl val | double | Count of heavy goods vehicles recorded by the sensor.Count of heavy goods vehicles recorded by the sensor. |
| 18.9% | pl | double | Percentage change in heavy goods vehicle traffic compared to previous period.Percentage change in heavy goods vehicle traffic compared to previous period. |
| 19.3% | vit_valVit val | double | Average vehicle speed measured at the sensor.Average vehicle speed measured at the sensor. |
| 18.4% | vit_evoVit evo | double | Percentage change in average speed compared to previous period.Percentage change in average speed compared to previous period. |
| 0% | comment | text | Free-text comment about the counting point or data.Free-text comment about the counting point or data. |
| 99.3% | 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.6% | sens_cirSens cir | text | Direction of traffic flow monitored by the sensor.Direction of traffic flow monitored by the sensor. |
| 0% | v85_vlV85 vl | text | 85th percentile speed recorded for light vehicles.85th percentile speed recorded for light vehicles. |
| 0% | v85_plV85 pl | text | 85th percentile speed recorded for heavy goods vehicles.85th percentile speed recorded for 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: -10
{
"pl": null,
"hpm": -10,
"hps": 1,
"mjo": -1,
"ident": "Z1CT14",
"pl_val": null,
"v85_pl": null,
"v85_vl": null,
"comment": null,
"hpm_val": 512,
"hps_val": 553,
"mjo_val": 8013,
"vit_evo": null,
"vit_val": null,
"nom_voie": "Bordeaux Quai Chartrons apres Hangar 14",
"sens_cir": "Nord > Sud"
}Record 2pl: — · hpm: -1
{
"pl": null,
"hpm": -1,
"hps": -2,
"mjo": 4,
"ident": "Z10CT21",
"pl_val": null,
"v85_pl": null,
"v85_vl": null,
"comment": null,
"hpm_val": 599,
"hps_val": 638,
"mjo_val": 10050,
"vit_evo": null,
"vit_val": null,
"nom_voie": "Bordeaux Tauzin après Haut Brion",
"sens_cir": "Sens Entrant"
}Record 3pl: — · hpm: 0
{
"pl": null,
"hpm": 0,
"hps": 0,
"mjo": 0,
"ident": "Z28CT6",
"pl_val": null,
"v85_pl": null,
"v85_vl": null,
"comment": null,
"hpm_val": 0,
"hps_val": 0,
"mjo_val": 0,
"vit_evo": null,
"vit_val": null,
"nom_voie": "St Médard Av. Montaigne avant Martin",
"sens_cir": "Sens Entrant"
}Record 4pl: -7.000000000000001 · hpm: 4
{
"pl": -7.000000000000001,
"hpm": 4,
"hps": 6,
"mjo": -3,
"ident": "Z30ENS",
"pl_val": 92,
"v85_pl": null,
"v85_vl": null,
"comment": null,
"hpm_val": 275,
"hps_val": 485,
"mjo_val": 3982,
"vit_evo": -0.02,
"vit_val": 42.6,
"nom_voie": "Mérignac Av. Bon Air (caserne du Burck)",
"sens_cir": "Sens Mérignac vers Pessac"
}Record 5pl: — · hpm: -4
{
"pl": null,
"hpm": -4,
"hps": -4,
"mjo": -5,
"ident": "Z9CT2",
"pl_val": null,
"v85_pl": null,
"v85_vl": null,
"comment": null,
"hpm_val": 995,
"hps_val": 1020,
"mjo_val": 13788,
"vit_evo": null,
"vit_val": null,
"nom_voie": "Bordeaux Blvd Gautier après Larminat",
"sens_cir": "Boulevards Nord > Sud"
}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_2019
License
- ✓ Redistributable
- ✓ Attribution required
Query examples
curl -s 'https://opendata.bordeaux-metropole.fr/api/explore/v2.1/catalog/datasets/comptage_trafic_2019/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.