[josm-dev] Ideas for avoiding false duplicates merged

[Alan Mintz]

>On 7/15/2010 11:16 AM, Alan Mintz wrote:
>>At 2010-07-15 07:54, Nakor wrote:
>>>     Hello,
>>>
>>>Now and then some user use the JOSM validator plugin to blindly merge 
>>>duplicate nodes in good faith but leading to more problems than before 
>>>(i.e. linking a road to a waterway where a bridge should
>>>actually be). One of the idea I had is to refine the validator plugin to 
>>>sub-classified duplicates nodes in different categories:
>>>
>>>- duplicate nodes linked to highways (i.e. all nodes at the same 
>>>positions are ONLY linked to highways)
>>>- duplicate nodes linked to railways
>>>- duplicate nodes linked to waterways
>>>....
>>>- duplicate nodes linked to mixed types of ways
>>>
>>>If there is no strong opposition against it I am willing to look into it 
>>>an propose a patch. Let me know your thoughts.
>>
>>I'm having trouble thinking of a case where "duplicates" (two nodes that 
>>are near each other) should ever be merged automatically. The only common 
>>case seemed to be administrative boundaries (e.g. city limits), and there 
>>is significant opposition to merging these with road nodes.
>The one case I use it for is duplicate highways nodes near counties limit 
>int the US. Sometimes you'll have two overlapping 70 nodes ways and you 
>cannot simply delete one of them because of different connections on one 
>side or the other.

Don't these get caught by the overlapping ways warning? Or are you saying 
you want to use the fix button to automatically fix them? When I've fixed 
these dup ways, I've always needed to do it manually to get intersections 
and geometry correct.

--
Alan Mintz <Alan_Mintz+OSM at Earthlink.net>