On Tue, Feb 1, 2011 at 5:47 PM, Mike <[email protected]> wrote: > @Chris - I currently geocode on 'dragend' - do you recommend changing > this? >
Okay, I'm trying again from home. I think it's because I dragged many times in short amounts. We *do* rate limit geocoding. I would suggest some combination of caching geocoding responses for large regions, and only re-geocode if the user moves far away enough from ones you've already fetched. dragend will definitely fire more than 'idle', so consider listening to the idle event. Alternatively, you could set a timeout on center_changed. At the moment you won't re-geocode if the user uses their keyboard or the pan control to navigate the map (pretty low use case, but one nonetheless) Chris -- http://twitter.com/broady -- 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.
