On Jan 26, 3:12 pm, CGIDev <[email protected]> wrote: > Has anyone noticed this? After diagnosing this issue internally, > adding the "sensor=false" query parameter to the request URL (http:// > maps.google.com/maps/geo?q=....") seems to have fixed our issue. As of > 5PM eastern time, both the old request (with out sensor parameter) and > the new request are working. > > My question is: since the API documentation located > here:http://code.google.com/apis/maps/documentation/geocoding/index.html#R... > indicates the sensor parameter is required, should we update our > client code which uses the premier API key to use this parameter as > well?
You probably should ask your Premier Rep. -- Larry --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
