| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
| |
Try to do it with forward and backward compatibility, which is
challenging with current miscojson.
Sometimes epe was used to 2D estimated erro. Sometimes for 3D error.
So make it explicit eph is 2D, and sep is 3D.
|
| |
|
|
| |
lat/lon/track/etc.
|
| | |
|
| |
|
|
| |
Better detection of NO FIX state.
|
| |
|
|
|
| |
Fixes long standing complaints that gpsd freezes instead of
reporting NO FIX.
|
| |
|
|
|
|
|
| |
Required a regression-test rebuild, of course. The field is still set by
the TSIP and SiRF drivers; the SiRF driver actually uses it. It may be
possible to eliminate the TSIP uses, but so far attempting this has
produced odd regression-test failures.
|
| |
|
|
| |
Required a regression-test rebuild.
|
| |
|
|
|
|
|
|
| |
Protocol version number is bumped. Python and C test clients are known
to work; interfaces of the C and Python client bindings are
unchanged. Third-party client-side bindings which rely on naively
copying JSON members will break (implementers have been repeatedly
warned not to do this).
|
| |
|
|
|
|
|
|
|
|
|
| |
These were causing port problems on systems with 32-bit time. It turns
out the problem was with the assumption that these devices always
deliver a valid time in $GPRMC. They don't when the navigation
warning bit (second field 'V') is on! The NMEA driver now knows.
Also, the code now contains a sanity check - it will log a complaint
if it sees a date moere than a year in the future. This invariably
indicates some driver-level problem with time extraction.
|
|
|
...to something more descriptive.
|
