The 2026-04-15.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.

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-04-15.0/

Amazon S3:

s3://overturemaps-us-west-2/release/2026-04-15.0/

Data changelog​

Microsoft Azure:

az://overturemapswestus2.blob.core.windows.net/changelog/2026-04-15.0/

Amazon S3:

s3://overturemaps-us-west-2/changelog/2026-04-15.0/

Bridge files​

Microsoft Azure:

az://overturemapswestus2.blob.core.windows.net/bridgefiles/2026-04-15.0/

Amazon S3:

s3://overturemaps-us-west-2/bridgefiles/2026-04-15.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-04-15.0/

Theme-specific updates​

Addresses​

• refreshed the NAD data source: now using v22
• de-duplicated data from the Državna geodetska uprava source, used for Croatian addresses

Base​

• made minor, incremental updates to the data

Buildings​

• removed ~98M Google and Zenodo sourced building features with small areas

Divisions​

• no changes

Places​

• confidence score updates: The March release contained unexpected changes to our confidence score normalization in Meta-sourced place data. This April release rolls back those changes. We have also increased the number of signals to our places data; ~10M places now receive updated confidence scores based on third-party signal data.

Transportation​

• OSM Cut-Off Date: 2026-03-31

Change Summary​

Count Changes​

Length Changes​

Schema changelog​

The changelog for Overture schema v1.16.0 is here.

Attribution​

You'll find information about attribution and licensing here.

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/

Theme-specific updates​

Addresses​

• improved city, street, or number column in Slovakia, Belgium, Austria, and in Quebec, CA
• added units to Portugal, Iceland, and Baden-Württemberg DE
• added data in Lower Saxony and Mecklenburg-Vorpommern, DE

Base​

• made minor, incremental updates to the data

Buildings​

• made minor, incremental updates to the data

Divisions​

• made minor, incremental changes to the data

Places​

• made improvements to the taxonomy and basic_category fields
• adjusted methods of calculating feature-level confidence scores

Transportation​

• fixed source linear references: the sources array for segment features previously dropped positional information (between) on the last source entry; now the sources array has correct linear references, and adjacent ranges with identical values are merged into cleaner, more compact output

• cleaned up routes: routes with no identifying properties and duplicate entries covering adjacent sub-ranges have been removed

• added more accurate timestamps: update_time in the sources array now reflects the most recent timestamp across both the feature and its components, a change that accounts for ~90M source-level differences (~28% of segments) but does not affect source identity or count.

Schema changelog​

The changelog for Overture schema v1.16.0 is here.

Attribution​

You'll find information about attribution and licensing here.

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.")

Two modes: Explore and Inspect​

The biggest change to Explorer is the introduction of two distinct modes, accessible from the navigation bar at the top of the page.

Explore mode is the new default. The data is styled, readable, and cartographically opinionated. Places have icons. Highways look different from residential streets. Buildings have fill colors. If you want to quickly orient yourself in an area, understand what Overture covers, or demo the data to someone who's never seen it, Explore mode is where you want to be. The layers panel on the left toggles Overture's six themes on and off. Click any feature to see its properties.

Inspect mode is the spiritual successor to the original Explorer experience: show as much of the data as possible, as directly as possible. The layers panel reorganizes to mirror the Overture schema itself — base breaks down into land, water, bathymetry, land cover, and land use; transportation shows segments and connectors; divisions shows areas, boundaries, and labels. Every feature type is symbolized uniformly as simple points, lines, and polygons. Little to no filtering, very few cartographic opinions.

Think of it this way: Explore mode asks what does this place look like? Inspect mode asks what's actually in the data? Both questions are worth asking.

Globe​

When you open Explorer, you're now looking at a globe. "The globe thing is kind of stupid," Jonah admits, "but it's too easy not to do." Dana disagrees on the stupid part. The previous default dropped you in Washington, DC. The globe communicates something truer: Overture is a global dataset. Go find your place in it.

Search​

Explorer now has a search bar, a feature people have been asking for in every uesr testing session since 2024. Use the Search Type dropdown to switch between three modes:

Locality and Country searches are powered by a geocoding service built entirely from Overture's own divisions data. It covers 450,000+ cities, neighborhoods, and administrative areas worldwide, with full-text search and autocomplete. It's a nice demonstration of what you can build on Overture data.

GERS search is the one that excites us most. Paste any GERS ID into the search bar and Explorer will fly directly to that feature on the map. This is powered by the GERS manifest in the Overture STAC catalog, which maps every GERS ID to a bounding box. If you've been writing queries and want to visually verify a feature — or if someone hands you a GERS ID and you want to know what it is — this is now a one-step operation.

Multilingual names​

Toggle between languages using the language selector to see place names rendered in dozens of languages. This comes directly from the names field in Overture data, which carries common names, alternate names, and translations from our source datasets. The richness packed into that property is easy to miss when you're writing queries; Explorer makes it visible.

Under the hood​

The styling refresh is powered by a token-based design system Jonah built for Explorer: primitives (color palette, fonts), semantics (feature-level color assignments), and components (stylesheet properties referencing the semantic values). The practical upshot is that adding a new map style — dark mode, for example — means changing one file. Explorer is also built on Next.js, which sets up a better foundation for adding features and making it easier for contributors to build on top of.

