<div class="gmail_quote">On Thu, Oct 15, 2009 at 2:18 PM, andrzej zaborowski <span dir="ltr"><<a href="mailto:balrogg@gmail.com">balrogg@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
2009/10/15 Ian Dees <<a href="mailto:ian.dees@gmail.com">ian.dees@gmail.com</a>>:<br>
<div><div></div><div class="h5">> On Thu, Oct 15, 2009 at 2:02 PM, andrzej zaborowski <<a href="mailto:balrogg@gmail.com">balrogg@gmail.com</a>><br>
> wrote:<br>
>><br>
>> Hi,<br>
>> the other day I talked to Richard Weait on irc about upload utilities<br>
>> and we thought it would be nice for big uploads, which need to be<br>
>> split anyway, to be split "logically", so that the changes appear in a<br>
>> similar order to how a human editor would draw them. This little<br>
>> script doesn't exactly achieve this but does the trick for me:<br>
>> <a href="http://www.openstreetmap.pl/balrog/bulkupload/smarter-sort.py" target="_blank">http://www.openstreetmap.pl/balrog/bulkupload/smarter-sort.py</a><br>
>><br>
>> A number of times I had a situation where my upload script first<br>
>> uploaded all the payload of new nodes, and then before I finished<br>
>> uploading ways, a human editor saw unused, untagged nodes and started<br>
>> deleting them causing conflicts, so now I run this script before<br>
>> splitting changesets.<br>
><br>
> What converter/upload script are you using that creates node payloads before<br>
> uploading the ways? I would say that you should be fixing your upload and/or<br>
> convert script before you worry about sorting changes...<br>
<br>
</div></div>I use a couple of simple python scripts, creations are sorted nodes<br>
first, then ways, then relations, modifications are left alone and<br>
deletions in relation-way-node order. What other ordering can you use<br>
to make (almost) sure the api doesn't barf at your changeset?<br>
</blockquote><div><br>Are you uploading one node at a time with the PUT API calls or are you using the osmChange diff upload? If you use the diff upload, the entire thing will show up on the map at the same time.<br><br>
Which brings up a good point -- why is it that data from changesets that are not closed show up on the API at all? If someone is in the middle of PUTting 1000s of nodes, followed by 100s of ways and relations, none of that data should show up until they explicitly call the changeset/close API call.<br>
</div></div>