a services oriented architecture for water resources data

55
A Services Oriented Architecture for Water Resources Data David R. Maidment Center for Research in Water Resources University of Texas at Austin

Upload: ashton

Post on 19-Mar-2016

52 views

Category:

Documents


0 download

DESCRIPTION

A Services Oriented Architecture for Water Resources Data. David R. Maidment Center for Research in Water Resources University of Texas at Austin. A Services Oriented Architecture for Water Resources Data. CUAHSI and WATERS WaterML and WaterOneFlow Hydrologic Information Server - PowerPoint PPT Presentation

TRANSCRIPT

Page 1: A Services Oriented Architecture for Water Resources Data

A Services Oriented Architecture for Water Resources Data

David R. MaidmentCenter for Research in Water Resources

University of Texas at Austin

Page 2: A Services Oriented Architecture for Water Resources Data

A Services Oriented Architecture for Water Resources Data

• CUAHSI and WATERS• WaterML and WaterOneFlow • Hydrologic Information Server• Modeling services

Page 3: A Services Oriented Architecture for Water Resources Data

A Services Oriented Architecture for Water Resources Data

• CUAHSI and WATERS• WaterML and WaterOneFlow • Hydrologic Information Server• Modeling services

Page 4: A Services Oriented Architecture for Water Resources Data

Ocean Sciences

What is CUAHSI?

• CUAHSI – Consortium of Universities for the Advancement of Hydrologic Science, Inc

• Formed in 2001 as a legal entity

• Program office in Washington (5 staff)

• NSF supports CUAHSI to develop infrastructure and services to advance hydrologic science in US universities

Earth Sciences

AtmosphericSciences

UCAR

CUAHSI

Unidata

HISNational Science Foundation

Geosciences Directorate

Page 5: A Services Oriented Architecture for Water Resources Data

CUAHSI Member Institutions

112 US Universities as of September 2007

Page 6: A Services Oriented Architecture for Water Resources Data

HISTeam

WATERSTestbed

WATERS Network Information System

NSF has funded work at 11 testbed sites, each with its own science agenda. HIS supplies the

common information system

Minnehaha Creek

Page 7: A Services Oriented Architecture for Water Resources Data

SuperComputerCenters:NCSA,TACC

Domain Sciences:

Unidata, NCARLTER, CZEN

GEON

Government:USGS, EPA,

NCDC

Industry:ESRI, Kisters,

MicrosoftCUAHSI HIS

HIS Team and its Cyberinfrastructure Partners

HIS Team:Texas, SDSC,Utah, Drexel,

Duke

Page 8: A Services Oriented Architecture for Water Resources Data

SupercomputerCenters:NCSA,TACC

Domain Sciences:

Unidata, NCARLTER, GEON

Government:USGS, EPA,

NCDC

Industry:ESRI, Kisters,

Microsoft

HISTeam

WATERSTestbed

WATERS Network Information System

CUAHSI HIS

HIS, WATERS and the CUAHSI Community

Page 9: A Services Oriented Architecture for Water Resources Data

SupercomputerCenters:NCSA,TACC

Domain Sciences:

Unidata, NCARLTER, GEON

Government:USGS, EPA,

NCDC, USDA

Industry:ESRI, Kisters,

OpenMI

HISTeam

WATERS Testbed

WATERS Network Information System

CUAHSI HIS

International Partners

CSIRO and Bureau of MeteorologyAustralian Water Resources Information System

European CommissionWater database design and model integration (OpenMI)

Page 10: A Services Oriented Architecture for Water Resources Data

HIS Goals• Hydrologic Data Access – providing better

access to a large volume of high quality hydrologic data across the nation

• Support for Observatories – integrating local observations by academic investigators with hydrologic data for a region

• Advancement of Hydrologic Science – modeling and analysis of “hydrology in a dynamic earth”

• Hydrologic Education – bringing more data into the classroom

Page 11: A Services Oriented Architecture for Water Resources Data

A Services Oriented Architecture for Water Resources Data

• CUAHSI and WATERS• WaterML and WaterOneFlow • Hydrologic Information Server• Modeling services

Page 12: A Services Oriented Architecture for Water Resources Data

