Overture’s August Release Shows Open Maps Becoming Data Infrastructure
Overture Maps Foundation’s latest release is easy to describe as another increase in address points, transport features and physical geography. The more consequential story, however, is how Overture is turning open map data into governed infrastructure that software, and increasingly AI agents, can consume predictably.
Published on August 19, release 2026-08-19.0 uses schema version 1.18.0 and distributes its datasets through GeoParquet, PMTiles and cloud-hosted registries. Overture’s base, buildings, divisions, places and transportation themes are considered generally available, while addresses remain alpha. The complete release notes are available here.
The release contains approximately 472.8 million candidate address records. Overture refreshed data from Fresno County and Statistics Canada, adding richer attributes, and incorporated several thousand records from Land Information New Zealand and Italy’s ICAR system.
Its base dataset also expanded. Infrastructure features increased by 1.8% to approximately 155.5 million, while land features grew by 1.6% to 75.6 million. Peaks, ridges, saddles, mountain ranges and volcanoes all increased, although the official notes do not support the previously circulated claim that exactly 131,189 mountain landforms were added.
Transportation changes include more parking facilities, parking spaces, bicycle parking, bus stops and stop positions. The release also added nearly 497,000 TomTom road segments and around 1.3 million OpenStreetMap segments, alongside improvements to attributes such as road surface, class and access restrictions.
Yet raw feature growth is not the best measure of the release.
Overture’s building count actually fell by 0.6%, to approximately 2.53 billion, despite millions of new Microsoft and OpenStreetMap contributions. Its places dataset also declined by 0.8%, even as BrightQuery and AllThePlaces supplied additional records.
Those reductions do not necessarily mean coverage deteriorated. They illustrate that conflation, deduplication, filtering and quality controls can matter more than simply accumulating objects. That is especially important for machine-driven applications, where duplicate or contradictory features can be more damaging than a slightly smaller dataset.
The release also advances an important schema transition. Overture has deprecated the broad categories field and will remove it in September, replacing it with basic_category and taxonomy. Developers have one transition release in which both representations are available.
This is the kind of change that determines whether an open dataset functions as dependable infrastructure. Stable identifiers, documented schemas and predictable migration paths are essential when map data feeds analytics pipelines, digital twins or the emerging class of machine-oriented maps.
The release notes also contain an unusually useful disclosure: an August changelog incorrectly classified 60,060 bathymetry features as newly added, when the correct number was zero. Publishing the correction strengthens transparency, but it also shows why downstream teams should validate machine-readable changes rather than treating release summaries as unquestionable truth.
Overture says its data is already being used by Microsoft, Esri, Meta, Uber and other members. In a Foundation case study, Microsoft reports that replacing an existing buildings layer with Overture improved address accuracy by several percentage points and shortened some map-production cycles from months to weeks. These remain company-reported results rather than independently audited benchmarks. Microsoft’s case study and Overture’s Esri User Conference report nevertheless offer evidence that the project is moving beyond experimental downloads.
Practitioner questions on Overture’s public GitHub forum continue to focus on confidence values, category decisions, changes in feature locations and practical data access. There was little substantive independent discussion of this exact release, suggesting adoption evidence still lags the Foundation’s technical progress.
As Geoawesome has previously explored in its discussion of Overture’s purpose and the relationship between Google Maps and OpenStreetMap, competition in mapping is no longer only about who possesses the most features. It is increasingly about who can provide reliable, interoperable and continuously governed spatial infrastructure.
Overture’s August release is another step in that direction, less a dramatic map update than an indication of how open maps are being prepared for machines.