Mechanical Edits/arrival-spring/Moving maxspeed conditions to conditional
Page content created as advised on Automated_Edits_code_of_conduct#Document_and_discuss_your_plans.
Who
I, arrival-spring using my account
contact
Message via OSM, I will be notified about incoming PMs via email and notifications in OSM editors.
What
Retagging all of the following to Conditional restrictions
- maxspeed:seasonal:winter=* to @ winter (3707 uses), voted as deprecated
- https://www.openstreetmap.org/changeset/140646286
- :forward https://www.openstreetmap.org/changeset/140646726
- :backward https://www.openstreetmap.org/changeset/140646797
- maxspeed:backward:seasonal:winter https://www.openstreetmap.org/changeset/140646926
- maxspeed:winter to @ winter (213 uses)
- seasonal:winter:maxspeed to @ winter (123 uses)
- maxspeed:seasonal:summer to @ summer (153 uses)
- maxspeed:summer to @ summer (11 uses)
- maxspeed:wet to @ wet (870 uses)
- https://www.openstreetmap.org/changeset/140549860 except for =RU:rural and traffic signs
- :forward https://www.openstreetmap.org/changeset/140647108
- :backward https://www.openstreetmap.org/changeset/140647216
- :lanes https://www.openstreetmap.org/changeset/140647287
- maxspeed:children_present to @ children_present (924 uses)
- https://www.openstreetmap.org/changeset/140546631 all remaining uses are on traffic signs (or nodes with no feature tag, probably signs)
- :forward https://www.openstreetmap.org/changeset/140646589
- maxspeed:flashing to @ flashing (52 uses)
- Not done, all elements are traffic_sign=maxspeed
- maxspeed:snow to @ snow (14 uses)
Additionally, some of these have directional suffixes, so e.g. maxspeed:wet:forward would be moved to maxspeed:conditional:forward = * @ wet
Some also have source prefix or suffix, these will be checked and moved as appropriate.
Some objects already have maxspeed:conditional, for those it would be checked if it is duplicating and if so then the redundant tag removed. If the condition is for something else then the values would be concatenated, see the examples section. In case of mismatch then object would not be edited but OSM note left instead.
Why
maxspeed:conditional=* is a standard way to map conditional restrictions that is used and supported by many data consumers and editors. No support has been found for any of these tags
Direct reason
During work on https://github.com/streetcomplete/StreetComplete/issues/4282 I was reviewing top taginfo values for speed limit keys ( https://taginfo.openstreetmap.org/search?q=maxspeed#keys ) and wanted to make sure that existing data was parsed and retained. It is easier to deal with one standard way of tagging conditional restrictions than many (possibly conflicting) keys.
Numbers
Between 6000 and 7000 objects are expected to be edited.
How
Example 1:
state before a mechanical edit:
state after a mechanical edit:
Example 2:
state before a mechanical edit:
state after a mechanical edit:
Example 3:
state before a mechanical edit:
state after a mechanical edit:
Changeset would be described and tagged with tags that mark it as automatic, provide link to this page etc. It would include at least
- mechanical=yes
- discussion:page=https://wiki.openstreetmap.org/wiki/Mechanical_Edits/arrival-spring/Moving_maxspeed_conditions_to_conditional
There would be one changeset per original key.
Edits would be conducted using JOSM.
Discussion
Forum discussion - https://community.openstreetmap.org/t/should-keys-like-maxspeed-wet-be-discouraged-and-maxspeed-conditional-used-instead/99783
Repetition
Redoing this edit in the future would be treated as a new mechanical edit with a new approval process.
Opt-out
Please comment in the discussion thread (see #Discussion).