Changes between Version 10 and Version 11 of Processing/Py6S_vs_Hyperspectral


Ignore:
Timestamp:
Oct 21, 2015 11:19:01 AM (4 years ago)
Author:
asm
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Processing/Py6S_vs_Hyperspectral

    v10 v11  
    5454The Py6S model selected for this simulation has no atmospheric correction and should have always higher values than the spectra measured by the Fenix instrument.
    5555
    56 Py6S has several parameters needed to run the model. For this script, ARSF have selected the most convenient ones for our use but do not expect perfect match of the hyperspectral spectra recorded from our sensor against the Py6S. A more detailed explanation about Py6S parameters and settings used by ARSF can be found here
     56Py6S has several parameters needed to run the model. For this script, ARSF have selected the most convenient ones for our use but do not expect perfect match of the hyperspectral spectra recorded from our sensor against the Py6S. A more detailed explanation about Py6S parameters and [wiki:Processing/Py6S_vs_Hyperspectral/Py6SParameters settings used by ARSF can be found here.]
    5757
    5858Both curves (Fenix and Py6S) should match general features. The peaks and depression (reflecfance-absorption) caused by vegetation have to match and there should be no other spikes on the Fenix spectra that does not match the Py6s. However, note that it is probably to have a spike on some Fenix spectra flightlines on the bands around band 349, close to 900-950 nm. This is caused by the shift on the SWIR bands detected on on October 2014 and those pixels are listed as bad pixels, therefore the spectra recorded by Fenix is correct. You can find a picture illustrating this issue which also suggest the type of spike you have to look for when they are not on the overlapping region.