Don't worry about the size of the query box. Focus instead on keeping the number of nodes and query time reasonable.
Overpass is perfectly happy doing continent or world-wide queries: and it's usually quite fast. Note that the web client bogs down with more than a few hundred results, but if you load straight into JOSM or a script, you can get many more. Non-square bounding boxes seem to be slower than square ones. On Sun, Mar 29, 2015 at 7:45 AM, James Conkling < [email protected]> wrote: > Yup, exactly, I was running many small queries in parallel. Aggregating > them into one query resolved it. If the query bbox grows too big--right > now looking at ~60% of the DRC, but will need to expand the query to run > across all of the Congo Basin--then I'll divide into country-sized queries > but be sure not to run them simultaneously. > > On Fri, Mar 27, 2015 at 4:20 PM, Roland Olbricht <[email protected]> > wrote: > >> Yeah, that all makes sense. I had spent a lot of time trying to limit >>> the area I was searching against, and the result was a /429 Too Many >>> Requests/ error. >>> >> >> Thank you for the feedback. >> >> Just for clarification: You should get HTTP 429 only if you submit more >> than one request in parallel. This help other users to also get a chance >> that their queries are executed. >> >> If you get HTTP 429 in another case, please enforce that there is no >> runaway query by calling >> http://overpass-api.de/api/kill_my_queries >> This kills another query from your IP adress if any is running. >> >> Best regards, >> >> Roland >> >> >> _______________________________________________ >> talk mailing list >> [email protected] >> https://lists.openstreetmap.org/listinfo/talk >> > > > _______________________________________________ > talk mailing list > [email protected] > https://lists.openstreetmap.org/listinfo/talk > >
_______________________________________________ talk mailing list [email protected] https://lists.openstreetmap.org/listinfo/talk
