In this release, we greatly have enhanced the support of the access of NASA HDF-EOS2 and HDF4 products. To take advantage of this feature, the software MUST be built using the HDF-EOS2 library and with the following configure options: ./configure --with-hdf4= \ --with-hdfeos2= \ --prefix= Since some HDF4 variable paths are pretty long. To follow COARDS conventions, build the software using: ./configure --with-hdf4= \ --with-hdfeos2= \ --prefix= --enable-short-name The following NASA HDF-EOS2 products are tested with IDV and Panoply, check the Limitation section for the limitations: 1). NASA GES DISC AIRS/MERRA/TOMS 2). NASA LAADS/LP DAAC/NSIDC Many MODIS products 3). NASA NSIDC AMSR_E/NISE products 4). NASA LaRC MISR/MOPITT/CERES-TRMM The following NASA special HDF4 products are tested with IDV and Panoply, check the Limitation section for the limitations: 1). NASA GES DISC TRMM Level 1B, Level 2B Swath TRMM Level 3 Grid 42B and 43B 2). OBPG(Ocean Color) SeaWiFS/MODIST/MODISA/CZCS/OCTS level 2 and level 3m(l3m) 3). Some LaRC CERES products CER_AVG_Aqua-FM3-MODIS,CER_AVG_Terra-FM1-MODIS CER_ES4_Aqua-FM3_Edition1-CV or similar ones CER_ISCCP-D2like-Day_Aqua-FM3-MODIS or similar ones CER_ISCCP-D2like-GEO_ or similar ones CER_SRBAVG3_Aqua or similar ones CER_SYN_Aqua or similar ones CER_ZAVG or similar ones There are some limitations in the current HDF-EOS2 module. For the details of limitations and others, please read README under the directory of the HDF4 handler code. To take advange of the above features with RPMS, one MUST use the RPMS built with EOS options.