When you start sending queries too quickly, the http geocoder service will start responding with error code 620 (too many requests). I've found through trial and error that including a delay of 110ms between requests is enough to appease the geocoder service.
On Sep 25, 12:10 pm, Matt Ball <[email protected]> wrote: > I'm writing a server-side batch geocoder in Java. I'd like to limit > the rate at which I make geocoder requests tohttp://maps.google.com/maps/geo. > In my experience with client-side geocoding (specifically, Maps > Javascript API v3) it was necessary to make sure I made requests no > more frequently than every 200ms or so. > However, when I do this in Java using a Java URL object > (URL::openStream() after some initialization) it seems like HTTP > request is self-rate-limited to about 160ms per request. Does the HTTP > Geocoder service actually handle rate-limiting in this case (e.g. > causing openStream() to block until sufficient time has passed)? Or, > do I still need to rate-limit my requests, and at what rate? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Maps API" 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-api?hl=en -~----------~----~----~----~------~----~------~--~---
