On Mon, Apr 27, 2009 at 12:36 AM, Mike Harris <[email protected]> wrote:
> Karl > > Thanks for this - I'm no longer a programmer (since about Fortran H!) but > this makes sense and is consistent with a couple of tests I ran trying to > delete and undelete some nodes. Thanks, too, for cross-posting to josm-dev - > I didn't know about that list or would have done it myself as it does begin > to look as though the problem may be as much with a josm/api6 > incompatibility as with api6 per se. Hope the josm gnomes can come up with > an answer so that I can get back to mapping - quite a backlog waiting to be > processed and then uploaded but have processed this particular data set > three times now and that's getting boring! > > Mike Harris > > I did take a look at the code, and my initial impression appears to be correct--it looks like the version number of the downloaded (conflicting) entity is not being copied to JOSM's working version of the entity so it uses the old version number, which causes a version number mismatch when you try to upload it. I don't know the JOSM data model very well, though, so I could be wrong. I think the fix could be as simple as adding a line in ConflictResolveCommand.java to copy the version from the downloaded entity. I don't have time to test it myself, though... Karl _______________________________________________ josm-dev mailing list [email protected] http://lists.openstreetmap.org/listinfo/josm-dev
