Tue 31 Oct 2017 03:22:34 AM UTC, comment #3:
> Just for the record as I see the issue is already closed:
Easy to reopen if you can make a case.
> gpsd in this case receives data from GPS receiver, data
> received by gpsd indicate that there is no fix (e.g. on RMC
> but also in
> other messages), but I understand that it's your
> intention/design decision to ignore this.
No, not at all. the case i thought we were talking about was where gpsd receives nothing, and thus has nothing to send.
So you need to supply more details. What exactly are you getting from your GPS that gpsd is failing to send on?
> the issue is though that instead of getting information about
> the missing fix immediately when it happens I must wait for
> the timeout to expire.
Yes, I agree, IFF gpsd is dropping data that is bad.
If you have data that shows that, I'll reopen this bug.
> Also JSON interface description of gpsd seems misleading as
> mode=1 is a documented value expected to be sent when there is
> no fix,
Not exactly. gpsd needs to be told by the GPS that there is no fix before sending a notification.
> i.e. timeout is not a documented way of finding out that there
> is no fix.
Documentation change requests will be happily reviewed. especially as this subject keeps coming up regularly.
|