gpsd-knowledge-patch

Current gpsd TPV field semantics for altHAE, altMSL, geoidSep, ECEF/NED coordinates, and RTK baseline data are maintained by this patch, ensuring you avoid outdated documentation when building gpsd clients.

Handling gpsd TOFF and PPS timing interfaces requires understanding their precision and clock fields; this patch provides updated reference patterns for these timing reports so your implementation stays aligned with post-training changes.

Using gps_mainloop and shared-memory patterns with the libgps client API is covered by this patch through reference patterns and example workflows, ensuring your gpsd tooling follows current API usage conventions.

Yes, ECEF and NED coordinate data from gpsd can be used for RTK baseline integration; this patch documents the current field semantics and velocity data needed to implement these spatial calculations accurately.

Your gpsd client code may rely on outdated TPV field definitions because post-training changes alter field semantics; applying this knowledge patch aligns your implementation with the current altHAE, altMSL, and ECEF/NED definitions.