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.
Does Google Maps V3 API have any form of built in caching system for geocoding? I was thinking whether the usage limit for a user will be reached if that user enters an address say “Boston, MA” and continues clicking a button that geocodes that same address?
I’m not aware of any, but it would be easy to put your own cache in front of the geocoding. Also you can try using client-side geocoding, which should eliminate the problem for the most part.
Check out this link:
http://code.google.com/apis/maps/articles/geocodestrat.html
If you decide to do your geocoding cache, make sure you aren’t violating the terms of service. A while back you couldn’t store the geocode results… I’m not sure if that’s still true or not.