W3C home > Mailing lists > Public > public-geolocation@w3.org > June 2008

onChange and raw position vs. error-corrected position

From: Chris Butler <cbutler@dash.net>
Date: Sat, 21 Jun 2008 09:26:27 -0700
Message-ID: <470455FBB46F8749A645E9F732A72C35025ADFF3@ex-be2.dash.net>
To: <public-geolocation@w3.org>

Hi everyone.

I was thinking about the onChange event for location and it occurred to me that there may be two different types of location change events we want to have:

1. Raw feed of lat/lon as understood by the browser (or device or service) which will have 'drift' and 'bounce' around the actual location.  In the case of GPS, this occurs every read of the location.  As a side note, it is up to the location supplier to decide the frequency which they allow a change event to happen, but it could be every available cycle for higher performance applications.  

One potential here is to set a frequency with which the callback wants to be called (maybe every available read, every second, every minute, etc.).

2. Error corrected lat/lon where the supplier of the data tries to remove any bounce and match to some other source of data (such as the case of road matching for a GPS device like Dash) or by using other technologies (such as accelerometers help to do dead reckoning).  Ideally, this would have a frequency that can be set as well...

Ideally, there would be #2 so that applications don't have to worry about trying to do their own error correction.

I would make #1 a MUST and #2 a MAY.



Chris Butler | Content Platform Evangelist, Dash Navigation | Office: 408-543-2939 | Mobile: 415-577-9130 | Fax: 408-400-0939 | Send an address to my car 
Received on Saturday, 21 June 2008 16:27:27 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:33:49 UTC