DefinitionThe CUAHSI Hydrologic Information System (HIS) is a geographically distributed network of data sources and functions that are integrated using web services so that they operate as a connected whole.

Page 13: A Services Oriented Architecture for Water Resources Data

Services Oriented Architecture• Service-oriented Architecture (SOA) is an

architectural design pattern that concerns itself with defining loosely-coupled relationships between producers and consumers.

• A major focus of Web services is to make functional building blocks accessible over standard Internet protocols that are independent from platforms and programming languages.

• The Web Services Description Language (WSDL, pronounced 'wiz-dəl' or spelled out, 'W-S-D-L') is an XML-based language that provides a model for describing Web services.

(from Wikipedia)

Defined by the World Wide Web Consortium (W3C)

Page 14: A Services Oriented Architecture for Water Resources Data

Web Pages and Web Serviceshttp://www.safl.umn.edu/ http://his.safl.umn.edu/SAFLMC/cuahsi_1_0.asmx?

Uses Hypertext Markup Language (HTML)Uses WaterML

(an eXtended Markup Language for water data)

Page 15: A Services Oriented Architecture for Water Resources Data

Rainfall & SnowWater quantity

and quality

Remote sensing

Water Data

Modeling Meteorology

Soil water

Page 16: A Services Oriented Architecture for Water Resources Data

Water Data Web Sites

Page 17: A Services Oriented Architecture for Water Resources Data

NWISWeb site output# agency_cd Agency Code# site_no USGS station number# dv_dt date of daily mean streamflow# dv_va daily mean streamflow value, in cubic-feet per-second# dv_cd daily mean streamflow value qualification code## Sites in this file include:# USGS 02087500 NEUSE RIVER NEAR CLAYTON, NC#agency_cd site_no dv_dt dv_va dv_cdUSGS 02087500 2003-09-01 1190USGS 02087500 2003-09-02 649USGS 02087500 2003-09-03 525USGS 02087500 2003-09-04 486USGS 02087500 2003-09-05 733USGS 02087500 2003-09-06 585USGS 02087500 2003-09-07 485USGS 02087500 2003-09-08 463USGS 02087500 2003-09-09 673USGS 02087500 2003-09-10 517USGS 02087500 2003-09-11 454

Time series of streamflow at a gaging station

USGS has committedto supporting CUAHSI’sGetValues function

Page 18: A Services Oriented Architecture for Water Resources Data

Observation Stations

Ameriflux Towers (NASA & DOE) NOAA Automated Surface Observing System

USGS National Water Information System NOAA Climate Reference Network

Map for the US

Page 19: A Services Oriented Architecture for Water Resources Data

Water Quality Measurement Sites in EPA Storet

Substantial variation in data availability from states

Data from Bora Beran, Drexel University

Page 20: A Services Oriented Architecture for Water Resources Data

Water Quality Measurement Sites from Texas Commission for Environmental Quality (TCEQ)

Page 21: A Services Oriented Architecture for Water Resources Data

Geographic Integration of Storet and TCEQ Data in HIS

Page 22: A Services Oriented Architecture for Water Resources Data

Observations CatalogSpecifies what variables are measured at each site, over what time interval,

and how many observations of each variable are available

Page 23: A Services Oriented Architecture for Water Resources Data

Point Observations Information ModelData Source

Network

Sites

Variables

Values{Value, Time, Qualifier, Offset}

USGS

Streamflow gages

Neuse River near Clayton, NC

Discharge, stage (Daily or instantaneous)

206 cfs, 13 August 2006• A data source operates an observation network• A network is a set of observation sites• A site is a point location where one or more variables are measured• A variable is a property describing the flow or quality of water• A value is an observation of a variable at a particular time• A qualifier is a symbol that provides additional information about the value• An offset allows specification of measurements at various depths in water

http://www.cuahsi.org/his/webservices.html

GetSites

GetSiteInfo

GetVariables

GetVariableInfo

GetValues

Page 24: A Services Oriented Architecture for Water Resources Data

Locations

Variable Codes

Date Ranges

WaterML and WaterOneFlow

GetSiteInfoGetVariableInfoGetValues

WaterOneFlowWeb Service

Client

STORET

NAMNWIS

DataRepositories

Data

