Sorry, you need to enable JavaScript to visit this website.

Browse the FAQs to find solutions to common questions.

No. The Routing API always uses the freshest available traffic situation where it is relevant for the planned route.

The Area Analysis (and Traffic Density) network has values for both directions in case the road segment is open in both directions. This is based on the digitized direction as in TomTom's mapping product MultiNet. The network is based on the digitized direction. To view this you can change the lines into arrows, you will then see the direction of each link. To properly visualize it you can use offsets per direction to correctly display it.

The three commonest problems with Traffic Icons calls are:

  1. Using the incorrect projection value for your coordinates. This API defaults to EPSG900913, so if you are making requests with latitude and longitude, you must tell it explicitly.
  2. zoom parameter set to greater than 6. Traffic incidents are not returned for zoom levels 0 - 5. There would be too many incidents per call to do so.
  3. boundingBox is too large. There is an internal limit to the size of bounding box that can return any traffic incidents, for performance reasons. If your projection is right (and where you think it should be) and your zoom level is OK, try using a smaller bounding box to see if you get incidents that way.

If you have checked all three of these issues and are still not getting traffic incidents, post a sample call via Contact Us form and the TomTom Developer Relations team will investigate.

Yes, caching data on the individual client app is an excellent way to improve response time and it is encouraged. You are not allowed, however, to cache the data on a central server and serve that to your clients.

Yes. You can find the related description in the API Documentation.

No. Our traffic tiles are only available via an API call. We do offer the same information as a bulk feed. Please contact the TomTom sales team for further details on this product via Contact Us page.

There are pre-set styles available for the various tile types and the traffic incident tiles and traffic flow tiles.  There is no facility to create or edit the styles provided.

There is no facility to filter traffic incidents by location. You can define a bounding box that covers the specific location (for countries, the HD Traffic Regions call provides one). Note that if the target location is not rectangular in shape, incidents that are outside of it but in the bounding box will be included in the call.

Yes, NavKit is integrated with the TomTom Traffic and Speed Camera services. The NavKit build in the SDK is configured to use a TomTom test environment, so you can develop and test traffic and speed camera functions for your application. To do this, you must request the necessary credentials from TomTom. Please contact your TomTom representative to gain access to these services.

It depends on the application you are developing. If you are implementing typical navigation use cases, then there is a good chance that Reflection will not be required.  You could use the Reference Reflection Context (RRC) instead of Reflection. RRC is a platform specific API wrapper that hides the complexity of Reflection. It is available for Android, Java and C++, and it will soon be available for iOS Objective C. RRC is not a managed API, in the sense that it may change at any time, and (new) NavKit features are not necessarily made available through RRC. Instead, RRC is provided in source code and serves as an example of how Reflection interfaces could be abstracted in a platform-specific way. If your application requires features that are not available through RRC, then you can extend RRC to adjust it to your needs.

Depending on the call, it may use both. Real-time route calculations (where departAt=now, or where the default of now is assumed) will use real-time traffic information where it's available. Longer-term traffic information such as road closures will also be included where it is relevant. In addition, all routes planned use TomTom's IQ Routes database of historic traffic information for the day and time provided.

Almost always, but in some rare occasions when have not enough data to even extrapolate meaningful probabilities there might be no probability/search time for a certain hour. Then also the corresponding <HourlyData>element is not present in the XML

 

Yes, schemas can be found here

Yes. Groups of up to 20 waypoints can be returned in an optimized route order if the computeBestOrder parameter is set to true. See the documentation for further information on this feature.

The Routing API does not offer this facility. Application developers should use the list of coordinates in the points section of the API response to draw the route path on their maps.

Unfortunately, the Online Search service does not return US Census information.

Client applications calling the Map Input Tracker must be registered with the service by contacting TomTom - see Request Access section. On registering, a client ID is issued which needs to be provided along with all the requests. The API requires an OAuth 2.0 authentication.

The activity list provides an ETag header in its response which is described on Get Activity List. If you specify this as a value on an If-None-Match header and the list hasn't changed, you will get a 304, NOT MODIFIED response.

