The Traffic Analytics module for roadway analysis provides road speed, and travel time analysis that allows traffic engineers to develop a better understanding of the efficiency, maintenance, and safety of the signalized intersections and roads that are under their responsibility.
This API returns speed and traffic metrics for either the selected corridor or all road segments in the zone provided.
The API will be in Corridor Mode if the road segment parameter is filled and the zones parameter is empty, otherwise, the API will be in Zone Mode.
Spot speed metrics are measured as the highest speed achieved by the vehicle while traveling on the road segment.
There are several metrics that depend on Free-flow speed:
FreeFlowSpeed
SpotSpeedPctOfFreeflow
TravelSpeedPctOfFreeflow
TravelTimeDelayFromFreeflow
These metrics will be NULL if Free-flow speed is not available. This can occur for roads less than 1 month old, or roads that have been assigned new segment Ids due to an OSM change or changes to its geometry.
Detecting and capturing harsh events allows us to measure the risks of drivers/vehicles and roadways.
Harsh events are divided into three types:
Harsh Acceleration
Harsh Braking
Harsh Cornering
A harsh event is registered when a vehicle’s rate of change in acceleration exceeds the set threshold for the event type.
Harsh event detection rules are currently threshold-based.
Provide an API that monitors harsh events (harsh braking, harsh acceleration, harsh cornering) down to the road segment and provides filters by vocation, industry, and vehicle class. The API will be part of the Roads module. Refer to the Altitude API Guide for details.
The first step to GPS-based harsh events detection is to calculate acceleration/deceleration of the vehicle. We use the following time series signals:
Timestamp
Latitude
Longitude
Speed
Ignition
Please note that harsh events are identified from March 1, 2021 onwards. Data prior to this date is not available.