What is difference between accurate and inaccurate position setting in aerotriangulation? Even if choosing accurate metadata it still uses compute method for position/rotation and produces wrong results even initial positions are correct. How accurate should be positions to count as accurate metadata?
Why even in accurate georeferencing the positions seems to be ignored? Seems the aerotriangulation is too relax and accurate metadata can be used even with consumer grade GNSS.
I asked this same question a couple of months ago. See communities.bentley.com/.../control-points
Farouk Rohoman
I see that it was left unanswered. Seems Contextcapture is acquired as black-box by Bentley as no in-depth technical info is shared.
For AT Estimation policies, why is Position and Rotation greyed out? I'm on update 16. I would like to change the Position from Compute to 'Adjust within tolerance' for use with my DJI P4 RTK. Thanks
For RTK you use accurate metadata option.