You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I query http://www.overpass-api.de/api/interpreter for streets within a fairly simple polygon, I successfully receive the data and status code 200. If I submit the same query with a slightly less-simple polygon, I receive status code 429 "too many requests" and no data. It does not matter what order these queries are posted, complex polygons always result in a 429 and simpler polygons always result in a 200 code. The API status page tells me I have slots available and adjusting my timeout changes nothing.
Most importantly, all of these queries worked for months, up until I last ran them a couple days ago. This problem only appeared this morning. I have production code using these queries to get streets within some polygon. My users are now getting 429 errors every time they try to use it.
Here is a minimal working example using Python and its requests package:
Note that the only difference between these two queries is the polygon. The second polygon is just a slightly simplified version of the first (simplified using the douglas-peucker algorithm). Also note that both queries (i.e., the values of the data variables) work just fine in Overpass Turbo.
The text was updated successfully, but these errors were encountered:
gboeing
changed the title
overpass-api.de 429s a request even when I am not over the limit
Overpass API 429s polygon queries
Apr 24, 2017
If I query http://www.overpass-api.de/api/interpreter for streets within a fairly simple polygon, I successfully receive the data and status code 200. If I submit the same query with a slightly less-simple polygon, I receive status code 429 "too many requests" and no data. It does not matter what order these queries are posted, complex polygons always result in a 429 and simpler polygons always result in a 200 code. The API status page tells me I have slots available and adjusting my timeout changes nothing.
Most importantly, all of these queries worked for months, up until I last ran them a couple days ago. This problem only appeared this morning. I have production code using these queries to get streets within some polygon. My users are now getting 429 errors every time they try to use it.
Here is a minimal working example using Python and its requests package:
Note that the only difference between these two queries is the polygon. The second polygon is just a slightly simplified version of the first (simplified using the douglas-peucker algorithm). Also note that both queries (i.e., the values of the
data
variables) work just fine in Overpass Turbo.The text was updated successfully, but these errors were encountered: