Graham<br>I think the only way to overcome this would be to do a series of smaller requests, unless I lift the limit.<br><br>The limit is there to kill silly requests that are trying to download the whole planet. It's difficult to achieve a suitable balance.<br>
<br>80n<br><br><div class="gmail_quote">On Thu, Nov 19, 2009 at 2:05 PM, Graham Asher <span dir="ltr"><<a href="mailto:graham.asher@btinternet.com">graham.asher@btinternet.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;">
<div bgcolor="#ffffff" text="#000000">
You're right - sorry to waste your time. I didn't know about that
limit. Can it be overcome somehow?<br><font color="#888888">
<br>
Graham</font><div><div></div><div class="h5"><br>
<br>
80n wrote:
<blockquote type="cite">Graham<br>
It's possible that you've hit the 1m element limit on these requests.<br>
<br>
Is there any message at the end of each file?<br>
<br>
80n<br>
<br>
<div class="gmail_quote">On Thu, Nov 19, 2009 at 1:40 PM, Graham
Asher <span dir="ltr"><<a href="mailto:graham.asher@btinternet.com" target="_blank">graham.asher@btinternet.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;">I've
found a bug in the OSM API v0.6 - is there a bug tracking system I<br>
can log it to?<br>
<br>
Details:<br>
<br>
<<<<<<<br>
The bug is this: when downloading a large amount of data by specifying a<br>
rectangular bounding box, quite often the south east corner is missing.<br>
Some evidence: note the sizes of downloaded data in the following
requests:<br>
<br>
$ curl<br>
<a href="http://osmxapi.hypercube.telascience.org/api/0.6/map?bbox=-88.546,41.327,-86.97,42.382" target="_blank">http://osmxapi.hypercube.telascience.org/api/0.6/map?bbox=-88.546,41.327,-86.97,42.382</a><br>
>chicago.osm<br>
% Total % Received % Xferd Average Speed Time Time Time<br>
Current<br>
Dload Upload Total Spent Left<br>
Speed<br>
100 308M 0 308M 0 0 155k 0 --:--:-- 0:33:48<br>
--:--:-- 224k<br>
<br>
$ curl<br>
<a href="http://osmxapi.hypercube.telascience.org/api/0.6/map?bbox=-88.427,41.399,-87.105,42.325" target="_blank">http://osmxapi.hypercube.telascience.org/api/0.6/map?bbox=-88.427,41.399,-87.105,42.325</a><br>
>chicago.osm<br>
% Total % Received % Xferd Average Speed Time Time Time<br>
Current<br>
Dload Upload Total Spent Left<br>
Speed<br>
100 311M 0 311M 0 0 144k 0 --:--:-- 0:36:42 --:--:--<br>
86062<br>
<br>
The second request is for a smaller area - an area entirely included in<br>
the bounds of the first area, and smaller on every side - yet more data<br>
arrives (311M instead of 308M) showing that something is awry.<br>
>>>>>><br>
<br>
[I have sent a copy of this message with an illustration, but it is<br>
greater than the 40K limit for postings, and awaiting approval. so I am<br>
sending a briefer version in the hope of getting a quick response]<br>
<br>
Graham Asher<br>
<br>
<br>
_______________________________________________<br>
osmf-talk mailing list<br>
<a href="mailto:osmf-talk@openstreetmap.org" target="_blank">osmf-talk@openstreetmap.org</a><br>
<a href="http://lists.openstreetmap.org/listinfo/osmf-talk" target="_blank">http://lists.openstreetmap.org/listinfo/osmf-talk</a><br>
</blockquote>
</div>
<br>
</blockquote>
<br>
</div></div></div>
</blockquote></div><br>