RTK & RTPK

[Shawn Billings - Javad]

It's the same data and represents one point collected. The data is simply processed in two different ways - but still one point. I would argue that technically if both processing schemes reach a similar conclusion that the two results should be averaged together. If the two do not agree within some tolerance, then the user should select between the solutions. I don't think it's appropriate to create two points from the same data though as it implies that the two points were derived separately, which is not the case.

 

[Clay Davidson]

It's the same data and represents one point collected. The data is simply processed in two different ways - but still one point. I would argue that technically if both processing schemes reach a similar conclusion that the two results should be averaged together. If the two do not agree within some tolerance, then the user should select between the solutions. I don't think it's appropriate to create two points from the same data though as it implies that the two points were derived separately, which is not the case.

Its 2 different calculations and 2 different points stored in 1 point number. Otherwise why even have rtpk. It is the same data processed 2 different ways. I respectfully don't agree with your statement.

 

[Nate The Surveyor]

Probably, the basis of shawn's statement is (in part) that they came from the same time window.
And, the basis of Clay's statement is (probably) that they were derived with different software.
So, I'm wanting that cluster screen back, on the collect or stake screen.
Let's put this all together. On the cluster average screen, so that we can have a check box, to "make cluster average from RTK, AND RTPK if they are x.xx apart, or less.
And another check box "create separate point numbers, for RTK, AND RTPK.

Then, put a link to cluster average, on the collect screen, and on the stake screen.

Thank you,
Nate
PS, Now Shawn is happy, Clay is happy, and Nate is Happy.
Happy, Happy, happy!