Hi
Am 07.10.2013 18:32, schrieb Roland Olbricht:
Dear Bryce,
I've cross-checked the Rambler instance. I'm sorry it indeed doesn't work on
that instance. It looks like an element on the network, most likely Nginx,
disconnects any connection if no data is sent for ten minutes.
A similar
On Sun, Oct 6, 2013 at 11:15 AM, Roland Olbricht roland.olbri...@gmx.dewrote:
Please do not use a cancel-restart strategy. This may double the load
because
not in all cases the Apache server cancels the abandoned query.
Sadly, it's all that I can get to work.
I suggest the following
Dear Bryce,
I've cross-checked the Rambler instance. I'm sorry it indeed doesn't work on
that instance. It looks like an element on the network, most likely Nginx,
disconnects any connection if no data is sent for ten minutes.
A similar thing happened on overpass-api.de after 20 to 30 minutes.
On Mon, Oct 7, 2013 at 9:32 AM, Roland Olbricht roland.olbri...@gmx.dewrote:
Dear Bryce,
I've cross-checked the Rambler instance. I'm sorry it indeed doesn't work
on
that instance. It looks like an element on the network, most likely Nginx,
disconnects any connection if no data is sent for
brycenesbitt wrote
On Sun, Oct 6, 2013 at 11:41 AM, Paul Norman lt;
penorman@
gt; wrote:
http://jxapi.openstreetmap.org/xapi/api/0.6/node[amenity=drinking_water]took
about 3 minutes total. 14.5MB result.
Thanks, however no luck here:
# wget
I ran your query on my server and it completed in 90 seconds, even
though another big query was already running. True, I do use an SSD for
the database, so it is very fast. However, it proved that there is
nothing in your query that gives Overpass indigestion.
The public servers do run a
Per the suggestion, I dropped the query time to 200 seconds, and same
result from the public servers. The query is still running after several
minutes, despite the timeout value of 200 seconds.
___
talk mailing list
talk@openstreetmap.org
In the past I could generally get the query to complete by running it once,
cancelling it, then running it a second time (maybe the 2nd time more data
was cached). Now I get either infinite timeout or a server rejection.
The query is:
osm-script timeout=990 element-limit=1073741824
http://jxapi.openstreetmap.org/xapi/api/0.6/node[amenity=drinking_water]
took about 3 minutes total. 14.5MB result.
From: Bryce Nesbitt [mailto:bry...@obviously.com]
Sent: Sunday, October 06, 2013 9:53 AM
To: talk@openstreetmap.org
Subject: [OSM-talk] Overpass or XAPI API servers for 60,000
On Sun, Oct 6, 2013 at 11:41 AM, Paul Norman penor...@mac.com wrote:
http://jxapi.openstreetmap.org/xapi/api/0.6/node[amenity=drinking_water]took
about 3 minutes total. 14.5MB result.
Thanks, however no luck here:
# wget
10 matches
Mail list logo
