Nodata value in SRTM result in wrong ortho-rectified image
Mantis Issue 253, reported by jmichel, assigned to abricier, created: 2011-03-11
When performing ortho-rectification in areas where SRTM have no data value (-32768), the ortho-rectified image is wrong : tiling and strip effects appear.
This bug has been fixed a while ago and is showing up again.
1299901618 - christopWhere is the test? ;)
1300197177 - julienI will see if I can add a small patch of coastal quickbird image and the related srtm tile so as to add a test.
1300208041 - julienTest added here : http://hg.orfeo-toolbox.org/OTB/rev/f004e6026a0c http://hg.orfeo-toolbox.org/OTB/rev/6623cf9ed9d4
With data here : http://hg.orfeo-toolbox.org/OTB-Data/rev/a1014576e728 http://hg.orfeo-toolbox.org/OTB-Data/rev/18015147106e
Experimental test failing on dashboard: http://dash.orfeo-toolbox.org/testDetails.php?test=3159401&build=43955
My guess is that in : http://hg.orfeo-toolbox.org/OTB/file/6623cf9ed9d4/Code/Projections/otbElevDatabaseHeightAboveMSLFunction.txx#l46
The default value should be 0, not -32768 (in fact it is how a generated the baseline), for two reasons :
- -32768 is the no data value for SRTM, but for DTED it is -32767, and this function aims at being independant from the DEM type,
- OSSIM converts SRTM no data values (i.e. -32768) into nan() so that they c