Skip to main content

2025-09-24 release notes

· 6 min read
warning

With the September release, Overture is implementing a data retention policy for publicly-available data releases.

What's changing:

  • Data releases will be publicly available for a maximum of 60 days (approximately two monthly releases)
  • Data files will be automatically removed from public distribution after this period using cloud storage lifecycle policies

What remains available:

  • The most recent two monthly data releases (last 60 days)
  • Versioned changelogs and bridgefiles for all releases
  • GERS registry
  • Release notes from all past releases

Why we're implementing this:

This policy ensures compliance with data protection regulations, including GDPR "right to be forgotten" requirements.

You can find complete details about our release schedule and policies on the releases page in the Overture documentation. Questions? Comments? Please contribute to this thread on our GitHub Discussions forum or reach out to us at info@overturemaps.org.

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/

2025-08-20 release notes

· 3 min read
info

August 26th, 2025

Today, Overture released a patch for the August data. The new release paths are:

Amazon S3

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

Microsoft Azure

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

During our final QA processes, we detected the following issue in the data: all Microsoft ML buildings were incorrectly assigned "is_underground": true. We decided to make the 2025-08-20.0 release public with the bug and follow up with a patch to the data.

Schema docs describing is_underground

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/

2025-07-23 release notes

· 2 min read

Overview

The 2025-07-23.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-07-23.0/

Amazon S3:

s3://overturemaps-us-west-2/release/2025-07-23.0/

Data changelog

Microsoft Azure:

az://overturemapswestus2.blob.core.windows.net/changelog/2025-07-23.0/

Amazon S3:

s3://overturemaps-us-west-2/changelog/2025-07-23.0/

Bridge files

Microsoft Azure:

az://overturemapswestus2.blob.core.windows.net/bridgefiles/2025-07-23.0/

Amazon S3:

s3://overturemaps-us-west-2/bridgefiles/2025-07-23.0/

GERS Registry

Microsoft Azure:

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

Amazon S3:

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

Using the GERS "system"

· 8 min read

In the June release, we introduced new components of GERS, including a new format for GERS IDs and a GERS Registry. In this blog post, we'll walk you through the GERS "system" and show you how to ask probing questions of the Overture datasets.

Understanding GERS IDs

First, let's look at the new ID format for GERS. As of the June 2025 release, all GERS IDs are UUIDs: 128-bit, randomly-generated identifiers (UUID v4) that Overture keeps stable across data releases and updates. These IDs are stored as strings with dashes: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.

For this release only, we're providing Parquet files that map GERS IDs from the May release to the new GERS UUIDs in June release. These files are partitioned by theme and 'type' and can be accessed here: s3://overturemaps-extras-us-west-2/june_to_may_id_mapping/.

2025-06-25 release notes

· 5 min read

Overview

The 2025-06-25.0 release of Overture data and v1.10.0 of the Overture schema are now available. We're pleased to annouce that GERS is now in GA! This means we've launched and updated several components of the "system" to make it production-ready.

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-06-25.0/

Amazon S3:

s3://overturemaps-us-west-2/release/2025-06-25.0/

Data changelog

No changelog for the June release

Bridge files

Microsoft Azure:

az://overturemapswestus2.blob.core.windows.net/bridgefiles/2025-06-25.0/

Amazon S3:

s3://overturemaps-us-west-2/bridgefiles/2025-06-25.0/

GERS Registry

Microsoft Azure:

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

Amazon S3:

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

2025-05-21 release notes

· 7 min read

Overview

The 2025-05-21.0 release of Overture data and v1.9.0 of the Overture schema are now available. This month we added PinMeTo as a new data provider for places, improved the taxonomy of the categories property, added new data sources for addresses, and fixed bugs. Also in this release, we're introducing bridge files and announcing a major change to how we generate GERS IDs starting with the June release.

The datasets are available as GeoParquet files stored on both AWS and Azure. The release paths are:

Microsoft Azure:

wasbs://release@overturemapswestus2.blob.core.windows.net/2025-05-21.0

Amazon S3:

s3://overturemaps-us-west-2/release/2025-05-21.0

2025-04-23 release notes

· 3 min read

Overview

The 2025-04-23.0 release of Overture data and v1.8.0 of the Overture schema are now available. This month we fixed several data issues and made small schema changes, notably to the divisions theme, where we added country and region properties to the division_boundary feature type and populated the local_type property with set values.

The datasets are available as GeoParquet files stored on both AWS and Azure. The release paths are:

Microsoft Azure:

wasbs://release@overturemapswestus2.blob.core.windows.net/2025-04-23.0

Amazon S3:

s3://overturemaps-us-west-2/release/2025-04-23.0

2025-03-19 release notes

· 4 min read
info

March 20, 2025

Today Overture released a patch for the March data. There was an issue with a data pipeline process that caused theme and type columns to show up in some of the Parquet files. This issue likely had minimal, if any, impact on users.

The new release paths are:

Amazon S3

s3://overturemaps-us-west-2/release/2025-03-19.1

Microsoft Azure

wasbs://release@overturemapswestus2.blob.core.windows.net/2025-03-19.1

2025-02-19 release notes

· 3 min read

Overview

The 2025-02-19.0 release of Overture data and v1.6.0 of the Overture schema are now available.

The datasets are available as GeoParquet files stored on both AWS and Azure. The release paths are:

Microsoft Azure:

wasbs://release@overturemapswestus2.blob.core.windows.net/2025-02-19.0

Amazon S3:

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

2025-01-22 release notes

· 3 min read

Overview

The 2025-01-22.0 release of Overture data and v1.5.0 of the Overture schema are now available.

The datasets are available as GeoParquet files stored on both AWS and Azure. The release paths are:

Microsoft Azure:

wasbs://release@overturemapswestus2.blob.core.windows.net/2025-01-22.0

Amazon S3:

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