Even,
Thank you for the suggestion to skip the driver, it is ok for me.
Concerning other files generated by ENVI, I am not sure how it is working,
but I have the only .hdr file after simple opening the CSK imagery.
Here is the content of the .hdr file :
--------
ENVI
description = {
COSMO SkyMed # 3 Prod Type: Level 1A Single-look Complex Sland Acquisition
Mode:ENHANCED SPOTLIGHT Pol: Vertical Tx/Vertical Rx}
samples = 19124
lines = 14378
bands = 2
header offset = 0
file type = ENVI Standard
data type = 2
interleave = bsq
sensor type = COSMO-SkyMed
byte order = 0
read procedures = {envi_cosmo_read_spatial, envi_cosmo_read_spectral}
subset procedure = envi_cosmo_read_scroll
wavelength units = Unknown
band names = {
Real-SCS_U-ENHANCED SPOTLIGHT-VV, Imaginary-SCS_U-ENHANCED SPOTLIGHT-VV}
cosmo info = {
/S01/SBI,
CSKS3_SCS_U_S2_19_VV_RD_SF_20140905173604_20140905173612_qlk_S01_00, none,
none, /S01/SBI,
CSKS3_SCS_U_S2_19_VV_RD_SF_20140905173604_20140905173612_qlk_S01_01, none,
none}
-------
Victor
On Mon, Sep 15, 2014 at 2:48 PM, Even Rouault <even.roua...@spatialys.com>
wrote:
> Selon vf <victor.fomi...@gmail.com>:
>
> >
> > 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. Suppression of the
> > generated .hdr file can fix the problem. Do you think that it is the only
> > solution ?
>
> Victor,
>
> You can define GDAL_SKIP=ENVI as environment variable as well to avoid the
> ENVI
> driver to be used at all.
> We could/should probably register the ENVI driver in last, so to be sure
> it is
> used only after all other drivers have been tried.
> Could you paste the content of the .hdr file ? It is a bit strange that
> such a
> file is generated without a BIL/BIP/BIQ image file that matches it (isn't
> there
> any other file next to the .hdr and .h5 file that would have been
> generated by
> ENVI?). There are perhaps some keywords in that .hdr file that would show
> it
> should be ignored.
>
> Even
>
> --
> Spatialys - Geospatial professional services
> http://www.spatialys.com
>
_______________________________________________
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/gdal-dev