Explorer is pinned to a specific Overture release. Updates go through a validation process — a script called, yes, dont-dream-its-overture — that audits stylesheets against the current schema and tile metadata before changes reach the live site. This means Explorer doesn't silently drift out of sync with the data. When you see a property in the inspector panel, it's a property that's actually in the schema.

We also want to be clear: Explorer is still fundamentally a data and schema inspector, not a finished cartographic product. But it's also proof of what's possible with Overture data. The components are open source and the design system is built to be extended. We hope people take it and run with it.

Source code is in the explore-site repository. Issues and PRs welcome.

What's next​

Explorer is a tool for getting oriented with Overture data. Once you know what you're looking for, the Python CLI and DuckDB are your next steps for downloading and querying at scale. The schema reference is the place to go when you want to understand what those properties in the inspector panel actually mean.

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/

Theme-specific updates​

Addresses​

• refreshed data in the following countries: Canada, Poland, Spain, Austria, US, Latvia, and Finland
• updated Norway and improved our schema thanks to user feedback from Johannes-Andersen.

Base​

• made minor, incremental updates to the data

Buildings​

• made minor, incremental updates to the data

Divisions​

• added new admin_level property to better represent a division's position in its country's administrative hierarchy, i.e. lower numbers correspond to higher level administrative units (0, 1, and 2).
• adjusted top-level subtypes in Antigua and Barbuda.

Places​

• refreshed Foursquare data
• updated matching priorities, causing a slight drop in the number of PinMeTo-sourced place records

Transportation​

• OSM cut-off date: 2026-02-08
• added TomTom-sourced road segments in 65+ new countries including Azerbaijan, Sri Lanka, Nigeria, and El Salvador
• ingested over 1.6M new TomTom-sourced road segments with a combined length of over 280k km
• increased the total number of connectors to 405.9M and the total number of segments to 341.7M

Schema changelog​

The changelog for Overture schema v1.16.0 is here.

Attribution​

You'll find information about attribution and licensing here.

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",

Why We Needed This​

Many of the examples in our docs instruct users to sip or gulp Overture data directly from our public cloud buckets, at very long endpoints like s3://overturemaps-us-west-2/release/2026-01-21.0/theme=buildings/type=building/*.parquet.

(*Not so long ago Paul Ramsey wrote that the trickiest part of accessing Overture data was figuring out how to construct the endpoint. Noted.*)

Using well-structured files on cloud storage as a de facto API for data distribution isn't new. It's actually one of the most important ideas in cloud-native geospatial. Back in 2014, when the AWS open data team put Landsat imagery on S3, they didn't build any custom tooling. No servers. They made well-structured data available on public cloud storage and let people have at it over HTTP. This principle is what makes Cloud Optimized GeoTIFFs work for raster imagery, PMTiles for map tiles, and GeoParquet for vector map data. The storage endpoint is the API.

For Overture, this means tools like DuckDB can query gigabytes of data because Parquet's Hive-style partitioning (theme=buildings/type=building/*.parquet) and built-in row group statistics let query engines skip irrelevant files and irrelevant chunks within files. Users can quickly download megabytes. They don't have to drink the ocean to get the data they want.

The pattern works best with stable endpoints. Things break when endpoints change unpredictably. Overture releases monthly, partitions data by theme and type, and divides its global datasets across multiple Parquet files. All of these factors go into the construction of the S3 and Azure paths. Hardcode a path today, and it's stale in few weeks. We knew this was a pain point for users, but we expected people to build their own solutions around it. Like the AWS team back in 2014, our philosophy was: give people the data and get out of the way.

Not everyone was happy about this. Many users have asked Overture to provide APIs (and SDKs, mostly to handle the complexity of our schema). We did build overturemaps-py, our Python client, to abstract from those long endpoints, but even early versions of that tool had a hardcoded path to the data and required a manual update after each release.

Internally, the pressure to build better tooling came from a different direction. As we migrated more data pipelines from member company infrastructure onto Overture infrastructure, we needed better solutions for keeping things in sync across themes and releases. STAC has helped tremendously. It also lets us access metadata to speed up queries and requests. And because it's the same catalog we publish externally, it solves a lot of user pain points too.

This Makes Your Life Easier Too (We Hope!)​

If you've ever hardcoded an S3 path to Overture data and had it break when we released a new version, we're sorry. Try using Overture STAC. The catalog rebuilds daily directly from our production environment. Instead of checking our release notes or guessing at paths, query the catalog directly to get the latest release:

curl https://stac.overturemaps.org | jq -r '.latest'

Or if you're in DuckDB:

SELECT latest FROM 'https://stac.overturemaps.org/catalog.json';

Even better, create a variable to use the latest release endpoint in all your queries.

SET VARIABLE latest = (SELECT latest FROM 'https://stac.overturemaps.org/catalog.json');

SELECT * FROM read_parquet(
    's3://overturemaps-us-west-2/release/'
    || getvariable('latest')
    || '/theme=addresses/type=address/*'
) LIMIT 10;

Your scripts stay stable even as the underlying data and cloud storage endpoints update.

Explore the Metadata​

You can quickly poke around the catalog using the STAC browser. Click into any release and theme, and you'll find links to GeoParquet files on AWS and Azure. You'll also see PMTiles listed under additional resources. Hover over those for a link to load the tiles directly in PMTiles Viewer. This is the data that powers our Explorer site.

