Any idea on what the issue might be with full size images giving this error?
I’ve just been down the road collecting over 800 images of a few sections of our road, which is in terrible condition, full of potholes, and I’m seeing this error again.
Processing continues past this error, but it would be nice to know why I’m seeing it.
[INFO] running “E:\WebODM\resources\app\apps\ODM\SuperBuild\install\bin\opensfm\bin\opensfm” match_features “E:\WebODM\resources\app\apps\NodeODM\data\aa3fad0a-98c6-485a-bab4-ce83d9451907\opensfm”
2022-03-13 14:30:17,244 INFO: Altiude is negative (-77.26879427249487) : viewing directions are probably divergent. Using default altide of 1.0
2022-03-13 14:30:17,244 INFO: Altitude for orientation based matching 1.0
2022-03-13 14:30:17,266 INFO: Altiude is negative (-77.26879427249487) : viewing directions are probably divergent. Using default altide of 1.0
2022-03-13 14:30:17,266 INFO: Altitude for orientation based matching 1.0
2022-03-13 14:30:17,335 INFO: Matching 1309 image pairs
The few images I’ve checked have altitudes in the 550-575m ASL range listed in EXIF.
It’s not only M2P images, another DJI drone’s camera I ran through a couple of days ago (Crop = 0 but still crop the corner) had an altitude over 200km below ground.
Where is it getting these numbers from?
The set of images I took this afternoon were between 8 and 25m above ground, as it says in the headers, and just under 650m ASL, also in the header, so how is this determined, as it bears no relationship to EXIF altitudes?
2022-04-02 14:08:24,373 INFO: Altitude for orientation based matching 1.8053909085861939