Traffic Counting Métropole 2018Comptage du trafic Métropole 2018
Comptage du trafic Métropole 2018Traffic Counting Métropole 2018
This dataset provides traffic counting data collected by a network of sensors installed by Bordeaux Métropole to monitor road traffic conditions across its territory for the year 2018. Real-time traffic can also be consulted via the sedeplacer.bordeaux-metropole.fr platform. The dataset is designed to be cross-referenced with the location of traffic counters, enabling spatial analysis of traffic flow. It is published as open data by Bordeaux Métropole and is useful for transport planning, mobility studies, and analysis of road usage patterns within the metropolitan area.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. |
| 90.5% | hpm_valHpm val | int | Traffic volume during the morning peak hour.Traffic volume during the morning peak hour. |
| 90.5% | hps_valHps val | int | Traffic volume during the evening peak hour.Traffic volume during the evening peak hour. |
| 90.5% | mjo_valMjo val | int | Average daily traffic volume.Average daily traffic volume. |
| 88.4% | hpm | text | Text representation of the morning peak hour traffic value.Text representation of the morning peak hour traffic value. |
| 88.6% | hps | text | Text representation of the evening peak hour traffic value.Text representation of the evening peak hour traffic value. |
| 88.6% | mjo | text | Text representation of the average daily traffic value.Text representation of the average daily traffic value. |
| 19.7% | pl_valPl val | double | Proportion or count of heavy goods vehicles.Proportion or count of heavy goods vehicles. |
| 19.4% | pl | text | Text representation of the heavy goods vehicle value.Text representation of the heavy goods vehicle value. |
| 19.7% | vit_valVit val | double | Recorded traffic speed value.Recorded traffic speed value. |
| — | vit_evoVit evo | geo_point_2d | Geographic coordinates associated with the speed measurement point.Geographic coordinates associated with the speed measurement point. |
| — | comment | text | Free-text comment about the traffic count record.Free-text comment about the traffic count record. |
| — | nom_voieNom voie | text | Name of the road or street being measured.Name of the road or street being measured. |
| — | sens_cirSens cir | text | Direction of traffic flow on the road.Direction of traffic flow on the road. |
| — | v85_vlV85 vl | text | 85th percentile speed for light vehicles.85th percentile speed for light vehicles. |
| — | v85_plV85 pl | text | 85th percentile speed for heavy goods vehicles.85th percentile speed for heavy goods vehicles. |
Schema captured from opendatasoft 1 day 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: —
{
"pl": null,
"hpm": null,
"hps": null,
"mjo": null,
"ident": "Z21CT4",
"pl_val": null,
"v85_pl": null,
"v85_vl": null,
"comment": null,
"hpm_val": null,
"hps_val": null,
"mjo_val": null,
"vit_evo": null,
"vit_val": null,
"nom_voie": null,
"sens_cir": null
}Record 2pl: — · hpm: —
{
"pl": null,
"hpm": null,
"hps": null,
"mjo": null,
"ident": "Z18CT5",
"pl_val": null,
"v85_pl": null,
"v85_vl": null,
"comment": null,
"hpm_val": null,
"hps_val": null,
"mjo_val": null,
"vit_evo": null,
"vit_val": null,
"nom_voie": null,
"sens_cir": null
}Record 3pl: — · hpm: -30,2%
{
"pl": null,
"hpm": "-30,2%",
"hps": "-5,4%",
"mjo": "-8,4%",
"ident": "Z29CT10",
"pl_val": null,
"v85_pl": null,
"v85_vl": null,
"comment": null,
"hpm_val": 230,
"hps_val": 442,
"mjo_val": 4211,
"vit_evo": null,
"vit_val": null,
"nom_voie": "Floirac Dubedout avant Allende",
"sens_cir": "Sens Sortant"
}Record 4pl: — · hpm: —
{
"pl": null,
"hpm": null,
"hps": null,
"mjo": null,
"ident": "Z13CT9",
"pl_val": null,
"v85_pl": null,
"v85_vl": null,
"comment": null,
"hpm_val": null,
"hps_val": null,
"mjo_val": null,
"vit_evo": null,
"vit_val": null,
"nom_voie": "Bordeaux Rue Johnston avant Arsenal",
"sens_cir": "Sens Entrant"
}Record 5pl: — · hpm: 17,3%
{
"pl": null,
"hpm": "17,3%",
"hps": "3,8%",
"mjo": "2,3%",
"ident": "Z25CT18",
"pl_val": null,
"v85_pl": null,
"v85_vl": null,
"comment": null,
"hpm_val": 218,
"hps_val": 512,
"mjo_val": 3561,
"vit_evo": null,
"vit_val": null,
"nom_voie": "Bordeaux Domergue S>N avant rocade",
"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_2018
License
- ✓ Redistributable
- ✓ Attribution required
Query examples
curl -s 'https://opendata.bordeaux-metropole.fr/api/explore/v2.1/catalog/datasets/comptage_trafic_2018/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.