Changelog MapTrip 5.10 and SDK 9.10
With MapTrip 5.10 and SDK 9.10, we have further enhanced our navigation technology in several areas. New mapping technologies, such as the Orbis format, combine up-to-date OSM data with TomTom’s data quality and are now available for production use for the first time. At the same time, dynamic map downloading enables leaner applications that reload maps as needed while still remaining capable of operating offline.
The map view is now more flexible thanks to the ability to freely position the vehicle icon; 3D buildings make it easier to find your way around the city; and we’ve adjusted the zoom behavior to provide a better overview.
We have put a great deal of detailed work into route calculation. Developers can precisely control the influence of statistical traffic data and choose between different routing strategies—so-called “flavors.” A new “Emergency Profile” has also been added for the emergency services sector, guiding responders to the scene even faster and more effectively.
Road Maps
Note regarding map compatibility and storage requirements
MapTrip 5.10 / SDK 9.10 requires map data from versions TOMTOM2025Q4, OSM2026Q1, HERE2026Q1, ORBIS2026Q1, or newer.
Because building outlines are now included, the data volume has increased significantly. Please note that this affects the amount of data transferred during online operation.
Europe with Buildings
17.7 GB (19,030,696,884 bytes)
Of which buildings: 7.54 GB (8,098,568,065 bytes) 42 percent
DACH with Buildings
2.31 GB (2,487,387,072 bytes)
Of which buildings: 987 MB (1,035,472,665 bytes) 41 percent
Germany with buildings
1.85 GB (1,996,138,408 bytes)
Of which buildings: 836 MB (877,054,416 bytes) 43 percent
Orbis — The new TomTom data format
Orbis is TomTom’s new map format. It combines the up-to-date information and level of detail found in OSM maps with TomTom’s superior quality. With MapTrip 5.10 and SDK 9.10, the Orbis map solution is now available to all customers—offering the “best of both worlds” for navigation solutions.
Automatic download
With SDK 9.10, it is now possible to develop applications that can be shipped with online map data and put into operation. As a result, the applications are very lightweight (approx. 160 MB package size) and can be easily installed on the target devices via a wireless interface. They initially run in online mode and can download the licensed map data as needed. This then enables offline operation.
More information for developers
Map display
Map viewer — 3D polygons
With MapTrip 5.10 / SDK 9.10, buildings can be displayed in 3D on the map. The building data helps users better orient themselves on-site; it is already included in all standard map data sets (TomTom, Orbis, HERE, OSM) and is automatically extruded into 3D.
Note: The system extrudes 2D floor plans upward—true 3D models with detailed roof shapes are not yet supported. For devices with lower performance, the 3D display should be limited to low zoom levels, as the calculation is computationally intensive.
For product managers, this means: a more modern map interface, better spatial orientation for end users, and the ability to integrate industry-specific 3D objects without any development effort.
More information for developers
Improved automatic zoom height
With SDK 9.10, navigation solutions can configure the automatic zoom level of the map display with significantly greater flexibility—a direct response to real-world customer feedback. Previously, the fixed zoom logic caused the map to zoom in too far in certain usage scenarios. Drivers reported that they lacked a clear spatial overview.
The new configuration options allow the zoom level to be precisely tailored to different usage scenarios. Developers can now control in detail how far out the map remains zoomed at various speeds. This means better orientation for drivers and a more professional user experience.
More information for developers
Position the vehicle icon as desired.
With SDK 9.10, applications can, for the first time, freely position the vehicle icon on the screen. This feature opens up new possibilities for modern user interface designs.
Previously, the vehicle icon was fixed in the center of the screen and could only be moved vertically. Now, its position can be flexibly adjusted in both directions. This is controlled using percentage values or directly via an SDK function at runtime. This enables entirely new screen layouts: In landscape mode, for example, the vehicle can be displayed on the right half of the screen, while the left side remains free for controls, lists, or other information.
This becomes particularly interesting with dynamic interfaces: When UI elements slide in or out, the vehicle icon can animate to make way and always remains centered within the visible map area. This creates smoother transitions and a more professional user experience.
For product managers, this means more modern app designs with better use of space, more intuitive operation, and greater design freedom.
More information for developers
Route calculation
Route Flavors
With the “Route Flavors” concept, we are introducing route calculation with different optimization goals.
- Fastest: The fastest route. Takes traffic conditions into account and avoids traffic jams.
- Direct: The direct route from A to B without detours to avoid traffic.
- Less Toll: The affordable route with reduced toll costs.
The routes can be retrieved in the SDK and the Server API using the “Fastest,” “Direct,” and “Less_Toll” flavors.
Fastest
This is the fastest route. It takes current traffic conditions into account and avoids traffic jams.
Direct
The Classic Route follows the standard route. It corresponds to the route you would describe to someone unfamiliar with the area: “To get from Cologne to Frankfurt, it’s best to take the A3.” The Classic Route does not avoid traffic jams; it simply takes traffic conditions into account when calculating the arrival time!
Less Toll
Selecting the “Less_Toll” setting chooses a route that incurs lower toll costs. This route is generally longer in terms of distance and travel time.
More information for developers
Configuration of the use of statistical traffic information
Statistical traffic information describes typical traffic conditions based on the day of the week and time of day. It enables the average driver to take a route that avoids chronic traffic congestion during the morning and evening rush hours. However, in many applications in logistics or safety-critical areas, there is a need to control the route calculation behavior more precisely.
That is why, with SDK 9.10, developers can now, for the first time, flexibly control how statistical traffic data is incorporated into route calculation.
Previously, statistical traffic data could only be turned on or off. Now, it is possible to precisely specify which type of speed information is used. This enables entirely new application scenarios: Customers who need reproducible routes (e.g., for route planning or in the emergency services sector) can ensure that the route always remains identical, regardless of the time of day. No more unexpected route changes between morning planning and evening execution.
This flexibility is reflected in four modes:
- “SpeedProfile” uses time-of-day-dependent speeds for each road segment. Depending on the time of day, different routes and travel times can be obtained. This is the default setting for standard navigation, for example, in logistics.
- “Average” uses constant average speeds for each road segment. It does not differentiate between day and time of day, but rather uses an average value for each road.
- The “FreeFlow” mode uses road-specific speeds and simulates optimal traffic conditions, such as those encountered in the middle of the night.
- The “None” mode uses no statistical traffic information whatsoever, but rather general speed assumptions for each road type. In this mode, local conditions (e.g., chronically congested roads) are not taken into account.
For product managers, this means: Tailored solutions for various industries—from reliable route planning to optimized emergency vehicle navigation—without any technical compromises.
More information for developers
Route Restrictions and Obstacles
SDK 9.10 provides developers with detailed information regarding rule violations along the route. Examples include entering pedestrian zones or roads restricted to local access, as well as truck-specific restrictions (height, width, weight, axle load, hazardous materials, tunnel categories).
Entry restrictions are ignored by the routing engine if no alternative route to the destination exists. This allows developers to issue precise warnings (e.g., “Caution: pedestrian zone in 100 meters”) or visually mark critical locations on the map.
More information for developers
Detour
Detour is a feature for editing map data that can be unlocked as an add-on to any MapTrip license. It allows you to edit maps—for example, to block or unblock roads—in order to customize route calculations to your individual needs.
Detour Basic — A new, simple locking function
Following numerous suggestions from the 112 sector, we have introduced a streamlined alternative to the powerful Detour feature, which can also be of great use in logistics.
MapTrip 5.10 / SDK 9.10 introduces a new, simple method for blocking roads or entire areas. With this new feature, just a few coordinates are needed to block a road or an area. We are thus incorporating a feature that many control centers already support.
Thanks to the streamlined implementation, even extremely narrowband data transmission (e.g., Tetra radio in the public safety sector) is sufficient to distribute road closures specifically to individual vehicles or groups of vehicles. The function operates locally on the device, meaning each vehicle manages its road closures locally and takes them into account in both local and server-based route calculations.
Entire areas can be restricted by defining a polygon. Restrictions can also be set for a limited time, such as for temporary traffic disruptions like public festivals. Transferring the restrictions to MapTrip is straightforward via the MTI interface (MapTrip Interface).
Detour Basic is limited to blocking roads and areas. In contrast, Detour offers the ability to make significantly more extensive adjustments, such as enabling, adding, and prioritizing roads, as well as editing truck restrictions.
More information for developers
112
Emergency Profile — Optimized emergency light routes
MapTrip 5.10 / SDK 9.10 fundamentally improves route calculation for emergency vehicles—with two key advantages that directly impact emergency response operations.
More direct, even faster routes: In emergency mode, the system specifically calculates routes that enable the shortest arrival time under emergency conditions. Unlike normal routing, which typically favors well-maintained roads, the Emergency Profile consistently uses the fastest possible route optimized for the emergency situation.
Realistic travel time calculation in traffic: Emergency vehicles with emergency lights navigate through congested traffic completely differently than regular vehicles. The SDK now allows for configurable settings that account for the fact that ambulances, fire trucks, and police vehicles can travel through traffic jams at higher speeds.
As a result, emergency routes do not bypass traffic jams with large detours but instead account for the higher speed of the emergency vehicle compared to normal traffic. This makes the arrival time estimate significantly more accurate and reflects real-world emergency conditions.
Both improvements work fully automatically without any programming effort—as soon as the emergency lights are activated, the SDK switches over on its own.
More information for developers
Emergency POIs
MapTrip 5.10 and SDK 9.10 now include detailed emergency POI data such as defibrillators, emergency response points, and water access points. The data is integrated by default and ready for immediate use—without the need for additional data acquisition or licensing fees.
This allows navigation solutions to be specifically tailored to emergency responders. Fire department apps automatically display the nearest water source, while emergency medical services solutions provide precise navigation to rescue points in the forest.
Updated SDK resources
With SDK 9.10, the included configuration files have been fundamentally revised and expanded. The mapservices.xml file now includes 3D building models, more detailed coastlines, and improved tunnel visualizations, giving navigation apps a more modern and spatially immersive look.
The Pois.xml file has been expanded to include emergency POIs, such as defibrillators and other emergency infrastructure. This enables applications in the healthcare and emergency services sectors to integrate life-saving information directly into navigation.
Particularly relevant for fleet management: The new TollCosts.xml file contains current toll rates (initially for the German TollCollect system) and automatically calculates vehicle-specific toll costs based on weight, emissions class, and route. Customers can now view precise cost comparisons between routes and recommend the most economical route to their drivers.
The StreetTypeSpeedProfiles.xml file has been moved from the map data to the SDK, enabling more flexible updates and customer-specific speed profiles.
Important for customers with customized configurations: Updates must be applied carefully to preserve custom changes while still benefiting from new features.