-
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
Playhouse not rendered in park #4816
Comments
I asume you mean this node:
|
Indeed, that is: a couple around there. I had not found the other issue/pull-request. |
Closing this as the specific request to selectively render #3161 was closed with the decision not to render playground details. We could revisit that decision in light of how widely these are meanwhile mapped (https://taginfo.openstreetmap.org/keys/playground#overview) and how meaningful these can be for a significant part of our target users base (kids and families with kids) and that we have an increasing interest in developing the high zoom levels (#4661). For this to actually have a chance (in particular in light of #3635) a concrete and viable design concept would be needed. Just dumping a number of additional POI symbols into the system - like #3161 attempted - is not likely going to find approval. What is necessary here is some solid, holistic design work with outside-the-box thinking (compare for example also #844). Anyone who wants to work on that should feel welcome to open a new issue. And for those who want to contribute but do not have the design skills - working on #3880 would help a lot here as well. |
For clarity. |
We are rendering (and have rendered since version 1.0) https://imagico.de/map/styleinfo/#style=osmcarto§ion=tags&key=leisure&value=playground We have never rendered any |
Here is an example of inconsistent behaviour in a park.
https://www.openstreetmap.org/#map=19/52.16277/4.47963
The text was updated successfully, but these errors were encountered: