-
Notifications
You must be signed in to change notification settings - Fork 819
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move loose bollards to z19 #2756
Comments
Do you have an example where this is a problem? |
You'd have to do something similar to the turning circle logic |
Here's a row of loose bollards, for example: http://www.openstreetmap.org/node/3102111067#map=17/52.22842/21.00874 |
I'd like to revive this issue. Loose bollards are still shown much too early. This does neither reflect their size nor their importance. |
sent from a phone
On 8. Oct 2018, at 07:53, Michael ***@***.***> wrote:
I'd like to revive this issue. Loose bollards are still shown much too early. This does neither reflect their size nor their importance.
what do you mean by „loose“? Is there a difference between a fixed bollard and a removable one, for a normal map user (i.e. someone not autorized to remove the bollard)?
Should we distinguish between strong bollards and those you can run over with only light damage?
When speaking about size, should we treat bollards differently according to their diameter?
|
sent from a phone
On 8. Oct 2018, at 07:53, Michael ***@***.***> wrote:
I'd like to revive this issue. Loose bollards are still shown much too early.
maybe barrier=bollard is not the right tag for something that doesn’t block a highway?
|
"Loose" means here "not a node included in some road". Typically they block the access to the sidewalk.
Map user would never be sure - it's just a warning that the road might be not passable. However for this we have access tag and it's better visible. |
Since when are |
It would be good to show bollards which are not part of the road later (z16->z19) to not clutter the map. How could I select loose/road bollards using SQL?
The text was updated successfully, but these errors were encountered: