Global Drought Monitoring Service through the GEOSS Architecture ...

More documents

Recommendations

Info

Architectural Implementation Pilot, Phase 3 Version: 2.0 Global Drought Monitoring and European Drought Observatory-Water SBA Engineering Report Date: 11/Feb/2011 B Informatics Section 3. Capturing User Requirements for the Global Drought Monitor and its Interoperability with the Global Earth Observation System of Systems (GEOSS) A key deliverable is the specification of a set of tools that will access information published through a distributed water data infrastructure. The tools in this case are represented by the applications which constitute the GEO Global Drought Monitoring Service. The tools are specified through completion of three phases: 1). Capture of User Requirements—who might use the GEO Global Drought Monitoring Service and the types of data and the types of functionality these users might require or expect 2) Design of a System Architecture—and associated enabling framework at the component level 3) Implementation Plan The GEOSS Architecture Implementation Pilot (AIP) task develops infrastructure components for the GEOSS Common Infrastructure (GCI) and the broader GEOSS architecture as a means of coordinating and deploying cross-disciplinary interoperability, such as the display on top of drought map layers, combined with layers of different water usage and agricultural water needs. The architectural implementation (AIP) task is envisioned as a way of developing the GEOSS informatics capability and architecture through pilot projects. The process includes user interactions; component deployment and interoperability testing; and SBA-focused demonstrations. 3.1 Assessment of Drought Vulnerability and Susceptibility The first section of this report dealt with drought indicators currently utilized by the drought community of practice. Indicators do not correlate well with historic drought impacts, and they need to be correlated with vulnerability. A direct linear proportionality between the severity of the drought, as expressed by a drought indicator and the observed and recorded impacts of a drought should not be expected. That is the role of the drought vulnerability factor (Iglesias and Schlickenrieder 2010). Values of indicators change with the region and social conditions. Page 30
Architectural Implementation Pilot, Phase 3 Version: 2.0 Global Drought Monitoring and European Drought Observatory-Water SBA Engineering Report Date: 11/Feb/2011 The same level of drought severity can cause a wide variety of drought impacts due to different underlying vulnerability of different regions. The multiple disciplinary information sources that assist decision makers in evaluating drought impacts include information on regional infrastructures, land use, residential water use, etc, which either are impacted by drought or may mitigate drought severity (such as groundwater availability). Land use information (forage for pasture animals in agricultural lands), crop type information with crop growing seasons, power plant locations (for identifying cooling water requirements), groundwater springs (to identify area of groundwater export) are all different types of data that can be combined together as “layers” within a Geographical Information System. The display of layers, one type of information on top of other layers, is the basis for the integration of multi-disciplinary information. Several types of multi-disciplinary data integration exist, and several tools were explored through testing for deployment for regional and global drought monitoring. 3.2 Capturing User Requirements and Implementation of Architecture to Design of the Global Drought Monitor 3.2.1 Portal Requirements: Drill-down capability Both the European Drought Observatory and the US NIDIS drought monitoring system portals support “drill down” capability from continental to national scale and from national scale to river basin scale. The spatial resolution of the drought maps are progressively higher, moving from global scale to continental scale to national scale and finally to river basin scale. This is not simply a matter of display preference, since a drought early warning system should be developed for local scales, particularly in the case of small-scale agricultural plots. Although existing national drought monitoring coverage (at its existing resolution) is incorporated into the GDMP, the GDMP is not simply the assembly of a collection of web page graphics into one location. 3.2.2 Top-down versus bottom-up Design There are several possible candidates for designing a global drought monitoring service: 1) a single, top-down system at coarse resolution; or 2) a single, top-down system at fine resolution; 3) a bottom-up system, or 4) a bottom-up system complemented with some top-down coverage where coverage is lacking. One example of a top-down global drought monitor is the University of College London Global Drought Monitor. 21 Another is the Beijing Climate Center Drought Monitor. 22 21 http://drought.mssl.ucl.ac.uk/drought.html?map=%2Fwww%2Fdrought%2Fweb_pag es%2Fdrought.map&program=%2Fcgibin%2Fmapserv&root=%2Fwww%2Fdrought2%2F&map_web_imagepath=%2Ftmp %2F&map_web_imageurl=%2Ftmp%2F&map_web_template=%2Fdrought.html 22 http://bcc.cma.gov.cn/Website/index.php?ChannelID=82&show_product=1 Page 31
Page 1 and 2: Global Drought Monitoring Service t
Page 3 and 4: Architectural Implementation Pilot,
Page 29: Architectural Implementation Pilot,

Global Drought Monitoring Service through the GEOSS Architecture ...

Create successful ePaper yourself

Delete template?

Save as template?