Overview​

The 2026-03-18.0 release of Overture data and v1.16.0 of the Overture schema are now available. You can access the datasets, changelog, GERS registry, bridge files, and PMTiles on AWS and Azure at the paths listed below.

What's new?​

The data changelog now includes columns_changed, capturing which properties changed, per feature. Also in this release, we've made several improvements to the pipeline architecture of the transportation theme, including adding several data quality improvements and fresher source data. This architectural change also lays the groundwork for integrating additional road network sources into Overture in the near future.

Deprecations​

The categories property in the places schema is now deprecated and will be removed in the June 2026 release, replaced by the new basic_category and taxonomy properties. All three properties will be available until then to ease the transition for our users. The taxonomy documentation is here.

Getting the data and release artifacts​

You can access this month's data and release artifacts by following the process outlined here. The paths to the data and release artifacts are listed below. We encourage you to ask questions and provide feedback on the Overture Maps Discussion forum on GitHub. You can also file issues and report bugs in our data and schema repositories. If you have a suggestion for a new dataset or if you have data you'd like to contribute to Overture, you can email us at community@overturemaps.org. We’d love to hear from you.

Release data​

Microsoft Azure:

az://overturemapswestus2.blob.core.windows.net/release/2026-03-18.0/

Amazon S3:

s3://overturemaps-us-west-2/release/2026-03-18.0/

Data changelog​

Microsoft Azure:

az://overturemapswestus2.blob.core.windows.net/changelog/2026-03-18.0/

Amazon S3:

s3://overturemaps-us-west-2/changelog/2026-03-18.0/

Bridge files​

Microsoft Azure:

az://overturemapswestus2.blob.core.windows.net/bridgefiles/2026-03-18.0/

Amazon S3:

s3://overturemaps-us-west-2/bridgefiles/2026-03-18.0/

GERS registry​

Microsoft Azure:

az://overturemapswestus2.blob.core.windows.net/registry/

Amazon S3:

s3://overturemaps-us-west-2/registry/

PMTiles​

Amazon S3:

s3://overturemaps-extras-us-west-2/tiles/2026-03-18.0/

When we launched Explorer back in the summer of 2024, we described it as an "x-ray data inspector" and made a deliberate choice to show everything at once — all themes, all feature types, all properties — with minimal cartographic polish. The goal was transparency, not beauty. We wanted you to see the data as it really is.

That was the right call for a launch. But as Explorer has matured and more people have come to rely on it, we've learned that "useful data tool" and "thing you actually enjoy looking at" don't have to be mutually exclusive. The person most responsible for closing that gap is Jonah Adkins, Cartography Lead at Meta. "I didn't have the intention of just redoing the whole thing," Jonah says, "but I was curious what I could get Claude to do." He came up with a plan, and it was, in his words, probably 5 to 6 hours of work total over a few days. By end of day one, Explorer looked like a different site. Dana let him keep going.

("I would have felt better with a heads up," Dana says. "But it's so pretty now.")

Overview​

The 2026-02-18.0 release of Overture data and v1.16.0 of the Overture schema are now available. You can access the datasets, changelog, GERS registry, bridge files, and PMTiles on AWS and Azure at the paths listed below.

What's new?​

In this release, we added a new admin_level property to the divisions schema to represent a division’s position in its country’s hierarchy, e.g. 0, 1, 2. We also updated our places guide with more information about our recent taxonomy work, including mappings across the basic_category, taxonomy, and categories properties. Last but not least, we updated our address data for Norway and made small improvements to our address schema thanks to user feedback from Johannes-Andersen. Keep the comments and discussions coming!

Deprecations​

The categories property in the places schema is now deprecated and will be removed in the June 2026 release, replaced by the new basic_category and taxonomy properties. All three properties will be available until then to ease the transition for our users.

Getting the data and release artifacts​

You can access this month's data and release artifacts by following the process outlined here. The paths to the data and release artifacts are listed below. We encourage you to ask questions and provide feedback on the Overture Maps Discussion forum on GitHub. You can also file issues and report bugs in our data and schema repositories. If you have a suggestion for a new dataset or if you have data you'd like to contribute to Overture, you can email us at community@overturemaps.org. We’d love to hear from you.

Release data​

Microsoft Azure:

az://overturemapswestus2.blob.core.windows.net/release/2026-02-18.0/

Amazon S3:

s3://overturemaps-us-west-2/release/2026-02-18.0/

Data changelog​

Microsoft Azure:

az://overturemapswestus2.blob.core.windows.net/changelog/2026-02-18.0/

Amazon S3:

s3://overturemaps-us-west-2/changelog/2026-02-18.0/

Bridge files​

