Support maxspeed:forward|:backward

[tordans]

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

• https://www.openstreetmap.org/edit?way=339558638
• More https://overpass-turbo.eu/s/1xVi

Description

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.

Status Quo

• Field maxspeed:forward/:backward #966 is a quick test on this topic
• Example Road with maxspeed:forward/backward https://pr-966--ideditor-presets-preview.netlify.app/id/dist/?way=339558638#background=Bing&disable_features=boundaries&id=w148117208&locale=en&map=19.02/52.43775/13.50665
• Example Road just with maxspeed https://pr-966--ideditor-presets-preview.netlify.app/id/dist/?way=339558638#background=Bing&disable_features=boundaries&id=w1111029439&locale=en&map=19.02/52.43762/13.50627

What would we need…?

• 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