W3C home > Mailing lists > Public > whatwg@whatwg.org > February 2007

[whatwg] Geolocation in the browser

From: Gervase Markham <gerv@mozilla.org>
Date: Thu, 22 Feb 2007 15:07:58 +0000
Message-ID: <45DDB1CE.1090504@mozilla.org>
Ryan Sarver wrote:
> The biggest problem with this implementation is that it requires an
> additional service on top of standard GPS. 

I wasn't envisaging any geocoding services. In my example, the address 
would be one the user had entered, and (assuming the machine has GPS at 
all) the browser had remembered as being at particular GPS coordinates. 
For desktop machines which never move, the browser may well have 
geocoded a typed-in address once and stored the lat/long to give to 
websites.

If the machine has GPS, the default option in the dropdown might be 
"Here: <lat>, <long>". But there would be other options. I think it's 
important that the user be able to give a location other than his 
current one - for example, if he's at work, but looking for the closest 
pizza restaurant to his home.

The "granularity" setting is for privacy; I was imagining that the 
browser would round the actual value to the nearest whatever was 
appropriate, in order to introduce the necessary degree of uncertainty.

Gerv
Received on Thursday, 22 February 2007 07:07:58 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:08:32 UTC