I imagine this to be a fairly significant caveat, though perhaps that's more theory than practice. Am I wrong? :<p>"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?
If I go to <a href="http://maps.google.com/maps/api/geocode/xml?address=sydney&sensor=false" rel="nofollow">http://maps.google.com/maps/api/geocode/xml?address=sydney&#...</a> with Chrome I don't get a JSON format:<p>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
Did it always do regions before? It was able to give me at least a rough bounds for "inner sunset san francisco":<p><a href="http://maps.google.com/maps/api/geocode/xml?address=inner%20sunset%20san%20francisco&sensor=false" rel="nofollow">http://maps.google.com/maps/api/geocode/xml?address=inner%20...</a>