[![Picto dictionary public](/assets/theme_image/dico_big.png) Dictionary Public](https://data.bordeaux-metropole.fr/dicopub/#/dico#pc_captv_p)
The dataset locates on Bordeaux Métropole the different recurrent counting sites of cycling flows. It distinguishes:
* bike sensors (counters/auto-loops) that count the number of cyclists in “real time” at 5 minute time
* occasional survey sites which are the subject of a periodic survey within the framework of the Bordeaux Métropole bike observatory.
Automatic sensors are magnetic loops located on a part of the roadway to identify the flow of bicycles by discriminating against other vehicle flows (cars, trucks, motorcycles, etc.).
On sites with sustained cycling traffic with simultaneous passage of several cyclists on the sensor, the data may slightly underestimate actual cyclist traffic.
Therefore, these data do not correspond to a comprehensive census of cyclists using the track where the sensor is located.
For automatic sensors, it is possible via the Bordeaux Métropole WebServices:
* to access current values
* to access values at a past T moment
* do data aggregation per day, month, etc.
The historicisation began at the end of 2020.
A dataset with the [time history of automatic sensors](https://opendata.bordeaux-metropole.fr/explore/dataset/pc_captv_p_histo_heure/information/) is also available.
* * *
This data set is refreshed all: 3 Minute(s).
Be careful, for performance reasons, this dataset (Table, Map, Analysis and Export tabs) can be updated less frequently than the source and a deviation may exist. We also invite you to use our Webservices (see Webservices BM tab) to retrieve the freshest data.
Build on reliable and scalable technology
FAQ
Frequently Asked Questions
Some basic informations about API Store ®.
Operation and development of APIs are currently fully funded by company Apitalks and its usage is for free.
Yes, you can.
All important information such as time of last update, license and other information are in response of each API call.
In case of major update that would not be compatible with previous version of API, we keep for 30 days both versions so you will have enough time to transfer to new version. We will inform you about the changes in advance by e-mail.