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

[Tomas Straupis]

2021-02-11, kt, 17:34 Dave F rašė:
> IT "experts" can write code to suit all variations.

  I see I need to clear up the difference between IT experts and coders.
  If we take an analogy of building a city:
  IT expert <-> architect, urban planner
  coder <-> brick layer
  Anybody can learn to code and quickly. Ant it takes years of
practice to become an IT expert.
  You will hardly get a good cathedral if you allow brick layer to do A to Z :-)

  Coder is rushing to write all code and everywhere. But it takes an
IT expert to know essential thing: when and where NOT to write code.

  We're not talking about technical minor things such as code here.
We're talking about practices, processes, rules, continuity,
usability, direction etc.

> Which "QA tools, data export tools, maps, web applications, blogs" are
> you maintaining which don't deal with both schemas?

  When you will answer my question I will be able to provide my list :-)
  The point is that people who do have to create/maintain those things
understand that changing is much more than "two hours in JOSM".

>>    What is a BENEFIT of changing waterway=riverbank to water=river when
>> it marks exactly the same features?
> I'm really surprised an IT expert can't see the data manipulation
> benefits of all water features are covered by the same tags.

  This would only be beneficial from coding perspective if you would
NEED those features to be covered by the same tags. But in GIS/Carto
you do NOT want to combine riverbanks with lakes/reservoirs or ponds,
or basins.

  And secondary point: coding perspective is not important. Coders
must adapt to business requirements not the other way round. That is
one of "IT basics" :-)

-- 
Tomas