Introduction
Overview
Open. Flexible. Built for business.
TomTom Orbis Maps is our mapping platform — a standardized, continuously updated map database that combines open data and TomTom proprietary data to deliver the world's freshest, richest, and most accurate maps across 235+ countries and territories.
TomTom Orbis Maps brings together data from:
- Overture Maps Foundation - co-founded by Amazon, Meta, Microsoft, and TomTom under the Linux Foundation. It provides an interoperable open base map with a common data schema.
- OpenStreetMap (OSM) - selectively used where coverage and quality meet TomTom's standards.
- TomTom proprietary data - including address points, speed limits, traffic restrictions, speed profiles, and traffic signs.
- Partner and sensor-derived observations - real-world signals that help keep the map fresh and accurate.
- Your own data (BYOD) - customer-specific layers that can be integrated directly into the platform.
All data is validated through TomTom's AI-native platform, with 5B+ data points continuously enriching and improving the map.
Why TomTom Orbis Maps?
-
Built on an open, interoperable standard. TomTom Orbis Maps is built on the Overture Maps Foundation schema — a common open standard co-developed with the biggest names in tech. Your integrations are built on a foundation designed for long-term interoperability and compatible with popular open-source tools and workflows.
-
Higher quality than open data alone. Open data from Overture or OSM is not enough for commercial-grade products. TomTom validates open data through AI-native quality control, enriches it with proprietary content, and continuously improves it using customer feedback and map expert reviews. The result is a map that is richer, fresher, and more accurate than any single open data source.
-
Flexible and ownable. Make our map yours. Layer in what you need — traffic, routing attributes, ADAS content, POIs, or your own datasets — and customize the experience to match your product, including 2D or 3D visualization, custom color schemes, dark mode, and more.
-
The forward path for TomTom customers. TomTom Orbis Maps supersedes TomTom's previous map products. It offers broader coverage, higher quality, and faster iteration. If you're currently using an earlier TomTom map offering, this is where to go next.
Before You Integrate
TomTom Orbis Maps APIs are distinct from TomTom Maps APIs. Plan for the following before you start:
-
New API endpoints. Orbis-based APIs use dedicated endpoints that are not interchangeable with TomTom Maps API endpoints. Your application needs to point to the new API surface.
-
New data schema. TomTom Orbis Maps uses the Overture-aligned data model, which differs from OSM tags and from TomTom's previous map schema. Budget time for a data model mapping exercise. OSM-to-Orbis documentation is available in the TomTom Orbis Maps specifications.
-
IP and licensing. Orbis data combines ODbL-licensed open data from Overture and OSM with TomTom proprietary data. Each attribute carries license information, and a per-feature, per-country license summary file is available. Verify ODbL compliance for your use case before shipping.
-
Access formats. TomTom Orbis Maps is available as uncompiled map content in PBF format, APIs, SDKs, and dedicated software applications across web, mobile, and embedded platforms.
Avoid Mixing TomTom Maps and TomTom Orbis Maps data
We strongly recommend against combining data from TomTom Maps APIs and TomTom Orbis Maps APIs in the same application.
The two platforms are built on different underlying databases and data models. Mixing them — for example, using a TomTom Maps routing API alongside an TomTom Orbis Maps Traffic API — can produce inconsistent results: geometries may not align, feature identifiers are not shared between the two platforms, and the same real-world location may be represented differently in each.
Choose one platform and use it consistently. If you are starting a new integration, use TomTom Orbis Maps APIs end-to-end.
Get Started
Explore the TomTom Orbis Maps APIs and SDK integrations in this documentation, or try live demo to experience the platform before diving into integration. You can also request a map sample in PBF or FGDB format.