1986 Landsat Data Continuity Briefing 1997 Jay Feuquay

1986 Landsat Data Continuity Briefing 1997 Jay Feuquay, USGS Ted Hammer, NASA Stan Schneider, NASA/NPOESS 100 km Deforestation: Amazon Courtesy TRFIC–MSU, Houghton et al, 2000. ASPRS Conference Baltimore MD 10 March 2005

Agenda • Background • Landsat Overview - L 5/L 7 Status • Interagency Working Group • Data Continuity Strategy • Landsat on NPOESS • Summary 2

Background • “The Secretary of the Interior shall provide for long-term storage, maintenance, and upgrading of a basic, global land remote sensing data set…. ” P. L. 102 -555 Land Remote Sensing Policy Act of 1992 • NASA and DOI/USGS established as Landsat Program Management via Presidential Decision Directive NSTC-3 signed 5/5/94; amended 10/16/00 • NASA built, then launched Landsat 7 in 1999; USGS operates satellite and manages national long-term satellite data archive • Over 250 Landsat 7 scenes (nearly 8 million square kilometers) obtained per day by USGS 3

Background, con’t. • NASA and USGS develop a schedule for seasonal, global coverage, ensuring archive imagery for long-term land-cover record and before/after imagery of floods, forest fires, hurricanes, etc. anywhere on Earth Pre Tsunami Post Tsunami Population Impact 4

Background, con’t. Landsat Archive 33 Years and Counting: • Over 1. 7 million Landsat scenes • Over 630 terabytes of data Note: terabyte = 109 DVD movies • Grows by over 320 gigabytes/day Fire History: Mesa Verde National Park, Colorado 5

Background, con’t. VIIRS Landsat's Role in Terrestrial Remote Sensing 3300 km swath • spatial resolution, 400/800 m (nadir (Vis/IR)) AVHRR/ MODIS 2048 km swath • spatial resolution, 250 m, 500 m, 1000 m MISR • global coverage, 2 days 360 km • spatial resolution, 275 m, 550 m, 1100 m Landsat • global coverage, 9 days 183 km • spatial resolution, 15 m, 30 m ASTER • 16 day orbital repeat • seasonal global coverage 60 km • 45 -60 day orbital repeat • global coverage, years • spatial resolution 15 m, 30 m, 90 m Commercial Systems • spatial resolution ~ 1 m • global coverage, 2 x/day/satellite ~ 10 km • global coverage, decades, if ever 6

Landsat's Role in Terrestrial Remote Sensing Landsat remote sensing plays an important role in that… • • It gives us the "big view“ (183 by 170 km) It gives us a consistent, historical context and record It provides complete multispectral coverage (visible to infrared) It permits us to map geophysical parameters on regional, continental and global scales • It permits characterization of global land changes Monitoring of gradual changes in ecosystems requires long-term, scientifically valid satellite coverage -- only Landsat provides that record Landsat-resolution data are required to: • precisely assess the area(s) affected • separate human disturbances from those having natural origins • bridge the gap between field observations and global monitoring 7

Landsat Overview - L 5/L 7 Status • Landsat 5 and its Thematic Mapper (TM) sensor are 18 years past 3 -year design life • Data transmitted real-time direct downlink only; no onboard payload data recorder • Full US and partial global coverage • Fuel depleted in Spring, 2009 • Landsat 7 and its Enhanced Thematic Mapper-Plus (ETM+) sensor surpassed original design life of 5 years on April 15, 2004 • ETM+ scan line corrector (SLC) failure occurred on May 31, 2003 • The Landsat 7 images contain gaps – USGS developed Gap-Filled products • May 2004 failure of 1 of 3 gyros; no impact to imaging, but risk to extend operations increased • Fuel depleted in Spring, 2010 8

Landsat 7 Merged-Scene Product Post-anomaly Landsat 7 image Gaps filled with next image of same site 9

Risk of Landsat 7 Failure Approach: • NASA engineers in consultation with USGS Flight Operations Team conducted a risk analysis • Used developer’s reliability analysis as a baseline • Analyzed gyroscopes from the same manufacturer as those on Landsat 7 (L 7) analyzed Results: • The predominant reliability drivers are the gyros • Probability of L 7 success decreases to 60% by second quarter CY 2005 • Probability of L 7 success in mid 2010 (approximate time of Landsat 7 End-of-Fuel) is very low ~1%; probability of failure is ~ 99% 10

