[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [gpsd-users] STATUS_DGPS_FIX mystery

From: Eric S. Raymond
Subject: Re: [gpsd-users] STATUS_DGPS_FIX mystery
Date: Thu, 21 Jan 2016 17:36:02 -0500
User-agent: Mutt/1.5.23 (2014-03-12)

Gary E. Miller <address@hidden>:
> Yo Roger!
> On Thu, 21 Jan 2016 08:07:59 +0000
> Roger Oberholtzer <address@hidden> wrote:
> > Is there any reason STATUS_DGPS_FIX has been removed from gps.h,
> > while STATUS_NO_FIX and STATUS_FIX remain?
> Good question.  Garmin and uBlox both distinguish between STATUS_GPS_FIX
> and STATUS_DGPS_FIX.  So gpsd can now report a status to userspace that
> userspace can not decode.
> I see the removal in this commit:
>     commit 46c8965d9061d2ca0f3db6710bec6eacea605f40
>     Author: Eric S. Raymond <address@hidden>
>     Date:   Tue Jan 13 08:29:11 2015 -0500
>         Clean STATUS_DGPS_FIX out of the public interface.  All
>       regression tests pas s.
> Eric, any reason for this commit?  Looks like a step backwards.  I
> would like STATUS_DGPS_FIX restored.

Why? What you really want to know in practuce is the XYZ %95 error , no?

I took this out because some devices don't report that status.  But we
can get 95% error ranges ever time from a comptation on the skyview.
                <a href="";>Eric S. Raymond</a>

Attachment: signature.asc
Description: Digital signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]