[Top][All Lists]

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

Re: [gpsd-dev] JASON output from gpsd

From: Eric S. Raymond
Subject: Re: [gpsd-dev] JASON output from gpsd
Date: Thu, 4 Sep 2014 15:24:22 -0400
User-agent: Mutt/1.5.21 (2010-09-15)

Doug Robinson <address@hidden>:
> Greetings;
> I may be not understanding the output of gpsd, but I am under the
> impression that the output of the support socket interface is pretty much
> plain NEMA 183.

No, by default it's a custom protocol built on JSON.

There's a "raw" option to allow sentences to be passed though from the
attached devices; if they emit NMEA, it will be NMEA.  There's also an
"nmea" option that synthesizes NMEA from whatever the device ships and
includes that in the socket stream.

Read gpsd_json(5), especially the desription of the WATCH command,
for how to set these options.

> When I queried PolarNavy support I received the following information:
> "*PolarView requires data in NMEA 0183 (or N2K) format.  As far as I know,
> gpsd provides data in their own (xml based) format, at least by default.
> You may want to check with gpsd developers to see if it can be configured
> to output NMEA 0183 data as well. --  Polar Navy Support*"

Polar Navy Support is deeply confused.  There is no mode in which gpsd
emits XML data. There is one *client* program in the distribution that
emits XML.
                <a href="";>Eric S. Raymond</a>

reply via email to

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