I imagine this to be a fairly significant caveat, though perhaps that's more theory than practice. Am I wrong? :
"Note however that it is a requirement of the Maps API Terms of Service that you use the Geocoding Web Service in conjunction with a Google map. This means that when it comes time to use cached geocoder results in an application, the application must display the results or any data derived from them on a map generated using one of the Google Maps APIs or Google Earth API."
"2,500 requests may be sent to the Geocoding Web Service per day from a single IP address" - I don't remember this restriction from the previous version of the API. Has this changed, or did I just miss a T&C somewhere?
The thing to keep in mind about this is that the limit applies to end users, not developers, since the requests will be coming directly from the users' browsers.
It all depends how you develop your map, of course, but this is a powerful incentive not to proxy the requests through your own server. And if you need to cache them or whatever, have the user's computer make the geocode request on your behalf, and then send it to the server for storage.
Off-course that depends on your method of usage. If you have a large DB of geo-based, but not geocoded, content, the only way to show relevant local items to the user is to geocode them all first. Then this daily limit is relevant.
"If more than 15,000 geocode requests in a 24 hour period are received from a single IP address, or geocode requests are submitted from a single IP address at too fast a rate..."
OK locality political Sydney NSW, Australia Sydney Sydney locality political New South Wales NSW administrative_area_level_1 political Australia AU country political -33.8671390 151.2071140 APPROXIMATE -33.8764033 151.1911066 -33.8578737 151.2231214 -33.8797030 151.1970330 -33.8559920 151.2229770
"Note however that it is a requirement of the Maps API Terms of Service that you use the Geocoding Web Service in conjunction with a Google map. This means that when it comes time to use cached geocoder results in an application, the application must display the results or any data derived from them on a map generated using one of the Google Maps APIs or Google Earth API."