Open boothym opened 3 years ago
JFYI, tagging topics are managed at https://github.com/openstreetmap/id-tagging-schema/issues nowadays. Once this project is actively maintained again, I think this issue will be moved there (moving issues is IMO better than creating a duplicate).
The way I understand you suggestion is, to replace direction
with priority
, which would be deprecating direction
in favor of priority
. Ideally with an "outdated tag" suggestion in iD.
Personally, I think this is a valid point. I used direction
in the sense that priority
is defined today. And I think that was the intend why it was added in 2016 (link below).
It would also allow to add deprecations / tag-update-alerts for the alternative tagging schema of
traffic_calming:right=choker
=> traffic_calming=choker + priority=left
traffic_calming:left=choker
=> traffic_calming=choker + priority=right
…:forward
, …:backward
, …:right
, …:direction
, backward:traffic_calming
Some more research:
priority
was added in 2017 to the wiki page traffic_calming
https://wiki.openstreetmap.org/w/index.php?title=Key%3Atraffic_calming&type=revision&diff=1505748&oldid=1504593priority
was added in 2021 to the wiki page traffic_calming=choker
https://wiki.openstreetmap.org/w/index.php?title=Tag%3Atraffic_calming%3Dchoker&type=revision&diff=2110683&oldid=689876xtdirection
was added to the preset in 2016 https://github.com/openstreetmap/iD/commit/72d16fd76dfec396194e4f8794f105297607bd73Some images for reference:
Update to my last comment: We talked about this in a OSM Community Meetup in Berlin.
I am not so sure about this change now. Here is why:
The priority key is described as something that is signed with a sign (https://wiki.openstreetmap.org/wiki/Key:priority). That is not the case for most choker we have inside the city of Berlin.
If we migrated direction
to priority
, we would change this implicit information. Right now, we can assume that a node with priority
also has a sign. But we cannot do the same for direction
.
This leads to more thinks to consider:
The sign could say "right lane may drive first" but the choker could be on either the right or the left. There are probably rules per country which direction should go first … and a few exceptions from this rule.
The local rules that translate priority to the position of the choker (given only one side has it), is probably different per country (especially countries that primarily use the left/right lane). So there is no easy path to migrate from the old to the new.
Considering those topic, I think direction is a fine. It give a clear information about the layout of the street and leaves it to the router to know the local rules. And a mapper could always add the priority
or (IMO even better) traffic_sign
key for additional information.
Perhaps this is better illustrated with an example of a choker in Scotland/UK: https://www.mapillary.com/app/?pKey=290824359298218
In this case the node would be tagged as priority=forward, following the direction of the way of course.
What should the direction tag value be? Because the "choking" applies to both directions of traffic, adding this tag doesn't seem right to me (or at least, it is redundant).
As for chokers in Berlin without any priority - wouldn't the tag just not be used in that case?
The preset currently has a direction=* field - which seems a bit redundant as a choker affects both directions by definition.
Having a field for the priority=* tag instead would be better, especially if there was a way to visually indicate which direction has priority.