Transportation Destinations

[ibnt1]

Description

Adds support for segment destinations as a top-level property.

These are intended to capture OSM destination=* tags on ways and destination_sign relations consolidated into a common schema.

Similar to the OSM destination tags on ways, destination property describes objects that are reached, when a the segment is being followed, but also includes references to the segments from which you need to transition to reach the destination, similar to the OSM destination_sign relations.

Reference

1. https://github.com/OvertureMaps/tf-transportation/issues/117

Testing

Added new examples, tested.

Checklist

Checklist of tasks commonly-associated with schema pull requests. Please review the relevant checklists and ensure you do all the tasks that are required for the change you made.

1. Add relevant examples.
2. Add relevant counterexamples.
3. Update any counterexamples that became obsolete. For example, if a counterexample uses property A but is not intended to test property A's validity, and you made a schema change that invalidates property A in that counterexample, fix the counterexample to align it with your schema change.
4. Update in-schema documentation using plain English written in complete sentences, if an update is required.
5. Update Docusaurus documentation, if an update is required.
6. Review change with Overture technical writer to ensure any advanced documentation needs will be taken care of, unless the change is trivial and would not affect the documentation.

Documentation Website

Update the hyperlink below to put the pull request number in.

Docs preview for this PR.

[vcschapp]

I'm basically leaving this alone right now until the nesting discussion gets resolved in a principled way.... Ideally we can make a final decision on nesting and all related churn in transportation will stop.

outdated