1296days since
Demo Capture

Recent site activity

Disaster Scenarios

This first draft of the scenario was taken from the CFP. Participants in the Disaster Management scenario are warmly invited to update this scenario.

This update may consist by adding missing steps, describing the Specialized Use Case (components from participants) and giving comments on both the use case or steps.

As draft, please use the table on the text below and then maitain it alive. The table mode on the bottom of the page will be updated later.
 
This will allow us to achieve a consolidated version by end of May .

Legend:
Services in blue
 Products in red
Actors in orange

Step

Description

Use Case

Specialized Use Case

Comments

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

GEOSS Portal shall provide minimum information about available services and how to access them.

Search for resources in Registry, Clearinghouse and Community Catalogs

 

 

 

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.

User presentation of information about available services, workflows, and alerts

 

Activity of client to consume services for datasets, sensors, models, workflows, etc)

 

 

 

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 WMSWCS or SOS. The output should be on daily time monitoring.

Register resources in the GEOSS OCS Registry

 

Configure and deploy a component with associated services

 

 

 

03

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

Activity of client to consume services for datasets, sensors, models, workflows, etc

 

 

 

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.

User presentation of information about available services, workflows, and alerts

 

Activity of client to consume services for datasets, sensors, models, workflows, etc)

 

Use portals and clients to present data in useful ways for interpretation and decision support

 

 

05

Based on Initiator acknowledgment, the Actuator (Regional civil protection) activates a feasability request for a new data acquisition to multiple Processors (Data Providers) throughSPS.

User presentation of information about available services, workflows, and alerts

 

 

 

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.

User presentation of information about available services, workflows, and alerts

 

Use portals and clients to present data in useful ways for interpretation and decision support

 

 

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. 

User presentation of information about available services, workflows, and alerts

 

 

 

08

In parallel with acquisition request, the Actuator (Regional civil protection) request data from catalogue before event for a pre-damage analysis.

Search for resources in Registry, Clearinghouse and Community Catalogs

 

 

09

Once data is acquired, a Processorsends 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.

Register resources in the GEOSS OCS Registry

 

Configure and deploy a component with associated services

 

Configure and deploy workflow consisting of one or more services

 

 

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 Managementdomain experts (e.g.the Carabean Disaster Response Agency) and ask for 'near real time' feedback on the produced maps.

Activity of client to consume services for datasets, sensors, models, workflows, etc

 

Use portals and clients to present data in useful ways for interpretation and decision support

 

 

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

Configure and deploy workflow consisting of one or more services

 

 

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 byinsurance company or by NGO organisation to help Public.

Activity of client to consume services for datasets, sensors, models, workflows, etc

 

Use portals and clients to present data in useful ways for interpretation and decision support

 

 

13

All maps produced are released for public communication and accessible via massmarket products such as KML.

 

 

 

Showing 4 items
StepScenarioUseCaseSpecializedUseCaseComments
Sort 
 
Sort 
 
Sort 
 
Sort 
 
Sort 
 
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. Search for resources in Registry, Clearinghouse and Community Catalogs   
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. User presentation of information about available services, workflows, and alerts. Activity of client to consume services for datasets, sensors, models, workflows, etc)   
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. Register resources in the GEOSS OCS Registry. Configure and deploy a component with associated services   
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). Activity of client to consume services for datasets, sensors, models, workflows, etc   
Showing 4 items
Comments