|
Scenario Name
|
Engineering Use Cases
|
Specialized Use Case
|
|
DM-01 Early Warning Signal
|
|
01.1. The Initiator is
in charge of searches for early warning
services that provide events or
predictions about potential disaster 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(ex. Typhoon path prediction
web services ) in GCI Registry
|
|
01.2. Based
on services found at Step 0, the Initiator identifies sensitive areas
and asks Actuator (Regional civil
protection) to activate early warning services (e.g. based on modeling such a Global
Flood Potential Model) and possibly
subscribe to any related Alert service to take care of this AOIs.
|
|
N°.
|
Name
|
Desc.
|
|
06
|
Interact with Services
|
Activity of client to consume services for datasets, sensors,
models, workflows, etc
|
|
User presentation of information about available
services(ex. Rainfall
prediction web services), workflows, and
alerts
Activity of
client (ex. SWCB) to consume services for datasets, sensors, models, workflows?
|
|
01.3. When
an alert is raised, Actuator (Regional
civil protection) requests Initiator to
activate monitoring services.
Initiator requests multiple Processors (Data
Providers) to activate such monitoring services.
|
|
Client invokes
resources (ex.SOS for CCD camera, SOS for in-situ
rainfall, transportation web services, WFS for evacuation map, WMS for
ortho-image) from GCI.
|
|
01.4. Processors (Data Providers) activate such
monitoring services.
The output should
be WMS, WCS or SOS on daily time monitoring.
|
|
N°.
|
Name
|
Desc.
|
|
06
|
Interact with Services
|
Activity of client to consume services for datasets, sensors,
models, workflows, etc
|
|
Client invokes
resources (ex.SOS for CCD camera, SOS for in-situ
rainfall, transportation web services, WFS for evacuation map, WMS for
ortho-image) from GCI.
|
|
01.5. Processors (Data Providers) configures/sends
an event notification to Actuator (Regional civil
protection) when monitoring
service 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
|
|
Processors (ex. SWCB)
send SAS (ex.SAS for debris flow disaster) to Actuator.
|
|
01.6 Based on Alert issuing by a Processor (Data Providers),
the Actuator (Regional civil protection) accesses the monitoring results of monitoring services using WCS or SOS (e.g. Daily Flood Map Prediction).
|
|
|
|
DM-02 Activation of Disaster Management
|
|
02.1.
According to the monitoring results analysis, the Actuator (Regional
civil protection) sends back to Initiator a demand for
activation of disaster management services with
a list of requested map and thematic products.
|
|
N°.
|
Name
|
Desc.
|
|
06
|
Interact with Services
|
Activity of client to consume services for datasets, sensors,
models, workflows, etc
|
|
|
|
02.2. Based
on Initiator acknowledgment, Initiator activates disaster management services.
Processor (Data
Providers) and Processor (Map Producer) are notified of
the crisis activation.
Requirements for new data acquisition are deduced from the list
of expected map and thematic products.
|
|
|
|
02.3. The Initiator search
for existing data,
maps or
thematic products (e.g reference map, evacuation plan) from catalogue before event for a pre-damage analysis.
Initiator notifies immediately about the result the Actuator (Civil Protection) which will be
able to access to existing map or thematic products.
Search and assessment
would be made through CSW and WMS <or W3DS>. Access would be made through WCS/WFS.
|
|
3D portrayal can be
used as enhanced visualizazion method
|
|
02.4 In parallel, the Initiator activates
a feasibility request for a new data
acquisition to multiple Processors (Data Providers) through
SPS.
The Initiator receives
back from multiple Processors (Data
Providers) feasibility sensor acquisition
results.
The Initiator analyses
feasibility study, both from SPS output to a dedicated SPS client application and from SPS
KML output.
|
|
N°.
|
Name
|
Desc.
|
|
06
|
Interact with Services
|
Activity of client to consume services for datasets, sensors,
models, workflows, etc
|
|
|
|
02.5. Based
on existing feasibility studies, the Initiator sends a request for
acquisition (tasking) through SPS to Processors (Data
Provider).
Once data is acquired, a Processor (Data Provider) sends
notification to Initiator and Processors (Map Producer) via WS Addressing or WS Notification.
|
|
N°.
|
Name
|
Desc.
|
|
06
|
Interact with Services
|
Activity of client to consume services for datasets, sensors, models,
workflows, etc
|
|
|
|
02.6 One or more Processors (Map Producer) produce requested maps and thematic
products and notify Initiator and Actuator (Civil Protection)
when they are available.
Notification is sent
to Initiator
and Actuator (Civil Protection). Maps
and thematic
products processing can
take benefit of a WPS or <OpenLS> interface.
Initiator handles disaster management services to ensure access to the requested maps and thematic
products.
|
|
N°.
|
Name
|
Desc.
|
|
06
|
Interact with Services
|
Activity of client to consume services for datasets, sensors,
models, workflows, etc
|
|
Those alert results
will be inputted to a fusion engine and be integrated with evacuation routing service(WPS) (ex.
WPS for routing analysis -> <comment:
it is possible to serve routing via WPS but there is a routing
interface integrated in the OGC Open GIS Location Based Services Spec.,
this interface regards special demands on routing> <Location
based services might be used for management purposes like emergency
routing, identifying near by facilties or support of mobile units>
|
|
02.7. Actuator (Regional civil protection) accesses
maps or thematic products (e.g evacuation map) via WCS or WMS <W3DS> as soon as possible, and should start to use them to manage the disaster.
|
|
N°.
|
Name
|
Desc.
|
|
06
|
Interact with Services
|
Activity of client to consume services for datasets, sensors,
models, workflows, etc
|
|
Alert results can be
demonstrated on client software by using WMS or other services (ex. WMS for monitoring results).
3D portrayal can be
used as enhanced visualizazion method
|
|
02.8 The Initiator 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 or thematic products.
Initiator informs Actuator (Civil Protection) about these feedbacks, especially about level of quality of the
available map
or thematic
product.
In case of major
quality issue, Initiator may request a new production of map and thematic
product by cycle loop
at step 02.4.
|
|
|
|
02.9 In case of availability of fresh data that may enable the production of an
up-to-date version of previously requested thematic product
the Initiator
may request to produce a new version of the thematic product
by cycle loop at step 02.4.
|
|
|
|
02.10 When disaster
management service does not need to be in activation
anymore, Actuator (Civil Protection) notifies the Initiator.
Initiator acknowledges the termination of the activation and notifies Processors (Data Provider and Map Producer).
|
|
|
|
DM-03 Post Crisis
|
|
03.1 Initiator ensure to make available all map and thematic product,
in the respect of their respective term and conditions, through WMS or <W3DS>.
Published map
and thematic product
would be used for
assessing damage by insurance company or by NGO
organization to help Public.
|
|
3D portrayal can be
used as enhanced visualizazion method
|
|
03.2 All maps and thematic product
produced are released, through WMS <or W3DS>, for public communication and accessible via mass market products in
the respect of the terms and conditions.
|
|
3D portrayal can be
used as enhanced visualizazion method
|
