Global Drought Monitoring Service through the GEOSS Architecture ...
Global Drought Monitoring Service through the GEOSS Architecture ...
Global Drought Monitoring Service through the GEOSS Architecture ...
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
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 />
B Informatics Section<br />
3. Capturing User Requirements for <strong>the</strong> <strong>Global</strong> <strong>Drought</strong> Monitor and its<br />
Interoperability with <strong>the</strong> <strong>Global</strong> Earth Observation System of Systems (<strong>GEOSS</strong>)<br />
A key deliverable is <strong>the</strong> specification of a set of tools that will access information<br />
published <strong>through</strong> a distributed water data infrastructure. The tools in this case are represented<br />
by <strong>the</strong> applications which constitute <strong>the</strong> GEO <strong>Global</strong> <strong>Drought</strong> <strong>Monitoring</strong> <strong>Service</strong>. The tools are<br />
specified <strong>through</strong> completion of three phases:<br />
1). Capture of User Requirements—who might use <strong>the</strong> GEO <strong>Global</strong> <strong>Drought</strong> <strong>Monitoring</strong><br />
<strong>Service</strong> and <strong>the</strong> types of data and <strong>the</strong> types of functionality <strong>the</strong>se users might require or expect<br />
2) Design of a System <strong>Architecture</strong>—and associated enabling framework at <strong>the</strong><br />
component level<br />
3) Implementation Plan<br />
The <strong>GEOSS</strong> <strong>Architecture</strong> Implementation Pilot (AIP) task develops infrastructure<br />
components for <strong>the</strong> <strong>GEOSS</strong> Common Infrastructure (GCI) and <strong>the</strong> broader <strong>GEOSS</strong> architecture<br />
as a means of coordinating and deploying cross-disciplinary interoperability, such as <strong>the</strong> display<br />
on top of drought map layers, combined with layers of different water usage and agricultural<br />
water needs. The architectural implementation (AIP) task is envisioned as a way of developing<br />
<strong>the</strong> <strong>GEOSS</strong> informatics capability and architecture <strong>through</strong> pilot projects. The process includes<br />
user interactions; component deployment and interoperability testing; and SBA-focused<br />
demonstrations.<br />
3.1 Assessment of <strong>Drought</strong> Vulnerability and Susceptibility<br />
The first section of this report dealt with drought indicators currently utilized by <strong>the</strong><br />
drought community of practice. Indicators do not correlate well with historic drought impacts,<br />
and <strong>the</strong>y need to be correlated with vulnerability. A direct linear proportionality between <strong>the</strong><br />
severity of <strong>the</strong> drought, as expressed by a drought indicator and <strong>the</strong> observed and recorded<br />
impacts of a drought should not be expected. That is <strong>the</strong> role of <strong>the</strong> drought vulnerability factor<br />
(Iglesias and Schlickenrieder 2010). Values of indicators change with <strong>the</strong> region and social<br />
conditions.<br />
Page 30