[josm-dev] Possible bug in JOSM r3738

[Alan Mintz]

After uploading changeset 6860813, I realized that something didn't look 
right with the city boundaries*. Somehow, 31 nodes that were part of the 
boundaries were moved to 2 locations (15 to one location, 16 to another). 
In both cases, the locations to which they were moved were outside the bbox 
of the layer I was working on. I fixed those nodes, but puzzled as to how 
this happened.

Can someone think of a function in JOSM that would intentionally do this 
(i.e. maybe I pressed a wrong key)? Any ideas about how to find out if any 
other nodes were moved? The validator does not report any further relevant 
problems. Auditing the nodes manually is impractical, as there appear to 
have been about 600-700 nodes that changed position.

*Actually, when attempting to upload, the validator warned me about the dup 
nodes. At the time, I believe what I did was to look at the history of a 
couple of the nodes, saw that they had not been changed in the current 
layer, and so assumed that the problem happened previously and I decided to 
take care of it after finishing this changeset. It's possible that I made a 
mistake here (I was tired), or that it really did not show me the change 
correctly.

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