Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
To get the altitude of several points, I use the Elevation API provided by Google. The problem I’m facing is that I regularly receive an OVER_QUERY_LIMIT error message, certainly because I’m asking altitudes at a too high rate.
The Google documentation speaks about such a limit but doesn’t give any value for it. Does anyone know at what level this maximum interrogation rate is set?
You are likely making too many requests per minute; this is known as a rate limiting, but the actual limit per minute is not published anywhere. I have seen some talk about a limit of 10 requests per second (i.e. 600 per minute) as an absolute limit on all Google APIs.
For their free APIs, such as the one you are using, and their Geocoding API, they just say they have a limit of what they deem to be a reasonable amount of requests per minute. This may go up and down depending on server load and/or time of the day.
This recent post seems to be suggesting that you require a delay of a clean 1 second between batches of 10 requests, where each of the 10 are individually separated by 0.1 second.
The answers to this question also backup the above:
How do I Geocode 20 addresses without receiving an OVER_QUERY_LIMIT response?