The HDF-EOS translation is implemented using NCSA/NASA support libraries; however, PCI has only ported these to selected Unix platforms. Therefore, this format is only supported on Solaris 2.x, IRIX, HP/UX, and Linux platforms.
HDF-EOS swath files are organized as a series of datasets, each called a swath. Typically each swath is the output of one band of a sensor instrument. However; the swaths can have different resolutions, make them difficult to treat as a single dataset in GeoGateway. In order to resolve this the user is required to include a swath name in the filename. This swath name selects the particular swath to be opened. If the regular filename is used, GeoGateway will attempt to open the file using the general purpose HDF translator and the following message will be reported:
ERROR: The file `GDS_L1A.hdf' is an HDF file, but it can't be read as an RI8, or SDS dataset. Only these HDF subformats are supported by GeoGateway. E019 ... Invalid header typeIn order to find out the possible swath names, it is necessary to try to open the file with a dummy swath name. For instance "GDS_L1A.hdf:junk". When this is done, an error message similar to the following will be produced:
ERROR: Couldn't find swath `junk', but the file does have the following swaths: VNIR_Band1,VNIR_Band2,SWIR_Band4,SWIR_Band5,SWIR_Band6,SWIR_Band7, SWIR_Band8,SWIR_Band9,TIR_Band10,TIR_Band11,TIR_Band12,TIR_Band13, TIR_Band14 E019 ... Invalid header typeThen to select a particular swath, substitute in the name. Some valid filenames would be:
See Also: FIMPORT, Hierarchical Data Format, SeaWIFS HDF