[Tagging] Deprecation - waterway=riverbank vs water=river

[Martin Machyna]

How I see this is that  waterway=* are supposed to form interconnected 
network that can be used for navigating ships,.. analogous to what 
highway=* is for cars,...   On other hand water=* is for marking areas 
covered by water surface analogous to what area:highway=* is for roads.

So what should be deprecated is waterway=riverbank. But I don't 
understand why we are even discussing this, because the original 
proposal explicitly states that it deprecates waterway=riverbank, 
landuse=reservoir and landuse=pond. Ignoring this violates the "One 
feature, one OSM element" rule.


Martin


> Volker Schmidt voschix at gmail.com
>
> (I suppose you mean by "redundant" that they have the same meaning)
>
> >From the purely practical point of view:
> If they have the same meaning and one of them is used twice as much as the
> other and, in addition, it needs only one tag and the other one needs two,
> I would stick with waterway=riverbank .
> BTW waterway=riverbank is still today  JOSM preset
> The statement " `waterway=*` is predominantly used to indicate the the
> location and topology of flowing waters," is in contradiction with the
> actual use and the wiki page
> waterway is not only for flowing water, but also for
> waterway=dam|weir|lock_gate|dock|boat_yard|water_point|fuel|milestone|sluice_gate
>
> And for intuitivity, waterway=riverbank to me seems better than 
> water=river
>
> If we deprecate one of the two keys, what do we win: additional work for
> many mappers, because as soon as we edit data that contains a deprecated
> key we get a warning, so many that I simply ignore them regularly..
>
> A different thing would be an automated mass-edit, combined with a massive
> information campaign to all mappers, that they have to switch habits for a
> frequent tagging situation.
>
>