130 likes | 292 Views
1. FY10-11 GIMPAP Project Proposal Title Page. Title : An Evapotranspiration Data Product Based on GOES Thermal Observations Project Type : Product Development Proposal Status : New Duration : 2 years Leads: Xiwu Zhan, STAR Other Participants : Rongjun Wu, UMD-ESSIC-CICS
E N D
1. FY10-11 GIMPAP Project Proposal Title Page • Title: An Evapotranspiration Data Product Based on GOES Thermal Observations • Project Type: Product Development Proposal • Status: New • Duration: 2 years • Leads: • Xiwu Zhan, STAR • Other Participants: • Rongjun Wu, UMD-ESSIC-CICS • Martha Anderson, USDA-ARS Hydrology and Remote Sensing Lab • Chris Hain, IMSG • Hanjun Ding, OSDPD • Michael Ek, NCEP-EMC • Istvan Laszlo, STAR • Zhanqing Li, UMD-ESSIC-CICS
2. Project Summary • NCEP Land Group has requested an evapotranspiration (ET) data product from GOES observations to cross-validate their land surface model simulations that impact their numerical weather and climate predictions. • Using the Atmosphere-Land Exchange Inversion (ALEXI) model many research activities have shown that land surface temperature (LST) and solar insolartion retrieved from GOES observations can be used to derive land surface evapotranspiration with satisfactory accuracy. • NESDIS STAR and OSDPD GSIP project are generating LST and solar insolation data products from GOES operationally since 2008. • We propose to import and test the ALEXI model using the GSIP LST and solar insolation products in order to demonstrate whether an operational ET product from ALEXI will satisfactorily meet the ET data request from NCEP. • Ultimate result of this project is expected to be an operational ET data product meeting user’s data need.
3. Motivation/Justification • Supports NOAA Mission Goal(s): Weather and Water, and Climate • Evapotranspiration (ET) is one of the most important energy and mass fluxes between the atmosphere and land surface that impact numerical weather and climate predictions. NCEP requires independent data sources to validate the accuracy of their operational land surface model output. • Some complicated approaches for estimating ET from satellites sensors (e.g. MODIS) have appeared in literature. However, none of these satellite ET data products have been generated and made available to users. • The Atmosphere-Land Exchange Inversion (ALEXI) is a simple two-source diagnostic land surface model that has shown reliability of their ET estimates using surface temperature and solar insolation data retrieved from GOES observations. • NOAA-NESDIS GSIP project has been made operational the generation of GOES surface temperature and solar insolation data products. Therefore, it is feasible to generate an ET data product from these GOES observations using the ALEXI model. • To transfer this feasibility to reality, it is necessary to import the ALEXI model code to NESDIS facility and test the reliability of its ET output using GSIP data product as input. • In addition to using the ALEXI-based ET observations from GOES in NCEP model validation, the ET data product could be used to monitor drought occurrences and severity too. Drought monitoring is part of NCEP operations.
SURFACE TEMPERATURE Tsoil & Tveg transpiration & evaporation Tveg TSoil soil evaporation 4. Methodology (1) • ALEXI model is a remote sensing approach to estimating ET (Anderson et al, 1997) from surface temperature observations: Given known radiative energy inputs, how much water loss is required to keep the soil and vegetation at the observed temperatures?
2002 2003 2004 APR Low MAY JUN EVAPOTRANSPIRATION (Wm-2) JUL AUG High SEP 4. Methodology (2) • ALEXI model has demonstrated satisfactory reliability of its ET estimates for test data sets (Anderson et al, 2007):
4. Methodology (3) Four Steps to import and test the ALEXI model at NESDIS: Port ALEXI infrastructure to standard NOAA data sources: to support automated model execution using meteorological, land surface temperature, and insolation datasets that are routinely available from NCEP GDAS and NESDIS GSIP in real-time, anticipating transition to operations. Generate ET data over the contiguous U.S (2000-present): to create baseline conditions for short-term climatological analyses using a consistent set of NOAA input products. Compare the ET data with in situ observations of AmeriFlux network: to validate ALEXI ET estimates with available in situ observations from the AmeriFlux network. Distribute ALEXI ET data product to NCEP-EMC and interested users: for them to evaluate their land surface model simulations in order to improve their numerical weather and climate predictions.
5. Expected Outcomes • The ALEXI model computer code will be imported to NESDIS, set up and run with NESDIS GSIP and NCEP North America Regional Reanalysis (NARR) data inputs. • This ALEXI model infrastructure may produce valuable ET data sets for cross-validating NCEP numerical weather and climate modeling results and in turn improve NCEP numerical weather and climate predictions. • Executing ALEXI model for long term (e.g. since 2000) may provide valuable climatological data of ET that can be used to map drought areas. • The feasibility of implementing ALEXI model within an operational environment will be assessed. • If running ALEXI at OSDPD will be proved feasible and results from ALEXI demonstrates valuable, a GOES PSDI proposal will be submitted to implement a new operational GOES-based ET product.
6. FY10-11 Milestones Product Name(s): GOES-based Evapotranspiration (ET) • Project Year 1: • Jan 10: Project Lead informed to start • Jun 10 (May 10): ALEXI model computer code imported to NESDIS-STAR • Aug 10 (Feb 10): Contractor starts to work with project lead • Sep 10 (Jul 10): GOES GSIP data or other available GOES LST and solar insolation data processed for ALEXI model as input • Oct 10: NCEP NARR data processed for ALEXI model as input • Dec 10: ALEXI model test run successful at NESDIS with NOAA input data • Dec 10: NESDIS ALEXI ET project yearly report due to GIMPAP office • Project Year 2: • Jan 11: Validation data sites for evaluating ALEXI model output identified • Mar 11: In situ ET measurement data of the validation sites processed • May 11: NESDIS ALEXI ET data evaluated for the validation sites • July 11: NCEP Noah land surface model (LSM) ET data processed • Aug 11: NESDIS ALEXI ET data analyzed against NCEP Noah LSM • Oct 11: Publications on NESDIS ALEXI ET prepared for journals and/or conferences • Nov 11: NESDIS ALEXI ET data delivered to NCEP and other interested users • Dec 11: Final project report due to GIMPAP office
8. FY10 Progressive Project Report Product Name(s): GOES-based Evapotranspiration (ET) • Contractor through UMD-CICS came to work late (Aug. 1) because of funding transfer and hiring process delays. • Project lead started to prepare the project by collecting NARR data from NCEP, purchasing disk raid for project data storage. • ALEXI model computer code is imported to Linux servers at NESDIS-STAR with help from ALEXI model developers. • Preliminary result of ET from ALEXI using NESDIS-GSIP and NCEP NARR data is encouraging (see maps on next slide) • Remaining Year 1 milestones will be reached on time. • More results will be reported to GIMPAP office by end of Year 1.
8. FY10 Progressive Project Report (Continued) ET from ALEXI-NESDIS vs ALEXI-UAH
7. Response to TAC Comments • Run ALEXI model at NESDIS; issue whether OSDPD is going to provide long-term maintenance for model software; option to install at NCEP. - will assess the feasibilities at either OSDPD or NCEP • Will processing speed be an issue? Also, how will ALEXI code be maintained if transitioned to operations? - No. ALEXI output are daily products. Computation consumption is low • Useful from a validation standpoint…but not used directly by NOAH LSM. - But a separate research is trying to assimilate the ALEXI output to Noah. • How much of an impact does this have on the evapo-transpiration calculated by ALEXI? - Quantitative assessment not done yet. Will know by later of the project • If research turns out to be promising, consider submitting a project plan at the FY12 Annual Review for Satellite Product Development. Plans will be due in July 2011. - Yes. Bullets are added to slide 7 to reflect this intent. • What is impact of GOES data? Determine impact of GOES data on model - A sensitivity analysis will be done in 2nd year of the project 13