DataData

EXTRACTTRANSFORMLOAD

WaterML

WaterML is an XML language for communicating water dataWaterOneFlow is a set of web services based on WaterML

Page 25: A Services Oriented Architecture for Water Resources Data

WaterOneFlow• Set of query functions • Returns data in WaterML

Page 26: A Services Oriented Architecture for Water Resources Data

NWISNWIS

ArcGISArcGIS

ExcelExcel

NCARNCAR

UnidataUnidata

NASANASAStoretStoret

NCDCNCDC

AmerifluxAmeriflux

MatlabMatlabAccessAccess JavaJava

FortranFortran

Visual BasicVisual Basic

C/C++C/C++

Some operational services

CUAHSI Web ServicesCUAHSI Web Services

Data SourcesData Sources

ApplicationsApplications

Extract

Transform

Load

http://www.cuahsi.org/his/

Page 27: A Services Oriented Architecture for Water Resources Data

GetValues for Dissolved Oxygenat Minnehaha Creek

http://his.safl.umn.edu/SAFLMC/cuahsi_1_0.asmx?WSDL

Page 28: A Services Oriented Architecture for Water Resources Data

A Services Oriented Architecture for Water Resources Data

• CUAHSI and WATERS• WaterML and WaterOneFlow • Hydrologic Information Server• Modeling services

Page 29: A Services Oriented Architecture for Water Resources Data

Hydrologic Information Server• Supports data discovery,

delivery and publication– Data discovery – how do I

find the data I want?• Map interface and

observations catalogs• Metadata based Search

– Data delivery – how do I acquire the data I want?

• Use web services or retrieve from local database

– Data Publication – how do I publish my observation data?

• Use Observations Data Model

Page 30: A Services Oriented Architecture for Water Resources Data

Water Resource Regions and HUC’s

Page 31: A Services Oriented Architecture for Water Resources Data

National Hydrography Dataset

Page 32: A Services Oriented Architecture for Water Resources Data

NHDPlus for Region 17E

Page 33: A Services Oriented Architecture for Water Resources Data

NHDPlus Reach Catchments ~ 3km2

About 1000 reach catchments in each 8-digit HUC

Average reach length = 2km 2.3 million reaches for continental US

Page 34: A Services Oriented Architecture for Water Resources Data

Reach Attributes

• Slope• Elevation• Mean annual flow

– Corresponding velocity• Drainage area• % of upstream

drainage area in different land uses

• Stream order

Page 35: A Services Oriented Architecture for Water Resources Data

Observations CatalogSpecifies what variables are measured at each site, over what time interval,

and how many observations of each variable are available

Page 36: A Services Oriented Architecture for Water Resources Data

Hydrologic Information Server

Microsoft SQLServer Relational Database

Observations Data Geospatial Data

GetSites

GetSiteInfo

GetVariables

GetVariableInfo

GetValues

DASH – data access system for hydrologyWaterOneFlow services

ArcGIS Server

Page 37: A Services Oriented Architecture for Water Resources Data

Minnehaha Creek Experimental Sitehttp://his.safl.umn.edu/DASH/

Page 38: A Services Oriented Architecture for Water Resources Data

Water Temperature (°C)

Dissolved Oxygen (mg/L) Depth (m)

Dissolved Oxygen (% saturation)

Page 39: A Services Oriented Architecture for Water Resources Data

Data Heterogeneity

• Syntactic mediation– Heterogeneity of

format– Use WaterML to get

data into the same format

• Semantic mediation– Heterogeneity of meaning– Each water data source

uses its own vocabulary– Match these up with a

common controlled vocabulary

– Make standard scientific data queries and have these automatically translated into specific queries on each data source

Page 40: A Services Oriented Architecture for Water Resources Data

• Search multiple heterogeneous data sources simultaneously regardless of semantic or structural differences between them

Objective

NWIS

NARR

NAWQANAM-12

request

request

request

request

request

requestrequest

request

request

return

return

return

return

return

returnreturn

return

return

What we are doing now …..

Michael PiaseckiDrexel University

Page 41: A Services Oriented Architecture for Water Resources Data

Semantic MediatorWhat we would like to do …..

NWIS

NAWQA

NARR

generic request

GetValues

GetValues

GetValues

GetValues

GetValues

GetValuesGetValues

GetValues

GetValues HODM

Michael PiaseckiDrexel University

Page 42: A Services Oriented Architecture for Water Resources Data

Hydroseekhttp://www.hydroseek.org

Supports search by location and type of data across multiple observation networks including NWIS and Storet

Page 43: A Services Oriented Architecture for Water Resources Data

A Services Oriented Architecture for Water Resources Data

• CUAHSI and WATERS• WaterML and WaterOneFlow • Hydrologic Information Server• Modeling services

Page 44: A Services Oriented Architecture for Water Resources Data

• Project sponsored by the European Commission to promote integration of water models within the Water Framework Directive

• Software standards for model linking• Uses model core as an “engine”• http://www.openMI.org

Page 45: A Services Oriented Architecture for Water Resources Data

OpenMI Conceptual Framework

VALUES

All values are referenced in a what-where-when framework, allowing different data resources or models to communicate data

Space, L

Time, T

Variables, V

D

An application of the data cube to integrate simulation modelsJon Goodall, Duke University

Page 46: A Services Oriented Architecture for Water Resources Data

Typical model architectureApplication

User interface + engineEngine

Simulates a process – flow in a channelAccepts inputProvides output

ModelAn engine set up to represent a particular location e.g. a reach of the Thames

Engine

Output data

Input data

Model application

Run

Write

Write

Read

User interface

Page 47: A Services Oriented Architecture for Water Resources Data

Accepts Provides

Rainfall(mm)

Runoff(m3/s)

Temperature(Deg C)

Evaporation(mm)

Accepts Provides

Upstream Inflow(m3/s)

Outflow(m3/s)

Lateral inflow(m3/s)

Abstractions(m3/s)

Discharges(m3/s)

River Model

Linking modelled quantities

Rainfall Runoff Model

Page 48: A Services Oriented Architecture for Water Resources Data

Data transfer at run time

Rainfall runoff

Output data

Input data

User interface

River

Output data

Input data

User interface

GetValues(..)

Page 49: A Services Oriented Architecture for Water Resources Data

Models for the processes

River(InfoWorks RS)

Rainfall(database)

Sewer(Mouse)

RR(Sobek-Rainfall

-Runoff)

Page 50: A Services Oriented Architecture for Water Resources Data

Data exchange3 Rainfall.GetValues

River(InfoWorks-RS)

Rainfall(database)

Sewer(Mouse)

2 RR.GetValues

7 RR.GetValues

RR(Sobek-Rainfall

-Runoff)

1 Trigger.GetValues

6 Sewer.GetValues

call

data

4

5 8

9

Page 51: A Services Oriented Architecture for Water Resources Data

Coupling the HIS with Models using OpenMI

ODM

ObservationsData Model

WaterOneFlow Web Services

Water Markup Language

WOF WaterML

MODFLOW HEC-RAS Others

OpenMI

SWATHSFP“academic models”

Page 52: A Services Oriented Architecture for Water Resources Data

Linking the HIS with HEC-RAS via OpenMI

HIS WaterOneFlow Web Service forNWIS Realtime

Streamflow

A HEC-RAS Model

Workflow “trigger”

Using real-time streamflow from the HIS as a boundary condition for a HEC-RAS simulation.

Page 53: A Services Oriented Architecture for Water Resources Data

SOAP-based Web Service for Models

HEC-RAS

USGSNWIS

WSDL

WSDLSimulation Model

Database

OpenMI Workflow

In an effort to build cyberinfrastructure for the hydrologic sciences, we are extending OpenMI to utilize models as web services.

Page 54: A Services Oriented Architecture for Water Resources Data

Extending OpenMI for Distributed Computing

Connects to remote database via web

services

Connects to remote model via web services

Goal: To allow a modeler to create a workflow from OpenMI components that wrap web services.

Model linkage designed on client machine

Page 55: A Services Oriented Architecture for Water Resources Data

Conclusion

The CUAHSI Hydrologic Information System (HIS) is a geographically distributed network of hydrologic data sources and functions that are integrated using web services so that they function as a connected whole.

For more information: http://www.cuahsi.org/his.html