If you want to go deeper, you can drill into a specific release to see which themes it contains and which schema version it uses, then into a theme to find PMTiles links and the available types. Each type is a STAC collection with feature counts, spatial extent, license, and column names, enough to know what you're getting before you download anything. The catalog also includes a peek into our GERS registry by providing a full manifest of the registry files.

If you're using Python, you can install pystac to explore the catalog programmatically. Here's a script that grabs feature counts in the latest Overture release.

import pystac

catalog = pystac.Catalog.from_file("https://stac.overturemaps.org/catalog.json")
latest = next(c for c in catalog.get_children() if c.extra_fields.get("latest"))

print(f"Release: {latest.id}")
print(f"Schema:  {latest.extra_fields['schema:version']}\n")

for theme in latest.get_children():
    print(f"{theme.id}:")
    for collection in theme.get_children():
        count = collection.extra_fields.get("features", "?")
        if isinstance(count, int):
            count = f"{count:,}"
        print(f"  {collection.id}: {count} features")

Release: 2026-01-21.0
Schema:  1.15.0

divisions:
  division: 4,575,616 features
  division_area: 1,068,997 features
  division_boundary: 87,814 features
places:
  place: 72,444,739 features
addresses:
  address: 460,734,720 features
transportation:
  connector: 401,294,301 features
  segment: 338,773,725 features
buildings:
  building: 2,540,587,907 features
  building_part: 3,577,657 features
base:
  bathymetry: 59,963 features
  infrastructure: 144,896,847 features
  land: 71,029,712 features
  land_cover: 123,302,114 features
  land_use: 53,037,060 features
  water: 63,442,033 features

Now let's dig into the metadata for the building type:

import pystac

collection = pystac.Collection.from_file(
    "https://stac.overturemaps.org/2026-01-21.0/buildings/building/collection.json"
)

num_files = sum(1 for link in collection.links if link.rel == "item")

print(f"Type:          {collection.id}")
print(f"Features:      {collection.extra_fields['features']:,}")
print(f"License:       {collection.license}")
print(f"Parquet files: {num_files}")
print(f"Columns:       {collection.summaries.lists.get('columns', [])}")

Type:          building
Features:      2,540,587,907
License:       ODbL-1.0
Parquet files: 236
Columns:       ['id', 'geometry', 'bbox', 'version', 'sources', 'level', 'subtype', 'class', 'height', 'names', 'has_parts', 'is_underground', 'num_floors', 'num_floors_underground', 'min_height', 'min_floor', 'facade_color', 'facade_material', 'roof_material', 'roof_shape', 'roof_direction', 'roof_orientation', 'roof_color', 'roof_height']

You can even fetch the bounding boxes and AWS and Azure paths to individual Parquet files. Exciting!

  00000
  bbox: [-179.9685336, -84.2945957, -2.8229824, -22.499915]
  aws: https://overturemaps-us-west-2.s3.us-west-2.amazonaws.com/release/2026-01-21.0/theme=buildings/type=building/part-00000-47160ab1-2f19-4475-89f8-cc1348df69a6-c000.zstd.parquet
  azure: https://overturemapswestus2.blob.core.windows.net/release/2026-01-21.0/theme=buildings/type=building/part-00000-47160ab1-2f19-4475-89f8-cc1348df69a6-c000.zstd.parquet

  00001
  bbox: [-71.7188172, -33.7503154, -56.249949, -28.1249106]
  aws: https://overturemaps-us-west-2.s3.us-west-2.amazonaws.com/release/2026-01-21.0/theme=buildings/type=building/part-00001-47160ab1-2f19-4475-89f8-cc1348df69a6-c000.zstd.parquet
  azure: https://overturemapswestus2.blob.core.windows.net/release/2026-01-21.0/theme=buildings/type=building/part-00001-47160ab1-2f19-4475-89f8-cc1348df69a6-c000.zstd.parquet

  00002
  bbox: [-67.5002494, -30.937648, -50.6249127, -22.4999315]
  aws: https://overturemaps-us-west-2.s3.us-west-2.amazonaws.com/release/2026-01-21.0/theme=buildings/type=building/part-00002-47160ab1-2f19-4475-89f8-cc1348df69a6-c000.zstd.parquet
  azure: https://overturemapswestus2.blob.core.windows.net/release/2026-01-21.0/theme=buildings/type=building/part-00002-47160ab1-2f19-4475-89f8-cc1348df69a6-c000.zstd.parquet

GERS Registry Manifest​

The catalog also includes the GERS registry manifest. The registry is split into dozens of Parquet files, sorted by ID, and the manifest lists the maximum ID in each file:

"manifest": [
  ["part-00000-...zstd.parquet", "0492a38d-6c33-417c-abd4-de67d7a1b2d8"],
  ["part-00001-...zstd.parquet", "09ff1f68-d9e0-4739-b3b3-ef375d8bf7fe"],
  ["part-00002-...zstd.parquet", "0edc25ba-2d73-4eb7-9c6e-2648644dc125"],
  ...
]

Since GERS IDs sort lexicographically, hex character by hex character, the Python CLI can check this manifest to find exactly which file contains a GERS ID of interest. It's one small JSON fetch instead of checking every file.

What's Next​

Many of the tools I mention in this post are in active development in public GitHub repositories. We welcome your comments, questions, and contributions:

