|
Differences Between Measuring and Averaging Q When collecting data the TSC1 has different "formats". Ie: topo point, control point, etc. It appears that when you go into Data Collection/Point
it is preset for 3 epochs. We played around with the epoch averaging value, but the manual states that may not be the best solution to
average. The TSC1 needs to see 3 out of 5 epoch meet the criteria for a topo point, and more if desired for the control point. Can
that be done in TDS? What is the difference between "measuring" and "averaging" in the data collection screen?
A Epoch averaging is a technique that should only be used when the receiver is not set to static
mode for point occupations. Reason is that when you set the receiver to static mode, the RTK engine starts to apply a Kalman filter to
the positions, effectively making each returned position more precise than the last. Therefore, if you average epochs with the receiver
set to static, you are actually downgrading your final solution by averaging it with several other solutions that are mathematically
inferior. In reality, after about 10 epochs, the solution is stable (watch the RMS values decrease for 10 epochs and then level off) so averaging after allowing the solution to stabilize is not a problem and will maybe filter out some pole wobble. My recommendation
is to hold the pole still and tap accept with no averaging once you are happy with the measurement.
Measuring means that the interface is displaying the latest values returned from the receiver. Averaging is displayed after user taps
accept and is collecting some epochs to average.
In TDS, best shot is taken by setting receiver to static, then waiting the desired amount of time (3-5 sec for topo point, up to 30 sec for control point) then tapping accept. |
