O.K. it's Mother's Day and my Mom-in-Law is in I.C.U. but that is no excuse.
Probably no-one knows the answer.
As a significant bump:
What GPSD does, and what it cannot do
GPSD solves some of the problems with GPS/AIS sensors. First: multiplexing; it allows multiple applications to get sensor data without having to contend for a single serial device. Second: coping with the hideous gallimaufry of badly-designed protocols these devices use — regardless of device type, you will get data in a single well-documented format. Third: on operating systems with a hotplug facility (like Linux udev), GPSD will handle all the device management as USB devices are plugged in and unplugged.
What GPSD can’t do is pull fix data out of thin air when your device hasn’t reported any. Nor is it a magic power supply, so its device management has to be designed around keeping the attached sensors open only when a client application actually needs a fix.
As you’ll see, these constraints explain most of the design of the GPSD wire protocol, and of the library APIs your client application will be using.
Oy what nice words. gallimaufry
(
It's a word, it's a word)
I'll bump it again with the document link after I read it all.
Oy is not a word but my sheep come to the barn when I yell it.
def: Oy!....you sheep the coyotes are waking up,.....get in here!...
Thanks for the distraction.
Jayburd...