• https://github.com/OvertureMaps/stac — STAC
• https://github.com/OvertureMaps/overturemaps-py — Python CLI
• https://github.com/OvertureMaps/explore-site — Explorer

You can also build your own thing with Overture STAC. Here's a tiny website I made to share at meetups and conferences. It answers a question I consistently get from users: what's the latest Overture release? You can grab the source code here.

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/

Theme-specific updates​

Addresses​

• re-promoted December data, which included new province-level dataset for Quebec from Le ministère des Ressources naturelles et des Forêts

Base​

• made minor, incremental updates to the data

Buildings​

• made minor, incremental updates to the data

Divisions​

• made minor, incremental updates to the data

Places​

• added ~150,000 place records from DAC Group

Transportation​

• added new road segments covering 85,000 km, expanding coverage across ~150 countries

Schema changelog​

The changelog for Overture schema v1.15.0 is here.

Attribution​

You'll find information about attribution and licensing here.

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/

Theme-specific updates​

Addresses​

• added new province-level dataset for Quebec from Le ministère des Ressources naturelles et des Forêts
• removed certain placeholder values like “N/A” and “unincorporated”

Base​

• refreshed OSM data 2025-11-30
• made minor, incremental updates to the data
• added 9,690 rollercoasters to infrastructure!

Buildings​

• refreshed OSM data 2025-11-30
• made minor, incremental updates to the data

Divisions​

• refreshed OSM data
• made minor, incremental updates to the data

Places​

• added new taxonomy property

Transportation​

• added more than 725k new TomTom-sourced transportation segments in the US, Puerto Rico, Canada, Algeria, Colombia, Belarus, and Bosnia and Herzegovina

• refreshed OSM data 2025-11-30

Schema changelog​

The changelog for Overture schema v1.15.0 is here.

Attribution​

You'll find information about attribution and licensing here.

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/

Theme-specific updates​

Addresses​

• repromoted the October data release

Base​

• added a new roller_coaster class to the schema (data coming next month!)
• refreshed OSM data
• made minor, incremental updates to the data

Buildings​

• refreshed OSM data
• made minor, incremental updates to the data

Divisions​

• refreshed OSM data on 6 November 2025
• made minor, incremental updates to the data

Places​

• added ~5,000 new POIs from RenderSEO
• added ~1,500,000 new POIs from AllThePlaces
• known issue: GERS ID churn on 12 million place records

Transportation​

• added new TomTom-sourced segment data to bring the total length of road segments from TomTom to more than 1 million kilometers across 115 countries
• refreshed OSM data on 2 November 2025

Schema changelog​

The changelog for Overture schema v1.14.0 is here.

Attribution​

You'll find information about attribution and licensing here.

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/

Theme-specific updates​

Addresses​

• added additional postal_city values to NAD-sourced US addresses
• added new data in the following locations:
  • Faroe Islands
  • Serbia
  • USA
    • Mississippi
    • Idaho: Ada County
    • Oregon: Jackson County
    • Florida: Orange County, Palm Beach County
    • Michigan: Musgekon County, Kent County, Allegan County
    • many others from NAD
• refreshed data in the following locations:
  • Austria
  • Australia
  • Canada
  • Japan
  • Finland
  • Germany (Berlin, Hamburg, Hesse, Saxony)
  • Hong Kong
  • Latvia
  • Lithuania
  • Luxembourg
  • Poland
  • Slovakia
  • Spain
  • Taiwan (CHA, KEE, KHH, KIN, MIA, NWT, TAO, TNN, TPE, TXG, YUN)
  • USA
• fixed the following bugs:
  • removed unincorporated placeholder value in address_level from NAD
  • added Estonia units
  • fixed missing numbers in Lithuania
  • removed various duplicate address records
  • fixed issue sometimes causing invalid address_level values in Slovenia
• identified the following "known" issues:
  • partial loss of data in: Placer County, CA, USA; Desoto County, FL, USA; Schleswig-Holstein, DE
  • full loss of data in Kern County, CA, USA

Base​

• made minor, incremental updates to the data
• refreshed OpenStreetMap data as of 2025-10-11

Buildings​

• fixed a de-duplication bug, allowing ~5 million more Google-sourced buildings in SE Asia
• populated the license property in sources for building height data
• refreshed OpenStreetMap data as of 2025-10-11

Divisions​

• refreshed OSM data on 2025-10-02
• made minor, incremental updates to the data

Places​

• added a new basic level category property the places schema
• populated the basic level category property with data : https://github.com/OvertureMaps/schema/pull/399

Transportation​

• added new TomTom-sourced segment data
• refreshed OpenStreetMap data as of 2025-09-29

Schema changelog​

The changelog for Overture schema v1.13.0 is here.

Attribution​

You'll find information about attribution and licensing here.

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/

Theme-specific updates​

Addresses​

• added a new license property within sources

Base​

• added a new license property within sources and populated with applicable license information

Buildings​

• added a new license property within sources and populated with applicable license information for Microsoft and OSM features.

Divisions​

• added a new license property within sources and populated with applicable license information

• added geoBoundaries-sourced counties in New Zealand

• added LINZ-sourced localities and neighborhoods in New Zealand

• mapped OSM features with an admin_level=7 tag in Argentina to localadmin

• fixed local_type for geoBoundaries-sourced counties

• refreshed OSM with updates to 2025-08-29

Places​

• added a new license property within sources and populated with applicable license information

• added a new operating_status property, indicating the operating status of a place ("open", "permanently_closed", "temporarily_closed"); set all values to "open" for the September release.

• added six million POIs from Foursquare

• implemented signal “patches” to dynamically update confidence property based on signals

Transportation​

• added a new license property within sources and populated with applicable license information

• added new TomTom-sourced segments

• made significant additions to the data in Italy, Portugal, Mexico, Egypt, Sweden, Indonesia

Schema changelog​

The changelog for Overture schema v1.12.0 is here.

Attribution​

You'll find information about attribution and licensing here.

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/

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.

Theme-specific updates​

Addresses​

• no updates

Base​

• added data for quay, railway, artwork classes

Buildings​

• added new data from Esri and Vancouver
• flagged a bug in the data: all Microsoft ML buildings described as underground

Divisions​

• no updates

Places​

• no updates

Transportation​

• no updates

Schema changelog​

The changelog for Overture schema v1.11.0 is here.

Attribution​

You'll find information about attribution and licensing here.

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/

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.

Theme-specific updates​

Addresses​

• no updates

Base​

• added OSM tags for quay, railway, artwork

Buildings​

• no updates

Divisions​

• added a new data source to populate favelas in Brazil: DadosAbertos
• added is_land geometries to the division_area type country subtype
• added new land polygons is_land=TRUE for regions that have access to oceans

Places​

• no updates

Transportation​

• fixed a small bug in the route source_id formatting
• added new data from TomTom in Turkey

Schema changelog​

The changelog for Overture schema v1.11.0 is here.

Attribution​

You'll find information about attribution and licensing here.

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/.

Exploring Overture data with GERS​

Let's start our exploration by examining how GERS IDs work in one Overture dataset. The divisions theme contains administrative boundaries and points for global administrative areas. In this example, we'll use DuckDB to connect to Azure and read the Parquet files from Azure blob storage. You can also access the files on Amazon S3.

CREATE TABLE slc AS (
    SELECT
        *
    FROM
        read_parquet('az://overturemapswestus2.blob.core.windows.net/release/2025-06-25.0/theme=divisions/type=division/*')
    WHERE
    -- ID for Salt Lake City, Utah
        id = 'c85948de-26de-4c4a-8479-1dac33fa8b04'
);

When we query that table, we can see the divisions hierarchy: Salt Lake City is a locality in Salt Lake County, which is in the region of Utah, within the country of the United States.

SELECT
    h.name,
    h.subtype,
    h.division_id
FROM
    slc
CROSS JOIN UNNEST(hierarchies[1]) AS t(h);

┌──────────────────┬──────────┬──────────────────────────────────────┐
│       name       │ subtype  │             division_id              │
│     varchar      │ varchar  │               varchar                │
├──────────────────┼──────────┼──────────────────────────────────────┤
│ United States    │ country  │ f39eb4af-5206-481b-b19e-bd784ded3f05 │
│ Utah             │ region   │ 506017c0-8932-44b5-b82c-92f9dcffdcf1 │
│ Salt Lake County │ county   │ 53d671bc-c294-44fb-a767-169bffedc5cb │
│ Salt Lake City   │ locality │ c85948de-26de-4c4a-8479-1dac33fa8b04 │
└──────────────────┴──────────┴──────────────────────────────────────┘

To retrieve the actual polygons for these entities, we can query the division_area type of the divisions theme, using division_id as the foreign key that links the datasets. Note: This query will take a few minutes to run.

COPY(
    SELECT
        names.primary AS name,
        subtype,
        id,
        geometry
    FROM
        read_parquet('az://overturemapswestus2.blob.core.windows.net/release/2025-06-25.0/theme=divisions/type=division_area/*') areas
    WHERE
        division_id IN (
            SELECT
                h.division_id
            FROM
                slc
            CROSS JOIN UNNEST(hierarchies[1]) AS t(h)
            )
    ) TO 'slc_hierarchies.geojson' WITH (FORMAT GDAL, DRIVER GeoJSON);

Next we'll load slc_hierarchies.geojson into KeplerGL so that we can see the complete hierarchy of divisions.

Looking up IDs in the GERS Registry​

Let's grab a GERS ID for an important place in Salt Lake City and see if it exists in the GERS Registry. The UUID for the Utah State Capitol is d724e74f-017a-4902-9031-bc784ffc1789. Is that part of GERS? We can search the GERS Registry with this query:

SELECT
    *
FROM
    read_parquet('s3://overturemaps-us-west-2/registry/*')
WHERE
    id='d724e74f-017a-4902-9031-bc784ffc1789';

