In the coming week, the Maps API geocode limit will change from a key-based system to an IP-based system, with a new limit of 15,000 queries per day. If you're a developer with a website that's using client-side geocoding via the GClientGeocoder object, this change means that each of your website visitors will now be subject to their own 15K quota. However, if you're a developer using the HTTP geocoder, this change means that all the geocodes from your script will be subject to the same 15K quota (your web server will send the same IP to us with each geocode). We've made this change in our geocoder due to the number of developers who've had issues with the GClientGeocoder and going over quota in times of high mashup user volume.
If you are using HTTP geocoding and suspect that you may be currently issuing more than 15K queries per day, you will need to take action to make sure that you don't go over the new limit (which would result in queries returning a 620 status code instead of a successful geocode). Here are some proposed workarounds:
- Switch over to using the GClientGeocoder. Check out an example from our documentation.
- Supplement your geocoding with another geocoder service. Check out a list of geocoding resources from our forum.
If you determine that you need to issue more than 15K daily queries for a single IP, we are open to the possibility of raising your IP's quota. Please send us an email with a description of your use of the geocoder and links to the website implementing it. We will review your request and let you know if we'll be able to fulfill it.
We apologize for any inconvenience you may experience while transitioning to the new IP-based system. Please post any questions you have about the new system in the Maps API forum.
