Hello everybody, A new version of Overpass API http://wiki.openstreetmap.org/wiki/Overpass_API is available. Please read http://wiki.openstreetmap.org/wiki/Overpass_API/versions#Overpass_API_v0.7.1 for details.
The most important thing is that this version accomodates 64-bit node ids. So the expected overflow over node id 2^31 in February 2013 will not harm Overpass API. The second most import thing is that the fair usage policy needs a subtle adjustment. You don't need to do anything, the server helps you automatically to comply to the policy. Some users (I assume a malformed JavaScript application) have sent a sequence of queries with very large bounding boxes within a few seconds. This used up all server ressources and harmed other users, and at the same time did not return useful results (due to oversize). A sample from the logfile: [07/Dec/2012:20:41:20 0100] runtime: 181, return size: 341, query string: /api/xapi?node[man_made=surveillance] [bbox=-73.63124999999955,-21.20088405484794,102.43124999999776,79.67900280484885] [07/Dec/2012:20:41:21 0100] runtime: 180, return size: 341, query string: /api/xapi?node[man_made=surveillance] [bbox=-29.615624999999774,17.868367821866197,58.415624999999785,69.46927728884238] [07/Dec/2012:20:41:22 0100] runtime: 180, query string: /api/xapi?node[man_made=surveillance] [bbox=-7.607812499999978,35.566567573194945,36.40781249999989,61.23135136351583] To avoid this, now queries from the same host (based on IP address) are serialized (executed one after another) and queries waiting for this reason for more than 15 seconds are rejected with HTTP code 429. If you have sent a runaway query and therefore receive 429 for subsequent queries, you can cancel the runaway query with http://overpass-api.de/api/kill_my_queries Cheers, Roland _______________________________________________ talk mailing list [email protected] http://lists.openstreetmap.org/listinfo/talk