We can see that d724e74f-017a-4902-9031-bc784ffc1789 is a place type that was first seen by the GERS Registry in the 2025-06-25.0 release. (This makes sense because the GERS Registry didn't exist to see any features before then!) It has a bbox of {'xmin': -111.888214, 'xmax': -111.8882, 'ymin': 40.777214, 'ymax': 40.77722} and it lives in this Parquet file: /theme=places/type=place/part-00001-f6d803dd-3ff7-47d7-a58f-7af6e054e9c4-c000.zstd.parquet.

Using the data changelog​

Every Overture release (except the June 2025 release) includes a changelog with a high-level overview of data added, removed, or changed, based on the ID. The changelog is partitioned by theme, type, and change_type. Let's query the changelog to identify all of the features added in Salt Lake City in Overture's May release.

Let's do query that dumps to the terminal all the new places in the May release for our area of interest.

SELECT
    id
FROM
    read_parquet('s3://overturemaps-us-west-2/changelog/2025-05-21.0/theme=places/*/*/*.parquet')
WHERE
    change_type = 'added'
    AND bbox.xmin > -112.461 AND bbox.xmax < -111.073
    AND bbox.ymin > 40.296 AND bbox.ymax < 40.955;

This gives us 5,727 new places in the Salt Lake City area added to the May release. Now let's write a query to join this list of new places to the full May data release by id and write out a new Parquet file:

COPY(
    SELECT
        places.id as id,
        names.primary as name,
        categories.primary as category,
        confidence,
        CAST(sources AS JSON) as sources,
        geometry
    FROM
        read_parquet('s3://overturemaps-us-west-2/release/2025-05-21.0/theme=places/type=place/*') places
    JOIN (
        SELECT
            id
        FROM
            read_parquet('s3://overturemaps-us-west-2/changelog/2025-05-21.0/theme=places/*/*/*.parquet')
        WHERE
            change_type = 'added'
            AND bbox.xmin > -112.461 AND bbox.xmax < -111.073
            AND bbox.ymin > 40.296 AND bbox.ymax < 40.955
            ) changelog
        ON places.id = changelog.id
        ORDER BY places.id ASC
    ) TO 'new_places_slc_may.parquet';

Let's go one step further and query the one-time May to June ID mapping to translate the May IDs in our list of new places to the new UUID system. Here's how we would do that:

COPY(
    SELECT
        newUUIDs.id
     FROM
         read_parquet('new_places_slc_may.parquet') oldIDs
     JOIN (
     SELECT
        *
     FROM read_parquet('s3://overturemaps-extras-us-west-2/june_to_may_id_mapping/theme=places/type=place/*')) newUUIDs
     ON newUUIDs.previous_id = oldIDs.id
     ) TO 'new_places_slc_may_UUIDs.parquet';

This tells us that all 5,727 new places in Salt Lake City that appeared in the May release were assigned new UUIDs before the June data release. Can we find all of those UUIDs in the June release? Let's take a look. Note: this query take several minutes to run.

COPY(
     SELECT
            june_places_UUID.id,
            names.primary as name,
            categories.primary as category,
            confidence,
            CAST(sources AS JSON) as sources,
            geometry
        FROM
            read_parquet('s3://overturemaps-us-west-2/release/2025-06-25.0/theme=places/type=place/*') june_places_UUID
        JOIN(
            SELECT
                id
            FROM
                read_parquet('new_places_slc_may_UUIDs.parquet')) may_places_UUID
            ON
                june_places_UUID.id = may_places_UUID.id
    ) TO new_places_slc_may_to_june_UUIDs.parquet;

Only 1,546 of new places that appeared in the May release show up in the June release with their newly- assigned UUIDs. This is a known quality issue with our source datasets. As tedious as this process might be, it demonstrates how we can use the GERS tools to track features across releases and gauge churn and data quality from one release to another. Overture is aware that some of our source data providers have significant churn in their data before the data is ingested in Overture pipelines each month. We're working hard to improve these issues. Transparency is the first step.

Using bridge files​

Now what? Let's move forward with our smaller-than-expected dataset of new places in the June release and see if we can find the Facebook pages for some of them. How might we do that? Bridge files are published mappings of GERS ID to source IDs for the datasets that Overture ingests before each release. We only create bridge files for established datasets with a meaningful record_id properites. ML-Derived buildings, for example, do not have stable meaningful input IDs, but place records from Meta have corresponding IDs that reference public Facebook pages.

The sources property in each Overture data release lists the original source of the data and any additional properties that Overture has added. We can use the bridge file for Meta's places data to map the GERS ID back to the source ID. Then we can look up the Facebook pages for the new places in Salt Lake City:

COPY(
    SELECT
        'https://facebook.com/' || cast(bridge.record_id as varchar) AS facebook_page,
            slc_places.*
    FROM read_parquet('new_places_slc_may_to_june_UUIDs.parquet') slc_places
    JOIN(
        SELECT
            id,
            record_id
        FROM
            read_parquet('s3://overturemaps-us-west-2/bridgefiles/2025-06-25.0/dataset=meta/theme=places/type=place/*')
        ) bridge ON slc_places.id = bridge.id
    ) TO 'new_places_slc_with_fb_pages.geojson' WITH (FORMAT GDAL, Driver GeoJSON);

One new place of note is the "Bootlegged Barber" in Sandy, Utah. On their Facebook page, the proprietors advertise themselves as a "NeoTraditional Barbershop | Where tradition and style meet."

Next steps​

• Checkout our GERS tutorial
• Read more about the components of GERS in our docs
• Read our "GERS Deep Dive" and "Introducing Bridge Files" blog posts

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/

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? Big changes to GERS.​

In this release, Overture has standardized the id property across all themes by adopting UUIDs, stored as strings. This is a one-time breaking change for our ID system. For this release only, we are offering Parquet files, partioned by theme and type that map the old May IDs to the new June UUIDs. You can find that file here: s3://overturemaps-extras-us-west-2/june_to_may_id_mapping/.

Overture is now producing bridge files with each release. You can find the latest bridge files here, partitioned by dataset, theme, and type:

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

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

The newest component of GERS is the GERS Registry, which will also be updated with each release. The GERS Registry files are here:

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

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

Breaking changes​

• added perspectives to the top-level names property
• added between to the top-level sources property
• added rail subtype to the transportation theme
• ensured no array is empty on place properties
• migrated GERS IDs to new GERS UUIDs

Theme-specific updates​

Addresses​

• added new Greenland data source: OpenAddresses/Asiaq, Greenland Survey
• added new Singapore data source: OpenAddresses/Singapore Land Authority
• added several new data sources in the United States
  • Clarke County, GA: OpenAddresses/GA/Athens-Clarke County GIS
  • State of Minnesota: OpenAddresses/MN/Department of Public Safety
  • State of Colorado: OpenAddresses/CO/Governor's Office of Information Technology
  • Lackawanna County, PA: OpenAddresses/PA/City of Scranton GIS
• made improvements to existing Mexico and Australia address data
• made improvements to existing US data and Australia address data

Base​

• increased number of features with names property populated with data
• increased coverage of certain classes, especially within land_use and infrastructure. Examples: communication_pole, pedestrian_crossing, plaza, street_lamp, cable_barrier, fire_hydrant
• addded all upstream source tages from OSM to the source_tags property

Buildings​

• added a new data provider: City of Vancouver, CA

Divisions​

• added new "land" polygons (is_land=TRUE) for regions that have access to oceans

Places​

• 64.37M total places compared to 61.68M in May
• added a new data provider: Krick
• made improvements made to neurologist category mappings

Transportation​

• added rail_flags and class properties: railway segments now have classes (e.g. standard_gauge, tram, subway) and linear-referenced flags (is_abandoned, is_freight, etc.)
• added linear references to sources, making it possible to trace exactly how a segment was constructed from its sources
• added new TomTom-sourced segments, improving coverage in Turkey

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:

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

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

You can find more information about [the data changelog in our documentation](https://docs.overturemaps.org/gers/changelog/).

## Schema changelog

The changelog for Overture schema `v1.10.0` is [here](https://github.com/OvertureMaps/schema/releases/tag/v1.10.0).

## Attribution

You'll find information about attribution and licensing [here](/attribution).

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

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​

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

Base​

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

Buildings​

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

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

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

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

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.

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

You can access the datasets by following the process outlined here. We encourage you to ask questions and provide feedback on the Overture Maps Discussions 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.

Breaking changes​

none

Deprecations​

none

Theme-specific updates​

Addresses​

Data changes​

• fixed overlapping datasets in two Florida counties
• added data for Lee and Marion counties in Florida

Base​

Data changes​

• added golf course data from OpenStreetMap
• explicitly specified the data type of the class property for water features as string (very minor schema change)

Buildings​

Data changes​

• made minor data fixes and updates

Stats​

Divisions​

Data changes​

• added country and region properties to division_boundary (minor schema change)
• calculated cartography.prominence values for subtype=locality
• populated local_type with set values; the default value is the same as subtype

Stats​

Places​

Data changes​

• made minor data fixes and updates

Stats​

Transportation​

Data changes​

• made minor data fixes and updates

Stats​

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-04-23.0

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

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

Schema changelog​

The changelog for Overture schema v1.8.0 is here.

Attribution​

You'll find information about attribution and licensing here.

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

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

Overview​

The 2025-03-19.0 release of Overture data and v1.7.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-03-19.0

Amazon S3:​

s3://overturemaps-us-west-2/release/2025-03-19.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 Discussions 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.

Breaking changes​

None.

Deprecations​

None.

Theme-specific updates​

Addresses​

• added new data sources for all California counties, aside from Sierra County
• added new county-level and state-level data sources in Florida
  • coverage now includes all but four counties
• added a new data source for Hong Kong
• added a new data source in Oregon

Base​

• minor data fixes and updates

Buildings​

• added ~13M new buildings from Instituto Geográfico Nacional, Spain

Divisions​

• corrected format of OSM source ids, which now include the @version format, as seen in other themes
• removed an incorrect Argentina perspective field value
• the local_type value is set on regions in the US and India
• all division boundary GERS IDs have changed since the February release

Places​

• minor data fixes and updates

Transportation​

• added an is_indoor road flag to the schema
• re-included 88,005 segments flagged as ‘indoor’, which had previously been filtered out

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-03-19.0

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

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

Schema changelog​

The changelog for Overture schema v1.7.0 is here.

Attribution​

You'll find information about attribution and licensing here.

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

You can access the datasets by following the process outlined here. We encourage you to ask questions and provide feedback on the Overture Maps Discussions 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.

Breaking changes​

None.

Deprecations​

None.

Theme-specific updates​

Addresses​

• added new data in the following US counties:
  • Hillsbough County, FL
  • Manatee County, FL
  • Dekalb County, GA
  • Oakland County, MI
• added new data in Yukon Territory, Canada
• updated the NAD source to v18
• removed erroneous address data in BE

Base​

• minor data fixes and updates
• refreshed data with 15 February 2025 OSM update

Buildings​

• fixed geometries from the Zenodo dataset
• refreshed data with 5 February 2025 OSM update

Divisions​

• added county boundaries in Colombia and Uruguay
• added ~12k new division_boundary features
• refreshed data with January 2025 GeoBoundaries update
• migrated pipeline to Apache Spark implementation which resulted in improved names, capitals and parenting properties

Places​

• released the first data update since September 2024, from a new and re-worked places conflation pipeline within Overture. This should result in more stable places releases moving forward
• added new places data, resulting in a ~12% increase in the total number of places
• removed a small number of places without a primary name or primary category

Transportation​

• added ~40000km of new TomTom-sourced roads in France, Germany, Italy, Jordan, Kuwait, Mexico, Monaco, Saudi Arabia, Switzerland, United Arab Emirates, United Kingdom, United States, and Yemen
• refreshed data with 5 February 2025 OSM update

Global Entity Reference System (GERS) changelog​

The GERS 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-02-19.0

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

You can find more information about the GERS Changelog in our documentation.

Schema changelog​

The changelog for Overture schema v1.6.0 is here.

Attribution​

You'll find information about attribution and licensing here.

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

You can access the datasets by following the process outlined here. We encourage you to ask questions, report bugs, and provide feedback via our data and schema repositories on GitHub. 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.

Breaking changes​

None.

Deprecations​

None.

Theme-specific updates​

Addresses​

• added five new data sources in Taiwan
• made minor fixes and updates

Base​

• made minor fixes and updates

Buildings​

• added 228.5M buildings from a new ML-derived building dataset of East Asian countries
• made minor fixes and updates

Divisions​

• new cartography column in the schema that has not yet been populated with data
• added is_land and is_territorial properties to division_area and division_boundary feature types
• refreshed data on 17 January 2025

Places​

A statement from the Places engineering team: “The places data has remained unchanged since the September 2024 release while we work on substantial pipeline upgrades. We anticipate releasing a new dataset in the coming months.”

Transportation​

• added approximately 4000km of new TomTom-sourced roads in the US
• refreshed data on 18 December 2024

Global Entity Reference System (GERS) changelog​

The GERS 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-01-22.0

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

You can find more information about the GERS Changelog in our documentation.

Schema changelog​

The changelog for Overture schema v1.5.0 is here.

Attribution​

You'll find information about attribution and licensing here.

First, let’s talk about what GA means for the transportation theme. We have a few guiding principles:

1. There are no "trust violations" in the schema and data. It needs to "just work" when a developer writes code based on our schema and documentation.
2. The road geometry and attributes should be on par with the roads in OSM.
3. Roads have stable GERS IDs and those IDs can be references for attaching additional data.
4. The road features we capture should support our core use cases: rendering for display, GERS referencing, and basic routing capabilities.

Most of our work over the past few months has been around #1 and #2. We've been resolving data-schema violations by fixing inconsistencies in our schema and issues with the data transformation steps in our pipeline. To satisfy #3, we’ve been monitoring changes in GERS IDs from release to release, and our metrics show the vast majority of roads are maintaining stable IDs.

We've had to break a few things in our schema to make way for improvements:

• To better support routing use cases, we added to the segment feature type a new property called connectors: an array of IDs with pre-computed linear reference values that explicitly link segments and connector features via coordinates. Each connector is a possible routing decision point, meaning it defines a place along the segment in which there is possibility to transition to other segments that share the same connector. This new property — a replacement for the old connector_ids property — will reduce complexity and improve accuracy as we calculate the intersections between segment and connector features. You can read more about this improvement here.

• In the November release, we removed lanes from the schema to eliminate a significant trust violation. The lanes property has existed in the schema for months but we never populated it with data in our releases, which is a poor experience for our community. We intend to redesign lanes in the coming months.

With these changes, we are confident we’ve met our requirements for general availability (GA). We'll continue refining our schema and improving our data throughout 2025. We encourage our community to keep the feedback coming, particularly around data quality and our core use cases of map display, routing, and matching data via GERS.

Here are some specific ways you can help:

1. Examine Overture transportation data in your areas of interest and compare it to local sources of data. Bonus: combine transportation data with Overture places, buildings, and base data to make a map. Here are some suggestions for downloading data using Overture's Python CLI.

Philadelphia area

overturemaps download --bbox=-75.8264,39.7032,-74.5213,40.444 -f geoparquet --type=segment -o overture-segments-philadelphia.geoparquet

Riyadh Province, Saudia Arabia

overturemaps download --bbox=38.97,21.33,48.66,25.98 -f geoparquet --type=segment -o overture-segments-riyadh.geoparquet

Campobasso, Italy

overturemaps download --bbox=13.8152,40.8473,15.6336,42.0773 -f geoparquet --type=segment -o overture-segments-campobasso.geoparquet

2. Test our transportation spitter tool and help us improve it. PRs are welcome!

3. Feed our data into a routing engine and let us know how it goes. Paul Ramsey from Crunchy Data shared a vehicle routing example using PostGIS and Overture data. We'd like to see our users trying Valhalla and Graphhopper too. We are considering building a native Overture router and/or adding support to an existing open source router, such as Valhalla and Grasshopper, so that Overture consumers can easily use transportation data out of the box.

4. Reach out to us at community@overturemaps.org if you have a specific use case that you'd like to discuss with us.