Re: [gpsd-dev] Newbie questions on gpsd_json discrepancies

[Gary E. Miller]

Yo Pete!

On Fri, 7 Sep 2018 15:52:01 +0000
"Liu, Pete" <address@hidden> wrote:

> I just started on gpsd-dev and hope that the questions are not super
> stupid. I was not able to find related posts in the archive.

Welcome!

> It looks like the "time" fields in all objects are intended to be in
> ISO8601. The descriptions for both GST and ATT objects stated Epoch
> time instead. Both the source code and the example for GST object
> actually use ISO8601. Are Table 4 and Table 5 incorrect?

ISO8601 is just one of many epoch times.  can you clarify your question?


> More importantly, the "time" field for the ATT object is actually not
> supported by gpsd.

The AIS stuff is a dark corner of gpsd.  Checking gpsd_json.c I see that
you are correct, there is no time in the ATT JSON.  You can infer the
time from surrounding messages.

> Although I added a sensor timestamp in the
> attitude struct and updated the JSON output, the client side never
> expects it and is unable to accept any ATT object because of the
> extra "time" field.

Do you really need yet another time stamp?  If so, not too hard to
add it.

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

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

pgp83phvUQY82.pgp
Description: OpenPGP digital signature