LaRC_MOPITT

This document describes the LaRC_MOPITT HDF-EOS2 files. This document is sub-divided into three sections: LaRC_MOPITT MOP01, LaRC_MOPITT MOP02 and LaRC_MOPITT MOP03 respectively.

MOP01

They are HDF-EOS2 swath 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)	106MB	Lat/Lon = 2D or 3D	2D,3D	1. Neither geolocation field nor datafield has ‘units’ and ‘long_name’ attributes; 2. There are fill values inside the data but there is neither a 'Fill_Value' attribute nor a 'missing value' attribute

MOP02

They are HDF-EOS2 swath files. The following table summarizes the information collected for the files:

The latitude and longitude of some files are stored as one dimension array each and the number of the elements for each array is the same.

File type	File size(avg.)	Geolocation Field	Datafield Dim. Range	CF-compliant information	Other special issues
HDF-EOS2 (Swath)	62MB	Lat/Lon = 1D	2D,3D	1. Neither geolocation field nor datafield has ‘units’ and ‘long_name’ attributes; 2. There are fill values inside the data but there is neither a 'Fill_Value' attribute nor a 'missing value' attribute	Some files contain 1-D latitude/longitude fields.

MOP03

They are HDF-EOS2 grid files and the projection 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)	6MB	1	Yes	GEO	1D-3D	1. Neither geolocation field nor datafield has ‘units’ and ‘long_name’ attributes; 2. There are fill values inside the data but there is neither a 'Fill_Value' attribute nor a 'missing value' attribute	1. Non-Standard Dimension name; 2. Wrong information in StructMetadata

To retrieve sample MOPITT files and read the detailed description, please click here.

Last modified: 06/02/2017