TomTom SDK for Android
TomTom's Android SDKs help you bring map visualization, location handling, and driver guidance to your Android application with minimal effort.
The Navigation SDK issues visual and audio turn-by-turn instructions at the right moments, and smartly handles events like deviations and traffic jams in the route ahead.
It is also highly customizable, letting customers redefine various aspects of the guidance logic.
See this Guide for how to get started quickly.
All modules:
The quantity module provides a set of classes used for representing physical quantities.
The annotations module provides a set of annotations used inside the SDK.
The common Android module provides a set of common classes and interfaces used across the SDK related to the Android SDK.
The common core module provides a set of common classes and interfaces used across the SDK.
This is a library to handle inaccurate locations provided by a location service. Using the raw location to update the current user’s position can lead to a position indicator that is unaligned with the Route. To solve this inaccuracy problem, Map Matching Engine produces accurate (map-matched) locations.
The Route Replanner module provides an interface for dynamic route planning during navigation, accompanied by models describing the configuration and response. The RouteReplanner interface facilitates the updating of the current route, planning the way back to the route, and incrementally calculating route content, such as instructions and lane guidance.
The Route Replanner Hybrid module provides an implementation of the com.tomtom.sdk.navigation.routereplanner.RouteReplanner for use in hybrid navigation mode. This module:
The Route Replanner offline module provides an implementation of the com.tomtom.sdk.navigation.routereplanner.RouteReplanner for use in offline navigation mode. This module:
The Route Replanner online module provides an implementation of the com.tomtom.sdk.navigation.routereplanner.RouteReplanner for use in online navigation mode. This module:
The Search Common module contains APIs that are frequently used across the Search SDK. Here you find general error handling classes, and classes that have a use-case in at least two separate Search APIs.
The Dynamic Data module includes four APIs that provide real-time information.
The Dynamic Data module refers to information that changes over time. Dynamic Data APIs are designed to complement the Search API by providing real-time or near real-time data updates. The implementation of the Dynamic Data API includes factories that create instances of Dynamic Data and in turn, provide information about EV charging, fuel prices, and parking details.
The Reverse Geocoding module contains the interface and data models for the Reverse Geocoding API. Reverse geocoding is the process of translating geographic coordinates in the form of latitude and longitude values
into a readable address or location description that can be easily understood by humans.
Hybrid implementation of the Reverse Geocoder API.
The Reverse Geocoder Offline module contains the offline implementation of the Reverse Geocoding API.
The Reverse Geocoder online module contains the online implementation of the Reverse Geocoding API.
The Search module encompasses the interface for the Search API, along with the models that encapsulate data relevant to its implementation.
Initializes an online Search API that offers customizable functionalities, such as the Search with Custom Points of Interest API with its create function.
The hybrid implementation of the Search API.
The offline implementation of the Search API.
The online implementation of the Search API.
The Structured Search module serves as a hierarchical address selection tool, designed to assist users in locating an address within structured address data.
Contains the package which holds the offline implementation of the Structured Search API.
The Search UI module offers a reference implementation which can be used to create a search UI within an application.
The Traffic Client module contains the internal implementation for the Traffic module. It also exposes methods to create a traffic client, and pass the (provider-specific) configuration. Once a traffic data provider instance is created and connected to a source of traffic, depending on the implementation, it starts receiving traffic data as offered by the provider, for example, near the current location, along the route, or for the current country/area.
The Traffic Model module provides the traffic event representation. Traffic events represent unusual situations on the road, like traffic congestion, accidents or road works.
The Traffic TPEG module has been deprecated and should no longer be used. Use the "Traffic Client" module instead.
The Traffic module is the entry point of the Traffic component, and should be used by other components to make use of the client-side traffic information. Traffic events from this module are primarily used for offline fallback route calculation and for visualizing them on the map. Traffic events from the this component can be useful to show incidents after a longer period without connectivity, or in a non-connected use case.