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

[Tomas Straupis]

2021-02-11, kt, 15:26 rašė:
> The redefinition of "deprecation" in the proposal is rather confusing,
> but I don't think it matters, nor has it been the premise of this
> thread. Whether it has been (properly) "deprecated" and there is a
> transition period or whether it has been "added", the current
> situation is such that with ~150k vs ~250k occurrences of the
> respective tags, an improvement is desireable.

  Sorry, what? :-) Numerous people are saying that proposal DID NOT
deprecate ANYTHING. Therefore even those who think that wiki proposals
are valid would have to agree that there was no depreciation.
  waterway=riverbank is almost twice as popular, but still you propose
to simply go and remove waterway?

  On what grounds? What is the logic here?

  I'm against pointless changes of tags in principle. We have river
polygon with waterway=riverbank and we have exactly the same with
water=river. Pointless addition of duplicate tag water=river.
Therefore water=river must be removed as it is a duplicate and it is
less popular.

  No value for consumers. While combining lakes and reservoirs into
one natural=water might be ok for most maps, adding riverbanks in to
the mix would definitely be bad for consumers. For example you will
not want to render labels for riverbank polygons (you put them on
centerlines). Also at middle scales you can remove polygons and use
only generalised centerlines in order to reduce clutter but at the
same time you will still render lakes/reservoirs.

-- 
Tomas