The dynamic feed include a Uuid for Charging Stations and Charging Points. These can be used to merge the feeds together.

 

For Maps Raster API you should use the Copyrights API which returns copyrights information for the whole world or for specific area. For Maps Vector API you should follow information specified here.

To view a report, you need a full set of results. First you unzip the results.zip file to a single folder using a zip program. Using your GIS software, import or drag your shape files and shape attribute files onto separate layers. Your network is now visible as a graphical image. Double click on the attribute files to see the road segment data for each set of times in your dataset.

Importing tracks can be useful if you want a route that covers the same roads, such as a fixed bus route.

You can push the routes to the device programmatically, but to quickly demonstrate the feature, you can simply copy a track to TomTom Bridge by connecting it to your pc via usb and copy the file to the root of the device, where it will be easy to find. Next, you share the file with the navigation application via a file browser, after which it should become available as a pre-set route in ‘My Routes’ in the main menu of the navigation.

In order to be able to do this, you need to have a file browser installed on TomTom Bridge. A good free example is the ‘open intents’ browser, ‘org.openintents.filemanager_2.0.5.apk’

https://play.google.com/store/apps/details?id=org.openintents.filemanager&hl=en

Open the application, and browse to the location of the file (if you just copied to the ‘root’ of the device memory, you can simply scroll down and you should find the file there:

If you long-press on the file you want to import as a route, the options become available to you. Select the ‘arrow’-button  in the top right corner. This will bring up a pop-up screen where you are given the option to share the file with a number of applications (usually ‘Navigation’ or ‘Bluetooth’). The TomTom navigation will be one of them:

After selecting the ‘import into navigation’ option, you should see a dialogue informing you that the file is being imported, after which you should see the following message:

This means the file is now available from the navigation menu under the section ‘my routes’.

Since TomTom Bridge does not support Google services, you can’t directly install applications from the store. Assuming the application you are trying to download and install is not itself relying on Google Services, the application should run normally on Bridge. You just need to use an alternative route to install it.

First, you need to change the security settings of the Bridge to allow it to accept applications from an unknown source. Go to Settings -> Security -> Unknown sources. Make sure the checkbox next to this is selected.

Now, if you insert a micro SD card into the slot, TomTom Bridge will prompt you to install any application (file with extension ‘apk’) that it finds on the card, one at the time.

If you can only access the apk by downloading and installing from Google Play, you need to do that on a device (tablet or phone) that does support Google services, extract the apk from that device, and copy it to a micro SD card. In order to do that, you need to install a so-called ‘apk extractor’ on your phone, of which many can be found on Google Play as well.

https://play.google.com/store/apps/details?id=com.infofledge.apkextractor&hl=en is one example.

After installing the application you want to run on TomTom Bridge on your phone, open the file extractor and look for the appropriate app. Selecting it will cause the apk you need to be created. Follow the instructions in the application to retrieve the file and copy it to the SD card. After inserting the card into Bridge, you will be prompted to install the application.

In all Traffic Stats APIs the timezone given in the request will be used.

How do I update my device to Android 6?
In order to update to Android 6 Marshmallow, please install the latest available software via our Updater as provided on our developer portal (indicated by Android 6).
 
Which map standard is compatible with Android 6?
The TomTom BRIDGE Android 6 version is only compatible with NDS maps. For more information about NDS, please see the dedicated “FAQ NDS” section.
 
Can I upgrade directly to Android 6 from any given software version?
As of our 16.4 release, you can update directly to Android 6. In case you use an older version than 16.4 software, first update to a version between 16.4 – 17.3 and then update to Android 6.
 
Can I downgrade back to Android 4.3?
It is important to note that once the upgrade to Android 6 has been done a device cannot be downgraded to 4.3. For that reason it is essential to test your solution thoroughly before rolling out the update.
 
Which NavApp SDK version can be used on Android 6?
If you're targeting API level 23, then NavApp SDK API level 9 or later has to be used.

The Traffic Model refreshes every two minutes. The Traffic Icons will return the current ID, along with the current traffic information if it's given an old model ID. Traffic layer calls to the Traffic Tile API that use out of date traffic models return a 500 error code.

In addition to the start and end points, the API can be called with a maximum of 50 intermediate points. See the documentation for how to include them in the call.

Note that optimized routing calls are limited to 20 waypoints in addition to the journey start and end.

Every day at midnight we add all newly received GPS data to the database used by Traffic Stats.

The static and dynamic feeds have different update frequencies. The following is reccomended: Update static a few times a day, dynamic once every minute.  

The Routing API uses latitude and longitude (EPSG4326/WGS84) coordinates for both input and output. The request must have a start point and an end point, and may have up to 50 intermediate waypoints between them. All input coordinates must be colon-delimited latitude,longitude pairs (lat1,lon1:lat2,lon2:lat3,lon3...). The first and last coordinates will be used as the start and end points of the route.

Assuming you have ADB via USB working on your computer, and you have both devices properly connected to WiFi, you can set up ADB via WiFi:

  • Run: adb shell ifconfig wlan0
    • This will give you the ip address used for WiFi by Bridge
    • You can also find this on the device via (Settings -> WiFi -> select active connection)
  • Switch ADBD to network mode by running: adb tcpip 5555
    • Device should respond with message: restarting in TCP mode port: 5555
  • Now disconnect the USB connection between the device and the PC
  • Connect to the device via WiFi by running: adb connect <ip-address>:5555
    • <ip-address> is the TomTom Bridge ip value you retrieved earlier
  • run: adb devices
    • you should see the device listed with IP address and port 5555
  • You can now connect to the device via WiFi. Note that a reboot will put adbd back into USB mode.

Not all functionality offered in the Basic Map Tiles API is available from the Maps Tile API yet. For example, there are no overlays related to the traffic data. Maps Tile API is also incompatible with legacy APIs like Viewport or Initialize.

If you are interested only in using the map tiles rendering functionality and you do not need to combine it with other legacy APIs, contact an account manager for guidance on how to transition your usage. Otherwise, continue to use the Map Kit Basic Map Tiles API.

Production key holders will be given advance notice before the Map Kit Basic Map Tiles API is withdrawn from use, and assistance with the migration will be available.

Not all functionality offered in the Map Kit Routing API is available from the Routing API call yet. If the functionality you need is available, contact an account manager for guidance on how to transition your usage. If it is not, continue to use the Map Kit Routing API.

 

Production key holders will be given advance notice before the Map Kit Routing API is withdrawn from use, and assistance with the migration will be available.

Production key holders will be given advance notice before the Map Kit Traffic API is withdrawn from use, and assistance with the migration to Traffic API's will be available.

Your API call does not contain your developer key for TomTom Sports Cloud. 
 This will be in the Api-Key header in any request except for Initiate OAuth2.0 Authorization Flow, where it is a query parameter (simply for the convenience of the user-agent - generally a browser)

The authorization code is a Base64 encoded byte array which has been URL (percent) encoded for management by a browser. When decoding a Base64 String, if the padding is dropped, it doesn't affect the underlying payload.

A problem in our 15.5 software release can cause a device that is being updated to a newer version to fail the update with an error message stating that there is not enough disk space to install the update. The way to fix the problem is to first install the update without the map, and delete the existing map in the process. The update can then be run again, but this time with the map included. Follow these steps to accomplish this:

 

  • Download the image you want to install from the release page on our Developer Portal

  • Unpack the downloaded zipfile to an SD card

  • Locate the file ‘update-locations’ on the SD card: /boot/2/bridge/update-locations

  • Remove the file from the folder, BUT KEEP IT SAFE ON YOUR COMPUTER FOR LATER

  • Put the following file in its place

    • The file has no extension: update-locations

    • The file has the following content

{
    "schema": "2",
    "files": [
        { "file": "package-list.system" }
    ]
}

  • Insert the SD card in TomTom Bridge and press ‘Software update’

  • The device will now update to the build version on the SD card and because the update-locations file does not refer to the map package list anymore the map is removed.

  • After the update, the device will give a ‘no maps found’-error, but will have been updated to the software version that was put on the SD card.

  • Remove the SD card from the TomTom Bridge and put it back in your computer

  • Go back to /boot/2/bridge/ on the SD card and replace the custom update-locations file with the original one from the release zip

  • Put the SD card back in the Bridge and run the updater again

  • This time, the process will take longer due to the large amount of map data that is installed, but afterwards, the device should boot into a state with both the latest map and software running on the device

 

On detection of an authorization error, the client is best served by invalidating any requests that are currently in flight and then ensuring that a single refresh call is made. Otherwise an inevitable race condition occurs where you simply don't know what the valid refresh token is.

For NavKit to correctly load the map, a device-specific map certificate must be installed on the device. You can obtain map certificates from your TomTom representative.

The limit of the amount of via points is 50. Any request with more than 50 via points will be rejected.

In theory, you could check that all of the path points in the response match. That would guarantee that the two routes have exactly the same geometry. However, a quick way to check is to compare the lengthInMeters of two routes. Although it's possible that two different routes to the same place could have exactly the same length, it's not likely.

There are no charges for using it.

Feel free to request parking data for new cities, and we will consider them for addition.

 

The map update cycle takes time. Expect this time to become shorter and shorter as one of TomTom's goal are the real-time maps.

You can help to ensure that all the important changes to the road network are reflected in our systems by submitting community feedback reports at: Map Share™ Reporter.

Road network changes all the time and the map update cycle currently does not allow inclusion of temporary changes.

Functional classification is the process by which roads are grouped into classes according to the character of service they are intended to provide. Cities, towns, businesses, farms, homes, schools, recreation areas and other places generate or attract trips. These trips involve movement of vehicles through a network of roads. It becomes necessary to determine how travel movement can be channeled within a limited road network in a logical and efficient manner. Functional classification defines the nature of this channeling process by defining the role that any particular road or street should play in serving the flow of trips through a road network. The heavy travel movements are directly served by major channels, and the lesser trips are channeled into somewhat indirect paths.  Functional Road Classes are designed to categorize segments based on their functional importance within the Transportation Network. There are nine classifications of the Functional Road Class:

 

FRC VALUE

Short Description

Long Description

0

Motorways; Freeways; Major Roads

All roads that are officially assigned as motorways.

1

Major Roads less important than Motorways

All roads of high importance, but not officially assigned as motorways, that are part of a connection used for international and national traffic and transport.

2

Other Major Roads

All roads used to travel between different neighboring regions of a country.

3

Secondary Roads

All roads used to travel between different parts of the same region.

4

Local Connecting Roads

All roads making all settlements accessible or making parts (north, south, east, west and central) of a settlement accessible.

5

Local Roads of High Importance

All local roads that are the main connections in a settlement. These are the roads where important through traffic is possible e.g.:

  • arterial roads within suburban areas, industrial areas or residential areas;
  • a rural road, which has the sole function of connecting to a national park or important tourist attraction.

6

Local Roads

All roads used to travel within a part of a settlement or roads of minor connecting importance in a rural area.

7

Local Roads of Minor Importance

All roads that only have a destination function, e.g. dead-end roads, roads inside living area, alleys: narrow roads between buildings, in a park or garden.

8

Other Roads

All other roads that are less important for a navigation system:

  • a path: a road that is too small to be driven by a passenger car;
  • bicycle paths or footpaths that are especially designed as such;
  • stairs;
  • pedestrian tunnel;
  • pedestrian bridge;
  • alleys that are too small to be driven by a passenger car.
What is NDS?
NDS stands for “Navigation Data Standard” and is the new automotive-grade mapping standard TomTom and TomTom BRIDGE products will be using moving forward. The NDS standard will allow us to bring the latest technologies with regards to maps and navigation to the BRIDGE products.
 
How do I update my device to the new NDS map format?
In order to update, please install the latest map and software via our Updater as provided on our developer portal. Please beware the new map standard also comes with a new state-of-the art map visualization embedded in our software. Both the latest software and map need to be updated simultaneously.
 
How do I configure which countries/regions I want to install?
Configuring map regions can be managed in the package list. An explanation is available on our developer portal. By installing fewer map regions, the disk space taken by the map can be reduced significantly. In addition, TTS voices can also be removed dependent on language requirements.
 
Who can configure which map regions can be installed?
Only integrators can configure which map regions to install via the package list. There is no end-user setting available for this.
 
I’m currently using the Map Library SDK for my application, do I need to change anything?
Yes, when you’re using our Map Library SDK, please beware you need to rebuild your application against the latest available MapLib SDK (version 13 or later) before updating to NDS. This is due to the fact that we have a new map visualization engine.
 
What are incremental map updates?
 When switching to NDS, weekly incremental map updates will become available to the end-user for specific attributes (like speed limits and direction of traffic flow). Those become available through the Navigation application.
 
How do I set my network policy for incremental map updates?
There’s an API available as part of the NavApp SDK to set those to 1) none, 2) Wi-Fi network only (default setting), or 3) all networks including cellular.
 
What is the approximate size of incremental map updates?
The size of the incremental map update is very much dependent on the region installed and whether the updates are installed every week. As a reference, incremental map updates for the whole European map could be around 10MB a week. Be aware that the first update will be larger since all updates will be installed at once.
 
How long do I receive incremental map updates?
Incremental map updates are only provided for a limited number of cycles to prevent data fragmentation. Afterwards, a new base map needs to be installed before incremental map updates can be received again.
 
Do I still need to perform map updates when enabling incremental map updates?
Yes, incremental map updates only contain a limited set of attributes. The quarterly map updates contain all attributes including updated geometry.
 
Can I upgrade directly to NDS from an any given software release?
As of our 16.4 release, you can update directly to NDS. In case you use an older version than 16.4 software, first update to a version between 16.4 – 17.3 and then update to NDS.
 
Is there still a difference between non-truck and truck maps?
When switching to NDS maps, there’s no difference anymore between truck and non-truck maps. When available in the region, all maps have integrated truck data. If you would like to lock-down the vehicle profile for the end-user, you can use the NavApp SDK to restrict the vehicle profile.
 
Can I downgrade my device from NDS maps back to TTC maps?
Yes, it is possible to downgrade your device back to the 17.3 or 17.2 release. You cannot downgrade to older releases than those. Please beware you need to downgrade both the map and the software.
 
