I never saw mention of what the specific rate is; however, they do mention that there is one and that they have prevention mechanisms to keep people from scapping their databases. The person in the post that Rossko used was rate limiting his requests to limit how fast he was tossing out requests. You could easily implement something along these lines with some clever timer usage. If you need some help with timers let me know.
On Fri, Jul 2, 2010 at 9:18 AM, JavaJive <[email protected]> wrote: > To judge from that, I certainly haven't exceeded the number of queries > per day (2,500) and am unlikely while testing to exceed the maximum > number of points per day (25,000), so it looks like the rate, but that > does not appear to be documented anywhere. What can I do about this? > > On Jul 2, 2:55 pm, Rossko <[email protected]> wrote: > > > I wasn't able to find any documentation on the actual limits to using > > > this service. > > > > We can hazard a guess that they are similar to geocoding limits. > > Another guess would be that you have broken the rate limit, rather > > than max counts. > > http://groups.google.com/group/google-maps-js-api-v3/browse_thread/th... > > -- > You received this message because you are subscribed to the Google Groups > "Google Maps JavaScript API v3" group. > To post to this group, send email to > [email protected]. > To unsubscribe from this group, send email to > [email protected]<google-maps-js-api-v3%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-maps-js-api-v3?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
