MODIS2LAS
Test Cases

Test # Requirement # Description


1a 1.1.1 Specify a valid mounting comment for COMMENT. Verify that this runs correctly and without errors.
1b 1.1.2 Specify a comment longer that 120 characters for COMMENT. Verify that this causes an error in TAE.
1c 1.1.4 Specify multiple mounting comments. Verify that this runs correctly and without errors.
1d 1.1.4 Specify 4 comments. Verify that this causes an error in TAE.
2a 1.1.3, 1.2.1, 1.2.6, 1.2.7.1 Specify a MODIS Level-3 HDF file in host (UNIX) format for the INFILE file name. Use a file that is in upper case. Verify that this runs correctly and without errors.
2b 1.2.6, 1.2.7.1 Specify a MODIS Level-3 raw binary file in TAE format for the INFILE file name. Use a file name with mixed case. Verify that this runs correctly and without errors.
2c 1.2.2 Specify a file name longer that 120 characters for INFILE. Verify that this causes an error in TAE.
2d 1.2.5 Specify multiple file names for INFILE. Verify that this causes an error in TAE.
2e 1.2.3, 1.2.4 Run the application without INFILE specified. Verify that this causes ani error in TAE.
2f 1.2.7 Specify a file name for INFILE that has an extension other than ".hdr" or ".hdf". Verify that this causes the application to exit with a fatal error.
3a 1.3.1, 1.3.2 Run the application specifying a single SDS to process for BANDS. Verify that this runs correctly and without errors.
3b 1.3.2 Visually verify that up to 36 SDSs may be specified (since there are currently no Level-3 data products with this many bands we can not run a test on it).
3c 1.3.4, 1.3.4.1 Input several SDSs in a random order. Validate they are output in the appropriate spectral order for the data product used.
3d 1.3.3, 1.3.3.1 Run the application with no SDSs specified. Verify that all available bands in supported data types are processed and that informational messages were generated to specify which bands were not processed.
3e 1.3.5 Specify an SDS number twice. Verify that this runs correctly and generates a warning message indicating the duplicate band specification.
3f 1.3.6 Specify an invalid SDS number. Verify that this causes the MRT to display a warning message and the application runs correctly without errors.
4a 1.4.1, 1.4.3 Specify a valid grouping for NBANDS so the sum of the bands in the groupings equals the number of BANDS specified. Verify this runs correctly and without errors.
4b 1.4.2 Visually verify that up to 36 band groupings for NBANDS may be specified (since there are currently no Level-3 data products with this many bands we can not run a test on it).
4c 1.4.1, 1.4.3 Specify a valid grouping for NBANDS so the sum of the bands in the groupings equals the number of BANDS specified. Verify this runs correctly and without errors.
4d 1.4.4 Specify a grouping for NBANDS so the sum of the bands in the groupings does not equal the number of BANDS specified. Verify this causes the application to exit with a fatal error.
4e 1.4.6 Specify a grouping for NBANDS so the number of groupings does not equal the number of output files specified. Verify this causes the application to exit with a fatal error.
5a 1.5.1, 1.5.2, 1.5.2.1, 1.5.4.1, 1.6.1, 1.6.2, 1.6.3, 1.6.5 Specify a valid set of sl, ss, nl, ns for WINDOW with UNITS being LS. Specify only SDSs in the same resolution for processing. Verify the output image was windowed correctly according to the sl, ss, nl, ns.
5b 1.5.2.1, 1.5.2.5, 1.6.4 Specify a valid set of sl, ss, nl, ns without specifying UNITS. Use a multi-resolution data product. Verify that the highest resolution of the spectral bands was used for the sl, ss, nl, ns values.
5c 1.5.4 Specify a set of sl, ss, nl, ns with sl being less than 0 and with UNITS being LS. Verify that this causes the application to exit with a fatal error.
5d 1.5.2.2, 1.6.2, 1.6.5 Specify a valid set of UL lat, UL long, LR lat, LR long with UNITS being DMS. Verify the output image was windowed correctly according to the UL lat, UL long, LR lat, LR long.
5e 1.5.2.3, 1.6.2, 1.6.5 Specify a valid set of UL lat, UL long, LR lat, LR long with UNITS being DEG. Verify the output image was windowed correctly according to the UL lat, UL long, LR lat, LR long.
5f 1.5.2.4, 1.6.2, 1.6.5 Specify a valid set of upper left Y, upper left X, lower right Y, lower right X with UNITS being PRO. Verify the output image was windowed correctly according to the defined window.
5g 1.6.5 Specify a valid set of sl, ss, nl, ns with sl and with UNITS being something other than DEG, DMS, LS, or PRO. Verify that this causes an error in TAE.
5h 1.5.3, 1.5.3.1 Run the application without specifying any window values. Verify the entire image is processed for each SDS specified for ingest.
6a 2.1.1, 2.1.6, 2.1.7 Specify a file name in host (UNIX) format for the OUT file name. Use a file that is in upper case. Verify that this runs correctly, without errors and that the output file is in the working directory.
6b 1.4.5, 1.4.5.1, 2.1.6, 2.1.7, 2.1.8, 5.1, 5.1.1 Specify a file name in TAE format for the OUT file name also specifying a directory path other than the current working directory. Use a file name with mixed case. Use a multi-resolution data product. Verify that this runs correctly, without errors and that the output files (one per resolution with the "_r#" appended to the output file name) are in the correct directory.
6c 2.1.2 Specify a file name longer that 120 characters for OUT. Verify that this causes an error in TAE.
6d 1.4.5, 1.4.5.2, 2.1.5.1.1 Specify the same number of file names for OUT as the number of bands specified for processing leaving NBANDS at its default. Verify that this runs runs correctly and without errors.
6e 1.4.3, 2.1.5.1 Specify the same number of file names for OUT as the number of bands grouping values entered in NBANDS. Verify that this runs runs correctly and without errors.
6f 2.1.5 Visually verify that up to 36 output file names may be specified (since there are currently no Level-3 data products with this many bands we can not run a test on it).
6g 2.1.3, 2.1.4 Run the application without OUT specified. Verify that this causes an error in TAE.
7a 3.1, 3.1.2, 11, 11.1 Set $DELFLG to "NO" and cause an error during ingest. Verify the output files do not get deleted. Also verify that error messages are output and that they comply with the format outlined in requirement 11.
7b 3.1, 3.1.1 Set $DELFLG to "YES" and cause an error during ingest. Verify the output files get deleted.
8a 4 Run the application once for each type of Level-3 data product. Verify that these run correctly and without errors.
9a 6.1, 6.1.1, 6.1.1.1, 6.1.1.2 Run the application with a data product and select for processing an 8-bit unsigned integer data SDS and a 16-bit signed integer data SDS. Verify that they were output to separate LAS files and that the files have the appropriate extension appended ("_byte" and "_i*2", respectively)
9b 6.1, 6.1.1, 6.1.1.3, 6.1.1.4 Run the application with a data product and select for processing a 32-bit signed integer data SDS and a 32-bit float data SDS. Verify that they were output to separate LAS files and that the files have the appropriate extension appended ("_i*4" and "_r*4", respectively)
10a 7, 7.1 Run the application with a supported data product on disk. Verify that this runs correctly and without errors.
10b 7, 7.2 Run the application with a supported data product on CD. Verify that this runs correctly and without errors.
10c 7 Run the application with a supported data product on DVD. Verify that this runs correctly and without errors.
11a 8.2 Run the application with a data product that contains an SDS with 8-bit signed integer data and request that band be processed. Verify that this causes the application to exit with a fatal error.
11b 8.2 Run the application with a data product that contains an SDS with 16-bit unsigned integer data and request that band be processed. Verify that this causes the application to exit with a fatal error.
11c 8.2 Run the application with a data product that contains an SDS with 32-bit unsigned integer data and request that band be processed. Verify that this causes the application to exit with a fatal error.
11d 8.1 Run the application with a data product that contains an SDS in an unsupported data type. Specify only SDSs of supported data types for processing. Verify that this runs correctly and without errors.
11e 8.2.1 Run the application with a data product that contains an SDS in an unsupported data type. Leave the SDSs to process at its default so it attempts to process the SDS in the unsupported data type. Verify that this runs correctly and only generates warning messages indicating which SDSs were in unsupported data types and were, therefore, not processed.
12a 9.1, 9.2, 9.3, 9.4, 9.5, 9.6, 9.7, 9.8, 9.9, 9.10, 9.11, 9.12, 9.13, 9.14, 9.15, 9.16, 9.17, 9.18, 9.19, 9.20 Run the application with a single resolution data product. Verify the fields in requirement 9 are correct in the LAS DDR.
12b 9.1, 9.2, 9.3.1, 9.4, 9.5, 9.6, 9.7, 9.8, 9.9, 9.10, 9.11, 9.12, 9.13, 9.14, 9.15, 9.16, 9.17, 9.18, 9.19, 9.20 Run the application with a multi-resolution data product. Verify the fields in requirement 9 are correct in the LAS DDR; make sure the pixel sizes reflect the correct resolution for each output product.
13a 10, 10.1 Specify an input file name that does not exist. Verify that this causes the application to exit with a fatal error.
13b 10, 10.2 Specify an output file name that already exists. Verify that this causes the application to exit with a fatal error.
14a 12 Run the application on each of the operating systems currently supported by LAS. Verify the application runs correctly and without errors.
15a 13.1.1, 13.1.6, 13.1.7.1, 14.1, 14.2, 14.2.1 Specify a MODIS Level-3 HDF file in host (UNIX) format for the INFILE file name. Use a file that is in upper case. Verify that MODISSDS runs correctly, without errors, that the correct information was printed to the display, that the band numbering is correct for the spectral order of the product used, and that the sds file was created and has the correct name.
15b 13.1.6, 13.1.7.1 Specify a MODIS Level-3 raw binary file in TAE format for the INFILE file name. Use a file name with mixed case. Verify that MODISSDS runs correctly and without errors.
15c 13.1.2 Specify a file name longer that 120 characters for INFILE. Verify that this causes an error in TAE.
15d 13.1.5 Specify multiple file names for INFILE. Verify that this causes an error in TAE.
15e 13.1.3, 13.1.4 Run MODISSDS without INFILE specified. Verify that this causes an error in TAE.
15f 13.1.7 Specify a file name for INFILE that has an extension other than ".hdr" or ".hdf". Verify that this causes MODISSDS to exit with a fatal error.