Looking for some input on best settings to get a properly geo-referenced aero-triangulation. Let me first say that I know that the input photo data is good as I have successfully produced a nice model of the data from the DJI Terra software that used the same photos (a little over thousand photos). I have read the few other posts on this forum on this topic and I was actually able to get one project to process successfully by following the advice in those posts and loading one of the pre-set low level settings described in those posts. However, this was when I was using CC Version 17.
I have recently upgraded to the latest version of Context Capture (version 10.18.0.270) and I have not been able to get a successful geo-referenced aero-triangulation on this version with the P1 camera. I saw in one of the other forum post that the processing engine changed for version 18 and it is no longer necessary to load the low level preset "do not use pose metadata for SfM". Also, I noticed that this preset is no longer available for selection in the list of presets.
My data set/photos are from a "smart-oblique" mission and I have selected the "structural aerial data set" in context capture.
I have literally tried at least 10 different aero-triangulation attempts with all different combinations of settings to no avail. I would post the settings, but I believe I have tried them all to no avail. The warning I get is shown below.
I would really appreciate any feedback as I am currently at a stand-still to model this project in Context Capture.
Update 18 processing engine changes are pretty terrible.It utterly fails to do aerotriangulation properly for large projects, only managing to produce a curved output. and no amount of adding tie points / GCPs or settings changes will fix that.
Only way I managed to get a multi-flight project processed, was to do AT on every flight separately, and then merge those projects. Which took forever. Bentley has some unfortunate habit of doing undocumented, or at the best case poorly documented, changes to ContextCapture, which utterly breaks existing workflows and processing settings.
This is far from only time when contextcapture update has lead to processing failures, using exact same settings that worked flawlessy on previous versions.
P1参数的问题,