What is the available RAM memory for third party applications using the new NDS configuration?
With this new software, there's approximately 200 MB RAM memory available for third party applications.
 
 

TomTom's Maps Raster includes API that provides pre-rendered map images at 18 zoom levels ranging from one global tile down to 40 square kilometer detailed map images. Each image is 256 x 256 or 512 x 512 pixels and corresponds with a position on an established zoom level grid system used by the WMS-C standard. Currently, three different layers (basic, hybrid and labels) in two styles (main and night) are supported. There is also support for WMS and WMTS operations.

We will configure per minute quotas to ensure our services are not overloaded. In the event that your calls are rejected because you hit the quota per minute limit ("Account Over Queries Per Minute Limit"), your application should back off and retry them. The initial limits of an evaluation license are different from the limits you would expect to see in production, and every application differs. Please contact us at DeveloperRelations@tomtom.com if you become aware of operational problems.

NDS stands for Navigation Data Standard. It is a new industry standard format for map storage, designed for automotive-grade use. For more information see: NDS Association.

An open source project that allows dynamic georeferencing. For more info see here.

Reflection is a TomTom technology for asynchronous, peer-to-peer, remote process communication. Please refer to the Developer's Guide for more information about Reflection.

The format of Request and Response is JSON.

By selecting the "full traversals" option, statistics on this route are calculated on the trips made by vehicles that traverse the full route. Data from vehicles that only traveled a part of the route will be excluded. Please note that this option could lead to a lower number of probe devices used in the results. If a small portion of the route is rarely traveled or a vehicle drives the whole route besides the last section - this will have a negative influence on the results. For longer, more complex and door-to-door routes full traversals is not advised.

