|
Tracking of known problems and subsequent fixes is an important issue for MODIS data users.
This page will act as a repository of all known MODIS Atmosphere Data Product problems,
as well as how to determine the problematic version (and the fixed version) of the HDF data --
therefore data users should check this page for updates regularly.
Data Users unfamiliar with how to properly track problems and fixes by determining the version of their downloaded HDF files
should refer to the documentation at the bottom of this page.
|
|
|
Collection 006 Issues
Click the colored buttons below for the known problems associated with each MODIS Atmosphere Data Product in Collection 6.
- Problems in input 04_L2, 05_L2, 06_L2, 07_L2, and 35_L2 propagate into 08_M3
Description:
See the Known Problem pages for the input Level-2 products 04_L2 (Aerosol), 05_L2 (Water Vapor), 06_L2 (Cloud),
07_L2 (Profiles), and 35_L2 (Cloud Mask) by clicking on the links or the colored tabs above.
|
Latest PGE Version Available (by Data Date)
How to Track MODIS Data File "Versions" (Important for Tracking Problems and Fixes)
Problems and fixes in MODIS Atmosphere Product HDF files can be tracked in one of two ways:
- the Product Generation Executive (PGE) Version Number that can be queried from any HDF file using the command:
ncdump -h *.hdf
- the HDF File "Production Date".
The HDF File "Production Date", which is the date the HDF file was actually generated or produced, can be found in the HDF filename itself (shown in green color below):
Level 2 Product Names:
|
Level 3 Product Names:
|
Note that 1.) all times are UTC time, not local time 2.) the DDD in the date denotes the Julian Date (001-366), and 3.) the MOD06_L2 (or MOD08_D3) prefix is only an example (MYD04_L2, MOD05_L2, MYD05_L2, MYD06_L2, etc. ... or MYD08_D3, MOD08_E3, MYD08_E3, MOD08_M3, MYD08_M3 could be substituted).
|
|