-
Notifications
You must be signed in to change notification settings - Fork 824
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
golf=tee and golf=green should be changed to draw on top of golf=fairway #4147
Comments
It's not rendering that way because of the golf tags. Since none of them are currently implemented. It's because of how the other added tags are rendered in priority. |
OK then I suggest that tee box and putting green, get a slightly lighter shade of green, and be drawn on top. |
There's already a couple of issues open for rendering golf tags. I'll probably work on it myself when I get some free time soon. Maybe comment what you want in one of them. Since this will more then likely get lost when it's closed. |
? Tee box and putting green should get a slightly lighter shade of green than fairway, and be rendered on top? I'm not sure what else I might describe. Exactly like how sand traps are rendered right now, but lime instead of yellow, should be applied to putting green and tee box. |
What you see rendered in the area you linked to is landuse=grass and natural=sand, not golf=* tags. Hence this seems to be a duplicate of #661 - closing as such. |
Expected behavior
"Golf Course Tee Box" and "Golf Course Putting Green" should draw on top of "Golf Course Fairway"
"Golf Course Sand Trap" already renders on top of "Golf Course Fairway", as one would expect.
Actual behavior
"Golf Course Fairway" draws on top of "Golf Course Tee Box" and "Golf Course Putting Green", defeating the point, and requiring very bad workarounds such as what you can see at https://www.openstreetmap.org/edit#map=17/37.42721/-122.43336
Links and screenshots illustrating the problem
https://www.openstreetmap.org/edit#map=17/37.42721/-122.43336
The text was updated successfully, but these errors were encountered: