You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Goal: For tags like parking:left|right|both=* it would be great if the directionCombo field for parking:left|right|both:orientation could "look at it's sibling tags". This would improve the mapper UX and likey data quality by showing smarter placeholder or disabling fields alltogether.
Example 1:
Field parking as parking:left=no|separate
In this case, the directionCombo for orientation should …
disable parking:left:orientation
or change the placeholder to something like "not expected due to parent tag"
Example 1:
Field parking as cycleway=lane + oneway=yes
In this case, the directionCombo for cycleway should …
change the placeholder for cycleway:{backward} to something like "implicit 'no' due to oneway"
I now see, we would also have to evaluate the direction of the way in order so know if "left" or "right" is meant
Description
Goal: For tags like
parking:left|right|both=*
it would be great if thedirectionCombo
field forparking:left|right|both:orientation
could "look at it's sibling tags". This would improve the mapper UX and likey data quality by showing smarter placeholder or disabling fields alltogether.Example 1:
Field parking as
parking:left=no|separate
In this case, the directionCombo for orientation should …
parking:left:orientation
Example 1:
Field parking as
cycleway=lane + oneway=yes
In this case, the directionCombo for cycleway should …
cycleway:{backward}
to something like "implicit 'no' due to oneway"I now see, we would also have to evaluate the direction of the way in order so know if "left" or "right" is meant
Ping #9212 (comment)
Ping openstreetmap/id-tagging-schema#675
Screenshots
No response
The text was updated successfully, but these errors were encountered: