GEOSS ADC Architecture Workshop Disaster Management February 5

GEOSS ADC Architecture Workshop Disaster Management February 5 th, 2008 Guy Séguin Canadian Space Agency Guy. seguin@space. gc. ca

Outline • • Background Objectives Disaster Cycle Phase-by-Phase Approach Methodology Example – Floods Issues Identifying Scenarios for ADC 2

Background • GEO Workplan 2007 -09 includes task to address “Use of satellites for risk management”: DI-06 -09 • In April 2007, CSA asked by GEO Secretariat to play a leadership role with UNOOSA in broadening scope and impact of task, ensuring development of a virtual constellation for risk management • DI-06 -09 to address all four phases of disaster management: mitigation, warning, response and recovery and to examine user requirements and system architecture for a global multi-hazard approach • UN-SPIDER recognizes the critical importance of compiling user requirements, and can serve as a bridge between space and disaster management communities

Background (II) • CEOS currently reo-organizing its contributions to GEO to ensure coordination within each SBA • New CEOS Disaster Working Group created in January and chaired by Guy Seguin • All inputs to “DI” tasks of GEO workplan will be coordinated through this group • New list of actions currently being elaborated focused on three main activities: development of architecture to meet user needs, technology demonstrations to increase user awareness and pilot projects to demonstrate operational feasibility

Objectives • Help space community understand specific needs of disaster management community, as well as operational mechanisms and interactions (local, provincial and national) • Collect information on needs of users to establish requirements • Establish ‘virtual constellation’ of satellites to address each phase of disasters, working through existing bodies such as International Charter and CEOS 5

Disaster Cycle 6

Tailored Solutions for Each Phase • For Response, broaden International Charter by inviting GEO Member states to designate authorized users; encourage new Charter membership • For Mitigation/Warning/Recovery, use pilot project approach with selection of regional champions that can integrate satellite data; organize volunteer contributions on mission-by-mission basis; define global “baseline” imaging scenario 7

Work to date • System Architecture Group (CSA Chair - Mtgs in June and October) – Participants from ASI, CSA, DLR, ESA, NASA, UN-SPIDER, International Charter, GEO Secretariat, Athena Global • User Requirements Group, in conjunction with UNSPIDER (UNOOSA Chair - Mtgs in June and October) – 25 participants from range of civil defense organizations, international organizations (ISDR, UN-OCHA, CDERA, ADPC), space agencies and private sector – presentations to broader conference and validation of results (80 people)

Outcomes 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)

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)

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

Example – Floods Starting Point – World Bank Risk Analysis ©The World Bank – Natural Disaster Hotspots: A Global Risk Analysis

User Requirements Roll-up – Floods Phase Requirements Mitigation Warning Response Recovery 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 Weeks Hours (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

Architecture Requirements – Floods (I) Phase Requirements Mitigation Warning Response Recovery Data type Low 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 -50 m 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 -50 m 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 Interferometric 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

Architecture Requirements – Floods (II) Phase Requirements Mitigation Warning Response Recovery Potential data source SRTM (background) SRTM DTED-2, Tandem-X DTED-3, Cosmo, etc…. GPM 3 -4 radar satellites on same orbit; 23 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 Application Integration with risk map Land cover maps Information used for bulletins and evacuation, warnings Situational awareness products Tracking affected assets

Issues • Insufficient frequency of observations of various satellite types (radar, optical, altimeters, etc) • Harmonization of platforms Example of one day coverage of selected satellites (Envisat, ERS-2, RADARSAT-1 and ALOS)

Proposed Way Forward • Work with International Charter to define process to broaden and simplify access to all GEO Member States during disaster response • Within CEOS context, ensure contributions from space agencies towards pilot projects • Identify champions within each disaster community of practice and choose pilot projects on a regional level for different disaster types to demonstrate the effectiveness of satellite imagery for disaster mitigation, warning and recovery

Identifying Scenarios • Last year, the ADC developed four disaster-related scenarios: ØHurricane warning: used archive data Øvolcano eruption: used archive data Øsub-Saharan wildfire: used EO 1 Hyperion data acquisition Øoil spill response:

Identifying Scenarios • Two pilot projects are being considered by CEOS Disaster Working Group: – Flood management in South America – Global wildfire response • Next step consist in the identification of region of interest and an implementation of a multi-hazard approach across all phases of disaster management • Proposals for 2008 are: – Multi-Hazard & phase approach for Hurricane strikes – Expand Sentinel-1 fire-Hazard to other regions

Multihazard Management in the Caribbean 1/2 • Summary: satelllite data is used to support a multihazard approach to risk management in the Caribbean (16 countries) – support to DI-06 -09 • Context: CDERA, a multinational organization with disaster preparedness and response responsibility for 16 nations, works with the GEOSS to map out risk zones and prepare response plans in preparation of a hurricane/flood, landslide and volcano/earthquake • Event: hurricane strikes island causes serious landslides

Multihazard Management in the Caribbean 2/2 • Actions – Mitigation: topographic data, demographic data, Hydrological model, critical infrastructure – Warning: Hurricane Watch, meteorological data/precipitation – Response: Planned acquisition from disaster Charter – Recovery: Disaster Charter data • Lead: CEOS disaster team. POC Stu Frye GSFC

Global Wildfire Management • Summary: satellite data used to predict high-risk zones for wildfires throughout a calendar year on a global basis • Context: supporting DI-06 -13, satellite data is integrated with in-situ information from GEOSS sources to assess fire risk and prevent losses • Event: a fire season, south west US or Australia (one calendar year) • Actions: Use the Sentinel Asia model and Sub-Saharan African Wild fire scenario of 2007 • Lead: EO 1 team/CEOS disaster team (POC. Steve Ungar)