<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<div><br></div><div><br></div><div><br></div><div>Jul 28, 2022, 10:16 by phil@wyatt-family.com:<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div class=""><p class=""><span style="mso-fareast-language:EN-US">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?</span><br></p></div></blockquote><div dir="auto">Tens of thousands refers to cases where human judgment is required.<br></div><div dir="auto"><br></div><div dir="auto">Where I see cases popular and clear enough to expose them to humans<br></div><div dir="auto">then I implement validator code or propose improvements.<br></div><div dir="auto"><br></div><div dir="auto">For example recently I implemented <a href="https://josm.openstreetmap.de/ticket/22102" rel="noopener noreferrer" target="_blank">https://josm.openstreetmap.de/ticket/22102</a><br></div><div dir="auto">which complains about more clear mismatches between track and surface,<br></div><div dir="auto">and created equivalent for StreetComplete in <br></div><div dir="auto"><a href="https://github.com/streetcomplete/StreetComplete/pull/4105">https://github.com/streetcomplete/StreetComplete/pull/4105</a><br></div><div dir="auto">taylor.smock reviewed and merged JOSM patch, SC one will likely be merged soon.<br></div><div dir="auto"><br></div><div dir="auto"><a href="https://github.com/openstreetmap/id-tagging-schema/issues/531">https://github.com/openstreetmap/id-tagging-schema/issues/531</a><br></div><div dir="auto"><a href="https://github.com/openstreetmap/id-tagging-schema/issues/547">https://github.com/openstreetmap/id-tagging-schema/issues/547</a><br></div><div dir="auto"><a href="https://github.com/openstreetmap/iD/issues/9209">https://github.com/openstreetmap/iD/issues/9209</a><br></div><div dir="auto">are improvements to handling unspecific values such as barrier=yes<br></div><div dir="auto">in iD, partially implemented by Martin Raifer<br></div><div dir="auto"><br></div><div dir="auto"><a href="https://github.com/openstreetmap/id-tagging-schema/issues/533">https://github.com/openstreetmap/id-tagging-schema/issues/533</a> <br></div><div dir="auto">was also recently implemented and should reduce popularity of<br></div><div dir="auto">some specific mistagging type.<br></div><div dir="auto"><br></div><div dir="auto">See <br></div><div dir="auto"><div dir="auto"><a target="_blank" rel="noopener noreferrer" href="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">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</a><br></div><div dir="auto">for JOSM validator improvements that I suggested and which were implemented.<br></div><div dir="auto"><br></div><div dir="auto">But some cases are better handled by bot edits.<br></div></div> </body>
</html>