[OSM-talk] Suggested mass edits

Mateusz Konieczny matkoniecz at tutanota.com
Tue Apr 20 10:38:11 UTC 2021


Note that reporting mhat makes sense only of it is caused or preventable by JOSM
and JOSM is not warning about invalid data.


Apr 20, 2021, 10:31 by pangose at riseup.net:

> Interesting.  Could you open a ticket on the JOSM bugtracker about this?
>
> Martin Machyna <machyna at gmail.com> skrev: (20 april 2021 00:14:04 CEST)
>
>> Just following up on this. I ran it on all changesets and the winner is 
>> definitely JOSM
>>
>> JOSM/1.5 29952
>> iD 2948
>> Potlatch 1820
>> Vespucci 243
>> Go 112
>> Merkaartor 98
>> reverter;JOSM/1.5 59
>> osmtools/30252 12
>> FixTypo7 4
>> Globe 2
>> ID 2
>> Sun 1
>> Osmose 1
>> egeotechindia 1
>> By 1
>> Holzer 1
>> osmapis/0.9.3 1
>> GNU 1
>> PushPin 1
>> osm-mechedit-fix-addr 1
>> osm2go 1
>>
>>
>> On 18.4.21 6:34 , Frederik Ramm wrote:
>>
>>>  Hi,
>>>
>>>  Another usual caveat is:
>>>
>>>  If these buggy objects appear in clusters, they might hint at a deeper 
>>>  problem. Are many of them created by the same user(s) or by the same 
>>>  editor(s)? If that is the case, more research might be appropriate so 
>>>  that editors or workflows can be improved. Sometimes analysis of the 
>>>  broken data can also point to a broken import or mass edit that has so 
>>>  far been undetected and will, upon closer look, have more problems 
>>>  than just these obvious ones. In such a situation, simply deleting the 
>>>  buggy objects will remove the "red flags" that would otherwise have 
>>>  pointed at the broken import or mass edits.
>>>
>>>  Bye
>>>  Frederik
>>>
>>
>> talk mailing list
>> talk at openstreetmap.org
>> https://lists.openstreetmap.org/listinfo/talk
>>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk/attachments/20210420/76a425ee/attachment.htm>


More information about the talk mailing list