VertexComponentAnalysis app output importing leads to mvd2 crash
Mantis Issue 754, reported by msavinaud, assigned to salbert, created: 2013-07-26
The output of VertexComponentAnalysis app is not well managed into mvd2. When we try to import it into the database, we have a segfault The image is correctly generated into the result directory.
the otb app alone works weel outside mvd2. The problem seems to come from the import of a quite weird image size=3x1 and 4 bands because when I try to open this image, mvd2 crash.
1381158336 - salbertSeveral crashes are due to: 1- Computed nb of resolutions is 0 in case of images with width or height less than 2 pixels when building GDAL overviews; 2- Images containing one single pixel value (e.g. blank image) when computing histogram from Scott's formula; 3- Images of 1 pixel when computing histogram from Scott's formula.
Fixes: 1- clamped nb of resolutions to 1; 2- forced single-bin histogram when importing 1x1 pixel image; 3- forced single-bin histogram when image has one single pixel value for whole image; 4- Included division by result of Scott's formula in ceil() function.