-
Notifications
You must be signed in to change notification settings - Fork 831
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
drop rendering for waterway=wadi #1365
Comments
I agree that the tagging you propose is more generic and might be universally applicable for similar features, but I don't agree that the meaning in Arabic (valley) is a problem, there has been a definition in the wiki, and the key waterway does give enough context not to apply this tag to valleys cheers, |
It sounds like the tagging change and rendering change are occurring in the wrong order |
I agree. |
What would be a good point to drop rendering? Used less than 1k times? Currently it is used 18 343 times - http://taginfo.openstreetmap.org/tags/waterway=wadi |
Now 11 170 ways with this tag. |
Down to 6253 usages on ways now. |
Reopening since:
|
+1 for dropping. |
+1 for dropping If the feature is ambiguous and can mean two different things, the rendering will always be bad for at least one the these two meaning. |
This is the most compelling part for me. |
As discussed on tagging mailing list[a] and described on wiki[b] this tag is ambiguous. It may mean ephemeral river, valley, typical course of flash floods. What worse word wadi is used in multiple languages with multiple meanings. There are also additional problems.
It is recommended to use waterway=river/waterway=stream + intermittent=yes for waterways, natural=valley for valleys.
I am proposing to drop rendering of this tag.
[a] https://lists.openstreetmap.org/pipermail/tagging/2015-January/thread.html - thread "waterway=wadi problem"
[b] http://wiki.openstreetmap.org/wiki/Tag:waterway%3Dwadi
The text was updated successfully, but these errors were encountered: