For Aerotriangulation... how can I force CC to use the positional information for WGS84 GPS coordinates and NOT let CC change those locations under any circumstance? I am fine with rotation or other details changing, but the coords are not being respected. We have a metadata file that has locations for every image. The locations have been verified outside of CC. If we process a small area, it seems to work. The larger the area, the worse the results.
Orange is (ironically) ground truth and are the images that were unable to be used. Green is what we end up with.
This is from a run of approximately 10,000 imagesHere are my AT settings:
A. Positioning/georeferencing:- Adjustment constraints: photo positioning metadata- Final rigid registration position: photo positioning metadata- Final rigid registration orientation: none- Final rigid registration scale: none
B. Main settings:- Key point density: Normal- Tags or QR Codes extraction: Disabled- Pair selection mode: Default- Color correction: blockwise- Splats: Enabled
C. Estimation policies:- Tie points: Compute- Position: Compute- Rotation: Compute- Pre-calibration stage: Enabled- Focal length: Adjust- Principal point: Adjust- Radial distortion: Adjust- Tangential distortion: Adjust- Aspect ratio: Keep- Skew: Keep
Just wondering why I could be doing wrong. Thanks
It is under presets - "C:\Program Files\Bentley\ContextCapture\data\Presets\AT\Legacy engine.cfg"
You have to import in last step in AT Settings window.
Sorry if I implied they were perfect or near perfect. I didn't expect them to move so much. They are standard GPS coordinates and are of reasonable enough accuracy from what I can tell.I will also try the Legacy Engine option in addition to "maximum position metadata confidence.cfg." I just need to find out where that is.
I just saw this “Maximum position metadata confidence.cfg" from your post and I'm trying it now.
Try "legacy engine" under low-level AT settings.
But your explanation is confusing as at first you said GPS positions are accurate and verified and not just standard GPS.Are all these images taken with same camera?
We have standard GPS positions. As far as I know, that's not going to give me <5cm precision. I'm actually not even noticing a difference when selecting "adjustment constraints" and "final rigid registration" in most some cases. Below is a set of captures going back and forth, capturing a scene from many angles to ensure there is a lot of overlap. I tried exhaustive pair selection and adjustment constraint in this case. You can see it totally trashes the locations of the points. This is a collection from ground level with a standard GoPro (4K images). If I just do a single, continuous video and extract that image set, it will work most of the time. Combining multiple sets even though they have similar overlaps in images almost never works.
I just don't understand why the positions would be allowed to move 20+ meters.
For my testing, I'm trying to capture a street. I go up and down the street and try to capture enough angles that the overlap should be obvious (N, NE, E, SE, S, SW W, NW). But I must be doing something wrong. Maybe my overlaps are not good enough. Maybe my fov is wrong. I know I have enough images because I'm using 0.5 meter spacing so there are a ton of images.
Maybe it doesn't like linear paths? The data is usually not oriented correctly (z up) when I do linear paths... even though it's specified as WGS84 and the height is present in the metadata.
I'm at a loss...
Ground truth (GPS)
Final AT
AT final position vs metadata
Settings for the run above:
A. Positioning/georeferencing:- Adjustment constraints: photo positioning metadata- Final rigid registration: none
B. Main settings:- Key point density: Normal- Tags or QR Codes extraction: Disabled- Pair selection mode: Exhaustive- Color correction: blockwise- Splats: Enabled