Changes between Version 112 and Version 113 of Procedures/DeliveryChecking


Ignore:
Timestamp:
Sep 25, 2018 1:59:19 PM (10 months ago)
Author:
dac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Procedures/DeliveryChecking

    v112 v113  
    2929  1. In this case additional information should be added into read me to explain why they are being masked
    3030  1. Check that underflows and overflows tabulated in ReadMe are sensible. Rerun autoQC with different settings or use fastQC if not.
    31   1. '''Check the z profile''' (spectral profile) over some green vegetation and it should look plausible. Check this for each level1 file. You can easily and quickly run [wiki:Processing/Py6S_vs_Hyperspectral Py6S for every flightline and check it by following the instructions on the wiki]. Or you can look for some vegetation on FastQC, [wiki:Procedures/DeliveryChecking/ExampleFenixSpectra see here for example spectra.]
    32  1. Check all of the lev3 mapped files open and look OK (don't need to go through all the bands)
     31  1. '''Check the z profile''' (spectral profile) over some green vegetation and it should look plausible. Check this for each level1 file. For Fenix data you can easily and quickly run [wiki:Processing/Py6S_vs_Hyperspectral Py6S for every flightline and check it by following the instructions on the wiki]. Or you can look for some vegetation on FastQC, [wiki:Procedures/DeliveryChecking/ExampleFenixSpectra see here for example spectra.]
     32 1. Check all of the level3 mapped files open and look OK (don't need to go through all the bands)
    3333  1. Make sure that all bands have been mapped (not just 3). You can use {{{check_num_bands.py *bil}}} to check the number of bands for all files.
    3434 1. Check the projection used is correct - especially the correct UTM zone for the data