| 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.
|
| |
|
|
| |
Odd that it was never there before...
|
| |
|
|
| |
Replace zero times with blanks.
|
| | |
|
| | |
|
| |
|
|
|
| |
This released a flood of GPGBS. But the GPGBS are wrong format
according to NMEA 3.0...
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The start of this overly large patch was to simply move the test
for MODE_2D/3D flipping, which only affect NMEA 183, back into
driver_nmea0813.c
But that was intertwined with how gpsd_error_model() computes
derived variables, which required major changes to how NMEA 183
mode_2D/3D are set.
This ultimatly led to major regression test results. Almost all for
the better.
I tried to break it up, but moving from one paradigm to another
needed one big jump...
|
| |
|
|
|
|
|
|
|
|
|
|
| |
At one point, the check for MODE_SET made sense in
gpsd_binary_quality_dump(). But since then, the calling code was
refactored to only invoke nmea_tpv_dump() when REPORT_IS is set,
eliminating the dupes.
Remove the MODE_SET check and update the affected binary regression
check files to contain the expected GSA sentences.
Signed-off-by: Gary E. Miller <gem@rellim.com>
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
...from a set of parallel arrays. This change flushed out a
longstanding bug in the computation of DOPs for estimated error bars.
Some test-load rebuilds were required:
geostar-geos1m-binary.log.chk: With this change error
estimates are computed and reported.
trimble-lassen_iq-3dfix.log, trimble-lassen_iq-3dfix.log: the
change revealed a bug in the computation of satellite-seen bits.
Error estimates did not change.
navcom.log: Error estimates changed.
With these rebuilds, all regression tests pass.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
Add macros for classifying PRNs into GPS, GLONASS, DGPS. Document the PRN
ranges on the gps_json manual page.
It turns out that U.S. GPS authorities reserve 1-64 for GPS birds, not just
1-32. So the way we map GLONASS PRNs had to change. This required a
regression-test rebuild for the geostar driver.
|
| |
|
|
| |
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).
|
| | |
|
| |
|
