jack newsome
Member
I collected these points yesterday. They are both shots on the same nail set, and both observations went through the Ph1- 3 validation process. The only reason I caught this is because this was one of two points collected in order to calculate a dist./dist. intersection to an inaccessible property corner, but the COGO routine gave a "no solution" message, which prompted me to check on the two nails set for the offsets. Pt. 51 is the first observation (and the "bad" shot) and pt. 54 is the second observation, which was good; both are on the same nail. The offset nails were close enough together that I could lay a tape down and check them manually.
The "boundary" profile settings used for these observations are: min duration 120 sec, phase 1 min duration 60 sec, 2 engine min, validate with at least 2 engines, verify with V6 re-set, 100 epochs, consistency 20. I was running on a subscription RTN.
This is very concerning, as I have always trusted the validation routine (it is what sets this GNSS equipment apart from others), and now I have to wonder, how many times this may have happened in past?
Maybe someone out there can look at these screen shots and see something I am missing. Any ideas or thoughts about what may have happened here would be appreciated.
The "boundary" profile settings used for these observations are: min duration 120 sec, phase 1 min duration 60 sec, 2 engine min, validate with at least 2 engines, verify with V6 re-set, 100 epochs, consistency 20. I was running on a subscription RTN.
This is very concerning, as I have always trusted the validation routine (it is what sets this GNSS equipment apart from others), and now I have to wonder, how many times this may have happened in past?
Maybe someone out there can look at these screen shots and see something I am missing. Any ideas or thoughts about what may have happened here would be appreciated.