id-tagging-schema
id-tagging-schema copied to clipboard
Suggest 'from', 'to' and 'via' only for public transport routes
Describe the bug
Currently, iD editor suggests from
, via
and to
for all type=route
+ route=*
relations. However, these keys are useful only for public transport routes and recreational routes where there are separate relations for A -> B and B -> A. For other route types there are only one relation for the route (with possible forward
and backward
roles of the members).
See:
- https://wiki.openstreetmap.org/wiki/Key:from
- https://wiki.openstreetmap.org/wiki/Key:via
- https://wiki.openstreetmap.org/wiki/Key:to
To Reproduce
- Add a new relation.
- Select road route.
- See the preset.
Expected behavior
Bi-directional routes should not have from
, via
and to
fields.
For other route types there are only one relation for the route (with possible forward and backward roles of the members).
Highway route relations in some countries are routinely modeled as separate relations per direction or per leg. from
and to
are sometimes the only possibility for distinguishing route relations that represent different legs of the same route. In other cases, these keys are a structured alternative to setting name
to a description.
Based on Taginfo there is 2X more usage of wikidata
and wikipedia
and 5X more usage of distance
. Why are from
, via
and to
in a preset where these keys are filled only in 4.2% of all route=road
relations?
The Road Route preset also includes fields for wikidata
, wikipedia
, and distance
.
If there is a consensus that from
, via
, and to
cannot appear on road routes in some countries, the field can be conditional on the country where it is located, just as the Direction field only appears in three countries (but probably should be added to a few more).