Microsoft Azure:

az://overturemapswestus2.blob.core.windows.net/bridgefiles/2026-02-18.0/

Amazon S3:

s3://overturemaps-us-west-2/bridgefiles/2026-02-18.0/

GERS registry​

Microsoft Azure:

az://overturemapswestus2.blob.core.windows.net/registry/

Amazon S3:

s3://overturemaps-us-west-2/registry/

PMTiles​

Amazon S3:

s3://overturemaps-extras-us-west-2/tiles/2026-02-18.0/

Over the past few releases, the Overture engineering team has gone from generating a STAC catalog as an ad hoc release artifact to making STAC the backbone of our tooling. Now our Python client, Explorer, internal QA tools, and data pipelines all use Overture STAC to stay in sync with the latest release. We did this to improve our own workflows, but we think it'll make things easier for everyone.

Here's our STAC, from the top. https://stac.overturemaps.org/.

{
  "type": "Catalog",
  "id": "Overture Releases",
  "stac_version": "1.1.0",
  "description": "All Overture Releases",
  "links": [
    {
      "rel": "root",
      "href": "./catalog.json",
      "type": "application/json"
    },
    {
      "rel": "child",
      "href": "./2026-01-21.0/catalog.json",
      "type": "application/json",
      "title": "Latest Overture Release",
      "latest": true
    },
    {
      "rel": "child",
      "href": "./2025-12-17.0/catalog.json",
      "type": "application/json",
      "title": "2025-12-17.0 Overture Release"
    }
  ],
  "latest": "2026-01-21.0",

Overview​

The 2026-01-21.0 release of Overture data and v1.15.0 of the Overture schema are now available. The datasets and release artifacts are available as GeoParquet files stored on both AWS and Azure.

Getting the data and release artifacts​

You can access this month's data and release artifacts by following the process outlined here. The paths to the data and release artifacts are listed below. We encourage you to ask questions and provide feedback on the Overture Maps Discussion forum on GitHub. You can also file issues and report bugs in our data and schema repositories. If you have a suggestion for a new dataset or if you have data you'd like to contribute to Overture, you can email us at info@overturemaps.org. We’d love to hear from you.

Release data​

Microsoft Azure:

az://overturemapswestus2.blob.core.windows.net/release/2026-01-21.0/

Amazon S3:

s3://overturemaps-us-west-2/release/2026-01-21.0/

Data changelog​

Microsoft Azure:

az://overturemapswestus2.blob.core.windows.net/changelog/2026-01-21.0/

Amazon S3:

s3://overturemaps-us-west-2/changelog/2026-01-21.0/

Bridge files​

Microsoft Azure:

az://overturemapswestus2.blob.core.windows.net/bridgefiles/2026-01-21.0/

Amazon S3:

s3://overturemaps-us-west-2/bridgefiles/2026-01-21.0/

GERS registry​

Microsoft Azure:

az://overturemapswestus2.blob.core.windows.net/registry/

Amazon S3:

s3://overturemaps-us-west-2/registry/

Overview​

The 2025-12-17.0 release of Overture data and v1.15.0 of the Overture schema are now available. The datasets and release artifacts are available as GeoParquet files stored on both AWS and Azure.

What's new?​

We added a new taxonomy property to our places schema this month, as part of our ongoing initiative to redesign the places category system. The new property offers a streamlined and logical structure with consolidated primary and alternate names and a hierarchy that makes clear the parent/child relationship between categories.

In October, we introduced the basic_category property. That property corresponds 1:1 to the primary place name in the new taxonomy property. (It also maps to the primary name in the original categories property.) The hierarchical paths in taxonomy support deeper and more logical structures. For example, in the restaurant branch, you can see a clear progression from very broad to very specific category names: restaurant > asian_restaurant > east_asian_restaurant > chinese_restaurant > cantonese_restaurant. This kind of structure makes it easier to aggregate and display POIs in meaningful ways.

The original categories property, with more than 2100 category names, will remain in the schema for the next several months so that users can compare the old system to the new taxonomy.

Examples:

1. Original categories system

properties:
   categories:
      primary: greasy_diner

2. basic_category mapped to primary category in original categories system

properties:
   basic_category: casual_eatery
   categories:
      primary: gas_station_sushi
      alternate:
         - bait_and_tackle

3. New taxonomy

properties:
   basic_category: casual_eatery
   taxonomy: 
      hierarchy: [food_and_drink, restaurant, casual_eatery, gas_station_sushi]
      primary: gas_station_sushi
      alternate:
         - gas_station
         - sushi_restaurant

Getting the data and release artifacts​

You can access this month's data and release artifacts by following the process outlined here. The paths to the data and release artifacts are listed below. We encourage you to ask questions and provide feedback on the Overture Maps Discussion forum on GitHub. You can also file issues and report bugs in our data and schema repositories. If you have a suggestion for a new dataset or if you have data you'd like to contribute to Overture, you can email us at info@overturemaps.org. We’d love to hear from you.

Release data​

Microsoft Azure:

az://overturemapswestus2.blob.core.windows.net/release/2025-12-17.0/

Amazon S3:

s3://overturemaps-us-west-2/release/2025-12-17.0/

Data changelog​

Microsoft Azure:

az://overturemapswestus2.blob.core.windows.net/changelog/2025-12-17.0/

Amazon S3:

s3://overturemaps-us-west-2/changelog/2025-12-17.0/

Bridge files​

Microsoft Azure:

az://overturemapswestus2.blob.core.windows.net/bridgefiles/2025-12-17.0/

Amazon S3:

s3://overturemaps-us-west-2/bridgefiles/2025-12-17.0/

GERS registry​

Microsoft Azure:

az://overturemapswestus2.blob.core.windows.net/registry/

Amazon S3:

s3://overturemaps-us-west-2/registry/

Overview​

The 2025-11-19.0 release of Overture data and v1.14.0 of the Overture schema are now available. The datasets and release artifacts are available as GeoParquet files stored on both AWS and Azure. This is a minor breaking change release.

What's new?​

We added a roller_coaster class to our schema this month. Buckle up because next month we're adding rollercoaster data!

Getting the data and release artifacts​

You can access this month's data and release artifacts by following the process outlined here. The paths to the data and release artifacts are listed below. We encourage you to ask questions and provide feedback on the Overture Maps Discussion forum on GitHub. You can also file issues and report bugs in our data and schema repositories. If you have a suggestion for a new dataset or if you have data you'd like to contribute to Overture, you can email us at info@overturemaps.org. We’d love to hear from you.

Release data​

Microsoft Azure:

az://overturemapswestus2.blob.core.windows.net/release/2025-11-19.0/

Amazon S3:

s3://overturemaps-us-west-2/release/2025-11-19.0/

Data changelog​

Microsoft Azure:

az://overturemapswestus2.blob.core.windows.net/changelog/2025-11-19.0/

Amazon S3:

s3://overturemaps-us-west-2/changelog/2025-11-19.0/

Bridge files​

Microsoft Azure:

az://overturemapswestus2.blob.core.windows.net/bridgefiles/2025-11-19.0/

Amazon S3:

s3://overturemaps-us-west-2/bridgefiles/2025-11-19.0/

GERS registry​

Microsoft Azure:

az://overturemapswestus2.blob.core.windows.net/registry/

Amazon S3:

s3://overturemaps-us-west-2/registry/

Overview​

The 2025-10-22.0 release of Overture data and v1.13.0 of the Overture schema are now available. The datasets and release artifacts are available as GeoParquet files stored on both AWS and Azure. There are several data updates and (minor) breaking schema changes in this release.

What's new?​

New basic_category property in the places schema​

In the places schema this month, we introduced a simple basic_category property that maps to our original categories.primary property. This change is part of a new initiative to reimagine Overture's category taxonomy. The new property is based on a commonly-used cognitive science concept called "basic-level categories," where category names balance being specific enough to be useful while general enough to be broadly applicable.

Major data updates and GERS stability in addresses​

The addresses theme has hit a new high of 455 million records, an increase of nine million records from our September release. More than 325 million of those records retained their GERS ID from the previous release, a major milestone for GERS stability as addresses moves toward General Availability next quarter.

Getting the data and release artifacts​

You can access this month's data and release artifacts by following the process outlined here. We encourage you to ask questions and provide feedback on the Overture Maps Discussion forum on GitHub. You can also file issues and report bugs in our data and schema repositories. If you have a suggestion for a new dataset or if you have data you'd like to contribute to Overture, you can email us at info@overturemaps.org. We’d love to hear from you.

The paths are:

Release data​

Microsoft Azure:

az://overturemapswestus2.blob.core.windows.net/release/2025-10-22.0/

Amazon S3:

s3://overturemaps-us-west-2/release/2025-10-22.0/

Data changelog​

Microsoft Azure:

az://overturemapswestus2.blob.core.windows.net/changelog/2025-10-22.0/

Amazon S3:

s3://overturemaps-us-west-2/changelog/2025-10-22.0/

Bridge files​

Microsoft Azure:

az://overturemapswestus2.blob.core.windows.net/bridgefiles/2025-10-22.0/

Amazon S3:

s3://overturemaps-us-west-2/bridgefiles/2025-10-22.0/

GERS registry​

Microsoft Azure:

az://overturemapswestus2.blob.core.windows.net/registry/

Amazon S3:

s3://overturemaps-us-west-2/registry/

Overview​

The 2025-09-24.0 release of Overture data and v1.12.0 of the Overture schema are now available. The datasets and release artifacts are available as GeoParquet files stored on both AWS and Azure. There are several data updates and (minor) breaking schema changes in this release.

What's new?​

New POIs from Foursquare Open Source Places​

This release adds approximately 6 million new POIs from Foursquare Open Source Places (FSQ OS Places) to grow the coverage of our data. We selected these records as POIs not previously included in Overture. We plan to add more Foursquare data as our validation models mature. You can find the original source for FSQ OS Places here.

Overture places is now a multi-license dataset​

Previously all places data was under a CDLA license, but in this release each place has a license based on its source property:

• Foursquare-sourced data is licensed under Apache 2.0.
• Data from other sources remains licensed under CDLA 2.0. Note that all Foursquare-sourced data is single sourced, meaning we do not blend its attributes with any other sources.

License requirements​

If you use, modify, or redistribute the Foursquare data, you must:

• Provide a copy of the Apache 2.0 license.
• State that you changed the files and include the date of any changes.
• Preserve attribution notices from the source NOTICE file, including at minimum: Copyright 2024 Foursquare Labs, Inc. All rights reserved.

More information on license requirements and data usage is available on Foursquare’s website. General information on Overture licensing is available in the licensing and attribution section of Overture's documentation.

How to filter for CDLA-only data​

To create a purely CDLA-licensed dataset, filter out all records where the source property is “Foursquare”.

New schema properties​

This month we added a new license sub-property within the sources property to more clearly link entities to the licensing information for their source data. This change affects all Overture themes, as sources is a top-level property in the Overture schema.

In the places theme, we added a new operating_status property, with all values set to "open". In future releases, we plan to update this property with data that indicates whether a place is "open", "permanently_closed", or "temporarily_closed".

Signal "patches"​

About a million POIs in our places theme now have a signal "patch" that determines the calculation of the score in the confidence property. POIs enhanced by these patches have "SparkGeo-confidence-conflation" in the sources property.

Getting the data​

You can access this month's data and release artifacts by following the process outlined here. We encourage you to ask questions and provide feedback on the Overture Maps Discussion forum on GitHub. You can also file issues and report bugs in our data and schema repositories. If you have a suggestion for a new dataset or if you have data you'd like to contribute to Overture, you can email us at info@overturemaps.org. We’d love to hear from you.

The paths are:

Release data​

Microsoft Azure:

az://overturemapswestus2.blob.core.windows.net/release/2025-09-24.0/

Amazon S3:

s3://overturemaps-us-west-2/release/2025-09-24.0/

Data changelog​

Microsoft Azure:

az://overturemapswestus2.blob.core.windows.net/changelog/2025-09-24.0/

Amazon S3:

s3://overturemaps-us-west-2/changelog/2025-09-24.0/

Bridge files​

Microsoft Azure:

az://overturemapswestus2.blob.core.windows.net/bridgefiles/2025-09-24.0/

Amazon S3:

s3://overturemaps-us-west-2/bridgefiles/2025-09-24.0/

GERS Registry​

Microsoft Azure:

az://overturemapswestus2.blob.core.windows.net/registry/

Amazon S3:

s3://overturemaps-us-west-2/registry/

s3://overturemaps-us-west-2/release/2025-08-20.1

wasbs://release@overturemapswestus2.blob.core.windows.net/2025-08-20.1

Overview​

The 2025-08-20.0 release of Overture data and v1.11.0 of the Overture schema are now available. The datasets and release artifacts are available as GeoParquet files stored on both AWS and Azure. The paths are:

Release data​

Microsoft Azure:

az://overturemapswestus2.blob.core.windows.net/release/2025-08-20.0/

Amazon S3:

s3://overturemaps-us-west-2/release/2025-08-20.0/

Data changelog​

Microsoft Azure:

az://overturemapswestus2.blob.core.windows.net/changelog/2025-08-20.0/

Amazon S3:

s3://overturemaps-us-west-2/changelog/2025-08-20.0/

Bridge files​

Microsoft Azure:

az://overturemapswestus2.blob.core.windows.net/bridgefiles/2025-08-20.0/

Amazon S3:

s3://overturemaps-us-west-2/bridgefiles/2025-08-20.0/

GERS Registry​

Microsoft Azure:

az://overturemapswestus2.blob.core.windows.net/registry/

Amazon S3:

s3://overturemaps-us-west-2/registry/