2025-05-21.0

Overview

The 2025-05-21.0 release of Overture data and v1.9.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-05-21.0

Amazon S3:

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

You can access the datasets 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 data@overturemaps.org. We’d love to hear from you.

What's new? Bridge files!

Overture is now releasing bridge files alongside our monthly data releases. Bridge files map GERS IDs to source data IDs, providing a mechanism to trace the origin of data in the Overture corpus, including data that doesn't appear in our published releases.

Overture's approach to conflation is to handle the complexity internally and deliver fully conflated, interoperable data products. We publish this conflated data every month but we haven't previously made our internal GERS ID matching available. Bridge files change this by sharing our conflation results, making it easier for you to understand data provenance and giving you an opportunity to be more provider-agnostic.

You can find the latest bridge files here, partitioned by dataset, theme, and type:

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

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

GERS IDs will become UUIDs in June

In next month's release (late June), Overture is standardizing the id property across all themes by adopting UUIDs, stored as strings.

Currently the structure of our IDs varies slightly across datasets, with some themes embedding metadata (e.g. H3) in the id property. The new UUIDs will be randomly-generated identifiers with no encoded information. Moving to UUIDs enables consistent ID generation and registration across our data pipelines, which is necessary for the successful implementation of GERS.

This is a one-time breaking change for our ID system. We plan to support our users by providing a file that maps the old IDs to the new UUIDs.

Theme-specific updates

info

The base, buildings, divisions, places, and transportation themes are in GA. The addresses theme is in alpha.

Addresses

• added new data sources for Waupaca County, WI and Sierra County, CA
• added a new data source for Italy that will replace the existing regional/municipal datasets

	added	data_changed	removed	unchanged
address	446,766,672	0	429,683,781	0

Base

• improved coverage of state park, forest, and taxiline class values
• improved processing of bathymetry geometries

	added	data_changed	removed	unchanged
bathymetry	0	60,057	0	3
infrastructure	122,924,152	0	121,608,805	0
land	65,191,767	0	64,726,006	0
land_cover	0	0	0	123,302,114
land_use	49,625,405	0	49,366,015	0
water	57,802,549	0	56,753,269	0

Buildings

• fixed an issue with duplicate IDs on IGN Spain buildings
• added names property to the building_part type

	added	data_changed	removed	unchanged
building	16,659,007	10,851,887	8,205,143	2,594,721,648
building_part	86,713	3,184,622	8,949	45,816

Divisions

• generated the point geometries for the division type from OpenStreetMap nodes instead of using centroids calculated from of division_area polygons
• fixed a bug in capital_of_divisions ID assignments

	added	data_changed	removed	unchanged
division	40,068	263,440	16,238	4,090,114
division_area	19,582	57,077	11,716	947,086
division_boundary	475	2,895	44	84,330

Places

• added PinMeTo as a new provider for places data
• improved the taxonomy of the categories property by fixing inconsistencies in the hierarchy
• made improvements to the data matching tools

	added	data_changed	removed	unchanged
place	6,490,353	18,049,066	10,853,004	37,142,400

Transportation

• released the same data that was in the 2025-04-23.0 release; stats reflect changes from 2025-03-19.1 to 2025-04-23.0

	added	data_changed	removed	unchanged
segment	0	1,592,251	1	319,936,718
connector	0	0	0	375,247,444

Data changelog

The data changelog captures any changes in Overture features between this release and the previous release. The changelog is available as Parquet files — partitioned by theme, type, and change type — at the following locations on Azure and AWS:

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

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

You can find more information about the data changelog in our documentation.

Schema changelog

The changelog for Overture schema v1.9.0 is here.

Attribution

You'll find information about attribution and licensing here.