All road segments are considered to be directed and a street usually consists of two road segments with opposite 
directions. These two segments are then peers of each other. They are linked by the peer field using the UUID.

 

The traffic situation is changing all the time. In order to deliver traffic information that's consistent enough to use in multiple API calls, TomTom creates periodic "snapshots" of traffic. Calling your interfaces with the same traffic model ID ensures that the data is consistent for a whole screen full of tiles, or for a traffic tile and an incident list. You can obtain the current TrafficModel ID from the Traffic Icons and Viewport API calls.

Our experienced moderation teams are structurally validating all submissions and adding the proposed map changes to our maps day by day.

NavKit provides a rich set of Reflection APIs. The APIs offer wide-ranging functionality within NavKit, including route calculation, guidance instructions, search, map rendering, driving context information, and much more. The SDK contains a document called Interface Summary, that provides a brief overview of all available interfaces, and detailed specifications of each interface.<

Our API is basically covering any map feature as long as a minimum amount of map data (categorized as mandatory) is being added to the report. Few examples of supported report types or map features: 1. Street name 2. Speed limit 3. Direction of traffc 4. Turn restrictions 5. Speed camera 6. Point of interest 7. Road geometry 8. House number etc.

You can enter any geographic information, such as the name or kind of a business, an address, or the name of a point of interest.

