(1) ODM fails if there is a space in the filename Ok, so I’ve dug a bit deeper and it looks like both those issues are true, ie running "/code/SuperBuild/install/bin/opensfm/bin/opensfm" export_visualsfm -points "/var/www/scratch/nodes/d31193b7-175a-4d0c-bd2e-236aa08e4856/opensfm" Thanks in advance 09:35:57,169 DEBUG: Undistorting image DJI_1681.TIF Is there any additional documentation beyond this page that explains how ODM manages multispectral datasets? Or does anyone know of any code or better workflows for digging through datasets of thousands of poorly named DJI multispec images to read their exif or something to label them in a less opaque way so we can make this process more user friendly? According to the multispec processing manual ( link) they do seem to be labelled in the EXIF at least, so we could write some code to rename or better organise the images and name them if this doesn’t exist already (although will this break other DJI data like RTK from the flight that refer to images by name?). This issue is made additionally confusing by DJI since the flights take so many images and there are frequently duplicated image numbers in different folders from the same flight so you end up with duplicate image names (eg “DJI_0041(2)”) for images from different parts of the flight, if you put them all in a single folder for easier data management post-flight and for upload to ODM. I have no doubt this flight is likely missing images from some bands for some photo points, but the images labelled missing in the log actually do exist, so I’m not clear if the error means I am actually missing image “DJI_0041(2).TIF” for example (which I shouldn’t be) or if it is looking for say the image that represents the 2nd band for that set of 5 images since the use of the _blue.nvm file implies that these are files for the blue band. However, given I own this stupid drone and need to do flights with it, I’m wondering if anyone knows either a workaround for this or can further explain the error message I’m getting (see below). This is squarely the fault of DJI’s horrible multispec implementation since they number the images from all multispec bands in the same shared numbering sequence (ie DJI_001, DJI_002, etc) and don’t bother to differentiate or label the different bands in any discernable way so there is no way for a user to audit their 2,000 TIF images from a flight to assure that each photopoint has all 5 images. In this flight I was capturing 5 bands but (as usual, the drone flight failed mulltiple times), so my interpretation of this error is that some of the image-sets aren’t complete b/c the drone didn’t get all 5 bands for a particular image. I’m trying to process DJI multispectral images and keep getting errors that it can’t find a particular TIF.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |