Thanks! I can see where you are coming from. If we assume that the oneway
tag only ever applies to vehicles and that it is nothing more than a translation into OSM tagging of a traffic sign that, as traffic signs do, only applies to vehicles, then of course a one-way hiking path in the mountains with the oneway
tag has simply been tagged wrong and needs to be corrected.
This is precisely the opposite of the argument that @SomeoneElse is making: that oneway
on a footway
for a one-way hiking path is perfectly fine (unless there is also a bicycle=yes
or similar, then it becomes ambiguous).
We discussed this quite a lot in other thread and a lot of examples came up and I came to the conclusion that there is no clear majority for either view, so I am proposing a compromise: Avoid using oneway
on footway
and path
altogether, and use a more specific tag wherever possible. But which one is the more specific tag that we should recommend? That’s what this poll is about.
That’s exactly what I am trying to address. Ideally when someone tags highway=footway bicycle=yes oneway=yes
, or when someone looks at a way that has been tagged like this, I’d like to see a validator warning pop up that says “Are you sure? The oneway tag is ambiguous. Use oneway:bicycle
and [either oneway:foot
or foot:backward
] to specify one way restrictions for each mode of transport separately."
But for that we should have some consensus in the community first (hence the proposal idea). Let me know what you think! (For comments on whether such a proposal is a good idea at all, the other thread is probably best.)