v0.12.0-beta

What's Changed

A. Theme-specific changes

1. Base
   • Fix issue where level property was not correctly populated for infrastructure, land_use, and water features.
   • Add sort_key as an optional cartography property, which is populated for land_cover features
   • Add surface property for infrastructure, land, and land_use features.
   • Improve source_tags pass-through for land features.
   • Improve subtype mapping for infrastructure.
   • Improve class mapping for land_use.
   • Other minor OpenStreetMap tag mapping improvements.
2. Buildings
   • Rename eave_height property to roof_height to simplify and make the schema easier to understand.
   • Spelling corrections and other tweaks to available building classes, building subtypes, and their OSM mappings
   • Add building classes: library and post_office
3. Divisions
   • division features:
     • Fix conceptual issue with perspectives property on division features, switching to an acceptance/inclusion versus dispute/exclusion model.
     • Add multiple capital division IDs on division features to handle multi-capital cases like the Kuyavian–Pomeranian Voivodeship (Województwo kujawsko-pomorskie), Bolivia, and South Africa.
   • boundary features:
     • Allow MultiLineString as a possible geometry type for boundary features. This allows simplifying all boundaries between two adjacent divisions into a single feature with a single GERS ID/Overture ID.
     • Align dispute modeling with division perspectives: add perspectives and is_disputed properties and drop the system of only being able to mark boundaries disputed from the perspective of the divisions to either side via the divisions[*].is_disputing property.
4. Places
   • Fix typo in categories mapping CSV (very minor).
5. Transportation
   • Add top-level routes property to segment feature to contain routes the segment belongs to (i.e. highway network).
     • This is analogous to, and today is generally sourced from, OpenStreetMap relations of type route.
   • Restructure the segment feature's properties as described in #203. We hope this is one of the last, if not the last, major breaking change for transportation.
     • Lifting properties that had previously been nested under the road property up to top level. The purpose of this change is to reduce nesting to a more manageable level and to make the Parquet schemas for segment properties manageable. The property changes here are:
       • road.restrictions.speed_limits becomes speed_limits
       • road.restrictions.access becomes access_restrictions
       • road.restrictions.prohibited_transitions becomes prohibited_transitions
       • road.surface becomes road_surface
       • road.flags becomes road_flags
       • road.width becomes width_rules
       • road.lanes becomes lanes
       • road.level becomes level_rules
     • Slightly simplifying the frequently-used when: vehicle: scoping structure.
     • Deprecating the road property. The road property will still be available in the June 2024 data release, so Overture users can temporarily ignore the restructuring change and continue to use road, but this property will be removed in the coming months. We expect users will prefer the new top-level properties because they will have structured Parquet schemas in the data release from day 1, unlike the road property which is an unwieldy JSON string, which is inconsistent with the rest of the Overture schema and also difficult to use.
   • Limit speed limit maximum value to 350 units (previously there was no maximum).
   • Reduce speed limit minimum value to 1 unit. The previous minimum of 20 units did not make sense and disagreed with the real world ground truth in many places, e.g. narrow pedestrian paths.

B. Documentation changes

• Return feature model, naming, scoping, and transportation pages to schema reference website.
• Build changes to maintain tight integration between schema documentation and the remainder of docs.overturemaps.org.
• Housekeeping changes.

Full Changelog

Full Changelog: v0.11.0-beta...v0.12.0-beta

New Contributors

• @jeffdefacto made his first contribution in #189