|
I have a large changeset that JOSM refuses to upload because of a "precondition error". It tells me there is a problem with "way id:230281711 because the node with id:4226001328 either does not exist or is not visible". The node does exist and is visible but nevertheless JOSM will not accept the upload. I have quite a bit of work invested in that changeset and would really like to salvage it if possible. However, I got frustrated the other night and saved my work in an OSM file to work on it the next day. But now the individual changes are no longer available in the command window or anywhere else that I can see. Is there any way to dissect an OSM file to see what changes might be there? And why oh why didn't JOSM present me with a conflict resolution dialog? I have a feeling nobody knows these answers but I remain hopeful I can resurrect my work somehow. Thanks, Dave |
|
I think File->Update data should trigger JOSM to generate the conflicts. Don't have a broken changeset to test with at the moment. If that doesn't work, I think searching for the way using the id and purging it should allow the upload to proceed. Purge is under the edit menu, select the way before selecting the menu item. Since you have the edits saved to a file, it's "safe" to try both things. Just delete the layer and reopen if it seems things have gone further sideways. 2
Wow, you are a lifesaver Max. After updating my data as you suggested a conflict dialog resulted with only one conflict listed. It still wouldn't accept my upload after that but, grabbing at straws, I selected & updated a few of the important individual objects I had worked on and then tried another upload. Finally JOSM accepted it and my work was saved. Usually I hate seeing the Conflict Dialog box appear but this time it was most welcome. I'm still wondering why JOSM did not generate a Conflict when it encountered this error. Without that one has no way to fix the error. Thanks a ton for your insight. It saved a ton of work for me. Dave
(12 Jun '16, 23:27)
AlaskaDave
|
