Overpass API/status
Please report any problems and issues here. Add the most recent entry first.
Invalid 2012-05-12 18:00 UTC: rambler is not working, returning "The requested URL /~roland/api/interpreter was not found on this server."
The correct URL is
http://overpass.osm.rambler.ru/cgi/interpreter
not
http://overpass.osm.rambler.ru/api/interpreter
-- Roland
- Ah, then it seems all the forms on this page need to be updated to use the correct URL. Thanks for your wonderful service! -- Joshdoe 03:37, 11 May 2012 (BST)
- Thank you for this hint. I have replaced the outdated documentation by a link to the current documentation. -- Roland
Solved 2012-03-20 04:35 UTC: Request to hhttp://overpass-api.de/api/xapi_meta?*[name%3DTschechieche+Spezialit%C3%A4ten+-+Handel+%26+Vertrieb] via taginfo faild with:
<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head> <meta http-equiv="content-type" content="text/html; charset=utf-8" lang="en"/> <title>OSM3S Response</title> </head> <body> <p>The data included in this document is from www.openstreetmap.org. It has there been collected by a large group of contributors. For individual attribution of each item please refer to http://www.openstreetmap.org/api/0.6/[node|way|relation]/#id/history </p> <p><strong style="color:#FF0000">Error</strong>: line 4: parse error: not well-formed (invalid token) </p> </body> </html>
- I can confirm this bug. It it due to improper treatment of ampersand charaters in the XAPI compability layer. I'll fix that during the day -- Roland
- It is fixed since quite some time, but I forgot to update this status page.
Solved 2012-01-21 08:00 UTC: Broken area-queries again, but this time with different error messages. E.g. the query from section "Download an entire city" at overpass-api.de fails with "Error: line 4: static error: Unknown tag "area-query" in line 4.". If I try to use area-query inside <query type="node"> element, I'll get only Internal Server Error.
- Thank you for reporting this. I can reproduce the error but I cannot do much before I'm back from vacancies next Saturday. I'm sorry. -- Roland
- It was possible to fix the error with simple means. It was a typo in a refactored piece of source code. -- Roland
Invalid 2012 Jan 12 12:55 UTC: wrong parameter order in bbox
- A All bbox queries are failing due to some sort of memory error. The same bbox queries were succeeding earlier in the day.
- A Example:
http://overpass.osm.rambler.ru/cgi/xapi?map?bbox=12.3486330,12.6123050,41.8040780,42.0003250
<?xml version="1.0" encoding="UTF-8"?> <osm version="0.6" generator="Overpass API"> <note>The data included in this document is from www.openstreetmap.org. It has there been collected by a large group of contributors. For individual attribution of each item please refer to http://www.openstreetmap.org/api/0.6/[node|way|relation]/#id/history </note> <meta osm_base="2012-01-08T12\:17\:02Z"/> <remark> runtime error: Query run out of memory in "recurse" at line 7 using about 640 MB of RAM. </remark> </osm>
- I assume that in the above query the second and third parameter are in wrong order. Note that the order is West, South, East, North.
http://overpass.osm.rambler.ru/cgi/xapi?map?bbox=12.3486330,12.6123050,41.8040780,42.0003250
selects 30 degress of longitude and latitude, including randomly two thirds of Europe.
http://overpass.osm.rambler.ru/cgi/xapi?map?bbox=12.3486330,41.8040780,12.6123050,42.0003250
selects a bounding box of meaningful size around Rome and works fine.
- No other bbox shows an error.
Solved 2012 Jan 1 21:05: bogus meta elements
- A mistake in the version update (forgotten --meta parameter to dispatcher on the command line) doomed the meta file indexes. The core data is not damaged and keeps going on.
- A new planet import is in progress and expected to be complete on early Friday morning. Meanwhile, please use the Rambler server with base link
- http://overpass.osm.rambler.ru/cgi/. It has not got the version update yet and serves meta data without any restrictions.
- Update: The Friday morning import has also two other flaws:
- I started the minute updates at the wrong date. All changes from 21 Dec are missing.
- I accidently deleted the wrong file when trying to get space on the server's hard disk. Thus, there are no meta data for nodes for the moment.
- I'm sorry for all that mess. I've done it too much in a hurry.
- Note: The new version itself isn't buggy. The dificulties are human failure while fiddling to install without service interruption.
- At sunday evening, the switch to the import succeeded. On Monday morning, the server also has catched up to the minutely diffs. This incident doesn't harm any more.
Solved 2011 Dec 28 20:00: area-queries appear to be broken - did not reappear.
- They fail with 'Error: runtime error: open64: 0 /osm3s_v0.6.95_areas Dispatcher_Client::request_read_and_idx::timeout. Probably the server is overcrowded.' While everything else works.
- This is fixed now. The measure was to restart the dispatcher, i.e. the internal serializer of queries. For an unknown reason it refused all reading requests before.
- It seems the problem mentioned below is back (2011 Dec 17 11:00). It has been fixed once again by a dispatcher restart. But it looks like there is a not reproducable bug in the software.
- With extended diagnostic capabilities also the self healing has been improved. It looks like this works as a remedy against the unknown bug. Neither diagnostic messages nor the bug did reappear for roughly a week.
- The update is not yet rolled out on the Rambler server.
Solved 2011 Oct 25 23:50: Some ways, e.g. way #4732211 showed no history information.
- The investigation is still going on. The bug doesn't appear on a freshly imported database on the rambler server. Thus, it is either a race condition or caused by a bad recovery after the power outage.
- A contributing factor has been identified: a bug in the print statement may have displayed bogus meta data. This doesn't explain the observed failures but influenced the symptomps.
- A further race condition in the IPC has been spotted and fixed.
- The freshly imported database on the rambler server has been checked as consistent. A new import on overpass-api.de is in progress. The bug will be considered closed once this import is up-to-date and still consistent.
- Both servers now have fresh imports with consistent data, even after several days of updates.
- Two bugs in the software have been removed; these bugs might have caused non-reproducible stray losses of meta data. It looks like the reproducibly lost meta data items had all a link to 23rd October, the day of the power outage.
- Note that the rebuild of the area data still takes time. It is expected to be available again at 8th November 06:00.
Solved 2011 Oct 24 10:42: The server did a sudden reboot due to a power outage at the hosting site.
- The automatic restart failed, and a manual restart has been done the same evening. The meta data has been incorrect until about 2011 Oct 25 noon, and areas are re-updated again since 2011 Oct 26 morning.
