v1.1.0

What's Changed

Read the full release notes here: https://docs.overturemaps.org/release/latest/. Below is a list of changes to the schema since the last release.

Schema-Wide Changes

No changes.

Theme-Specific Schema Changes

Addresses (Status: Alpha)

🏗 The addresses theme is in alpha status. Schema changes with potential backward-incompatibility are likely from month to month until the addresses schema increases in maturity. When these changes occur, we will try to provide some notice and a "bridge" period where the old schema is also supported.

No changes.

Base (Status: GA)

🟢 The base theme is in GA status. We are striving to avoid backwardly-incompatible schema changes and to deliver adequate notice should they occur.

No changes.

Buildings (Status: GA)

🟢 The buildings theme is in GA status. We are striving to avoid backwardly-incompatible schema changes and to deliver adequate notice should they occur.

Minor changes to some SQL mappings from OpenStreetMap tags to Overture schema property values. PR #258.

Divisions (Status: GA)

🟢 The divisions theme is in GA status. We are striving to avoid backwardly-incompatible schema changes and to deliver adequate notice should they occur.

No changes.

Places (Status: GA)

🟢 The places theme is in GA status. We are striving to avoid backwardly-incompatible schema changes and to deliver adequate notice should they occur.

No changes.

Transportation (Status: Beta)

🏗 The transportation theme is in beta status. The transportation schema is nearing maturity, but backwardly-incompatible schema changes may occur from month to month until GA status is achieved. When these changes occur, we will try to provide some notice and a "bridge" period where the old schema is also supported.

The following changes were made to the transportation schema. These changes are also discussed extensively in the August 15, 2024 blog What to expect in Overture’s August release.

1. Destinations are added to segment features via the destination property.
   • Destinations allow functionality such as "follow signs for downtown" to be added in routing engines.
   • This is a purely additive feature and does not introduce any backward-incompatibility issues.
   • PR #176
2. The connector_ids property of a segment feature, which only included the feature ID of the target connector, is replaced by a more general connectors property which includes both the target connector ID and its LR offset on the segment.
   • The connector_ids property will remain supported in the August 2024 and September 2024 data releases but will be permanently removed from the schema in the October 2024 release.
   • Transportation data users should migrate to connectors by October.
   • PR #257
3. More granular information is now available on the real-world role of segment features via the subclass_rules and subclass properties.
   • The subclass_rules property contains linear referencing rules that assign a more granular role information to linearly-referenced ranges of the segment. For example, a segment with class footway may be refined to sidewalk or crosswalk via subclass_rules.
   • If the whole segment has the same subclass (it is not different for different LR ranges), this is captured in the subclass property. Otherwise, subclass captures the "most dominant" subclass from subclass_rules.
   • This change is almost fully backwardly-compatible. However, a few members of the roadClass enumeration used to populate class have been migrated to subclass_rules/subclass. Also, the is_link member of the segment flags has been deprecated and will be deleted in a future release because link status is now captured in subclass_rules/subclass.
   • PR #180
   • There is some additional information on segment subtypes on the docs website here.

Full Changelog

Full Changelog: v1.0.0...v1.1.0

New Contributors

• @stepps00 made his first contribution in #263