Hey there,
Absolutely - I am very much aware that it's unreliable and isn't
always able to geolocate you, however, it seems to not work _at all_
now.
ie: We run it as one of several geodetection methods we use on our
app, and a few days ago, the Google client location simply stopped
returning values for everyone (as far as we can tell) - Wondering if
anyone else had noticed this.
Short of GeoIP, do you have any other particularly recommended
options?
Cheers,
Fenn.
On Jan 26, 11:27 am, Jeremy Geerdes <
jrgeer...@gmail.com> wrote:
> This is a very well known issue with the ClientLocation feature. If Google can't geocode the IP address, it returns null. And it does this a lot. Simply put, the ClientLocation feature is to be considered absolutely unreliable for production applications. There are many alternative services that you should consider instead.
>
> Jeremy R. Geerdes
> Generally Cool Guy
> Des Moines, IA
>
> For more information or a project quote:
>
jrgeer...@gmail.com
>
> If you're in the Des Moines, IA, area, check out Debra Heights Wesleyan Church!
>
> On Jan 25, 2011, at 6:13 PM, Fenn wrote:
>
>
>
>
>
>
>
> > Hey All,
>
> > I've noticed in the past few days that the Google loader JS API seems
> > to have lost its ability to geocode.
>
> > I'm not 100% certain that it's the API and not just me, however I have
> > been unable to find an IP across several countries that can
> > successfully geocode.
>
> > In all cases,
http://www.google.com/jsapi(with or without key) always