[timeout] Alternative to Overpass?

Help and support
1

Hello,

Since yesterday, I’ve been unsuccessful querying Overpass through OverpassTurbo:

Query Error
An error occurred during the execution of the overpass query! This is what overpass API returned:
Error: runtime error: open64: 0 Success /osm3s_osm_base Dispatcher_Client::request_read_and_idx::timeout. The server is probably too busy to handle your request.

Is there a (simple) alternative to search the OSM database?

Thank you.

2

Hello and welcome to the OpenStreetMap Community.

First of all, there is already a long thread about the Overpass performance issues in general: Overpass API performance issues

You can also use Postpass: Postpass – a public OSM PostGIS instance

It provides a public PostGIS database with OSM data.

Another option is to use your own PostgreSQL + PostGIS database. You can import OSM data and run queries locally. This is more stable for larger or repeated queries.

1 Like
3
4

@chris66 Overpass Ultra uses the same Overpass API just like Overpass Turbo, doesn’t it?

3 Likes
5

Dunno, but I read from the OrigPost that this is not a requirement.

6

I think it is, because that error is an Overpass API error not an Overpass Turbo one (although it’s really not obvious from the message unless you know).

You can point an Overpass Turbo instance at a different Overpass API (there is a “settings” option on the menu bar), and you can also point it at Postpass (likely the best solution here, until the scrapers discover that). See “Postpass” in the OSM wiki for full details.

You can deploy your own Overpass API, but that’s more complicated than many other parts of the OSM ecosystem…

Just to complicate things, I separately noticed this morning a couple of issues with the default Overpass Turbo instance (issues with saved queries and shortening of new ones). But that is unrelated to the main problem…

Edit almost 2 weeks later: The Overpass Turbo issues were resolved a week or so ago. See also this post (about addressing timeouts at the main Overpass API instance directly).

2 Likes
7

I tried this new server with some old queries that used to work fine, and it’s still showing the “too busy” box.

8

@Kovoschiz Whats wrong with ultra? Is it also having the issues?

9

I’ve just tried it with this query:

nwr[archaeological_site="oppidum"];
out center;

and got

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

I noticed too. I use some shortened queries on a wiki page and nothing works now.
When trying the ‘Share’ button it gives a very long URL.
It seems the short URL function is.. removed.

11

The problem is in the Overpass API, not in any frontends like Overpass Turbo or Overpass Ultra.

12

For commercial use, it is more sensible not to use any service funded by donations but to switch to a commercial provide, e.g. Geofabrik Overpass API.

2 Likes