[whatwg] Geolocation in the browser
kornel at osiolki.net
Sat Feb 24 06:32:53 PST 2007
On Fri, 23 Feb 2007 15:15:13 -0000, Gervase Markham <gerv at mozilla.org>
>> Postcode would be easiest way to integrate location API with existing
>> services (especially via userjs/greasemonkey, where using
>> location->postcode database may be difficult).
> The problem with suggestions like this is that they require geocoding on
> the server side. Geocoding services are not always readily available;
> there's no free, unencumbered implementation I know of. And you need a
> different database for every country.
API I've suggested allows browsers to provide various representations of
the location, so there can be best effort on both sides.
> I guess I don't object to the browser returning this information
> additionally if it knows it - but lat/long should be the baseline,
> always-present info.
But what about browsers that don't have access to GPS device nor geocoding
service? These browsers could still return city and postcode information
provided by the user and that could be enough for many applications
(nearest branch locators, etc.).
>> navigator.getGeolocation() would return location with best precision
>> allowed by default (without asking user every time). If user set in
>> preferences that every page can get location with 10km precision, that
>> would be returned.
> I think it's better to ask every time and remember the precision
> allowed. I would certainly much prefer to know who knows where I am.
Ofcourse there should be option to ask every time, but it can't be the
only option. Some users may prefer not to be bothered and have
location-based services just working. Also there are IP<>geo databases, so
some users may want to allow giving away information that has
approximately same accuracy.
regards, Kornel Lesiński
More information about the whatwg