The reason is bandwidth & processing footprint. I am developing on a mobile platform where bandwidth and processing resources are scarce - so I would much rather just get the data and skip the GClientGeocoder javascript download. I understand there is a trade-off though, I'll take a look at the footprint of the GClientGeocoder js client and re- consider if needed
Thanks! On Oct 30, 1:09 pm, Barry Hunter <[email protected]> wrote: > The question is why are you using the geocoder directly in this way? I > wouldn't be surprised if it gets blocked. > > Within a webpage, you have GClientGeocoder which you should use. > > There is a HTTP interface for server side access. > > But they are the only documented access methods. > > 2009/10/30 Hugo <[email protected]>: > > > > > > > As of yesterday aJSONPcall to get reverse-geolocationdata worked > > just fine - no longer seems to be the case today. > > > If you paste this link (w/jsonpcallback arguments) in your browser > > it will return a 400 "Bad request" > > >http://maps.google.com/maps/geo?callback=jsonp1256888593627&_=1256888... > > > If you take out the callback arguments, leaving the rest of the URL > > unchanged, all is good (200 http code, json data returned) > > >http://maps.google.com/maps/geo?q=37.758199,-122.394628&key=ABQIAAAA-... > > > Havejsonpcalls been banned? That would seem...surprising... > > -- > Barry > > -www.nearby.org.uk-www.geograph.org.uk- --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
