<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<div>Note that reporting mhat makes sense only of it is caused or preventable by JOSM<br></div><div>and JOSM is not warning about invalid data.<br></div><div><br></div><div><br></div><div>Apr 20, 2021, 10:31 by pangose@riseup.net:<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div>Interesting. Could you open a ticket on the JOSM bugtracker about this?<br></div><div><br></div><div class=""><div>Martin Machyna <machyna@gmail.com> skrev: (20 april 2021 00:14:04 CEST)<br></div><blockquote style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;" class=""><pre class=""><div>Just following up on this. I ran it on all changesets and the winner is <br></div><div>definitely JOSM<br></div><div><br></div><div>JOSM/1.5 29952<br></div><div>iD 2948<br></div><div>Potlatch 1820<br></div><div>Vespucci 243<br></div><div>Go 112<br></div><div>Merkaartor 98<br></div><div>reverter;JOSM/1.5 59<br></div><div>osmtools/30252 12<br></div><div>FixTypo7 4<br></div><div>Globe 2<br></div><div>ID 2<br></div><div>Sun 1<br></div><div>Osmose 1<br></div><div>egeotechindia 1<br></div><div>By 1<br></div><div>Holzer 1<br></div><div>osmapis/0.9.3 1<br></div><div>GNU 1<br></div><div>PushPin 1<br></div><div>osm-mechedit-fix-addr 1<br></div><div>osm2go 1<br></div><div><br></div><div><br></div><div>On 18.4.21 6:34 , Frederik Ramm wrote:<br></div><blockquote style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;" class=""><div> Hi,<br></div><div><br></div><div> Another usual caveat is:<br></div><div><br></div><div> If these buggy objects appear in clusters, they might hint at a deeper <br></div><div> problem. Are many of them created by the same user(s) or by the same <br></div><div> editor(s)? If that is the case, more research might be appropriate so <br></div><div> that editors or workflows can be improved. Sometimes analysis of the <br></div><div> broken data can also point to a broken import or mass edit that has so <br></div><div> far been undetected and will, upon closer look, have more problems <br></div><div> than just these obvious ones. In such a situation, simply deleting the <br></div><div> buggy objects will remove the "red flags" that would otherwise have <br></div><div> pointed at the broken import or mass edits.<br></div><div><br></div><div> Bye<br></div><div> Frederik<br></div></blockquote><div><hr>talk mailing list<br></div><div>talk@openstreetmap.org<br></div><div><a href="https://lists.openstreetmap.org/listinfo/talk" rel="noopener noreferrer" target="_blank">https://lists.openstreetmap.org/listinfo/talk</a><br></div></pre></blockquote></div></blockquote><div><br></div> </body>
</html>