Schema v0.9.0 release

What's Changed

A. Structural changes.

1. snake_case. We changed over all property names and enumeration member names from camelCase to snake_case. This is a big one-time churn to improve SQL compatibility. We don't expect another churn of this magnitude.
   • #127
   • #129
2. The transportation segment's connectors property is renamed to connector_ids for consistency with our agreed direction on relationship modeling. #137
3. Various changes in the transportation theme have been made to eliminate cases where JSON Schema types can be mixed, i.e. like a property that can be either an array or an object. The purpose is to improve Parquet compatibility by bringing us to a point where 100% of the JSON Schema can be converted to strongly-typed Parquet schema. We are almost there.
   • #85
   • #135

B. New themes.

1. Divisions. We have re-imagined the schema for administrative data. The re-imagined schema is in theme divisions and is quietly included in this schema release, although not the documentation yet. In the April, 2024 data release we will populate data in the divisions theme and will begin the process of deprecating the admins theme.
   • #130
   • #139

C. Transportation theme improvements.

1. Road width is pushed down to road.width and now supports linear referencing. #121. (Starting with the 2024-03-12 data release we are also now generating road width data.)
2. Alley class is supported. OvertureMaps/tf-transportation#122
3. Abandoned/disused segments are now flagged. #132

D. Other

1, Documentation improvements.
2. Validation improvements: #112
3. OpenStreetMap mappings have been documented:

• For the base theme: #133
• For the buildings theme: #89

Full Changelog

Full Changelog: v0.8.0...v0.9.0