Transcript Slide 1

Publishing Observations Data:
from ODM to HIS Central
Hydrologic Information System Service Oriented Architecture
Deployment to test beds
Customizable
web interface
(DASH)
Global search (Hydroseek)
Other popular online
clients
HTML - XML
Desktop clients
Data publishing
Streaming Data
Loading
Ontology tagging
(Hydrotagger)
Server config
tools
WSDL and ODM
registration
ETL services
Controlled
vocabularies
HIS Lite
Servers
Ontology
ODMTools
Metadata
catalogs
ODM DataLoader
WaterOneFlow Web
Services, WaterML
WSDL - SOAP
Test bed HIS
Servers
ArcGIS
Matlab
IDL
MapWindow
Excel
Central HIS
servers
External data
providers
Programming
(Fortran, C, VB)
Modeling
(OpenMI)
Hydrologic Information Server
WaterOneFlow services
DASH – data access system for hydrology
GetSites
GetSiteInfo
GetVariableInfo
GetValues
ArcGIS Server
Observations Data & Catalogs
Geospatial Data
Microsoft SQLServer Relational Database
WORKGROUP
HIS
SERVER
ORGANIZATION
STEPS FOR
REGISTERING
OBSERVATION
DATA
DASH Web Application
6
Web Configuration file
MXD
Stores information about registered networks
Stores information about layers
5
4
Spatial store
WOF services
NWIS-IID WS
NWIS-DV WS
1
. . . More synced layers
BearRiver
2
Web services from a
common template
BearRiver points
TCEQ
More WS from
ODM-WS template
My new
WS
ODM
DataLoader
TCEQ points
STORET
BearRiver WS
...
STORET points
ASOS
TCEQ WS
TCEQ
ASOS points
NWIS-DV
STORET WS
EPA
NWIS-DV points
NWIS-IID
ASOS WS
NCDC
NWIS-IID points
SQL Server
USGS
. . . More databases
My new ODM
My new
points
3
ODMs and catalogs.
All instances
exposed as ODM (i.e.
have standard ODM tables or views:
Sites, Variables, SeriesCatalog, etc.)
Geodatabase
or collection
of shapefiles
or both
Background
layers
(can be in the same
or separate
spatial store)
New network registration steps
(if you publish in HIS Appliance)
1
2
3
4
5
6
7
Using the ODM DataLoader or other, load your data into a
blank ODM instance (this will create all ODM tables that
HIS relies on)
Copy Web Services template to a new folder, edit the
template web.config file to point to the new ODM, test to
make sure the new service works as expected
Create a point layer (a feature class in GDB, or a shapefile)
from the new ODM’s Sites table using the GetSitesTool.
Add the point layer to the MXD document, specify
symbology, scale-dependent rendering, etc.
Add information about the new ODM, the associated web
service, and the associated point layer, to HIS
configuration file (see the first slide for the exact content)
Restart the HIS service
Register and test the new service at the HIS Central:
http://hiscentral.cuahsi.org/
New network registration steps
(if you publish in HIS Central)
1
2
Using the ODM DataLoader or other, load your data into a
blank ODM instance (this will create all ODM tables that
HIS relies on)
Copy Web Services template to a new folder, edit the
template web.config file to point to the new ODM, test to
make sure the new service works as expected
3
Prepare service abstract, citation, symbology
4
Register and test the new service at the HIS Central:
http://hiscentral.cuahsi.org/
5
Service is harvested
6
Tag your variables to the CUAHSI ontology
Water Data Services
• Set of query functions
• Returns data in WaterML
NWIS Daily Values (discharge), NWIS Ground Water,
NWIS Unit Values (real time), NWIS Instantaneous
Irregular Data, EPA STORET, NCDC ASOS, DAYMET,
MODIS, NAM12K, USGS SNOTEL, ODM (multiple sites)
WaterML design principles
• Driven largely by hydrologists; the goal is to capture
semantics of hydrologic observations discovery and retrieval
• Relies to a large extent on the information model as in ODM
(Observations Data Model), and terms are aligned as much
as possible
– Several community reviews since 2005
• Driven by data served by USGS NWIS, EPA STORET,
multiple individual PI-collected observations
• Is no more than an exchange schema for CUAHSI web
services
• The least barrier for adoption by hydrologists
• A fairly simple and rigid schema tuned to the current
implementation
• Conformance with OGC specs not in the initial scope – but
working with OGC on this
WaterML Overview
Method:GetSites
•Returns a list of sites, without series information
Method:GetValues
•Returns a list of data values for a single site and
single variable
Method GetSiteInfo
•Returns a single site with series information
Method: GetVariableInfo
•Returns one or more variables
Method:GetValuesObject WaterML TimeSeriesResponse
Generic OD Web Service Demo
One Data Source
► Use the MSI Installer
► Single database
Multiple Data Sources
► Use zip file
► Install “Web Application”
for each data source
• Need to know
•Brief Code that will be used to identify your data source
•Database connection string
Central
HIS
Data
Services
Catalog
► http://hiscentral.cuahsi.org
Metadata Catalog
Road Ahead








Publish and document Hydroseek web services to provide an
open API to the metadata catalog
Add service logging and reporting so contributors will know how
often their services are being utilized
Use OLAP technologies with the metadata catalog to allow users
to better visualize and explore the metadata catalog
Ability to upload ODM databases
Registration of additional data types beyond observation data as
they are incorporated into CUAHSI HIS
Add feedback mechanism to allow clients to annotate services.
Many more minor enhancements slated. Your feedback is
welcome.
Development continues…
CUAHSI HIS as a mediator across
multiple agency and PI data
– Maintains integrated metadata catalog and
services registry
– Keeps identifiers for sites, variables, etc. across
observation networks
– Manages and publishes controlled vocabularies,
and provides vocabulary/ontology management
and update tools
– Provides common structural definitions for data
interchange
– Provides a sample protocol implementation
– Governance framework: a consortium of
universities, MOUs with federal agencies,
collaboration with key commercial partners, NSF
support for core development and test beds