NavKit is a portable navigation engine that runs on Android, iOS, Linux, QNX and Windows CE. The SDK comes with NavKit builds for Android, iOS and x86 Linux. If you require support for other platforms, contact your TomTom representative for more information.

Allowing users to 1) submit map feedback through POST request and 2) query the status on their submitted reports through GET request  - see API Documentation. As of April 2016 you'll be able to check the TomTom product version (i.e. MN-R version) in which a submitted report has been taken up.

Devices that are running software version 15.6 or below may have difficulties detecting certain types of (higher speed) SD cards. From 16.1 onward, we have full support for all speed classes. Older builds will accept all default speed (Normal Bus) cards (class 2, 4, 6), but may struggle with other speed types.

If your device is running 15.6 or lower, and the inserted micro SD card is not recognised, we recommend upgrading the device to the latest software version (or at least 16.1), using a default speed class 2, 4 or 6 card. 

If you are calling multiple APIs and want all of the information coming back from them to be consistent, you should use an explicit TrafficModelID. Otherwise, you may end up with a "patchwork" effect with traffic tiles, or situations where the traffic incident descriptions do not match the visual data returned.

If the token was previously functional, then it is likely to have expired.

We are in early stages of development and will review token lifetimes regularly.

The MapKit APIs & SDKs are being deprecated in favor of new APIs & SDKs. Although existing licensed users of the MapKit can continue to do so in the short term, they will have to migrate to new TomTom services in the near future. This process will be supported with migration guides and assistance from TomTom. No new licenses will be issued for the MapKit APIs.

Note that because there is no new replacement for the Traffic APIs (Traffic Icons and Segment Flow Data), those will remain available on the Developer Portal under the name Traffic API.

To keep the API as simple as possible we just return all activities, because the activity list itself is generally smaller (for almost all users) than a single 2 hour activity. At some point in the future we will inevitably add filtering to the activity list, and this will be backward compatible (e.g. just adding query parameters) though this will inevitably compromise ETAG based caching.

The Routing API calculates the fastest route through the given waypoints, taking traffic into account if the traffic parameter is true. For example, suppose there are two routes from point A to point B. One of them is a motorway with a speed limit of 100kph, but traffic has slowed cars down to 80 kph. The other route is an empty surface street with a speed limit of 30kph. In those circumstances the software will choose the motorway route, because even though it goes through traffic, it is still the quickest way from A to B.

We provide TCX and GPX links for outdoor activities, but no GPX for indoor activities. This is because GPX documents are structured around points with longitude and latitude, i.e. GPS positions and so indoor activities can't be described this way.

When the zoom level is distant, the API returns traffic incidents grouped into clusters, to allow for display in very small map space. The way that nearby incidents are grouped into clusters is determined by the zoom level.

At the moment we accumulate data for all weekdays and for the weekend. In near future this might change and the probabilities for each individual weekday will be different.