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>Drought</strong> <strong>Monitoring</strong> and Water Activities within <strong>the</strong><br />

Group on Earth Observations (GEO)<br />

A. <strong>Global</strong> <strong>Drought</strong> <strong>Monitoring</strong> <strong>Service</strong> and <strong>the</strong><br />

<strong>Global</strong> <strong>Drought</strong> Community of Practice<br />

1.1 Scope of this document<br />

This is an overview and documentation of <strong>the</strong> drought monitoring service as implemented<br />

<strong>through</strong> <strong>the</strong> Group on Earth Observations System of Systems (<strong>GEOSS</strong>) and <strong>the</strong> European<br />

<strong>Drought</strong> Observatory implementation of advanced semantic search capability <strong>through</strong> <strong>the</strong><br />

Euro<strong>GEOSS</strong> Discovery Broker tools. A key deliverable is <strong>the</strong> specification of a set of tools that<br />

will access information published <strong>through</strong> a distributed water data infrastructure. The<br />

development of <strong>the</strong> specification of <strong>the</strong>se tools includes: 1) capturing user requirements <strong>through</strong><br />

expressing <strong>the</strong> GEO Water Societal Benefit Area users within a “scenario,” that is, who might<br />

use <strong>the</strong> GEO <strong>Global</strong> <strong>Drought</strong> <strong>Monitoring</strong> <strong>Service</strong> and <strong>the</strong> types of data and functionality that<br />

<strong>the</strong>se users require or expect; 2)Design of a system architecture and <strong>the</strong> enabling framework for<br />

this at <strong>the</strong> component level; 3) integration of this system architecture within <strong>the</strong> <strong>Global</strong> Earth<br />

Observation System of System (<strong>GEOSS</strong>) architecture and its components; and 4)<br />

implementation. The development efforts of <strong>the</strong> GEO <strong>Global</strong> <strong>Drought</strong> <strong>Monitoring</strong> Portal have<br />

involved multiple parties, including <strong>the</strong> Architectural Implementation Pilot (AIP) Water and<br />

<strong>Drought</strong> Working Group, <strong>through</strong> <strong>the</strong> GEO <strong>Architecture</strong> and Data Committee level; <strong>the</strong><br />

Scientific Officer for Water of <strong>the</strong> GEO Secretariat (<strong>through</strong> <strong>the</strong> <strong>Global</strong> <strong>Drought</strong> <strong>Monitoring</strong><br />

Initiative); drought task activities of <strong>the</strong> Integrated <strong>Global</strong> Water Cycle Observations (IGWCO)<br />

Community of Practice; Princeton University Land Surface Hydrology Group, USA National<br />

Integrated <strong>Drought</strong> Information System (NIDIS), <strong>the</strong> European <strong>Drought</strong> Observatory, Italian<br />

National Research Council, <strong>the</strong> Joint Research Centre, <strong>the</strong> University College of London, <strong>the</strong><br />

Technical University of Vienna, Canadian Group on Earth Observations (CGEO), Argentina<br />

Servicio Meteorologico Nacional, Australia Bureau of Agricultural and Resource Economics and<br />

Sciences (ABARES), and <strong>the</strong> Australia Bureau of Meteorology.<br />

This report is divided into two sections to increase its accessibility. The first section<br />

explains why certain portal Information Technology (IT) capabilities (“user requirements”) were<br />

selected for implementation and deployment within <strong>the</strong> global drought monitoring service. The<br />

first section deals with development of a web-based, real-time Geographic Information System<br />

GIS server with a distributed database federation, used for hydrologic alerts in drought<br />

conditions, a prototype global drought early warning system. The second section explains why<br />

certain advanced search capabilities (including “semantic” search and discovery)—again, user<br />

requirements—were developed for implementation within <strong>the</strong> European <strong>Drought</strong> Observatory<br />

and <strong>the</strong> Euro<strong>GEOSS</strong> discovery broker. These technologies can also be eventually migrated for<br />

implementation within <strong>the</strong> <strong>Global</strong> <strong>Drought</strong> <strong>Monitoring</strong> Portal (GDMP), combining with<br />

concurrent semantic components being built within <strong>the</strong> <strong>Global</strong> Earth Observation System of<br />

System <strong>through</strong> <strong>the</strong> Data Integration and Analysis System (DIAS), <strong>the</strong> Japanese Aerospace<br />

Exploration Agency (JAXA) contribution to GEO, and <strong>the</strong> Euro<strong>GEOSS</strong> European Union<br />

contribution.<br />

Page 8

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

Saved successfully!

Ooh no, something went wrong!