11.01.2013 Views

Global Drought Monitoring Service through the GEOSS Architecture ...

Global Drought Monitoring Service through the GEOSS Architecture ...

Global Drought Monitoring Service through the GEOSS Architecture ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Architectural Implementation Pilot, Phase 3 Version: 2.0<br />

<strong>Global</strong> <strong>Drought</strong> <strong>Monitoring</strong> and European <strong>Drought</strong><br />

Observatory-Water SBA Engineering Report<br />

Date: 11/Feb/2011<br />

<strong>the</strong> GDMP Scenario<br />

As noted above, a scenario is <strong>the</strong> listing, step-by-step, of <strong>the</strong> user requirements (for<br />

drought monitoring), showing which <strong>GEOSS</strong> resources and components are utilized within <strong>the</strong><br />

retrieval of drought maps and information (such as soil moisture) for users.<br />

Table 4<br />

Objective: Obtain a <strong>Drought</strong> Overview of a Given Area on <strong>the</strong> Terrestrial Earth, along with<br />

detailed information on affected regions<br />

Step 01: Obtain <strong>Drought</strong> Indices from <strong>the</strong> <strong>Global</strong> <strong>Drought</strong> Monitor<br />

Step 01.1: Obtain <strong>Drought</strong> Indices <strong>through</strong> standard services<br />

Step 01.2: A dedicated WPS processes <strong>the</strong> drought index and calculates <strong>the</strong> drought hazard<br />

Step 02: A dedicated WPS processes <strong>the</strong> drought index and calculates <strong>the</strong> drought hazard<br />

Step 02.1: The WPS retrieves <strong>the</strong> <strong>Drought</strong> Index <strong>through</strong> <strong>the</strong> WCS<br />

Step 02.2: The WPS executes <strong>the</strong> hazard detection model and, where detected, sends an alert to<br />

<strong>the</strong> decision support tool<br />

Step 03: <strong>Drought</strong> Hazard Related Information Discovery<br />

Step 03.1: The decision maker uses <strong>the</strong> decision support tool to submit a query to <strong>the</strong> augmented<br />

search component in order to discover drought hazard related information (datasets)<br />

Step 03.2: The Euro<strong>GEOSS</strong> Broker mediates <strong>the</strong> query request, distributing it to its federated<br />

services<br />

Step 03.3: The Decision maker uses <strong>the</strong> Decision Support System to select one or more drought<br />

hazard related information datasets, among <strong>the</strong> ones returned by <strong>the</strong> query<br />

Presentation of Reachable <strong>Service</strong>s and Alerts<br />

Step 03.4: The Decision Support Tool submits an access request to <strong>the</strong> Euro<strong>GEOSS</strong> Broker in<br />

order to retrieve <strong>the</strong> user-selected drought hazard information datasets<br />

Interact with <strong>Service</strong>s<br />

Step 04: Visualization and Assessment of Information<br />

Step 04.1: The Decision Support Tool displays <strong>the</strong> accessed drought hazard information datasets,<br />

combining <strong>the</strong>m with <strong>the</strong> potential hazard layer<br />

Step 04.2: The decision maker assesses <strong>the</strong> drought hazard impact<br />

4.3.1 Display of Selection Bar for <strong>Drought</strong> Indices, Processing to Derive<br />

Dehydration and <strong>Drought</strong> Severity, and <strong>Drought</strong> Map Republication<br />

The <strong>Global</strong> <strong>Drought</strong> Scenario steps, by <strong>the</strong>mselves, are relatively abstract, and are best<br />

understood by following <strong>the</strong> actual presentation given within <strong>the</strong> videos, “<strong>Drought</strong>—<strong>Global</strong>.” 31<br />

31 http://www.ogcnetwork.net/pub/ogcnetwork/<strong>GEOSS</strong>/AIP3/pages/Demo.html<br />

Page 42

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!