position accuracy

[Henri Bergius]

On 8/8/07, Jussi Kukkonen <jhkukkon at cc.hut.fi> wrote:
> First, I can't imagine where lat and lon would have (meaningfully)
> different errors... This is not available from gpsd as an example. Maybe
> this was a mistake and the errors were meant to be for horizontal and
> vertical?

So: accuracy_2d and accuracy_3d?

Also, I'm not sure if meters are really the way to go here.

In Midgard I've been using just an integer that gives approximate info
(1=very accurate, 9=maybe city-level accuracy).

This would probably play best with different backends, as for example
we have no idea of per-meter accuracy of hostip.

> Second, the return value "fix_type" is really gps-specific. I don't mind
> the gps-specific parts of the position API (e.g. satellites_data,
> satellites_in_view) too much when they're in their own methods, but I'm
> not too fond of that "fix_type" there.

Just remove it, IMO.

> -jussi

/Bergie

-- 
Henri Bergius
Motorcycle Adventures and Free Software
http://bergie.iki.fi/

Skype: henribergius
Jabber: henri.bergius at gmail.com
Jaiku: http://bergie.jaiku.com/