FAQs
How do I get access to Junction Analytics?
Request access to Junction Analytics via your local partner or TomTom account manager.
To use the 30-day free trial — whether through the MOVE Portal or the API — create a MOVE account at move.tomtom.com. Once you are logged in, your API key can be found in the menu.
How do I use my API key?
In every request, provide your API key as the value of the key query parameter, for example key={Your_API_Key}.
See Authentication for details.
Can I use Junction Analytics without writing code?
Yes. Junction Analytics is available both as a set of RESTful APIs and as a companion web application in the MOVE Portal, where you can create junctions, view configured intersections on a map, and validate road segments without coding.
See the MOVE Portal documentation for the web application.
Why is my junction not returning live data yet?
A junction definition has to be processed before live data is served. The junction status tells you where it is in that process:
| Status | Meaning |
|---|---|
PREVIEW | Junction is processing, live data is not served. |
ACTIVE | Junction is processed, live data is served. |
PENDING_UPDATE | Junction is processing after an update, live data is not served. |
ERROR | The junction could not be processed. The statusDetail field explains why. |
Monitor the status with the Junction definition details endpoint.
How often are the results refreshed?
In the MOVE Portal, the Auto Refresh Data option refreshes the results every minute. You can disable it if you want to keep a set of results on screen for longer.
Through the API, pull live data for processed junction definitions periodically, either per junction with Junction live data details or in bulk with Junction live data list.
Which statistics does a junction return?
Live metrics are returned for each junction approach, and include travel time, delay, stops, queue length, and turn ratios for each exit. On demand, the response can also contain the junction model: the junction boundary, its approaches, and its exits.
What is the difference between Junction Analytics and Enhanced Junction Analytics?
Enhanced Junction Analytics is an additional module that analyzes individual traces in the context of a junction. It extends each approach with up to three Arrival Points that report speed and time metrics, and it adds control statistics such as control delay and approach delay.
Enhanced Junction Analytics works only if you have been granted access to the enhanced features, and only newly created or updated junctions provide enhanced data.
See the Enhanced Junction Analytics service page.
Where are the arrival points located?
By default, the three arrival points are placed at the stop bar (0 feet), 40 feet from the junction, and 350 feet from the junction. You can supply your own arrival points in the request body of the manual junction creation or update endpoint.
How do I get historical junction data?
Use the archive endpoints. Junction archive availability tells you which period is available for a junction, and Junction archive returns the archived data.
For larger exports, use Generate Historical Data Archive and track the job with the task status endpoints, or set up a recurring S3 Data Export.
Which coordinate system is used?
Latitude and longitude coordinates are in EPSG4326 / WGS84 format, for both input and output. This is the only supported coordinate system.
Is my junction location supported?
Coverage depends on the available traffic data at the intersection. The quickest way to check a specific location is to run a junction definition preview, which returns the junction model that would be created for it.
For coverage in a specific market, contact us.