It seems a few changes are needed in the specifications: - The Zonal Average object only exist in HDF-EOS5 implementation. Therefore, in section1.2 (last paragraph) it should be made clear that this object is only in hdf-eos5 (it does not exist in hdf-eos2).
- The field dimension orders are explicitly presented in the tables for Swath, Grid, and Zonal Average objects, and it has been emphasized that they are in C or FORTRAN order. The only inconsistency that I found is at the beginning of section 5.1.2 where dimensions are listed from slow to fast, while for grid and zonal average the dimensions are listed from fast to slow (beginning of sections 5.2.2, and 5.3.2).
- This specification uses HDF-EOS5 and GCTP for handling projection implementation in its grid objects. Since for Geographic projection HDF-EOS assumes -180 to +180 limits for longitude, considering 0 to 360 for grids longitude limits will cause subestting and projection conversion problems as seen in some hdf-eos2 products (e.g. AMSR_E_L3_RainGrid_B05 global products with upperleft longitude of 0 and lowerright longitude of 360 fail subsetting when using HEG)
RFC Author response: We have documented what each instrument team is using. Since MLS has released their grid products, they do not want to change their longitude limits and acknowledge the fact that subsetting their products may be broken.
|
|
