Azure path: wasbs://release@overturemapswestus2.blob.core.windows.net/2024-06-13-beta.1

AWS path: s3://overturemaps-us-west-2/release/2024-06-13-beta.1

Overture's 2024-06-13-beta.0 release is available in GeoParquet and stored on AWS and Azure. You can access the datasets by following the process outlined here. We encourage users to report bugs and provide feedback on the data, schema, and GERS via any publicly-available Overture Maps repository on GitHub:

• Schema
• Data
• Docs
• Python command-line tool
• Explore site

Depending on feedback, we anticipate moving to a general availability (GA) release soon.

New data: GERS changelog​

You'll find in this release a new GERS changelog that captures feature changes from the previous release to the current release. The changelog is available as Parquet files — partitioned by theme, type, and change_type — at the following locations:

wasbs://changelog@overturemapswestus2.blob.core.windows.net/2024-06-13-beta.0

s3://overturemaps-us-west-2/changelog/2024-06-13-beta.0

Valid values for the change_type include:

• added: Overture ID is new and was not in the previous release
• removed: Overture ID is not in the current release and was in the previous release
• data_changed: Overture ID is in the current release and was in the previous release and the feature's attributes or geometry have changed
• unchanged: Overture ID is in the current release and was in the previous release, and the feature's attributes and geometry have not changed

Breaking changes​

In response to feedback from developers and data analysts in the Overture ecosystem, we simplified ("flattened") the structure of our road data to make it easier to query road attributes. To make this transition easier for users, we included the now deprecated road JSON column in this release. We will remove the road JSON column in the next release.

Also in this release, we simplified the non-geometry vehicle scoping block.

speed_limits:
  when:
    ...
    vehicle:
      axle_count:
        is_more_than:
          value:
          unit:
        is_less_than:
          ...
        ...
        ...
      height:
        ...
      length:
        ...
      weight:
        ...
      width:
        ...

speed_limits:
  when:
    ...
    vehicle:
      - dimension: <axle_count, height, length, weight, width>
        comparison: <greater_than, greater_than_equal, equal, less_than, less_than_equal>
        value: str
        unit: str

Deprecations​

In the transportation theme, we deprecated the road JSON column and will remove it in the next release. We replaced the road JSON column with structured Parquet columns for road attributes.

We deprecated the admins theme and replaced it with the divisions theme. This will be the last supported release for the admins schema and data. In the next release, admins will be available in an archive but not supported.

Schema changelog​

See our schema changelog here.

Theme-specific updates​

Divisions/Admins

• added support for MultiLineString geometries to improve the stability of Overture IDs for boundary features
• extended the schema to support multiple capitals of a division
• added the option to include or exclude boundaries based on perspectives
• updated OpenStreetMap data to 2024.06.05
• changed modeling of municipalities/cities in Brazil from counties to localities, which we believe better reflects ground truth
• made improvements to the names data and fixed several bugs

Base

• added the surface attribute to infrastructure and land feature types
• made incremental updates from OSM, based on Daylight v1.48
• added to the land_cover feature type a new cartographic property cartography.sort_key: an ascending number signifying the importance of a feature in relation to other features.

Buildings

• made regular updates to buildings, including adding the latest open data from OSM, Esri Community Maps, and Microsoft
• expanded the previous definition of class for buildings to include specific amenity tags that are either already an official Overture place category or can be matched to one

Places

• began a comprehensive audit of data quality
• worked on calibrating confidence values

Transportation

• updated speed limit min/max values
• added 19K previously filtered segments which contained self-intersecting lines that are still OGC-valid
• fixed OSM source ids for connectors
• known issue: in road_flags a value of 0 or 1 on the linear referencing between property can be null in some cases

Attribution​

You'll find information about attribution and licensing here.