-1

I'm trying to download historical data from overpass-turbo and I keep getting this error. 

Error: runtime error: open64: 0 Success /osm3s_v0.7.54_osm_base Dispatcher_Client::request_read_and_idx::timeout. The server is probably too busy to handle your request.

This is after trying to increase the timeout and maxsize on the query and using the "raw data directly from Overpass API" export function. I need to do this for all of US and Canada. Breaking it up by state and province is fine or one big download will work as well. Am I exceeding the limits and need to find another way of doing this? The files don't seem to be too big. California is about 10MB and Ohio is about 2MB. Here are my basic queries.

 [adiff:"2016-10-23T15:00:00Z","2017-10-22T15:00:00Z"];

{{geocodeArea:california}}->.searchArea;
(
  way["highway"="motorway_link"](area.searchArea);
);
out body;
>;
out skel qt;



[adiff:"2016-10-23T15:00:00Z","2017-10-22T15:00:00Z"][timeout:99999][maxsize:10737418240];

{{geocodeArea:california}}->.searchArea;
(
  way["highway"="motorway_link"](area.searchArea);
);
out body;
>;
out skel qt;
Improve this question
13
  • 1
    for large downloads use download.geofabrik.de/north-america.html
    – Mapperz ♦
    Commented Oct 24, 2017 at 4:29
  • This is intentional, because the server would be overloaded most of the time otherwise. You can set up your own overpass instance on a full or part planet database if you need the query part.
    – AndreJ
    Commented Oct 24, 2017 at 6:24
  • 3
    Besides, both timeout and maxsize values are both ridiculously large: 99999 seconds is more than 1 day (!), maxsize is >10GB. That's why the query always runs into a timeout. As @AndreJ already said, running your own instance is way to go.
    – mmd
    Commented Oct 24, 2017 at 7:58
  • @Mapperz I need the historical data and the geofabrik downloads don't work for me. I'm on a PC and unless you know how to get osmosis to work on one that is out of the question.
    – brink
    Commented Oct 24, 2017 at 15:58
  • @mmd, that's just a sample. I tried a bunch of different combos for time and size. I got it to work once with out both and the file was 10MB which doesn't seem like a lot.
    – brink
    Commented Oct 24, 2017 at 16:09

1 Answer 1

Reset to default
0

Am I exceeding the limits

Given that quoted error includes

Dispatcher_Client::request_read_and_idx::timeout. The server is probably too busy to handle your request.

Yes, you requested more than server is able to provide. Try splitting queries into smaller.

Also, from comments:

Besides, both timeout and maxsize values are both ridiculously large: 99999 seconds is more than 1 day (!), maxsize is >10GB

It is possible that server rejects queries with outrageous maxsize and timeout values.

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.