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?
All version 2 analyses are calculated on TomTom Orbis Maps.
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.
Results are released once the analysis reaches the ACCEPTED status. Until then, the analysis preview response carries no result URLs.
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, the convex hull area, and the date and time ranges — see Flow Matrix product usage limits.
For a Selected Link analysis, the link can be a GeoJSON LineString or a GeoJSON Polygon: the longest supported LineString is 2 km (1.24 miles) and the largest supported Polygon is 3 km², unless a higher area limit is granted to your contract — see Selected Link product usage limits.
The values on those pages apply to a trial or standard account. Your own limits may differ — the Report limits shown while you create an analysis are the ones that apply to your account.
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.
How do I create a version 2 analysis?
Send “analysisVersion”: 2 in the body of a Flow Matrix or Selected Link creation request. A request that omits the field creates a version 1 analysis.
What does a version 2 Selected Link analysis add?
Every node of the result carries its share of the traffic of the selected link, together with the half width of a 95% confidence interval, and reports the name of its last road segment. For a Polygon link, a third result direction describes the trips inside the region. Average travel time, traveled distance, and estimated traffic volume can be requested as enhanced metrics.
See Analysis version 2.
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.