#1 After 70 hours I had some weird/missing results with the ortho when using ORB (more on that later), I’m trying again with SIFT, with these parameters:
Created on: 18/11/2021, 15:06:45
Processing Node: node-odm-1 (auto)
Options: crop: 1, dsm: true, matcher-distance: 60, matcher-neighbors: 24, mesh-octree-depth: 12, mesh-size: 300000, min-num-features: 11000, pc-rectify: true, split: 2000, split-overlap: 200, use-3dmesh: true
When matching image pairs it appears there are 3 possible results:
2021-11-20 13:19:36,821 DEBUG: Matching DJI_0304_5.JPG and DJI_0301_5.JPG. Matcher: FLANN (symmetric) T-desc: 51.936 T-robust: 0.026 T-total: 51.972 Matches: 701 Robust: 659 Success: True
2021-11-20 13:21:19,594 DEBUG: Matching DJI_0020_5.JPG and DJI_0924_9.JPG. Matcher: FLANN (symmetric) T-desc: 67.559 T-robust: 0.018 T-total: 67.582 Matches: 30 Robust: 11 Success: False
2021-11-20 09:26:11,558 DEBUG: Matching DJI_0749_6.JPG and DJI_0804_9.JPG. Matcher: FLANN (symmetric) T-desc: 54.974 Matches: FAILED
EDIT- it appears this 3rd instance happens when there is almost no overlap, which could happen when the terrain is higher, without allowance being made in the flight plan.
However, it appears some points are misplotted, not using the EXIF position.
The single plotted camera position is a long way from the images either side of it, within the dense camera area below it. The position in the header looks to be ok, so why would it be plotted so far away?