Re: GPSD doesn't report signal dropout

[Gary E. Miller]

Yo Greg!

On Tue, 13 Oct 2020 09:25:02 -0400
Greg Troxel <gdt@lexort.com> wrote:

> "Gary E. Miller" <gem@rellim.com> writes:
> 
> > There is more to this than meets the eye.  The messages that we are
> > talking about here do not include any status at all.  Most NMEA
> > never outputs any status.  The Quectel never outputs status.  So
> > the problem is in the client.
> >
> > status is for binary protocols like u-blox.
> >
> > I did change libgps_json.c to default status to STATUS_NO_FIX if
> > there is otherwise no status.  
> 
> That sounds like progress.
> 
> Where I'm coming from is not remembering all these details and the
> notion that the json interface should be usable without knowing
> anything about the receiver.   So ideally, I'd think the status
> information should be synthesized from what exists (such as the
> validity flags). Otherwise, I don't see how a user of  the json can
> decide whether to respect the status information without  knowing
> more than it ought to know, abstraction wise.

Once again, this is NOT in the JSON.  status is only reported in the
JSON when available.  The stupid Qeuctel is not reporting status and
gpsd is not passing on what it does not have.

This is a client problem.

Also, if you have no fix, it makes no difference if it is 2D, 3D, DGPS, or
other type of fixe, because you hahve no fix to qualify like that.

RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
        gem@rellim.com  Tel:+1 541 382 8588

            Veritas liberabit vos. -- Quid est veritas?
    "If you can't measure it, you can't improve it." - Lord Kelvin

pgpXxhegdBkbV.pgp
Description: OpenPGP digital signature