Disasters Response WG
Disaster Management Scenario
Work in progress : uniquely identify the scenario Actors, Services, and Products that build-up a scenario
|
Transverse Technology Use Cases
Work in progress : map and document generic/reusable Use Cases, that help to understand the AIP-2 architecture (as-is, or to-be)
|
Specialized Use Cases
Work in progress : document the available implementations for the Pilot, as well as identify the AIP-2 participants being supportive providers of such concrete use cases in their offerings to GEOSS
| GEOSS Registry references
|
DR-DM-00. The Initiator is in charge of searches for warning services that provide events or predictions about potential flood on a given area. These services should be discovered by accessing GEOSS Portals (eg geoportal.org).
A GEOSS Portal shall provide minimum information about available services and how to access them. |
|
ESA GEOPortal client (e.g. connecting to specific RSS feeds)
http://www.geoportal.org/c/portal/layout
Should we register NOAA RIDGE Portal ?
http://radar.weather.gov/ridge/kmzgenerator.php
(RIDGE Image and Warning Output to KML/KMZ)
|
ESA GEOPortal is Registered
|
DR-DM-01. Based on services found at Step 0, the Initiator identifies areas where monitoring is needed and asks Actuator (Regional civil protection) to activate services that offer Early Warning (e.g. based on modeling such a Global Flood Potential Model) to monitor AOIs.
Then the monitoring action consists to activate some Early Warning service and possibly subscribe to any related Alert service. |
|
Anticipated : UC#5 "Present Alerts" specialized use case (carrying "Potential Floods" CAP content) / that is a "Monitoring" specialized use case
Anticipated : UC#6 "Interact" specalized use case to extract information useful for producing a documented request from Initiator to Actuator
01-01 SIREN portal
http://geoss1.ms.northropgrumman.com
Drought,
Station Climate Data, Space Weather Data … and services
KML currently downloaded from Mitigation and Response tabs, with WMS services
available on most tabs from live data sources.
(within Victoria COP space)
01-02 Hurricane tracks from National Hurricane Center / Tropical Prediction Center (only downloads so far)
http://www.nhc.noaa.gov/
01-01 and 01-02 for Prediction & Warning
01-03 NOAA Sensors in-situ SOS
http://sdf.ndbc.noaa.gov/sos/server.php?request=GetCapabilities&service=SOS
http://opendap.co-ops.nos.noaa.gov/ioos-dif-sos/SOS?service=SOS&request=GetCapabilities
(both covering caraibean area)
- NASA Global Flood Potential Model (GFPM) : through SPS ? (setup ongoing, follow-up: Stu)
|
NGC SIREN Portal is Registered
|
DR-DM-02. When an alert is raised, Actuator (Regional civil protection) requests multiple Processors (Data Providers) to activate monitoring services.
Processors activate such services. The output of such services should be WMS, WCS or SOS. The output should be on daily time monitoring.
|
|
Daily analysis (manually) for Decision Aid
Mid or low resolution data for monitoring (MODIS, GOES,...), in-situ sensors...
MODIS tiles for the Cairibean region :
(ongoing, follow-up: Stu)
GOES : see with NOAA response GOES-R (CLASS component accessing GOES archive)
Might be contributed by the WFS from GMU CSISS response ?
| |
DR-DM-03. A Processor configures/sends an event notification to Actuator (Regional civil protection) when monitoring detects upcoming disaster conditions.
The notification can be send by using Sensor Alert Service (SAS).
|
| N°. |
Name |
Desc. |
| 06 |
Interact with Services |
Activity of client to consume services for datasets, sensors, models, workflows, etc |
|
UC#6 "Interact" specialized use case to advertize a SAS from a sensor node event/alert, and configure the SAS with thresholds.
| |
DR-DM-04. Based on Alert issuing by a Processor, the Actuator (Regional civil protection) accesses the result of observations using WCS or SOS (e.g. Daily Flood Map Prediction).
Based on the map analysis, the Actuator (Regional civil protection) sends back to Initiator a demand for activation of new data acquisition.
|
|
UC#5 "Presentation" specialized use case, from client perspective, that must be Extensible Messaging and Presence Protocol (XMPP) enabled to comply with SAS.
UC#6 "Interact" specialized use case for WCS / SOS
(might requires cross telecon to discuss that link between EO specialists and more global users)
UC#7 Map analysis (through client like GEOPortal, or other desktop application...).
Could be real-time geo-collaboration scenario for decision aid.
http://geoss.erdas.com/titan
|
ERDAS TITAN client is Registered
|
DR-DM-05. Based on Initiator acknowledgment, the Actuator (Regional civil protection) activates a feasability request for a new data acquisition to multiple Processors (Data Providers) through SPS.
|
|
UC#5 specialized use case (request feasability) for SPS client ?
NASA SPS client : Campaign manager ?
SPOT SPS client application:
http://ws.spotimage.com/labs/GEOSSDemoPage.htm
Others ?
Space Time Toolkit, ESA SSE
| |
DR-DM-06. The Actuator (Regional civil protection) receives back from multiple Processors (Data Providers) feasibility sensor acquisition results.
The Actuator analyses feasibility study, both from SPS output to a dedicated SPS client application and from SPS KML output.
|
|
SPOT SPS client application
http://ws.spotimage.com/labs/GEOSSDemoPage.htm
UC#5 specialized use case (feasability study) for SPS client ?
Google Earth 5 client application for analysis of KML output from SPS (using time dimension)
http://earth.google.com
| |
DR-DM-07. Based on existing feasibility studies, the Actuator (Regional civil protection) sends a request for acquisition (tasking) through SPS. If possible the acquisition should be for data before, during and after event.
|
|
UC#5 specialized use case (tasking/Acquisition request) for SPS client ?
| |
| DR-DM-08. In parallel with acquisition request, the Actuator (Regional civil protection) request data from catalogue before event for a pre-damage analysis. |
|
UC#4 specialized use case with ESA EO Clearinghouse (SSE) to search Providers catalogs (archived acquisitions)
| |
DR-DM-09. Once data is acquired, a Processor sends notification to Actuator (Regional civil protection) via WS Addressing or WS Notification.
One or more Processors (Data Providers) make ortho-image available (pre and after).
Geometric processing / Ortho-processing can be activated via WPS.
Publication is made through WCS / WMS.
|
|
WMS on ALOS Data (Areas : xxx)
http://virgo.exst.jaxa.jp/cgi-bin/wms_AIP2?service=WMS&VERSION=1.3.0
UC#8 WPS for orthoprocessing
WCS output :
http://ws.spotimage.com/wcs/coverage/Burma?request=getCapabilities&service=WCS |
JAXA ALOS WMS Server is Registered
Spor Image SPOT 5 WCS/WMS Server is to be Registered
|
DR-DM-10. Actuator (Regional civil protection) accesses the data via WCS or WMS and should start the analysis process.
The Actuator can submit such results to an Hydrology/Meteorology Disaster Management domain experts (e.g.the Carabean Disaster Response Agency) and ask for 'near real time' feedback on the produced maps.
|
| N°. |
Name |
Desc. |
| 06 |
Interact with Services |
Activity of client to consume services for datasets, sensors, models, workflows, etc |
|
Pre and Post analysis tool
TITAN client for geo-collaboration over TITAN Network
http://geoss.erdas.com/titan | |
DR-DM-11.In parallel, Actuator (Regional civil protection) should request thematic processing from Processors (Map producer).
This would involve the WPS running a classification or detection algorithm, and production of PNG and KML overlays on the raster result (GeoTIFF) from the WPS
|
|
UC#8 WPS for orthoprocessing
http://aiweb.jpl.nasa.gov/wps/cgi-bin/wps.py?REQUEST=GetCapabilities&service=wps
| |
DR-DM-12. The result of processing is released and make available through WCS or WMS.
Depending on when the data is acquired, and whether the Alert was issued quite early before event, the data should be thematically processed to update the state of road network, and publish that map via WMS.
The WMS is used on-the-field by Actuator (Regional civil protection) , e.g. for building an evacuation plan.
Whether data is acquired but delivered too late during or after event, the Actuator should provide damage map after event.
This information should be available through WMS and used for assessing damage by insurance company or by NGO organisation to help Public.
|
| N°. |
Name |
Desc. |
| 06 |
Interact with Services |
Activity of client to consume services for datasets, sensors, models, workflows, etc |
|
Insert "Map producers" role ?
TITAN client for geo-collaboration over TITAN Network
Secure communities (
http://geoss.erdas.com/titan | |
| DR-DM-13.All maps produced are released for public communication and accessible via massmarket products such as KML. |
|
| |
UML Disaster Management Final Report attached