Opened 17 years ago
Closed 17 years ago
#1351 closed defect (fixed)
how to support HDF-EOS format
Reported by: | Owned by: | warmerdam | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | GDAL_Raster | Version: | 1.3.2 |
Severity: | normal | Keywords: | |
Cc: | Juergen.bayer@… |
Description (last modified by )
I have a problem ! I can get the subdatasets in a hdf file,but when I use GDALOpen to open one of the subdatasets, It tell me that "ERROR 4: `HDF4_EOS:EOS_SWATH:"d:\Swathc_Test.hdf":OnedGeo:CalB' does not exist i n the file system, and is not recognised as a supported dataset name." why this happened? what should I do if I want to support the hdf-eos format Subdatasets: SUBDATASET_1_NAME=HDF4_EOS:EOS_SWATH:"d:\Swathc_Test.hdf":Simple:Temperature SUBDATASET_1_DESC=[100x40] Temperature (32-bit floating-point) SUBDATASET_2_NAME=HDF4_EOS:EOS_SWATH:"d:\Swathc_Test.hdf":Simple:Conduction SUBDATASET_2_DESC=[100x40] Conduction (32-bit floating-point) SUBDATASET_3_NAME=HDF4_EOS:EOS_SWATH:"d:\Swathc_Test.hdf":Simple:DataOne SUBDATASET_3_DESC=[100x40] DataOne (32-bit floating-point) SUBDATASET_4_NAME=HDF4_EOS:EOS_SWATH:"d:\Swathc_Test.hdf":Swath64:SensorA SUBDATASET_4_DESC=[100x40] SensorA (32-bit floating-point) SUBDATASET_5_NAME=HDF4_EOS:EOS_SWATH:"d:\Swathc_Test.hdf":SwathLatonly:Gain SUBDATASET_5_DESC=[100x40] Gain (32-bit floating-point) SUBDATASET_6_NAME=HDF4_EOS:EOS_SWATH:"d:\Swathc_Test.hdf":Swathco:BandC SUBDATASET_6_DESC=[100x40] BandC (32-bit floating-point) SUBDATASET_7_NAME=HDF4_EOS:EOS_SWATH:"d:\Swathc_Test.hdf":OnedGeo:CalA SUBDATASET_7_DESC=[100x40] CalA (32-bit floating-point) SUBDATASET_8_NAME=HDF4_EOS:EOS_SWATH:"d:\Swathc_Test.hdf":OnedGeo:CalB SUBDATASET_8_DESC=[100x40] CalB (32-bit floating-point) SUBDATASET_9_NAME=HDF4_EOS:EOS_SWATH:"d:\Swathc_Test.hdf":Index:Fakedata SUBDATASET_9_DESC=[40x40] Fakedata (32-bit floating-point) ERROR 4: `HDF4_EOS:EOS_SWATH:"d:\Swathc_Test.hdf":OnedGeo:CalB' does not exist i n the file system, and is not recognised as a supported dataset name. but the file "d:\Swathc_Test.hdf" is really exist in my harddisk
Change History (4)
comment:2 by , 17 years ago
I guess this is a problem with the drivename included as mentioned somewhere other. gdal_translate -of HFA HDF4_SDS:UNKNOWN:"D:\proc\x\PullDir\0300682042tdpfSc\MOD09Q1.A2005169.h18v04.004.2005179041252.hdf":0 abxx.img failes; same as gdal_translate -of HFA HDF4_SDS:UNKNOWN:"D:/proc/x/PullDir/0300682042tdpfSc/MOD09Q1.A2005169.h18v04.004.2005179041252.hdf":0 abxx.img while gdal_translate -of HFA HDF4_SDS:UNKNOWN:"MOD09Q1.A2005169.h18v04.004.2005179041252.hdf":0 abxx.img runs (thouth his HDF probably is hdf5 and not supported yes with fwtools 1.08 Regards Juergen
comment:3 by , 17 years ago
Based on the error message, it seems that the double quotes used to protect the filename from parsing on the drive letter colon do make it into GDALOpen(). This *should* be sufficient for things to work. But based on what you indicate perhaps there is a parsing problem that needs to be addressed in the HDF code. I'll try and get back to testing this later today.
comment:6 by , 17 years ago
Description: | modified (diff) |
---|---|
Priority: | highest → normal |
Resolution: | → fixed |
Severity: | blocker → normal |
Status: | assigned → closed |
I have done a bit of testing, and as long as I preceed the double quotes in the filename with a backslash in the dos commandline things seem to work. I think this problem actually got fixed in May 2006 with this change:
I would appreciate it if either of you could re-test this with a recent FWTools and ensuring you prefix the double quotes with backslashes if you are doing this in the FWTools shell command window.
I'm tentatively closing this as fixed, but just re-open if it isn't fixed.
Note:
See TracTickets
for help on using tickets.