| 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.
|
| |
|
|
| |
Odd that it was never there before...
|
| | |
|
| |
|
|
|
| |
A concerted effort to reduce all tests to below 10K in volume each while
preserving all significant test features.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
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.
The immediate reason for this was Savannah bug bug #37810:
satellites_used always zero via gpsd socket with multi nmea GSA/GSV. As the
user reporting said:
The "satellites_used" field in a "struct gps_data_t" filled in by
"gps_read" is always returning zero.
This module emits GNGSA messages in a group of three. My information
is that the first GNGSA pertains to GPS, second to GLONASS, third to
QZSS. It also emits GSV messages using talker id's GL,GP,QZ.
The larger point is that DOPs are likely to be valid for longer than
a GSV reporting cycle; they change only slowly as the actual sat
configuration does. So it makes sense to retain them.
|
| |
|
|
| |
Required a regression-test rebuild.
|
| |
|
