Missing part of the processing output (map/3d model)

even though there are quite a couple of postings about incomplete output or input images being ignored, this thing seems to be a bit different, at least I haven’t found any duplicate:

First, let me share with you the data I’m talking about:
Input set of images: https://drive.google.com/drive/folders/1np1w3S9B-gCciH7F_H1NI9vCPY5Pnh3j?usp=sharing
Task output: https://drive.google.com/file/d/12NBpYoi-nfKVjNmHxkzIKysbqFIEcgSd/view?usp=sharing
I’m using ODM through WebODM installed from git and updated (webodm.sh update) just recently. My server OS is Linux 5.7.0 AMD64, Debian Bullseye (11). I installed WebODM according to this guide: https://docs.opendronemap.org/installation.html#linux
My (client) browser is firefox 77.0.1 amd64.
I have tried with original as well as downsized images (2048px), and several different parameters (Default, Forest, Fast Orthophoto), the result is always the same:

The dataset comprises 301 5k images captured at constant altitude (84.5m) and angle (-90°) using a DJI P4P.

The capture area has a “neck” to it, i.e. it’s two bigger areas connected by a narrow bridge.

The output however only consists of the area behind the neck. It seems all images are somehow processed, but ODM seems to yield two separate chunks and gives me only one of them (just a guess).

What’s going wrong here and is there a way to fix it using the given image set?

Thanks a million and best regards!

1 Like

I’d like to bring my topic back up a little bit since it seems to be ignored pretty much and I’m hoping for some advice…

Is there something wrong with my questions? Do you need any further details? Are the files accessible?

I’m a newbie in this, so take the following with a lot of salt.
In my case, I got back the missing parts changing these 2 parameters:

min-num-features (integer) 8000 -> 1000
matcher-neighbors (integer) 8 -> 0

probably because my data set had not all the required qualities.

I hope that helps.

Hi all - I am curious if the suggestion above helped? or if any further changes improved things? I am suffering from something similar…missing sections of the ortho (missing in 3D as well). Interestingly, I am able to run them in sub-sections with no issue at 32k min-features, however when combined part of the image set seems to be ignored at any min-feature setting. If I change the matching-neighbors I am able to switch with portion/area “disappears” in the output…

Any thoughts or updates to above would be greatly appreciated.

1 Like