It is likely due to this change: http://groups.google.com/group/google-maps-api-notify/browse_frm/thread/7a24c2837f9195dd
<http://groups.google.com/group/google-maps-api-notify/browse_frm/thread/7a24c2837f9195dd>This would also be a good time to evaluate whether it would be better to use GClientGeocoder instead of the HTTP Geocoder (I've seen various developers make the less optimal choice). I would recommend GClientGeocoder for user entered addresses, and HTTP Geocoder for pre-caching addresses. - pamela On Sat, Oct 17, 2009 at 5:24 AM, Rossko <[email protected]> wrote: > > > Yeah I'm also getting the same problem. I have a script that's > > grabbing off the geocoding service. So I definitely didn't change > > anything in my api key > > Nobody said you did. Before the last few days, it was possible to > get geocoding with a either a broken key, or a missing sensor= > parameter, or both. You wouldn't have known if either of those were > wrong or missing. Now they seem to be enforcing the rules. So it > may never work again if you don't now change something. > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Maps API" 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-api?hl=en -~----------~----~----~----~------~----~------~--~---
