Traffic counts api
- devices: List with name and location of the traverses and their detectors by lane.
- live: The latest livestream data for all detectors, by traverse or by lane. The data is updated every minute.
- json: Default value, available for all requests.
- csv: Only available for devices.
- Optional parameter for :w
live requests. The value should be a traverse name or lane detector.
- Optional parameter for live requests. The parameters makes a filter for the measurement time space. Possible values are '1', '5', '15', '60' and 'all'. The value defines the time space in minutes. The default value 'all', gives you all data.
- Optional parameter for live requests. If the parameter is set 'true', the response gives also the data by lane. The default value is 'false'.
- Optional parameter for live requests. If the parameter is set 'true', the response gives only the last timestamp value. The default value is 'false'.
The following attributes are used in the responses:
- traverses: A traverse is a set of detectors, covering all lanes of a road.
- detector: A detector is a counting element for one lane.
- descr: Description of the counting location.
- orientation: Orientation of the traffic in degrees. Traffic towards the south gets value 0. The orientation is measured clockwise, with 360° for a full circle.
- number_of_lanes: The number of lanes the traverse is composed by.
- detectors: List of associated lane detectors.
Generally the last two timestamp values are given. t1 is the last value, t2 is the timestamp before the last one.
- count: Number of vehicules passed between start and end time.
- speed: Average speed of counted vehicules.
- occupancy: Percentage of time the detector is covered by a vehicule.
- from: Timestamp of start time.
- to: Timestamp of to time.
Geowebservices are available at the following links:
- WMS: https://data.mobility.brussels/geoserver/bm_traffic/wms?layers=bm_traffic:traffic_live_geom
- WFS: https://data.mobility.brussels/geoserver/bm_traffic/wfs?typeNames=bm_traffic:traffic_live_geom
- On map: https://data.mobility.brussels/mobigis
- Countings: an error rate <5% in free-flow traffic conditions. The accuracy depends on various factors (speed, light, …). Especially in congested traffic the accuracy can quickly decrease (up to 20-30%).
- Speed: devices (loops and cameras) have not been calibrated to measure accurate speed (like radars or other approved devices). Relative speed values can be used to detect speed decrease or congestion. Absolute values cannot be used in order to control speed limit compliance for example.
Thanks for making use of this data. We like to share the fun you have using this data. Feel free to inform us about your use on firstname.lastname@example.org. All questions and remarks are welcome.