-
Notifications
You must be signed in to change notification settings - Fork 827
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
Spring icon invisible under waterway=river #3253
Comments
Would you like to prepare the code solving this problem? |
I haven't understood the reason yet. The icon is supposedly painted above the water layer, so I don't understand why both the darker blue and the white halo remain invisible. Or my analysis is wrong. |
Things were getting more mysterious. There are examples, where the icon is rendered when surrounded (or on the border of) natural=water, and some where not. The reason however is simple: the icon is covered by the waterway=river line, which is typical for larger springs. When attached to a stream on the other hand, the icon is wider than the stream line. Shown: These examples reveal another oddity: within a lake, the spring icon appears to have a blue middle dot. This however is the blue from the lake looking through the transparent centre of the icon. Not shown: Just on a river, no water body around: Queries: So, to conclude, the easiest solution would be to give up the rendering under waterways and move the icon layer above them... |
Beware that the spring layer was added below the waterways on purpose, to make the last interrupt the spring outline and suggest that the water outputs from the spring. What you are describing here seems merely a size problem between the river way width and the spring icon size. Typically, springs output a stream and not directly a river, and that shows no such problem AFAIK, so changing the fundamental design of the icon for this issue, which seems a corner case to me, sounds overkill. Please note that I took part in the new spring rendering, so I cannot affirm that this answer is objective enough. |
I ran across another case of this: https://www.openstreetmap.org/#map=18/47.53435/-111.23012 I don't think it's that much of a corner case, |
Corner case was not the right term here; I meant that the case of a river outgoing from a spring is a reduced subset of all springs, and, therefore, should not be the sole reason to trash the new design, which works for a vast majority of cases. |
Small springs output a stream, big springs output a river. 13 cubic meters per second from Big Spring in Missouri fail the OSM definition of jumping over a stream. Something that works on the majority of small cases but fails on the prominent ones is a bug for me. During my search above I have found plenty cases where the spring is not connected to a waterway at all, so to expect that the waterway is part of the icon message is inconsistent. I know it was intentional, but as it leads to inconsistency, I suggest to drop it. I'd also like to close the transparent middle of the icon as it leads to another inconsistency. Filling with blue creates a nice circular 'wave ripple' effect, you can study that on springs in water bodies that are not covered by a river. |
This design was rejected because of risk of confusion with other water features, which could ultimately lead to mistagging. |
I think this ticket could be closed, since implementing #3461 would resolve also this problem: |
Well, but close it at the time the other one is implemented, not because it will be implemented. |
Fixed by #3738 |
The spring icon was recently refurbished as a blue ring with a white halo #3189.
Unfortunately this was not tested when surrounded with a body of water, which is a common case for a spring. Example: Big Spring Missouri, mapped as a node in a body of water. The old 'S' icon was visible, see example in comment. The new one is not:
![204155](https://user-images.githubusercontent.com/8266355/40260580-b57bbe2a-5afb-11e8-8032-1aad2a4a5e7c.png)
The ring is defined slightly darker than water colour and has a halo, so it is not clear to me why it is completely invisible. I had done some analysis so far (from #3189):
The text was updated successfully, but these errors were encountered: