-
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
Toboggan not rendered #2858
Comments
How should it look like in your opinion? It's not obvious to me. We don't render many other sports because of that - golf is an exception. |
No raceway is for motor vehicles and is clearly wrong here. |
leisure=track sounds plausible, so it was a bit short-sighted from the editor of the way cited in the first picture to remove the physical tag from the feature without providing a better one. |
Tagging has been improved in both cases - but now we depend on Rendering leisure=track on lines #2632 :-( |
@kocio-pl Rendering of a summer toboggan could be a medium dark grey line with dots. It may be be a bit broader than an aerial cableway and the dots (round, not squared?) could be less visible as those of an aerial cableway. But I am not an expert in map designing! |
@kocio-pl I think the rendering should be based on the attraction=summer_toboggan attribute not on sport=toboggan. As sport=* is an non-physical tag it is probably okay not to be rendered. The summer_toboggan is a big and good visible structure. |
@HolgerJeromin leisure=track did not help. Do you think that should be rendered? |
We have #2632 for that |
So I close my own issue. Thanks. |
At http://www.openstreetmap.org/#map=17/46.91400/13.86941
there is a toboggan http://www.openstreetmap.org/way/55284714 in the database
and it is not rendered. I think it should be rendered.
There is another one which has the extra tag "highway=raceway" and I suppose that is why its rendered:
See http://www.openstreetmap.org/way/40454225
According to https://wiki.openstreetmap.org/wiki/DE:Tag:sport=toboggan the extra tag should maybe not be there.
The text was updated successfully, but these errors were encountered: