Empty Orthophoto and DSM

WebODM
1

Hi

I used webODM in this case (though I am also using ODM and don’t think this makes a difference here) and was able to complete full process without any errors. Looks like the log came clean and I was able to download all assets, but the actual orthophoto file and DSM file themselves, i.e. the TIF, are empty (2kB and not 100s of MB). I am not sure what happened since everything seemed normal. Trying to look at the outputs in webODM I get a “bad request message” at the top left.

log file attached: log_empty_outputs.txt - Google Drive

5
51526×181 22.3 KB
52
52785×343 14.8 KB

52
521572×771 148 KB

Has anyone come across this? Can anyone point to another relevant thread?

Thank you

1 Like
2

This could be lots of things. Is this a dataset you can share for testing?

1 Like
3

It just happened again today using ODM (not webODM) on this data set:

I’m running ODM 0.9.8 on Ubuntu 18.04, 32GB. I ran with default params except --dsm and --dtm options only.

ortho, dsm dtm were on the order of KB and not 100s of MB. I accidentally did not save the log but I have all output folders. Couldn’t find the log there. Is there a place where the log from the run is automatically saved?

I’ll upload the other data set and post it here. I already linked in the previous post to the log of that run.

4

Attached is the data of my first post. It has two sets of JPG images. Using both sets invokes a multi-camera mode in ODM with the log message:

 [INFO]    Increasing matcher neighbors to 16 to accomodate multi-camera setup
 [INFO]    Multi-camera setup, using BOW matching

As noted it ran all the way through as if all was well. The multi camera mode seemed to have worked, cameras.json file is:

    "sony a7_lower_left 3776 2502 brown -5537. agro_a7": {
        "p2": 0.0, 
        "p1": 0.0, 
        "width": 3776, 
        "projection_type": "brown", 
        "height": 2502, 
        "k3": 0.0, 
        "k2": 0.0, 
        "k1": 0.0, 
        "focal_y": -5537.604456824513, 
        "focal_x": -5537.604456824513, 
        "c_y": 0.0, 
        "c_x": 0.0
    }, 
    "sony dsc-rx0 4800 3200 brown 0.6666 rx0": {
        "p2": 0.0, 
        "p1": 0.0, 
        "width": 4800, 
        "projection_type": "brown", 
        "height": 3200, 
        "k3": 0.0, 
        "k2": 0.0, 
        "k1": 0.0, 
        "focal_y": 0.6666666666666666, 
        "focal_x": 0.6666666666666666, 
        "c_y": 0.0, 
        "c_x": 0.0
    }

Also, textured model was created:

6
6703×624 166 KB

https://drive.google.com/file/d/1ANH9rD5EZnsxV4TTPjzchvA4YQTFJwDN/view?usp=sharing

Since this happened in two data sets and webODM and ODM - I suspect there may be a chance it is not data related, but I may be wrong.

5

I have the same problem. Have you resolved?
Thanks

6

Actually I wasn’t able to point out why it happened. Subsequent data sets in multi-camera did not yield this phenomenon.

Are you using multi-camera?

7

Thanks for answering. No, I’m not using multi-camera.