bz at datenkueche.com
Wed Mar 17 16:24:56 GMT 2010
If it's more than 10m I stop recording and start a new track if signal
is ok again.
Here I can just walk around the block. I'm still sitting here in Phnom
Penh with bad
med. disc <http://www.dict.cc/englisch-deutsch/disc.html> prolapse
<http://www.dict.cc/englisch-deutsch/prolapse.html> and can't test
(walk,ride,drive) that much.
I will set the accuracy to 100000000m for testing and then change it to
steve brown schrieb:
> I personally find anything over 10m accuracy is pretty worthless, and
> thats the value I use in my own code. I can usually get 2-3m accuracy
> (as reported by phone) when holding my phone in my hand.
> OpenSatNav for Android currently uses 50m, as one of our developers
> wanted to use it for mountain biking with the phone in his pocket, but
> I'm going to add in a slider so the user can choose a level of accuracy.
> Hope that helps
> On 17 March 2010 15:22, Bernhard zwischenbrugger <bz at datenkueche.com
> <mailto:bz at datenkueche.com>> wrote:
> Hi again
> iPhone has the geolocation API.
> There is a parameter "accuracy".
> It's a value in meter that gives you information about
> exactness <http://www.dict.cc/englisch-deutsch/exactness.html>
> Indoors the API findes the position with wifi or what ever
> The accuracy is sometimes at 500m or more.
> What's the OSM accuracy. When to drop?
> I need a value in meter.
> What's ok as a OSM GPX coordinate and what is not.
> Btw. real GPS data have a height value.
> dev mailing list
> dev at openstreetmap.org <mailto:dev at openstreetmap.org>
More information about the dev