[OSM-talk] Proposed bot edit: remove "surface=no data" and other useless surface values

[Mateusz Konieczny]

Jul 28, 2022, 10:16 by phil at wyatt-family.com:

>
> Given you are finding ‘tens of thousands’ of these issues are bots the best way or would it be better to concentrate on the editors and validators to ensure they don’t reoccur?
>
>
Tens of thousands refers to cases where human judgment is required.

Where I see cases popular and  clear enough to expose them to humans
then I implement validator code or propose improvements.

For example recently I implemented https://josm.openstreetmap.de/ticket/22102
which complains about more clear mismatches between track and surface,
and created equivalent for StreetComplete in 
https://github.com/streetcomplete/StreetComplete/pull/4105
taylor.smock reviewed and merged JOSM patch, SC one will likely be merged soon.

https://github.com/openstreetmap/id-tagging-schema/issues/531
https://github.com/openstreetmap/id-tagging-schema/issues/547
https://github.com/openstreetmap/iD/issues/9209
are improvements to handling unspecific values such as barrier=yes
in iD, partially implemented by Martin Raifer

https://github.com/openstreetmap/id-tagging-schema/issues/533 
was also recently implemented and should reduce popularity of
some specific mistagging type.

See 
https://josm.openstreetmap.de/query?status=closed&resolution=fixed&component=Core+validator&reporter=~mkoniecz&max=1000&col=id&col=summary&col=status&col=component&col=type&col=priority&col=milestone&col=time&report=2&order=id
for JOSM validator improvements that I suggested and which were implemented.

But some cases are better handled by bot edits.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk/attachments/20220728/a60db1c1/attachment.htm>