Overturemaps

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.
- https://github.com/OvertureMaps/schema/pull/127
- https://github.com/OvertureMaps/schema/pull/129
2. The transportation segment's `connectors` property is renamed to `connector_ids` for consistency with our agreed direction on relationship modeling. https://github.com/OvertureMaps/schema/pull/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.
- https://github.com/OvertureMaps/schema/pull/85
- https://github.com/OvertureMaps/schema/pull/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.
- https://github.com/OvertureMaps/schema/pull/130
- https://github.com/OvertureMaps/schema/pull/139

C. Transportation theme improvements.

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

D. Other

1, Documentation improvements.
2. Validation improvements: https://github.com/OvertureMaps/schema/pull/112
3. OpenStreetMap mappings have been documented:
- For the `base` theme: https://github.com/OvertureMaps/schema/pull/133
- For the `buildings` theme: https://github.com/OvertureMaps/schema/pull/89

Full Changelog

**Full Changelog**: https://github.com/OvertureMaps/schema/compare/v0.8.0...v0.9.0

What's Changed
- Documentation improved, see at https://docs.overturemaps.org
- Admins schema: `adminLevel` simplified to use ordinal numbers 1, 2, 3, ...
- Admins schema: `adminLevel=1` is now used for countries
- Admins schema: `population` property added
- Admins schema: `wikidata` property added
- Base theme: `elevation` property added
- For all features types, `names` property updated to a new "unified" format that is simpler in most cases and also supports linearly-referenced and "side-of-street" road names. The `road.roadName` property is dropped as names now always appear in the top-level `names` property
- Bug fixed: `updateTime` regular expression validation corrected
- Bug fixed: `road.surface` default value corrected
- Bug fixed: `level` property dropped from connector
- Bug fixed: temporal scoping removed from road flags
- Bug fixed: `isPrivate` flag dropped from road flags, as that is handled via access restrictions scoped to private

**Full Changelog**: https://github.com/OvertureMaps/schema/compare/v0.7.0...v0.8.0

What's Changed
* Add footway to road class enum by brad-richardson in https://github.com/OvertureMaps/schema/pull/93
* Improve Transportation diagrams with dark/light theme and Overture color palette by vcschapp in https://github.com/OvertureMaps/schema/pull/94
* fix: spelling of cafeteria by JanCallewaert-TomTom in https://github.com/OvertureMaps/schema/pull/86
* Fix type maxiumum->maximum on linearlyReferencedPosition by DavidKarlas in https://github.com/OvertureMaps/schema/pull/73
* December Schema Update by jenningsanderson in https://github.com/OvertureMaps/schema/pull/90

New Contributors
* JanCallewaert-TomTom made their first contribution in https://github.com/OvertureMaps/schema/pull/86

**Full Changelog**: https://github.com/OvertureMaps/schema/compare/v0.6.0...v0.7.0

November 14th, schema release.

What's Changed
* update turn restriction documentation to reflect by jenningsanderson in https://github.com/OvertureMaps/schema/pull/65
* Fix charity_organization taxonomy by Cj-Malone in https://github.com/OvertureMaps/schema/pull/66
* [Admins] Add Area type and allow only Point on Locality by DavidKarlas in https://github.com/OvertureMaps/schema/pull/72
* Base theme updates by jenningsanderson in https://github.com/OvertureMaps/schema/pull/75
* Fix lane scoping example by brad-richardson in https://github.com/OvertureMaps/schema/pull/77
* M2 Release by jenningsanderson in https://github.com/OvertureMaps/schema/pull/71

New Contributors
* Cj-Malone made their first contribution in https://github.com/OvertureMaps/schema/pull/66
* brad-richardson made their first contribution in https://github.com/OvertureMaps/schema/pull/77

**Full Changelog**: https://github.com/OvertureMaps/schema/compare/v0.5.0...v0.6.0

October 19, 2023 pre-release.

June 15, 2023 [pre-release](https://overturemaps.org/overture-maps-previews-data-schema-and-reference-system/).