diff options
author | Eric S. Raymond <esr@thyrsus.com> | 2011-03-16 19:09:03 -0400 |
---|---|---|
committer | Eric S. Raymond <esr@thyrsus.com> | 2011-03-16 19:09:03 -0400 |
commit | 37f1778c509870731ea52831a58e430c95fdacb0 (patch) | |
tree | bd7cded04ff04b2d5df3a2cd2fd3fb9e1d0d7578 | |
parent | e08c827fe22c3ee2dd107d4795183e0538d8d179 (diff) | |
download | gpsd-37f1778c509870731ea52831a58e430c95fdacb0.tar.gz |
Revised section on time accuracy.
-rw-r--r-- | gpsd.xml | 14 |
1 files changed, 5 insertions, 9 deletions
@@ -2605,15 +2605,11 @@ over ground, 1 second of lag corresponds to 13.8 meters change in position between updates.</para> <para>The time reporting of the GPS system itself has an intrinsic -accuracy limit of 0.000,000,340 = -3.4×10<superscript>-7</superscript> seconds. A more important -limit is the GPS tick rate. While the one-per-second PPS pulses -emitted by serial GPS units are timed to the GPS system's intrinsic -accuracy limit,the satellites only emit navigation messages at -0.01-second intervals, and the timestamps in them only carry -0.01-second precision. Thus, the timestamps that -<application>gpsd</application> reports in time/position/velocity -messages are normally accurate only to 1/100th of a second.</para> +accuracy limit of 14 nanoseconds, but this can only be approximated by +specialized receivers using that send the high-accuracy PPS +(Pulse-Per-Second) over RS232 to cue a clock crystal. Most GPS +receivers only report time to a precision of 0.01s or 0.001s, +and with no accuracy guarantees below 1sec.</para> <para>If your GPS uses a SiRF chipset at firmware level 231, reported UTC time may be off by the difference between whatever default |