I don't think that is so easy. To avoid conflicts, when replacing node/way/relation that is on server with newer version, server sends internal ID/revision number of the way and you have to pass this back (so two people won't overwrite the same way with their version and "last upload wins" - in 0.6, first one upload, second one gets a conflict and will have to resolve it first before being able to upload)
You will have to add these revision numbers to all objects for upload to work, changing 0.5. to 0.6 won't do it ... Martin > AFAIK, the .osm files that JOSM is able to save to disk are pretty much the > same for 0.5 and 0.6. Your best shot is to save a 0.5 .osm file, open it up > with JOSM on monday, and try to upload it. The api version auto-detect > feature of the latest JOSM releases *should* handle this issue gracefully. > > If that fails, open the .osm file with a text editor, and change the first > line to read "0.6" instead of "0.5". _______________________________________________ talk mailing list [email protected] http://lists.openstreetmap.org/listinfo/talk
