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
Le vendredi 06 février 2015 12:32:22, vf a écrit :
> 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
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
Victor,
>
> 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
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
