Deprecated maps and datasets

In your MapTiler account, older resources now have a deprecated label. A resource can be either a map (style) or a dataset (tileset).

Deprecation means that the map or dataset has become legacy and we have replaced it with a newer version. For example, the 3rd generation of our main dataset MapTiler Planet has been deprecated and replaced with 4th generation.

Note that some deprecated maps and datasets may no longer be listed in your MapTiler account at all, as their use in new projects is not recommended.

How it affects your maps

We don’t remove deprecated maps and datasets. We just stop active development to focus on the latest versions, so there won’t be any further maintenance of the deprecated resources except for critical bug fixes.

• API endpoints: Existing API endpoints, TileJSON URLs, style.json URLs, and XYZ raster tile requests continue to serve data.
• Data updates: Deprecated vector and raster tilesets don’t receive updates. New roads, changed points of interest (POIs), or modified political boundaries won’t show up.
  • Exception: The MapTiler Planet v3 tileset will continue to receive data updates for a limited transition period of a few months.
• Map updates: Deprecated map styles don’t receive design updates, typography tweaks, or new map layer additions.
• Maintenance: We don’t patch technical issues, rendering artifacts, or data anomalies discovered in deprecated versions.
  • Exception: We’ll fix critical bugs that could cause your projects to stop working.

Use latest resources

For all new projects, we strongly recommend using the latest datasets and map styles, labelled new in your MapTiler account. These resources will be now getting the maintenance, improvements, and features unavailable in previous versions. Main benefits of using new resources include:

• Continuous global data updates
• Better performance thanks to optimized data schemas
• Better customization experience in Map Designer
• New rendering features: 3D buildings, dynamic terrain, localization, etc.

Migrate existing projects

The steps to replace deprecated resources in your existing projects depend on the project implementation:

Catalog maps

If you’re using one of our older catalog maps without any design customization, upgrade it to a new map style by updating the map_id or the style.json URL in your map initialization code.

Example

This iFrame code uses the older Outdoor v2 map:

<iframe width="500" height="300" src="https://api.maptiler.com/maps/outdoor-v2/?key=YOUR_MAPTILER_API_KEY#2.5/49.34892/15.26930/"></iframe>

To update the code to use the new Outdoor v4 map instead, replace the map style ID outdoor-v2 with outdoor-v4.

Custom maps

Upgrading a deprecated custom map is more complex because different product generations use different internal data structures, so older maps are incompatible with newer datasets and vice versa. For example, the Streets v2 map uses MapTiler Planet v3 as its main data source, and it cannot be switched to MapTiler Planet v4.

This means that if you have a custom map based off of an older catalog map like Streets v2, you can’t simply replace the underlying data source to get the latest data updates. In this case, you have two options:

• Re-create your custom map design using the new map style, or
• Keep the old design which continues to work, but without data updates.

Tilesets

If your map project is consuming raw vector tiles, please review the schema documentation for the new generation, as schema modifications may have introduced breaking changes to data parsing.