On Fri, 7 Feb 2020 at 10:50, Christoph Hormann <o...@imagico.de> wrote:
> On Friday 07 February 2020, Peter Elderson wrote: > > E.g. if a solution would be to tag hedge areas as natural=hedge > > or landcover=hedge, then the change path would be for the renderer to > > temporarily render the old AND the new tagging, so mappers can edit > > the old tagging to the new tagging. > > We always try to avoid that because it never works towards a more > consistent tagging but only perpetualizes the use of both tags as > synonyms because mappers get feedback that both tags are correct. > All it takes is for editors to use the new synonym for its presets and to alert users when they edit an object with the old synonym with an offer to upgrade the tags. Like iD does for many other tags that have been obsoleted (like old bus stop tagging). Mappers DO get feedback about which tag is correct, at least in iD. This list regularly suggests things like replacing landuse=grass with landcover=grass, and proposes that editors make the appropriate changes. Then we give up on entirely sensible ideas because Carto insists on a "no synonyms" rule. Which leads me to say, frequently, that OSM doesn't do joined-up thinking. We could make this work very easily for landuse=grass. Existing objects, when edited for other reasons, would warn about outdated tags and the mapper would have the option to check iif the area is landcover=grass (grass is grown there for no purpose other than landcover) or if it's something like a meadow. For new objects, when the user types in grass then the editor would throw up a list of suitable presets for grass/meadow/whatever. It's all perfectly feasible, except "no synonyms." OSM doesn't do joined-up thinking. -- Paul
_______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
