Route Monitoring

FAQs

Important Note
Explore ready-to-use traffic reports and data visualizations immediately by signing up for a 30-day free trial on the MOVE Portal. Once registered, you’ll receive an API key to start using the Traffic Analytics APIs right away. Alternatively, you may contact our Sales team for a tailored solution.

What areas of the world are covered by Route Monitoring?

See our Market Coverage page for detailed information.

Which roads can I monitor?

Data is guaranteed for roads with Functional Road Classes (FRC) 0 to 4. For roads with a lower class (FRC 5 to 7), data may still be available, but not necessarily for every segment of the route.

Why does my route have a Failed status?

A route gets the Failed status when the road is impassable. The same error can appear when the road network has changed since the route was created.



Routes in this state should be deleted, or updated with new geometry. See Troubleshooting.

The route does not follow the roads I expected. What can I do?

Add additional via points when creating or editing the route, so that the route covers exactly the roads you want to monitor.

Do I need to write code to use Route Monitoring?

No. Route Monitoring is available both as a RESTful API and as a ready-to-use web application in the MOVE Portal, where you can pre-define routes and monitor them through a map interface.



See the MOVE Portal documentation.

What does the data confidence value mean?

Confidence is a measure of the quality of the provided travel time and speed. A value of 100 means full confidence, that is, the response contains the highest quality data. Lower values indicate the degree to which the response may vary from the actual conditions on the road.



The API returns routeConfidence for the whole route and confidence per segment.

What is typical travel time, and how is it different from travel time?

Travel time is the duration of traversing the route under current conditions. Typical travel time is the travel time expected at that time of day, based on TomTom Speed Profiles data, calculated per five-minute time bin.



If a typical travel time is not available, the missing bits are replaced with the current travel time where possible. If real-time data cannot be accessed, the average historical travel time is used instead.

What does flow coverage tell me?

Flow coverage is the percentage of the route for which real-time data is available, in relation to historical data. In the API, it is returned as typicalTravelTimeCoverage.

Can I see results per part of the route?

Yes. Overall route values are returned for the whole route length, and detailed segments provide travel time, speed, length, and confidence down to short length extensions.



See Segment information.

Can I connect Route Monitoring to Variable Message Signs?

Yes. Route Monitoring is commonly used to feed travel times and alternative route suggestions to Variable Message Sign (VMS) displays, as well as ITS and traffic management systems.