Difference between revisions of "Landsat ETM+/TM/MSS"

From Snow
Jump to navigationJump to search
(New page: MSS/TM crossover http://wiki.snow.ucsb.edu:8888/santa-ana/160)
 
m
 
(15 intermediate revisions by the same user not shown)
Line 1: Line 1:
 +
== TM/ETM+ ==
  
  
MSS/TM crossover
+
To be added:
 +
1)fVEG by merging multiple TMSCAG runs (write matlab function)
 +
2)use emissivity for each landcover type to determine actual temperature instead of brightness temperature
 +
3)post-processing with option for subset to be saved in specific location
 +
4)populate database Karl database with file locations for Landsat 5 and 7
 +
5)pre-processing function that skips when the output already exists
 +
 
 +
Output 1:
 +
.mat -
 +
    1) fsca raw - values are 0 to 1 and NaN (-9999 from TMSCAG, 0 for TMSCAG<0)
 +
    2) fsca - values are 0 and 0.15 to 1 and NaN from above. Product has had the following masks applied as NaNs
 +
    3) masks 7 bands:
 +
                1) edge mask - to deal with bands having different spatial extents
 +
                  a) NLDAS processing did a similar thing. All output from USGS is currently not trimming the edges. See current [https://landsat.usgs.gov/products_IP_LPGSvsNLAPS.php]
 +
                2) "other land"  - always applied for 0 and 127 - optionally calculated and applied: herbaceous wetlands or other classes
 +
                3) shadow mask (all bands < 0.10)
 +
                4) temperature mask (if fsca>0.15, emissivity is 0.98, otherwise ASTER emissivity set used
 +
                5) water mask (all bands < 0.10 & NLCD indicates water) - this is a subset of 2...inverse is snow covered lake
 +
                6) optional cloud mask (calculated for scene only applied w/ flag - rarely used)
 +
                7) fsca < 0.15
 +
               
 +
    5) snow covered lake (NLCD=Water,fSCA>0.15
 +
    5) RGB - bands 5,4,2 (stretch version of surface reflectance)
 +
    6) surface reflectance (6 bands)
 +
    7) brightness temperature
 +
    9) ndsi - (2-5)/(2+5)
 +
    10) 3 band saturation mask indicating combination of saturation that resulted in different TMSCAG "runs"
 +
    11) geoinfo from geotiffinfo on original file
 +
    12) structure of pr, dateS, utmZone 
 +
 
 +
== MSS/TM crossover 1985-1987 ==
 
[[http://wiki.snow.ucsb.edu:8888/santa-ana/160]]
 
[[http://wiki.snow.ucsb.edu:8888/santa-ana/160]]

Latest revision as of 13:17, 6 May 2010

TM/ETM+

To be added: 1)fVEG by merging multiple TMSCAG runs (write matlab function) 2)use emissivity for each landcover type to determine actual temperature instead of brightness temperature 3)post-processing with option for subset to be saved in specific location 4)populate database Karl database with file locations for Landsat 5 and 7 5)pre-processing function that skips when the output already exists

Output 1: .mat -

   1) fsca raw - values are 0 to 1 and NaN (-9999 from TMSCAG, 0 for TMSCAG<0)
   2) fsca - values are 0 and 0.15 to 1 and NaN from above. Product has had the following masks applied as NaNs
   3) masks 7 bands:
               1) edge mask - to deal with bands having different spatial extents
                  a) NLDAS processing did a similar thing. All output from USGS is currently not trimming the edges. See current [1]
               2) "other land"  - always applied for 0 and 127 - optionally calculated and applied: herbaceous wetlands or other classes
               3) shadow mask (all bands < 0.10)
               4) temperature mask (if fsca>0.15, emissivity is 0.98, otherwise ASTER emissivity set used
               5) water mask (all bands < 0.10 & NLCD indicates water) - this is a subset of 2...inverse is snow covered lake
               6) optional cloud mask (calculated for scene only applied w/ flag - rarely used)
               7) fsca < 0.15
               
   5) snow covered lake (NLCD=Water,fSCA>0.15
   5) RGB - bands 5,4,2 (stretch version of surface reflectance)
   6) surface reflectance (6 bands)
   7) brightness temperature
   9) ndsi - (2-5)/(2+5)
   10) 3 band saturation mask indicating combination of saturation that resulted in different TMSCAG "runs"
   11) geoinfo from geotiffinfo on original file 
   12) structure of pr, dateS, utmZone  

MSS/TM crossover 1985-1987

[[2]]