Opened 18 years ago
Closed 13 years ago
#995 closed defect (invalid)
reading hdf5 in gdal 1.3.1
Reported by: | Owned by: | warmerdam | |
---|---|---|---|
Priority: | high | Milestone: | |
Component: | GDAL_Raster | Version: | unspecified |
Severity: | normal | Keywords: | hdf |
Cc: | Mateusz Łoskot, antonio |
Description (last modified by )
Problem to translate hdf5 format to other formats examples
gdal_translate -sds -of AAIGrid -co "TILED=YES" sat.h5 sat.ascii
error is:
szFilenname sat.h5 Segmentation fault sat.h5 and other he5 formats are in on upper url
Change History (5)
comment:2 by , 18 years ago
Dennis, Frank; Thank you very much for help. However I have still a problem when using gdal 1.3.1 and Debian Linux. I have installed recently gdal, hdf5, grass, mapserver from debian packeges. And It doesn't work when reading hdf5 with gdal.Ex: gdalinfo HDF5:"sat.h5"://image3/image_data Error: GDAL: Auto register /usr/local/lib/gdalplugins/gdal_GRASS.so using GDALRegister_GRASS. szFilenname sat.h5 Segmentation fault Do you thing that problem is with hdf5 installation? Thx; Blaz Kurnik (In reply to comment #1) > Blaz, Frank > > I have fixed up the core dump problem for HDF5. I have changed SUBDATASET so > that you can retrieve same dataset name. I have found that sat.h5 have many > datasets called image_data. To solve this, I added the HDF5 Path before the > dataset name. > > Ex.: > gdalinfo HDF5:"sat.h5"://image3/image_data > > I tried Blaz command: > gdal_translate -of AAIGrid -co "TILED=YES" sat.h5 sat.ascii > > It worked fine. Thanks for the URL it was very helpful. > > Note: For hdf5 there are no "SDS" dataset so you do not need -sds flag
comment:3 by , 16 years ago
Cc: | added |
---|---|
Description: | modified (diff) |
Keywords: | hdf added |
comment:4 by , 15 years ago
Cc: | added |
---|
comment:5 by , 13 years ago
Resolution: | → invalid |
---|---|
Status: | reopened → closed |
Closing in the hope it is no longer valid
Note:
See TracTickets
for help on using tickets.