Had executed below command to generate DSM from tiff file(file size > 1GB) with following command: docker exec -it python3 /code/run.py --project-path /datasets project --dsm --orthophoto-resolution 2 --geo /code/geo.txt The previous issues wrt file size & undistorted are resolved. Now the script …

Hope the above information will be helpful to the community.

Had ran ODM with few values and following were outcomes: When ran ODM with 5 files with default max_texture_size it failed with an error - ran out of memory. Here 99% of texturing step got completed and it failed at last stage Next when ran ODM with 24 files with default value it failed with s…

Maybe try this: MAX_TEXTURE_SIZE (439330 * 1024) That should fit an entire image in one texture page… No idea how bad this will break, though.

It failed with an error std::bad_alloc

Alright, so it seems like we’re exceeding something in MVS_Texturing that just setting the MAX_TEXTURE_SIZE bigger doesn’t address. https://en.cppreference.com/w/cpp/memory/new/bad_alloc Okay, it looks like we’re using UINT (Unsigned Integer), which I think is just slightly too small to allocate s…

I’m pretty sure you cannot process images this large with ODM (what kind of images are these? Satellite?)

Can you help with updated the script?

Trust me, you do not want me near code.

After Max_texture_size 24*1024, the script starts failing with an error std::bad_alloc…

Yep, so like I said above, I think we’d need to be re-writing the code to use another UNIT storage that is bigger than 32bit since we’re getting larger texture dimensions than it can hold. Just adjusting the script isn’t going to address that limitation.

OpenDroneMap Community

Mystex stage fails

ODM

docker

Saijin_Naib October 1, 2021, 8:10pm 13

PIL.Image.DecompressionBombError: Image size exceeds limit of pixels ODM

These are actual raw images and resizing is not an option because camera parameter needed for DSM calculation will not be applicable.

show post in topic

Home
Categories
Guidelines
Terms of Service
Privacy Policy

Powered by Discourse, best viewed with JavaScript enabled