[Talk-us] Road Expansions and Seattle Imports (if you're the Seattle importer, please read!)

[Serge Wroclawski]

On Sat, May 19, 2012 at 1:31 PM, Mike N <niceman at att.net> wrote:
> On 5/19/2012 12:52 PM, Serge Wroclawski wrote:

>
>  Ultimately, the only way to get a 100% successful upload is to query the
> changeset on failure to determine what was actually uploaded, then resume
> from that point.

While true, that method in isolatiuon is a bit complex and should be
unnecessary.

The OSC upload method is transactional in nature. If you get a
positive response from it, you can know the upload succeeded. The
issue is that there can be a network interruption between the upload
completion and the return response. During that time the transaction
has completed successfully but the client won't know.

If there is a 1:1 correlation between OSC and changeset, that's fine,
but generally uploads are often done with large chagesets.

There are a few ways to handle this (including async upload methods in
the API code, which has been proposed), but right now, AFAIK, there's
no public code for making reliable mass uploads to OSM.

Assistance requested!

I'll post something when it's more ready, but if you're a python
programmer, I'd like your help.

- Serge