WebODM Task Finishes Successfully, but Exported Assets Will Not Import Into WebODM

Hey guys and gals,

I recently noticed I have a bit of a recurring issue. Recently I began processing RGB image jobs through my Workstation node but exporting the results to a local Server node to host for internet viewing and access. Both computers are Windows 10 Pro running WebODM through Docker with Chrome as the browser. WebODM I believe is up to date on each computer. After processing/exporting/importing around 15-20 tasks, I realized that ~3-4 have processed successfully on the Workstation and export a ZIP file fine. However, when I import to the Server or even back to the Workstation via WebODM, it fails saying “Invalid ZIP File”. The WebODM task bar is red and the file count for the project indicates zero. One or two of the jobs I have reran and reexported which allowed the ZIP file to import successfully. However, I just had a job run twice with it producing an ‘invalid zip file’ error when importing both jobs back to WebODM.

I’m about to rerun the project for a third time, but I wanted to see if anyone else has had similar issues or any input? Project specs for each run are below:

Options: min-num-features: 14000, camera-lens: brown, depthmap-resolution: 1000, mesh-size: 275000, mesh-octree-depth: 12, dtm: true, dsm: true, dem-resolution: 5, orthophoto-resolution: 2.5, verbose: true

The dataset link is below for the project that failed twice (667 images @ 12MP each), as well as the Task Log File and an exported ZIP of this dataset is included after running successfully but failing to import:

1 Like

Ran the project for a third time and it finished successfully, and it also imported successfully to both of my computers. The only thing that seems different this time around is the file size. The first two runs produced an exported ZIP file of 2,630,870 kb, while the third run produced a ZIP that was 2,616,600 kb.

1 Like