Luisa,
you didn't mention which GDAL version you are using. Since Brent manages to
make it work with a very similar command line that the one that fails for you,
I highly suspect you are using an old version. There was indeed a bug very
similar to your issue ( http://trac.osgeo.org/gdal/ticket/
Luisa,
That sounds like a bug. A possible work-around might be to set your
current working directory to D and don't put the drive letter in the
filepath:
cd D:
gdalinfo \data\GL.hdf
But this may not work with your desire to use a GRASS script...
Best Regards,
Brent Fraser
Hey Brent
I'm using ESA's GLOBCOVER data.In this case I'm trying to set a GRASS script
to run gdal directly.
I do:
gdalinfo C:\data\GL.hdf and I retrieve all basic information plus HDF's
layers
Driver: HDF4/Hierarchical Data Format Release 4
Files: c:\data\GL.hdf
Size is 512, 512
Coordinate System
Luisa,
I use GDAL to access MODIS data in HDF4 on Windows like this:
gdalinfo
HDF4_EOS:EOS_SWATH:"G:\Projects\temp\image3\MOD02HKM.A2011186.1640.005.NRT.hdf":MODIS_SWATH_Type_L1B:EV_500_RefSB
So I'd suggest using double quotes around your path.
Best Regards,
Brent Fraser
On 8/9/2011 8:24
Greetings
This seems odd but it does not work with
HDF4_EOS:EOS_GRID:C:/filepath
only
HDF4_EOS:EOS_GRID:filepath
And if my MERIS data is not placed in my main hard disk (C:) it does not
work.
Anyone with some experience on this in WINDOWS?
Thanks
Luisa
___
