Hi Greg, Thank you for your video. However can you explain why you do not get any 1D and 2d Accuracy after the Adjustment of the traverse? You get it only before?
@@surveyorpop Thank you, I'm currently learning Infinity. So you get 1D/2D Accuracy in the Adjusted Traverse results only when the values change more than the rounding settings. In few words if they are blank in the adjusted final results means they are the same as the values Before the Adjustment?
In infinity the error on traverse propertys says 21mm for height but in the wizard with no adjustment is 3mm. I need them to be consistent to trust them
I get the same results in infinity if I select use forward observations only. Coords and error I'm processing the exact same. There is not that option in captivate tho
@@xxploitx Without seeing your data or traverse process I would suggest that you make sure the significant digits are the same on both platforms. That may resolve most of your issue. But, be aware that Infinity allows up to six decimal places while Captivate allows four. This can result in rounding differences.
Really enjoyed your explanation and thank you for sharing 🙏🏾🎊
Another great video! You da man Greg!
Thanks very much!
Thanks for your video, but can you explain me which type method this traverse?
This is a simple compass rule adjustment with angles balanced.
Hi Greg,
Thank you for your video.
However can you explain why you do not get any 1D and 2d Accuracy after the Adjustment of the traverse? You get it only before?
Increase the distance rounding settings in Infinity. You may need to go from 0.001 to 0.0001 or larger.
@@surveyorpop Thank you, I'm currently learning Infinity. So you get 1D/2D Accuracy in the Adjusted Traverse results only when the values change more than the rounding settings. In few words if they are blank in the adjusted final results means they are the same as the values Before the Adjustment?
Got 1mm difference on a couple of eastings. Between infinity and captivate. Can you think of a reason?
In infinity the error on traverse propertys says 21mm for height but in the wizard with no adjustment is 3mm. I need them to be consistent to trust them
I get the same results in infinity if I select use forward observations only. Coords and error I'm processing the exact same. There is not that option in captivate tho
@@xxploitx Without seeing your data or traverse process I would suggest that you make sure the significant digits are the same on both platforms. That may resolve most of your issue.
But, be aware that Infinity allows up to six decimal places while Captivate allows four. This can result in rounding differences.
Thank you very much for your excellent content.
If there's a way to Method PPP
Please explain what you mean by method PPP?