Input File Database Query Specifications

This page outlines the list of rules that need to be followed by the input file database when querying the input HDF files for the Basic Fusion program.

1. Files that must be included
   1. 1. MOPITT

• MOP01-...

1. 1. 1. CERES

• CER_BDS_Terra-FM1_Edition3_...
• CER_BDS_Terra-FM2_Edition3_...

1. 1. 1. MODIS

• MOD021KM...
• MOD03...
• MOD02HKM...
• MOD02QKM...

1. 1. 1. ASTER

• AST_L1T_...

1. 1. 1. MISR

• MISR_AM1_GRP_ELLIPSOID[...]\_AA_...
• MISR_AM1_GRP_ELLIPSOID[...]\_AF_...
• MISR_AM1_GRP_ELLIPSOID[...]\_AN_...
• MISR_AM1_GRP_ELLIPSOID[...]\_BA_...
• MISR_AM1_GRP_ELLIPSOID[...]\_BF_...
• MISR_AM1_GRP_ELLIPSOID[...]\_CA_...
• MISR_AM1_GRP_ELLIPSOID[...]\_CF_...
• MISR_AM1_GRP_ELLIPSOID[...]\_DA_...
• MISR_AM1_GRP_ELLIPSOID[...]\_DF_...
• MISR_AM1_AGP...
• MISR_AM1_GP_GMP...
• MISR_HRLL...

1. Specification for the ordering of the inputFiles.txt file

• All MOPITT files first, then all CERES, MODIS, ASTER then MISR.
• All MOPITT should be listed from top to bottom by increasing time (top is earliest, bottom is most recent)
• CERES granules come in pairs, an FM1 and FM2 file. An arbitrary number of pairs can be listed, but FM1 always comes before FM2. Each pair of files should also have identical dates as listed in the filename (non-blocking until database is fully populated). Pairs are listed in time-ascending manner like MOPITT.
• MODIS files listed in time-ascending manner. Files must be listed as a "group" where each group can either be:

[...]/MODIS/MOD021KM.A2007184.1610.006.2014231113627.hdf [...]/MODIS/MOD03.A2007184.1610.006.2012239144154.hdf

• • OR**

[...]/MODIS/MOD021KM.A2007184.1625.006.2014231113702.hdf [...]/MODIS/MOD02HKM.A2007184.1625.006.2014230150204.hdf [...]/MODIS/MOD02QKM.A2007184.1625.006.2014230073105.hdf [...]/MODIS/MOD03.A2007184.1625.006.2012239144215.hdf So note that the next file after 1KM file can be either MOD03 file or MOD02HKM, nothing else. If the next file is MOD02HKM, what follows MUST be a QKM file followed by MOD03 file. The only file that can follow the MOD03 file is either another 1KM file or simply the first file for the next instrument. Each file group should have the same dates as listed in the filename, but this requirement should be non-blocking until we get a full database population (won't break the program, but will lead to an invalid Fusion file)

• ASTER is easy, just list in time-ascending manner.
• MISR must have files listed as such:

[...]/MISR/MISR_AM1_GRP_ELLIPSOID_GM_P022_O040110_AA_F03_0024.hdf [...]/MISR/MISR_AM1_GRP_ELLIPSOID_GM_P022_O040110_AF_F03_0024.hdf [...]/MISR/MISR_AM1_GRP_ELLIPSOID_GM_P022_O040110_AN_F03_0024.hdf [...]/MISR/MISR_AM1_GRP_ELLIPSOID_GM_P022_O040110_BA_F03_0024.hdf [...]/MISR/MISR_AM1_GRP_ELLIPSOID_GM_P022_O040110_BF_F03_0024.hdf [...]/MISR/MISR_AM1_GRP_ELLIPSOID_GM_P022_O040110_CA_F03_0024.hdf [...]/MISR/MISR_AM1_GRP_ELLIPSOID_GM_P022_O040110_CF_F03_0024.hdf [...]/MISR/MISR_AM1_GRP_ELLIPSOID_GM_P022_O040110_DA_F03_0024.hdf [...]/MISR/MISR_AM1_GRP_ELLIPSOID_GM_P022_O040110_DF_F03_0024.hdf [...]/MISR/MISR_AM1_AGP_P022_F01_24.hdf [...]/MISR/MISR_AM1_GP_GMP_P022_O040110_F03_0013.hdf [...]/MISR/MISR_HRLL_P022.hdf

This is the only valid order, all files for each granule group must be present.

1. Rules for including files during database query
   1. 1. MOPITT

If the MOPITT granule overlaps with the orbit at all, include it. MOPITT is subsetted by the basic fusion program.

1. 1. 1. CERES

If the CERES granule overlaps with the orbit at all, include it. CERES is subsetted by the basic fusion program.

1. 1. 1. MODIS

If the MODIS granule's start time resides within the orbit time, include it.

1. 1. 1. ASTER

If the ASTER granule's start time resides within the orbit time, include it.

1. 1. 1. MISR

If the MISR granule's start time resides within the orbit time, include it.