[Tagging] Landcover... not again?....!
Mateusz Konieczny
matkoniecz at tutanota.com
Fri May 6 09:45:47 UTC 2022
May 6, 2022, 10:52 by dieterdreist at gmail.com:
>
>
> sent from a phone
>
>> On 6 May 2022, at 10:32, Marc_marc <marc_marc at mailo.com> wrote:
>>
>>> The main objection against the proposed landcover key was that massive retagging of the enormous installed base is not going to happen, mainly
>>>
>>
>> if there was a will to do it, it would be 2x1h to put it in automatic
>> in iD/josm and assimilated and/or make a mecanical edit
>>
>
>
> I am not advocating an automatic edit, but with render support the key would be adopted, this is already demonstrated by the 300.000 uses even without support by any notable data consumer. Most/many people are not interested in using tags that have no effect in the “main” applications like OpenStreetMap carto (or routing, with respect to different tags). Also lots of people just use presets. If carto would add support for landcover, editing apps would likely add presets.
>
That is wrong order, OpenStreetMap Carto should not be used as a hammer to
force editors to adapt tagging.
For example landcover=trees tagging was soundly rejected by JOSM and iD developers
https://github.com/gravitystorm/openstreetmap-carto/issues/2548
https://josm.openstreetmap.de/browser/josm/trunk/data/validator/ignoretags.cfg?rev=11949
And also OSM Carto developers
https://github.com/gravitystorm/openstreetmap-carto/issues/2548
(yes, including me)
Note also that proposal was never brought to a vote by its authors
since it was created in 2010, presumably because it does not have a
clear support.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tagging/attachments/20220506/0dd3e0b5/attachment.htm>
More information about the Tagging
mailing list