Position API rewrite (was: position accuracy)

[keith preston]

>
> Looks great, although it's pretty hard to read:



Attached as a file


> Agreed, except I don't like returning 0 for missing data -- that has
> bitten me in the ass several times (you can imagine how nice a 3D
> terrain model looks like when some random points in the model have a
> missing altitude value, and that's expressed with a zero...).
>



> > Do you see any good addition to the status enum?   I was going to add a
> > bunch and then I though a human readable string would be better.   The
> only
> > ones I thought might be useful are.   "No Service Available, No Position
> > Available, Currently acquiring position.", are these useful to a program
> or
> > just the user?  If it is useful to the program, then I would add, to the
> > user then piggy back on the string message.
>

I rethought status and here's what I think is better.

A set of flags. bit packed into a int.

0 No Service available
1 currently acquiring Altitude
2 currently acquiring Long
4 currently acquiring Lat
8 Altitude Available
16 Long Available
32 Lat Available

This would solve the hostip altitude probem it could have a status (48)
meaning only lat and long are valid.  So technically you would

call init
call status
call position

hook up signal to position and status to find when things changed.



> > I've been thinking now that we should add a "position_hint" input to the
> API
> > for use in auto submitting your position to Host IP.   There could be
> some
> > kind of configuration for privacy in geoclue master.  I wonder if this
> could
> > be generic for more API.   I know you can do assisted GPS.   is there a
> good
> > way to add this too?
>
> I'm undecided on the data submission issue... I'd probably put the
> submission in a separate program.
>
> I fully agree on the privacy config: there should be geoclue-wide
> position privacy settings that geoclue _and_ applications can use.
> Although it might not be a top priority just yet, this will be very
> important when our position data starts to escape to the internet (like
> with the Gajim XEP-0080-implementation). Speaking of which, we probably
> should follow and take part in xmpp/XEP work in that area.


I think privacy is an issues, but we shouldn't let it affect our api too
much. It should a UI type configuration setting.
I won't put it in now.   I guess it wouldn't be hard for the hostapi to put
it's own listen into itself.

Keith Preston
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freedesktop.org/archives/geoclue/attachments/20070809/c682b06c/attachment-0001.htm 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: position_glue.xml
Type: text/xml
Size: 6008 bytes
Desc: not available
Url : http://lists.freedesktop.org/archives/geoclue/attachments/20070809/c682b06c/attachment-0001.bin