Re: [gdal-dev] GDAL 1.11.0 and Cosmo-skymed L1A imagery

2015-02-06 Thread vf
Well, you are right, I do not find neither the code that I pasted before in the .diff. Probably, it should be a local 'patch' used with gdal 1.10.1 to read correctly CSK imagery. Sorry. I will look what can be done with this code and gdal 1.11.0 version and put the patch in the tracker. -- V

Re: [gdal-dev] GDAL 1.11.0 and Cosmo-skymed L1A imagery

2015-02-06 Thread vf
Thank you for the reply, Even I agree that the patch was firstly to handle correctly dimensions of h5 files : previously it was [width, height, 2] -> nbBands = width. Using patch, dimensions were correctly interpreted. However, the patch contained the following code to handle complex data type (se

[gdal-dev] GDAL 1.11.0 and Cosmo-skymed L1A imagery

2015-02-06 Thread vf
Hello GDAL developers, Recently, I updated GDAL to the version 1.11.0 and found the problem when read CSK L1A imagery : gdalinfo HDF5:"CSK_SCS_TEST_FILE.h5"://S01/SBI shows that image has 2 bands encoded as Int16 While 1,5 year ago, in the ticket http://trac.osgeo.org/gdal/ticket/4227 there was

[gdal-dev] Problem with HDF5 CSK files and .hdr files generated by ENVI

2014-09-15 Thread vf
Dear GDAL developers, I constate that GDAL (e.g. gdalinfo) fails to open correctly CSK hdf5 files which have been read before by ENVI software (and .hdr file is generated near .h5 source file). In this case GDAL uses driver "ENVI/ENVI .hdr Labelled" instead of HDF5 if the file is not present. Sup