This web page describes the CERES HDF-EOS2 and HDF4 files.
The following table summarizes the information collected for the files:
File type | File size(avg.) | Geolocation Field | Datafield Dim. Range | CF-compliant information |
---|---|---|---|---|
HDF-EOS2 (Swath) | 275MB | Lat/Lon = 2D | 2D | 1. Both geolocation field and datafield have 'units' and 'long_name' attribute. 2.'units' attribute for latitude and longitude is 'degree'. |
The grid files have 7 grids with 1 V-dataset. The projection for the files is GEO. The following table summarizes the information collected the files:
File type | File size(avg.) | Number of grid | Has lat/lon | Projection | Datafield Dim. Range | CF-compliant information | Other special issues |
---|---|---|---|---|---|---|---|
HDF-EOS2
(Grid) |
25MB | 7 | No | GEO | 2D-3D | 1. All the datafields missing 'units' and 'long_name' attributes; 2. Special characters, such as hyphen '-'* | Some files contain following issues: The parameter information is wrong in StructMetadata. |
The HDF4 files have datasets, groups and V-datasets of varying amount. They provided 'core-metadata' and 'archive-metadata' but not 'struct-metadata'.
The following table summarizes the information collected for the HDF4 files:
File type | File size(avg.) | Datafield Dim. Range | CF-compliant information | Other special issues |
---|---|---|---|---|
HDF4 | 3.9MB to 640MB | 2D | 1. Both geolocation field and datafield have 'units' and 'long_name' attribute; 2.'units' attribute for latitude and longitude is 'degree'; 3. There are fill values inside the data but there is neither a 'Fill_Value' attribute nor a 'missing value' attribute; 4. Special characters, such as hyphen '-'* | Some files contain following issues: 1. Not all HDF4 files have latitude and longitude information; 2. The same field/vgroup name is shared across different vgroups. |
To retrieve sample CERES files and read the detailed description of these files, please click here.