Open k-yle opened 1 year ago
I think this is an artifact from old "red private footway" rendering which was removed a few years ago in #2257
A grey arrow on a grey pattern is going to be hard to see. It seems low quality information to render if the way is not public. Are these actually useful cases? The main use of oneway footway is surely to manage traffic volumes, which shouldn't be an issue for private access?
The first example looks like an implied oneway from say an emergency exit, i.e. the way itself can be traversed in both directions - it is the exit itself that is oneway.
In other examples, the access information is poor: the RHS Wisley footway has: access=private
, foot=yes
, highway=footway
, which is confusing the renderer.
Drop rendering of oneway arrow if the path will be rendered as private access? It doesn't fix the access tagging problem, but at least looks better.
Are these actually useful cases? The main use of oneway footway is surely to manage traffic volumes, which shouldn't be an issue for private access?
This is a common real world occurrence. Like in amusement parks for example - or other privately managed tourist destinations.
Surely access=private relates to whether a way is accessible to the general public, not the ownership of the operation? access=customers would be the more correct tagging in the case of amusement parks etc.
A footway that is coloured in grey (due to
access
tags) should probably have grey oneway arrows?I think the current colour is a bit confusing, since it's rather different to the path itself
view map ↗ view map ↗
view map ↗ view map ↗
view map ↗ view map ↗