|
|
|
This document describes the GESDISC TRMM pseudo hdf-eos2 and special HDF4 data files.
The following table summarizes the information collected for the files:
| File type | File size(avg.) | Geolocation Field | Datafield Dim. Range | CF-compliant information | Other special issues |
|---|---|---|---|---|---|
| pseudo hdf-eos2 (swath) | 3.75MB-98MB | geolocation=3D | 2D, 3D | 1. None of the datafields or datasets have 'units' or 'long_name' attribute; 2. There are fill values inside the data but there is neither a 'Fill_Value' attribute nor a 'missing value' attribute; | Both latitude and longitude are stored in one 3-D variable 'geolocation'. Users need to make extra efforts to retrieve individual latitude and longitude values; |
The following table summarizes the information collected for the files:
| File type | File size(avg.) | Number of grid | Has lat/lon | Projection | Datafield Dim. Range | CF-compliant information | Other special issues |
|---|---|---|---|---|---|---|---|
| pseudo hdf-eos2 (grid) |
500KB-7MB | 1 | Yes | GEO | 3D, 4D | 1. None of the datafields or datasets have 'units' or 'long_name' attribute; 2. There are fill values inside the data but there is neither a 'Fill_Value' attribute nor a 'missing value' attribute; | The users are not able to find latitude and longitude information from the file. The information of latitude and longitude may rely on additional information outside the HDF files. |
They are special HDF4 files which include point and image.
To retrieve sample TRMM files and read the detailed description of these files, please click here.