Select to expand quote
Roo said..
Love all the enthusiasm but the reality is 1 cm level precision in a stand alone hand held unit will never happen in my lifetime.
You're probably right about the 1 cm precision; typical real-world precision claims are 2 cm to 8 cm. Although your "not in my life time" reminds me a lot of what people said early in the Human Genome Project. Several articles come to mind where the authors painstakingly explained by it would be impossible to exceed the current performance by much, claiming physical limits had been reached or similar. They were proven wrong within a few years, as others discovered how to get around the limits.
In the United States, many states already have public base station networks, where the necessary reference data can be downloaded for free*. The state I live in, Massachusetts, has base stations spaced about 50 km apart**. Two of these are within less than 10 km of a speedsurfing location, and thus close enough. They state
"the MaCORS Network Solution typically achieves an RTK accuracy of 1-2 cm horizontally and 2-3 cm vertically." Your comments regarding simplicity are certainly valid. There are several members in our GPSTC team who find posting data quite challenging. Some of them like the ka72.com site, which simplifies things for them. Setting up a similar web service that analyzes raw GPS data is not much harder. The service could either load the reference data from the web automatically (if available), or require the upload of a second file from a reference station. So maybe that's twice as hard.
Regarding the accuracy of doppler data, I usually have a hard time finding anything that contains actual data, other than Tom Chalko's original paper. Sure, spikes are
much less common, and having accuracy estimates is great. But what is the actual accuracy?
For GT-31 data, typical errors (given by GPSResults) for single data point in speed around 30 knots are +-0.5 to 1 knots. 10 second run errors are typically +- 0.3-0.5 knots. That's 1-2% accuracy.
For 5 Hz ublox data, I get errors of +- 0.3-0.6 knots at speeds around 30 knots. That's 1-2%. That goes down to +- 0.15 knots when looking at 10 second runs. 0.5% accuracy.
If we had positional data with an accuracy of +-3 cm (relative to the base station, not absolute), we'd also have an accuracy of +-1-2% for 1 second data points, since 30 knots is about 3 m/sec. But the error model for average speed changes! To get Doppler speed for 10 seconds, we average the individual speeds. By assuming that errors are random, we get lower errors when looking at more data points - either longer runs, or higher frequency data. Of course, if there is a systematic error in the doppler speeds, our accuracy estimates will be incorrect.
For positional data, however, the errors do not accumulate. If any point has a precision of +- 3m cm, the expected error for two points that are 10 seconds apart is +-6 cm or less. 6 cm of 30 meters is 0.2%. That's
better than 5 Hz doppler data.
Note that for 500 m record runs, using positional data is actually conceptually more similar to gate timing than using Doppler speeds. Again assuming 3 cm errors, but allowing for 3 sigma on both ends, the observed time different to cross a distance of 500.18 m would give us a reliable estimate of the minimum achieved speed. Adding the 18 cm "safety" would add an expected error of 0.036%. For comparison, the +- error margins I get in GPSResults for 500 m runs are around 0.8% for GT-31 data, and 0.3% for 5 Hz ubox data. So positional data could actually be substantially more accurate, even at +- 3 cm.
*
www.gpsworld.com/finally-a-list-of-public-rtk-base-stations-in-the-u-s/ **
macors.massdot.state.ma.us/spiderweb/frmIndex.aspx