Landsat Data Gap Study Team NASA, USGS and Landsat user community representatives formed as team • Objective: Recommend options, using existing and near-term capabilities (not a gap filler mission), to populate the National Satellite Land Remote Sensing Data Archive with science-quality data for land use/land cover change • Process: Identify needs, identify existing and near term capabilities, compare, synthesize methodologies, identify resources for implementation • Constraints and Assumptions – – – – Focus on data acquisition solutions, NOT spacecraft or mission solutions Focus on and be consistent with Public Law 102 -555 LDCM data specification is a requirement threshold Though no single or combined data sources will fully meet Landsat continuity needs, team will recommend what can be done to lessen the impact of a data gap Assume L 7 failure in 2007 L 5 limited lifetime and capability OLI data available 2010 • Some data sources under investigation: Resource. Sat-1, DMC, CBERS, SPOT, ASTER, EO -1/ALI, Rapid. Eye • Team to complete first phase in March 2005 11

LDCM Interagency Working Group • Interagency Working Group convened by White House (NSC, OMB, OSTP) after commercial replacement deemed not practical • Members of LDCM Working Group: – – – NASA NOAA USGS NGA NRO • Process: 6 -8 months, examined over one hundred alternatives (e. g. , flights of opportunity, dedicated mission) to meet the land imaging requirement • Final decision is consensus of White House and agencies 12

Landsat Data Continuity Strategy Memorandum from EOP/OSTP issued August 13, 2004, states that: • Landsat is a National Asset • The Do. D, Department of the Interior, Department of Commerce and NASA agree to: – Transition Landsat measurements to an operational environment on the National Polar-orbiting Operational Environmental Satellite System (NPOESS) – Plan to incorporate a Landsat imager (Operational Land Imager – OLI) on the first NPOESS (known as C-1) scheduled for a late 2009 launch date • This strategy will be justified through the normal budget process 13

OLI/NPOESS Mission Advantages • Transition of Landsat into a truly operational measurement • Extension of the Landsat data record past 2020 • Leverage of proposed NPOESS infrastructure • Benefits derived from combining data from OLI with Visible/Infrared Imager Radiometer Suite (VIIRS): – Large scale processes of change detected by VIIRS can be more closely analyzed by OLI – OLI data can be used to better calibrate VIIRS and validate Environmental Data Records (EDRs) derived from VIIRS data conversely VIIRS spectral bands can be used to atmospherically correct OLI data – Terra (MODIS sensor) and Landsat 7 results have already demonstrated the potential of combining data 14

NOAA/NASA/Do. D Tri-agency Effort to Leverage and Combine Environmental Satellite Activities METOP • Mission NPOESS • Provide a national, operational, polarorbiting remote-sensing capability • Achieve National Performance Review (NPR) savings by converging Do. D and NOAA satellite programs 1730 1330 • Incorporate new technologies from NASA • Encourage International Cooperation 2130 Specialized Satellites Local Equatorial Crossing Time NPOESS 15

Landsat on NPOESS Notional Location Nadir Operational Land Imager (OLI) Direction of Motion Visible/Infrared Imager Radiometer Suite (VIIRS) 16

NPOESS Orbit Is Reasonable Fit for Landsat Mission Parameter Landsat NPOESS Orbital Altitude 705 km (438 miles) 828 km (517 miles) Type Sun synchronous, 980 inclination Equatorial crossing time 10 am +/- 15 min, descending 930 am +/- 10 min, descending (2130 ascending) Repeating Ground Track period 16 days 17 days Landsat Worldwide Reference System 57, 784 standard scene blocks, each 115 miles (183 km) wide by 106 miles (170 km) long, each taken at least 2 x per year -NPOESS can meet this requirement via synthesis of scenes - Non-standard scene blocks can be collected since sensor is always on 17

OLI on NPOESS Space Segment • NASA and NOAA/Integrated Program Office (IPO) technical team working together to address detailed technical requirements, specifically to: – Support OLI Request for Proposal (RFP) – Finalize location on NPOESS spacecraft – Conduct trade analyses for interface – Refine definition of spacecraft bus and operations modifications – Define testing approach – Develop Interface Control and Requirements Documents 18

OLI/NPOESS Concept of Operations NPOESS Safety. Net Architecture Landsat data are stored in a separate solid state recorder – NPOESS and OLI data downlinked to the Safety. Net. TM sites on every pass • Recorder has capability to store up to 250 scenes • System capability is 400+ scenes per day – USGS to command OLI for acquisitions – OLI data will be forwarded to the USGS over commercial fiber cable from Safety. Net sites – Users pick up data directly from USGS or USGS can “push” data to local users 19

Landsat in the President’s 2006 Budget • Successful transition of Landsat (OLI) onto the NPOESS platform requires adequate funding of partner-agency responsibilities: – USGS to develop OLI data processing system, command OLI – NASA to develop two OLI instruments – NOAA/IPO to perform OLI integration on NPOESS, transmit OLI data to USGS • The budget also requests funds for USGS to address revenue losses resulting from the failure of the Landsat 7 scan-line corrector in ETM+ instrument • Details of individual funding requests are presented in each agency’s Congressional Justification • Not providing this funding or sustaining other reductions to the NPOESS program will increase the duration of a data gap and may threaten the viability of the Landsat partnership. 20

Summary • Implementation of the Operational Landsat Imager allows: – Extension of the Landsat data record past 2020 – Transition of Landsat into a truly operational measurement – OLI and VIIRS to provide mutually enhancing observations • NASA and NOAA/IPO teams working detailed technical requirements for implementing OLI on an NPOESS spacecraft • NASA, USGS as well as other representatives from the Landsat community working to identify an approach to lessen the potential impact of a Landsat data gap 21

BACK UP 22

Gap Filler Mission Option Decision • Gap Filler Mission deemed too high risk based upon cost and schedule analysis – Proposed Plan: Implement a Gap Filler mission that will fly in a 705 WRS-2 orbit • Does not address long term transition of Landsat to an operational measurement • Option needed to procure a Landsat instrument for delayed implementation on NPOESS (target NPOESS C-4 in the 2014 timeframe) – Cost and schedule benefit analysis resulted in low return for investment • Cost: – Additional funds required to procure instrument for a delayed implementation on NPOESS • Schedule: – Provides only one year of operational capability before NPOESS solution 23

Integrated Operational Requirements Document (IORD) Example Atmospheric Vertical Temperature Profile Highly accurate measurement of the vertical distribution of temperature in the atmosphere in layers from the surface to 0. 01 mb Major Applications 1)Initialization of Numerical Weather Prediction Models 2)Complementary data for derivation of moisture/pressure profiles and cloud properties Disciplined Iterative, Requirements Process Ensures Users Needs are Met 25

Pre-Planned Product Improvement (P 3 I) EDR Candidates Tropospheric winds Neutral winds All weather day/night imagery Coastal sea surface winds Ocean wave characteristics Surf conditions Oil spill location Littoral current CH 4 column CO 2 column Optical background Sea and lake ice Coastal ocean color Bioluminescence potential Coastal sea surface temperature Sea surface height coastal Bathymetry Vertical hydrometeor profile Salinity 26

NPOESS Operational Concept 2. Downlink Raw Data 1. Sense Phenomena 3. Transport Data to Centrals for Processing TSKY T O BS TATM L L CL AT M L RN FOG Field Terminals eij Monitor and Control Satellites and Ground Elements Safety. Net™ Receptors Global fiber network connects 15 receptors to Centrals 4. Process Raw data into EDRs and Deliver to Centrals NESDIS/NCEP MMC (Suitland) Schriever MMC FNMOC AFWA NAVO Full Capability at each Central 27

NPOESS Top Level Architecture GPS NPP (1030) NPOESS 1330 NPOESS 1730 NPOESS 2130 Space Segment Command & Control Segment Low Rate Data/ High Rate Data (LRD/HRD) NPP Science Data Segment Field Terminal Segment Svalbard CLASS 15 Globally Distributed Receptor Sites FNMOC Alternate MMC at Schriever AFB Mission Management Center (MMC) at Suitland NPP Data & Control Flow NAVOCEANO AFWA NESDIS/NCEP Interface Data Processing Segment NPOESS Data & Control Flow NOAA Comprehensive Large CLASS Array Data Stewardship System EROS Data Center, Sioux Falls 28

NPOESS Satellite and Sensors 1330 1730 2130 NPP VIIRS X X X CMIS X X X Cr. IS X X X ATMS X X X SESS X X OMPS X ADCS X X SARSAT X X X ERBS X SS X X X ALT X TSIS X APS Landsat X X X = changed since award Single Satellite Design with Common Sensor Locations and “ring” Data Bus Allows Rapid Reconfiguration and Easy Integration 29

Safety. Net™ –Low Data Latency and High Data Availability Spain 75% of NPOESS Data Products at the Nation’s Weather Centrals within 15 min. . . . the rest in under 30 min Forteleza Perth Safety. Net™ -- 15 globally distributed SMD receptors linked to the centrals via commercial fiber -- enables low data latency and high data availability 30

31

Program Schedule 2002 A&O Contract Award 2003 NPP Delta Critical Design Review 2005 NPOESS Preliminary Design Review 2006 NPOESS Critical Design Review NPP Ground Readiness 2007 NPP Launch 2009 NPOESS Ground Readiness 2009 NPOESS C 1 Launch 2011 NPOESS C 2 Launch Field Terminal Segment Readiness Initial Operational Capability 2013 NPOESS C 3 Launch 2015 NPOESS C 4 Launch 2017 NPOESS C 5 Launch 2020 End of Program Reliable and timely collection, delivery, and processing of quality environmental data 32