-
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
waterway=stream + tunnel=flooded isn't rendered as a tunnel #5006
Comments
Thanks for the suggestion.
We render Closing this as wontfix/duplicate of #3179 - since we made the decision in #4087 to selectively only support As said before a more comprehensive look at the whole artificial water infrastructure domain and how to render this in a consistent and differentiated fashion would be very desirable - see in particular #3180, #3354, #4405 and #4087 (review) |
I don't understand how you can defend the idea that something tagged as There are very legitimate cases of |
We render tags, not keys. And i have explained that currently As said there are <1000 uses of that tag combination, there is no documentation on what this combination is supposed to mean, You have provided no example of how the tag is used in a distinctly meaningful way or a description of how you think the tag should be used that we are supposed to support with our rendering. That IMO leaves zero basis to even consider supporting it at this time. Regarding rendering of |
This is a small flooded tunnel coming from a small dam that diverts part of a small stream into an artificial lake. |
I don't think it is anywhere close to global consensus to map penstocks as |
You're right, it should be a canal because it's artificial, but since it's only a fraction of a stream less than a meter in width, the current rendering isn't appropriate. I think the tunnel is 0.3m in width. |
waterway=stream + tunnel=culvert ✔️
waterway=canal+ tunnel=flooded ✔️
waterway=stream + tunnel=flooded ❌ is rendered as a normal stream, should be tunnel
The text was updated successfully, but these errors were encountered: