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
Can we use the new directionalCombo for the maxspeed:forward|:backward tag?
Goal
Make the hidden data visible in iD so users see the data right away in the fields section.
Why
When evaluating the safety of highway especially when looking at safe cycling maxspeed is super important. We have quite a few roads between villages that have different speed limits for forward/backward. Right now, this data is hidden in ID, which results in mappers missing it and wrongly edit the maxspeed instead.
A way to specify the format of data as part of a preset; there was a discussion on this somewhere when the directionalCombo was introduced. Right now, the maxspeed field is of "type": "roadspeed", which we cannot configure as part of the directionalCombo — Next step: Add measurement field type ideditor/schema-builder#15
UI: A way to make the forward/backward a special case, not the default case. It feels wrong to push the forward/backward in front of all users (even though iD handles the tagging correctly by only tagging maxspeed=123 when both directions have the same value). Ideally the UI would have a button which optionally splits the field in two.
UI: A way to show the minimal UI based on the given tags. This tagging usually(?) has all tree tags maxspeed, maxspeed:forward, maxspeed:backward with maxspeed being the more conservative of the two. AFAIK this is done to be backward compatible to data consumers that do not yet look at the split version of the tags. — Cases via Overpass
The text was updated successfully, but these errors were encountered:
OSM Tag(s)
maxspeed:forward|:backward=number
How would you like this tag to see supported?
As an Option of a Field
Link to OSM Wiki page
https://wiki.openstreetmap.org/wiki/DE:Key:maxspeed#Unterschiede_nach_Fahrtrichtung
Status of the Tag
De Facto
Usage of the tag
120 754 maxspeed:forward; 116 401 maxspeed:backward (https://taginfo.openstreetmap.org/search?q=maxspeed%3A#keys)
Regional Tag?
global
Example
Description
Can we use the new
directionalCombo
for themaxspeed:forward|:backward
tag?Goal
Make the hidden data visible in iD so users see the data right away in the fields section.
Why
When evaluating the safety of highway especially when looking at safe cycling maxspeed is super important. We have quite a few roads between villages that have different speed limits for forward/backward. Right now, this data is hidden in ID, which results in mappers missing it and wrongly edit the maxspeed instead.
Status Quo
What would we need…?
directionalCombo
was introduced. Right now, the maxspeed field is of"type": "roadspeed"
, which we cannot configure as part of thedirectionalCombo
— Next step: Add measurement field type ideditor/schema-builder#15maxspeed=123
when both directions have the same value). Ideally the UI would have a button which optionally splits the field in two.maxspeed
,maxspeed:forward
,maxspeed:backward
with maxspeed being the more conservative of the two. AFAIK this is done to be backward compatible to data consumers that do not yet look at the split version of the tags. — Cases via OverpassThe text was updated successfully, but these errors were encountered: