1. GEOSS ADC Architecture Implementation Pilot 2 Disaster Management Scenario Caribbean Flood Pilot Sensor Web Report from the AIP2 Kick-off Meeting Boulder, Colorado 25-26 September 2008 Stuart Frye Pilot Leader and Technical POC NASA-GSFC-SGT stuart.frye@nasa.gov

2. 2

3. 3 Outline Background Objectives Input Outputs Outcomes Capacity Building Relevance User and Architecture Requirements Results to Date AIP Kickoff Partners

4. Background (1/2) GEO Workplan includes task to address Use of satellites for risk management: DI-06-09; DI-06-09 addresses all four phases of disaster management: mitigation, warning, response and recovery and examines user requirements and system architecture for a global multi-hazard approach, including developing pilots to demonstrate usefulness UN-SPIDER recognizes the critical importance of compiling user requirements, and can serve as a bridge between space and disaster management communities UN-SPIDER workshop in Barbados in July 2008 served as catalyst to define Caribbean Pilot to focus attention on how EO can better support disaster management in the Caribbean Flooding identified as best place by Caribbean users AIP Call for Participation identified as best vehicle to frame proposal and move pilot forward

5. Background (2/2) Participation in this Pilot anticipates Refinement and augmentation of the GEOSS Common Infrastructure including GEO Web Portal, Clearinghouse and Registries solutions (available for Pilot) Registration of components and services hosted by the participating organization in the GEOSS Registry to support access by the Clearinghouse and Portal, and that to support demonstration of a set of user scenarios. Participation in the development of a set of user scenarios that support the GEO Societal Benefit Areas. Participation in the refinement of the initial architecture based upon the pilot activities.

6. 6 Objectives To provide information on which flooding relevant data and models are already available for the Caribbean region To produce a one year flooding composite image from various satellites, and To make relevant data and services accessible via the GEO Portal

7. Input Satellite data: –MODIS –ASTER –Landsat –AMSR-E –TRMM –RADARSAT –ALOS –ALI and Hyperion (EO-1) –ENVISAT Other data sets: –Socio-economic data (administrative boundaries, populations, cadastral data, transportation networks, energy infrastructure) –Land cover, DEMs, catchment boundaries –Historical precipitation data and forecast precipitation data

8. Outputs Services and virtual infrastructure to support services: –Geospatially enabled campaign manager: visualization of available data products over given geographic area; automatic tasking of satellites and automated data retrieval mechanisms –Flood products: UM global flood potential product from TRMM data and DFO Satellite-based Flood Detection and Flood Risk Assessment to be adapted to regional context. Other flood products based on MODIS, ALOS, ENVISAT, EO-1 and RADARSAT data –Decision support tools: software marrying input from satellites and socio-economic data sets –Train the trainer modules: dedicated capacity building tools to support training in Caribbean region

9. Outcomes Decision makers: better enabled to take critical decisions in context of flood planning and response Regional civil protection agencies: better able to face flooding, find information and increase awareness of flood impacts The public: more aware of flood impact during and after events Data suppliers: increased awareness of gaps in data supply and need for support during mitigation and warning phases, rather than only during response

10. Capacity Building Capacity building is central to the success of the pilot Pilot plans to link technical personnel from end-user organizations with those knowledgeable with regard to satellite resources and their tasking In-person training sessions with willing end users planned Virtual capacity building to be developed through train the trainer modules that make up part of pilots outputs

11. Relevance Pilot will raise awareness of usefulness of satellite EO in area strongly affected by disasters Flooding is most serious and common disaster both in Caribbean and on global basis Caribbean offers smaller scale to work out technical issues and strong willingness of user community to collaborate Pilot expected to showcase need for increase data with regard to mitigation and warning phases Limited commitment in pilot context should encourage stronger participation from space agencies and other suppliers

12. User Requirements Establish user requirements (for each disaster type and phase): –Identify region of interest (priority areas) –Identify target characteristics (what do we want to see?) –Identify temporal revisit period –Establish timeliness/latency requirements –Identify end use for data by intermediate user (application, service, etc)

13. Architecture Options Establish architecture requirements (for each disaster type and phase): –What type of satellite data? (SAR, optical, altimetry, etc) –Number of satellites and coverage mode? –Ground segment –Application Roll-up across all disaster types to establish overall requirements of virtual constellation Simulate architecture options

14. Floods ©The World Bank – Natural Disaster Hotspots: A Global Risk Analysis

15. User Requirements-Floods Phase Requirements MitigationWarningResponseRecovery Target/data Topography Hydrological models Historical atlas of floods Flood models/simulations New infrastructure, houses Land-use classification Monitoring of dikes and dams Precipitation Water level (rivers, lakes) Weather forecast Soil moisture Snow-water equivalent Signs of catastrophic infra failure Water level (rivers, lakes) Extent of flood Status of critical infrastructure Weather forecast Status of critical infrastructure Damage assessment Flooded areas Revisit 1 to 3 years (imagery) 5 to 10 yrs (topography) Daily or better during high risk period Daily in early morning; twice daily if possible Weekly (major floods) for several weeks to several months Timeliness WeeksHoursHours (2-4 max)1 day End use Integration in land use planning/zoning Baseline for response Decision support for warnings & evacuation Situational awareness Resource allocation support Initial damage assessment Tracking affected assets Charting progress

16. Architecture Requirements-Floods1 Phase Requirements MitigationWarningResponseRecovery Data typeLow res DEM for flow rates (radar, stereo, laser) Higher res DEM (DTED-2 or better) for extent and location (radar, stereo, laser)_ Medium to high res (scale, other image sources, urban/rural) Optical or radar overlay (geo-coded, ortho- rect.) Archived imagery of previous floods Interferometric analysis of subsidence (and other changes) Met sats Precipitation radar X, C or L-band SAR 10- 50m data Passive microwave (for soil moisture) Hi res optical upstream for slow flood Altimeters Interferometric analysis of subsidence (and other changes) Precipitation radar X, C or L-band SAR 10-50m data (extent of flood – large areas) ; higher res radar and optical for urban areas or flash floods (damage) Met Altimeters Med to high res optical and radar Interferomet ric coherent change maps Coverage and revisit Continuity of existing optical and radar missions (need to develop background mission coverage in areas on flood map) Daily coverage in regional areas affected Pre-dawn or dawn required Daily early morning coverage in regional areas affected Continuity of existing optical and radar missions

17. Architecture Requirements-Floods2 Phase Requirements MitigationWarningResponseRecovery Potential data source SRTM (background) SRTM DTED-2, Tandem-X DTED-3, Cosmo, etc…. GPM 3-4 radar satellites on same orbit; 2-3 satellites using same frequency in same orbits Optical: comparable? 3-6 radar satellites on same orbit Optical hi res (2 or more) 2 radar satellites using same frequency Optical hi res (1) Ground segment (need for development) Using existing ground segments Fast download, fast tasking (northern/southern stations, geostationary com links) Very fast download and tasking (northern/southern stations, geostationary com links) Using existing ground segments ApplicationIntegration with risk map Land cover maps Information used for bulletins and evacuation, warnings Situational awareness products Tracking affected assets

18. Disaster Response This image from September 8, 2008 was provided by the U.S. Navy. Homes seen in Port De Paix, Haiti remain flooded after four storms in one month devastated the area and killed 800+ people. The amphibious assault ship USS Kearsarge was diverted from the scheduled Continuing Promise 2008 humanitarian assistance deployment in the western Caribbean to conduct hurricane relief operations in Haiti. (Getty Images)

19. Disaster Response The surge before the Hurricane Ike swamps Galveston Island, Texas, and a fire destroys homes along the beach as the storm approaches Friday, Sept. 12, 2008. (AP Photo/David J. Phillip). Top left: Gilchrist, TX on 14 Sep 08 (David J. Phillip-Pool/Getty Images).

20. Results to date Consensus on methodology to collect user requirements for multi-hazard disaster management for all phases Buy-in to process from large representative user body (including civil defense, international organizations) Commitment from space agencies to provide support to modeling scenarios, and to work towards solution in context of CEOS Negotiations underway with International Charter: –Mechanisms for broadening of Authorized User community (those that activate the Charter during response) to include all GEO Member States currently under discussion –Advice sought on how to better access archived data to support other phases (beyond response)

21. AIP-2 Kickoff Workshop Results. Summary of Disaster Responses (1/2) Speaker/OrganizationTitle Stu Frye – Session Lead (NASA)Overview of GEOSS Pilot and GEO Tasks for Disaster Response Ron Lowther* (NGC)Agenda, Timelines, and List of Primary Participants Didier Giacobbo* (Spot Image)List of Services and Components from Primary Participants Morris Brill (NGC)Northrop Grumman (NGC) Response to GEOSS AIP-II CFP Stu Frye (NASA/SGT)Caribbean Flood Pilot Sensor Web Didier Giacobbo (Spot Image)Spot Image Response to the GEOSS AIP-2 CFP Jeff de La Beaujardiere (NOAA IOOS) NOAA IOOS Data Integration Framework (DIF) Contribution to the GEO AIP-II Ken McDonald (NOAA) and Dr. Liping Di (GMU) NOAA-NASA GOES-R and GMU CSISS joint efforts for persistent GOES data services, weather scenarios, Web geoprocessing services, and BPEL-based workflows Prof. Natalia Kussul, SRI NASU- NSAU (GEO-Ukraine) Sensor Web for Flood Applications * Ron Lowther and Didier Giacabbo co-leads for the AIP-2 Disaster Management Scenario

22. AIP-2 Kickoff Workshop Results. Summary of Disaster Responses (2/2) Satoko H. MIURA and Kengo AIZAWA (JAXA) Catalog Server for ALOS data Steve Del Greco (NCDC)The Next Generation Weather Radar system SURA/SCOOP, GoMOOS, and NIMSAT Communication of Disasters and Mitigation of Post-Disaster Damage ICAN (Oregan State U.)International Coastal Atlas Network (ICAN) (CNES) CENTRE NATIONAL DETUDES SPATIALES Disaster Charter Catalog Server for GML-EO Metadata Harvesting and HMA-compliant Web Services Access (ERDAS) The Earth to Business Company Geospatial Collaboration and Information Sharing Infrastructure for GEOSS Work Plan Development / Open Discussion What is missing and still needed: services, components, and data/product gaps? What would result in paradigm shifts to meeting our objectives rather than simple evolutionary paths? Adjourn SessionCo-Leads will present summary of the session and work plan (with dates/actions) at closing Plenary Speaker/OrganizationTitle

23. Partners Flood Pilot includes range of partners at this time, with further partners expected: NASA Goddard SFC (Lead) CEOS Disaster SBA Team (advisory role) UNOOSA/UN-SPIDER (advisory role) Caribbean Disaster Emergency Response Agency (CDERA) CATHALAC/SERVIR ESA Caribbean URISA Charter West Indies University American Institute of Technology (ITLA) School of Earth & Environmental Sciences at the University of Portsmouth, UK Others invited to join

24. 24