averaging observations after calibrating site
when setting up a job with GPS (off the VRS) i typically observe all control points for 3 minutes, then take two that span the scope of the site (preferably in a line such as a prop line, section line...)and use those to calibrate horizontal. then ill use a city benchmark to establish vertical control. however, sometimes i find when i come back the next day to start staking improvements, i will have variances of up to a tenth, mostly vertical, but sometimes 5 hun or so horizontal as well. to improve accuracy, before staking improvements i will re observe all control with 3 min obs and avg the shots. today, i noticed the coords did not change at all though for my point that i had previously used as horizontal calibration.
my question is, once you calibrate the site, are those points that are used in the calibration not affected by averaging observations? if not, does this make avg control points a bad idea, as those used in the calibration may deviate more from those that are averaged multiple times through different 3 min obs? thus, creating more discrepency between control used in calibration, and control not used in the site cal?
only been at it for 2 years now and im thrown to the wolves with no mentor, so i gotta figure stuff out solo.
thanks , cole
Not sure what software you are using, but most major brand software (I know Trimble Access for sure) does not recalibrate on the fly when control points are re-observed. The idea is that all points are observed to desired precision, and then as many as possible are used in the calibration to minimize residuals. (It is highly recommended to use more than just two points. Four points spaced around the exterior of the site is the rule-of-thumb minimum.)
Once the calibration is computed, it is just a set of transformation parameters to go directly from the raw GNSS measurements to local values, so it is not "looking at" the control points any more. So it will not change until you tell it to re-calibrate.
Re-calibrating can be VERY dangerous if you are in the middle of performing stakeout. Read up on how your software handles it before making that decision. Changing a calibration midway through a job is dicey at best.
Also, it all depends on what you are doing, but 0.05' horizontal and 0.10' vertical is pretty great for RTK, even network RTK. Well within tolerances, at least in the areas that I have worked...
There was a recent post about the accuracy of VRS. It seems the general consensus is the vertical accuracy is not as good as a base rover system. We just bought a VRS system and I agree it’s not as accurate as base rover. It also depends on the quality of the VRS systems and how close some bases are.
I also agree I wouldn’t change a calibration once done. I’d also say a calibration doesn’t increase the accuracy of a VRS. I rarely calibrate any more unless forced to by control not on state plane.
That should probably read "not referenced to the same datum as the VRS and on a well-defined projection that the data collector can handle."
I was bringing up state plane because I wasn't sure the OP thought maybe doing a calibration would make the VRS better and more accurate instead of working in state plane coordinates. I'm not sure if that was what he was thinking or not.