Why do I get different results when reading my HDF-EOS2 file, depending on whether I use the “.hdf” or “.hdfeos” extension?
If you use the “.hdf” extension, then NCL uses the underlying HDF4 interface to read your data, whereas if you use the “hdfeos or “he2” extension, NCL reads the file using the HDF-EOS2 library interface. Using the “.hdfeos” extension software will give you slightly more information, since the HDF-EOS2 software provides software to calculate additional lat/lon information. Side tip: if your HDF-EOS2 file has an “.hdf” extension, then you can force NCL to read this file as an HDF-EOS2 file simply by appending an “.he2” or “.hdfeos” to the file name in the addfile call (you don’t need to rename the file). For example, if your file is called “swath.
If you use the “.hdf” extension, then NCL uses the underlying HDF4 interface to read your data, whereas if you use the “hdfeos or “he2” extension, NCL reads the file using the HDF-EOS2 library interface. Using the “.hdfeos” extension software will give you slightly more information, since the HDF-EOS2 software provides software to calculate additional lat/lon information. Side tip: if your HDF-EOS2 file has an “.hdf” extension, then you can force NCL to read this file as an HDF-EOS2 file simply by appending an “.he2” or “.hdfeos” to the file name in the addfile call (you don’t need to rename the file).
Related Questions
- I get different nutrition results depending on what international settings I have specified in Windows. What is happening?
- Why do I get different results when reading my HDF-EOS2 file, depending on whether I use the ".hdf" or ".hdfeos" extension?
- Why there are different results depending on the clicked symbol?
