|
I downloaded a section of the OSM map from http://download.geofabrik.de/north-america.html that was only 20 hours old and I was using JOSM to move tags from a POINT to a underlying POLYGON and then deleted the POINT. When I tried to UPLOAD, I got the error "Uploading failed because the server has a newer version of one of your nodes, ways, or relations. Click Synchronize entire dataset to synchronize the entire local dataset with the server" I logged into ID EDITOR and verified that no one modified this POINT or POLYGON in the last 24 hours and cannot see why it would not upload my changes. I am new to JOSM v9329, but I though I understood uploading conflicts and how to resolve them. I am very good at ID editor. Please help, I would like to use JOSM for more off-line work on the OSM data. |
|
That sounds like a work flow that is bound to cause issues. While the the extract file might have only been 20 hours old the data is likely to have been a bit older. In any case is their any reason you are not simply using the normal JOSM download mechanism? With the further information you have given the picture is a bit clearer. I would point you to the POSM (see https://github.com/AmericanRedCross/posm ) project as a potential alternative, alas I suspect that they simply haven't thought the synchronisation part of their project really through. I would suggest that you should simply accept such issues as you experienced as not avoidable and live with having to work through any conflicts on upload (you can minimize them but not completely avoid). Further splitter is really a special purpose tool and likely not suitable for generating extracts as you need them, osmosis and others are likely better suited. 3
Also, why didn't you do as josm suggested and synchronize the data (file -> update data/selected/modified) ? Or view the node or the polygon's history from within josm (Ctrl-h) rather than in iD ?
(27 Feb '16, 22:06)
Vincent de P... ♦
|
|
Did the .osm file come via mkgmap's "splitter" or by something else that could have removed version information (I'm guessing after reading http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2016q1/024578.html). If so, I would expect that that would cause the problem. Couldn't you instead:
For info, I've always used "osmosis" http://wiki.openstreetmap.org/wiki/Osmosis to split larger PBF downloads into smaller ones. Never tried it for editing and upload though, as (like everyone else) I've always assumed that data would be out of date too quickly.
(28 Feb '16, 14:59)
SomeoneElse ♦
1
I'd add that osmconvert will also split out a section of a larger file and may be more convenient than Osmosis. However, you still need to do some synchronisation of OSM elements with the main API DB before uploading
(28 Feb '16, 16:16)
SK53 ♦
|
|
Yes, it turns out that SPLITTER is removing dataset version information and that is why my 20 hour old data is totally different that what I downloaded. I do not have internet access all the time and downloading large section of my country allow my the flexibility to use a 'splitter-type' program to break these large 'states' into smaller, JOMS sized chunks. If my dataset versions were preserved, the only UPLOAD CONFLICTs I should have would be if someone modified the exact same objects that I have modified off-line. This should not happen very often and I can deal with a few conflicts if they should arise. Forcing me to use JOSM to DOWNLOAD .osm data, forces me to be online anytime I want to work on a defferent area of the country. and 'storing' .osm data is very time consuming because the maximun area you can download in JOSM is relatively small. Using a TDB editor, shows me all of the splitter output files graphically and I can quickly choose a smaller .osm file to open in JOSM and start working. |
"only 20 hours old"? Ideally you should save / upload your changes as soon as possible, spreading larger work over multiple changesets.