How to deal with MW output extension .img
Mantis Issue 16, reported by jinglada, assigned to cvalladeau, created: 2008-10-29
Collision of image format extensions between ERDAS (Gdal) and MegaWave.
Eric Bughin has modified the class in order to accept .img, .mw and no-extension files for read, but only .mw for write.
1231834475 - julienSame problem for pds data available here : http://download.osgeo.org/gdal/data/pds/
1231841781 - julienAdded four tests to hightlight this in Testing/Code/IO. The tests highlight that one of the two images available on gdal.org is properly read by gdal and otb::ImageFileReader, while the other is not : gdal can not read it, and that is probably why MWImageIO is trying to read it too.
It is important to note that gdalinfo is not able to read this image outside of the Orfeo ToolBox.
1313594153 - C ValladeauThe 4 MWImageIO tests seems to pass now. What's the status of the bug?
1313637534 - christopNo test is checking if we can write megawave img (but is that something we want?)
1321458250 - C ValladeauHFAGeoreferenced.img => mg not from MW QB_Toulouse_Ortho_PAN.img => from MW
I've made some tests : The ioTuMWImageIOCanRead Tests applied to a .img from MW returns true. The ioTuMWImageIOCanRead Tests applied to a .img not from MW returns false. The ioTuMWImageIO