#18951 closed enhancement (fixed)
deprecate water=riverbank in favor of water=river
| Reported by: | Klumbumbus | Owned by: | team |
|---|---|---|---|
| Priority: | normal | Milestone: | 20.03 |
| Component: | Core validator | Version: | |
| Keywords: | Cc: |
Description (last modified by )
No panic. water=riverbank not waterway=riverbank.
Attachments (0)
Change History (6)
comment:1 by , 6 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
comment:2 by , 6 years ago
| Description: | modified (diff) |
|---|
follow-up: 4 comment:3 by , 6 years ago
Replying to Klumbumbus:
No panic. water=riverbank not waterway=riverbank.
But it is close and who says that water=river was meant and not waterway=riverbank? e.g. no autofix and suggesting both would be better or do you have a deeper analysis available?
comment:4 by , 6 years ago
Replying to skyper:
who says that
water=riverwas meant and notwaterway=riverbank?
They are duplicates, with water=river being the newer one which will replace waterway=riverbank.
do you have a deeper analysis available?
https://taghistory.raifer.tech/#***/waterway/riverbank&***/water/river
comment:5 by , 6 years ago
Does it also add natural=water (together with water=river) ? As otherwise water=river does not mean much.



In 16173/josm: