FAQs
What data is O/D Analysis based on?
O/D Analysis is based on Floating Car Data (FCD). Millions of TomTom navigation devices, in-dash systems, and apps send anonymized data to our servers in real time, from which historical traffic information is derived.
What counts as a trip?
Our algorithms analyze the probe traces coming from each device. A trip is a sequence of probe points (GPS pings) originating from the same anonymous device ID, connected into a single line with a start and an end point.
See Trip definition for details.
Can a trip be traced back to an individual driver or address?
No. Trips come from completely anonymized data, which protects individual devices from being associated with specific drivers.
When is map matching applied to my analysis?
Map matching ‘snaps’ GPS positions to the road network, which removes inaccuracies caused by low GPS precision or small gaps in the signal.
It is enabled when the convex hull area of the regions in the analysis is below 3,000 km², and disabled above that, because map matching all traces on such a large scale heavily affects the required calculation power.
In the MOVE Portal, being able to select a map version while defining the zones indicates that the results are based on map-matched traces.
Which map version should I use?
ORBIS is the recommended map type. GENESIS is a legacy map type that will be deprecated in the future.
To check which map versions are available for an area, use the Available maps endpoint.
How long does an analysis take?
The API is asynchronous. Processing takes from a few minutes up to a few hours, depending on the size of the analysis.
Do not repost your request if you do not get feedback within seconds — the results will be delivered.
Why do I have to accept an analysis before I get results?
An analysis is prepared first, and calculated only after you confirm it. Use Analysis Accepting to confirm an analysis and start the calculation, or Analysis Rejecting to discard it.
Is there a limit to the size of an analysis?
Yes. Both analysis types have their own default usage limits.
For a Flow Matrix analysis, limits apply to the number of regions, the analyzed area, and the date and time ranges.
For a Selected Link analysis, limits apply to the link length, the radius, the polygon area, and the date and time ranges. The longest supported selected link is 2 km (1.24 miles); requests with a longer link are rejected.
See Product usage limits for the values of both.
Which coordinate system is used?
Latitude and longitude coordinates are in EPSG4326 / WGS84 format, for both input and output. Other coordinate systems are not supported.
What is the difference between O/D Analysis V1 and V2?
V2 is the next major version of the product. It normalizes probe counts, consolidates the time-related conditions into a single universal time condition, reports traffic within a Polygon link region, and adds enhanced metrics to Selected Link results.
V1 and V2 are available in parallel during the rollout. V1 will be deprecated at a later stage, with advance notice. See the V2 Release Notes.