I am using Google Maps API to display about 50 locations on the map. I am using client side geocoding. I am using window.setTimeout to control the number of geocode requests that the application sends per second. If I send more than 1 request per second, I am getting an OVER QUERY LIMIT response.
Question: Isn't this limit supposed to be 10 queries per second? If yes, then what could I be doing wrong? If no, then does Business API has more generous queries per second limit?
Please note that our application is not going to hit the 25,000 queries per day.
This approach is not correct beacuse of Google Server Overload. For more informations see https://gis.stackexchange.com/questions/15052/how-to-avoid-google-map-geocode-limit#answer-15365
By the way, if you wish to proceed anyway, here you can find a code that let you load multiple markers ajax sourced on google maps avoiding OVER_QUERY_LIMIT error.
I've tested on my onw server and it works!:
Example:
Often when you need to show so many points on the map, you'd be better off using the server-side approach, this article explains when to use each:
Geocoding Strategies: https://developers.google.com/maps/articles/geocodestrat
The client-side limit is not exactly "10 requests per second", and since it's not explained in the API docs I wouldn't rely on its behavior.
The geocoder has quota and rate limits. From experience, you can geocode ~10 locations without hitting the query limit (the actual number probably depends on server loading). The best solution is to delay when you get OVER_QUERY_LIMIT errors, then retry. See these similar posts:
OVER_QUERY_LIMIT in Google Maps API v3: How do I pause/delay in Javascript to slow it down?
How do I Geocode 20 addresses without receiving an OVER_QUERY_LIMIT response?