Error in OdmTexturing:

[ghost]

Im using the test files to do a test of this app, so far I like what I see but when I run it on my VM Ubuntu 64bit I get the same issue no matter which data folder I run it in. Here are the lines leading up the error

---- Total: 0 secs ----


  - running meshing - 


  - running texturing - 
Error in OdmTexturing:
Error in OdmTexturing:
Failed to read image:
'/home/jamison/Desktop/copr//IMG_0028.jpg'

For more detailed information, see log file.


quitting cause: 
    "/home/jamison/Desktop/copr/../odm/bin/odm_texturing" -bundleFile /home/jamison/Desktop/copr/reconstruction-with-image-size-1200/pmvs/bundle.rd.out -imagesPath /home/jamison/Desktop/copr/ -imagesListPath /home/jamison/Desktop/copr/reconstruction-with-image-size-1200/pmvs/list.rd.txt -inputModelPath /home/jamison/Desktop/copr/reconstruction-with-image-size-1200-results/odm_mesh-0000.ply -outputFolder /home/jamison/Desktop/copr/reconstruction-with-image-size-1200-results/odm_texturing/ -textureResolution 4096 -bundleResizedTo 1200 -textureWithSize 3600 -logFile /home/jamison/Desktop/copr/reconstruction-with-image-size-1200/odm_texturing/odm_texturing_log.txt
returned with code 256
jamison@jamison-VirtualBox:~/Desktop/copr$

my guess is that it has something to do the fact that its not finding the images

Failed to read image:
'/home/jamison/Desktop/copr//IMG_0028.jpg'

Need to figue out how to take out that extra '/' in the file address

[bgirardot]

Hi, this is a known issue at the moment.
It is because the file name extensions are uppercase in the test images.
A quick fix is to cd into the directory of images and run this command:

rename 'y/A-Z/a-z/' *

and that will make the whole file name lowercase, things should run fine after that.

[ghost]

Thanks i'll give it a go... I would like to contribute where I can, I do web design and development so if you guys need help in that realm then I could help there

[smathermather]

Working on fixing this in the example data in advance of a patch to compensate for the difference in naming.

[smathermather]

OK. All example datasets have been fixed. We will still want a catch in the code for this, but at least now we won't immediately drive new users crazy... :

OpenDroneMap/odm_data_apt@0ece0bf
OpenDroneMap/odm_data_benchmark@2ccef98
OpenDroneMap/odm_data_caliterra@cb3476a
OpenDroneMap/odm_data_copr@faa0753
OpenDroneMap/odm_data_glam@82e18fa
OpenDroneMap/odm_data_langley@b28267b
OpenDroneMap/odm_data_pacifica@76ab267

[smathermather]

Here's the original issue: #33