[Tagging] Deprecation - waterway=riverbank vs water=river
Dave F
davefoxfac63 at btinternet.com
Thu Feb 11 15:34:34 UTC 2021
On 11/02/2021 08:34, Tomas Straupis wrote:
> 2021-02-11, kt, 10:07 Marc_marc rašė:
>
> Do you think it is good for a project to accept decisions, which are
> counted as bad by IT experts?
IT "experts" can write code to suit all variations. They can also amend
code to suit any changes. It's not the purpose of OSM contributors to
work to those who refuse to change.
>
> How many QA tools, data export tools, maps, web applications, blogs
> have YOU created and are maintaining?
Which "QA tools, data export tools, maps, web applications, blogs" are
you maintaining which don't deal with both schemas?
>
> 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.
>> fragmentation is an issue, a major one because everybody
>> need to take care of both (or more) schemas.
> Yes, fragmentation is an issue. So lets prevent fragmentation in the
> first place.
The horse has bolted on that one. OSM is organic, when more adaptive
tagging techniques emerge they get adopted. I'm pretty sure when Steve C
first sat down to decide how to tag he started out with a basic list of
a couple dozen.
DaveF
More information about the Tagging
mailing list