1 / 17

Hervé Caumont, OGC GEO IX Plenary November 23 rd , 2012

Architecture Implementation Pilot-5 Disasters Management WG Encourage mature systems to interoperate with the GEOSS Common Infrastructure. Hervé Caumont, OGC GEO IX Plenary November 23 rd , 2012. GEOSS connects Observations to Decisions.

auryon
Télécharger la présentation

Hervé Caumont, OGC GEO IX Plenary November 23 rd , 2012

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Architecture Implementation Pilot-5 Disasters Management WGEncourage mature systems to interoperate with the GEOSS Common Infrastructure Hervé Caumont, OGC GEO IX Plenary November 23rd, 2012

  2. GEOSS connects Observations to Decisions

  3. GEO Task DI-01Informing Risk Management & Disaster Reduction Priority Actions • Provide timely information relevant to the full cycle of disaster management (mitigation, preparedness, warning, response and recovery) Approach (C1 & C5) • Increase use of satellite data for disasters management cycle, develop EO data integration best practices • Integrate EO data (fresh & archive) with 'baseline' data: provide easy to access combined information • Review Global and regional disaster management systems: identify gaps wrt data, metadata, functionalities, lifecycle... • Develop Regional End-to-End Pilots

  4. GEO Task IN-05GEOSS Design and Interoperability Priority Actions • GEOSS Research and Prototyping • GEOSS Interoperability Analysis and Support • Encourage mature systems to interoperate with GCI     • Ensure access to GEOSS Data-CORE     Approach • Manage evolutionary architecture of GEOSS • Standards and Interoperability Forum (SIF) • Architecture Implementation Pilot, Phase 5 (AIP-5)

  5. Architecture Implementation Pilot and DM AIP-1: GEOSS Common Infrastructure (GCI) prototype • Applied to DM: oil spill, volcano, hurricane AIP-2: Disaster Management Scenario • Scenario and Use Case driven development • Applied to flooding; Recast to other disasters AIP-3: Near- real-time dispatching during response • Component architecture confirmed AIP-4: DM based on EC BRISEIDE project AIP-5: Coordination with CEOS on DM – in process “Fostering interoperability arrangements and common practices for GEOSS”

  6. AIP-5 DM scenario Participants support • Global- and regional-scale data related to disasters and vulnerabilities • Urbanization and human settlements parameters • Contributions to the GEOSS Data-CORE • Services structured to encourage full participation of end-users • Countries / regions that need to be involved in the generation of their own disaster management resources • Services for near real-time processing of satellite acquisitions, like near real-time satellite tasking • Deliver more dynamic disaster related product generation workflows and more responsive collaboration. • Select events for Demo capture and acquire imagery (thru AIP-5: EO-1, Radarsat, Formosat, GeoEye…)

  7. Disaster Management cycle • Many activities by many players • Many ad hoc arrangements • Limited effectiveness, efficiency • How new suppliers can plug in their data / services • How new users can tap into these data / services • What resources are shared … missing … interdependent … isolated • Need to establish partnerships, standards, vocabulary, etc., in advance of disaster events • Need a precise, common understanding of processes, resources, and needs Graphic based on World Economic Forum, 2011, “A vision for managing natural disaster risk: proposals for public/private stakeholder solutions,” p. 21.

  8. Satellite Programing Satellite Tasking One Stop Telemetry(Data) Satellite Scheduling Receiving station Satellite Scheduling Receiving station User Interface http://140.134.48.12:443/quasiST/login

  9. GEOSS and CEOS coordination on DM • GEO and CEOS are advancing the use of Earth Observations (EO) in Disaster Management (DM) • Systems in GEOSS informing risk management and disaster reduction with EO-derived information. • Architecture Implementation Pilot (AIP) to describe, interconnect, capitalize, share • CEOS developing GEOSS Architecture for the Use of Satellites for DM and Risk Assessment • GA.4.Disasters • Coordinated GEOSS and CEOS activities

  10. GEOSS AIP Architecture Community Objectives Enterprise Viewpoint GEOSS Vision and Targets Societal Benefit Areas System of Systems/ Interoperability Use Cases Services Information Framework Abstract/Best Practices Catalog/Registry Access and Order Processing Services Sensor Web User Identity Earth Observations Geographic Features Spatial Referencing Metadata and Quality GEOSS Data-CORE Information Viewpoint Computational Viewpoint Tutorials Optimized Design/Development Engineering Viewpoint Component Types Technology Viewpoint RM-ODP Viewpoints

  11. GA.4.Disasters:Enterprise Viewpoint • Purpose, scope, structure • Disaster lifecycle phases and types – e.g., • Natural: Geophysical, Hydrological, Climatological, Meteorological, Biological • Manmade: Conflict, Famine, Displaced populations, Industrial / Transport Accidents • Stakeholders • National/Regional DM agencies; Global data brokers; • CEOS / WGISS member agencies; GEO/GEOSS; UN-SPIDER • Policies / Objectives / Procedures • GEOSS data sharing principles; Interoperability arrangements • (Interoperating) System of (autonomous) Systems • More effective, efficient use of satellite data in disaster management Graphic: “Is ‘Flood Risk Management’ Identical to ‘Flood Disaster Management’?” Vanneuville et al., posted on March 21st, 2011, Earthzine on-line magazine published by IEEE and ICEO, http://www.earthzine.org/2011/03/21/is-flood-risk-management-identical-to-flood-disaster-management/

  12. GA.4.Disasters:Information Viewpoint • Observation requirements vs. disaster types and lifecycle phases • Observations by satellite sensor types • Satellite data processing e.g., • Decoding raw satellite feeds • Georeferencing / georectification • Atmospheric correction • Image interpretation, feature extraction • Image resampling / tiling for interactive visualization • Image enhancement (e.g., pan sharpening) • Semantics / ontologies / translation • Metadata for discovery and assessing fitness-for-use • Data Licensing

  13. GA.4.Disasters:Computational Viewpoint • Priority service types for satellitedata in disaster management • Data Access • Data Processing • esp. Image Interpretation • Portrayal • Sensor Tasking • User Management • esp. for sensor tasking • Constraints and requirements for satellite data services in DM • Near-real-time performance • Cross-community interoperability • Easy access by a variety of users • Service-oriented approach vs. push / broadcast

  14. Conclusions • Shared information: • GEOSS Data-Collection of Open Resources for Everyone (CORE) • The data are free of restrictions on reuse; • User registration or login to access or use the data is permitted; • Attribution of the data provider is permitted as a condition of use; • Marginal cost recovery charges (i.e., not greater than the cost of reproduction &distribution) are permitted. • Actionable information: • Sensors • Further coordinate ‘activations’, Agencies and AIP testing and release cycles • Maps • Further address gaps in Capacity Building for Map-based decision making • Have more timely dissemination, sustained workflows • Develop collaborative tools for regional teams • Alerts • Leverage new channels for early warnings • Showcase geolocation enabled alerts • Indicators • To inform policies for Planning & Mitigation • For Recovery, Reconstruction

  15. References • GEO • earthobservations.org • GEO Architecture Implementation Pilot • www.ogcnetwork.net/AIpilot • http://twiki.geoviqua.org/twiki/bin/view/AIP5/DisastersSBATopic • GEOSS registries and SIF • geossregistries.info

  16. Contacts Hervé Caumont, AIP-5 DM WG lead (OGC) herve.caumont@terradue.com George Percival, IN-05-C1 task lead (OGC) percivall@myogc.org

More Related