[OSM-talk] RFC: what are empty nodes and how should we use them?

[Aun Johnsen]

(1) It's not exactly more reliable with dedicated bulk upload scripts
> either. If the API takes too long to check the uploaded osmChange for
> validity, the TCP session appears to timeout. The script/JOSM never receives
> the OK from the API, including the new object IDs. The next time you hit
> upload to resume, it will reupload that failed chunk in its entirety,
> leading to (in my example) 5k duplicate objects on the server.
>
I have often tried to upload smaller or larger chunks from slow/unstable
connections, and have experienced various problems, I have even come to the
point where I have had ~100 items left when the connection have timed out,
with the result that the entire upload had to be done again. The only way to
fix it afterwards is to do a code validation of the area, but with these
unstable lines that I suffer from time to time, that doesn't solve much
either.

Having JOSM or similar intelligently combine nodes and ways in these chunks,
as well as accepted that "all but the last" have been transferred correctly,
than that would have helped imensely on the end result.


This makes sense in in certain situations. E.g. you upload 20000 objects
>  and you get "precondition failed" on the last 100 of them. That would mean:
>  (1) - upload 19899+i objects
>  (2) - upload is aborted by server -> get the server error
>  (3) - fix the problem (e.g. download way and fix it)
>  (4) - i++
>  (5) - goto (1)
>
> If you have a slow connection, this is not acceptable.
>
> This is exactly what I am talking about
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk/attachments/20100816/7758b4e1/attachment.html>