publishing observations data: from odm to his central
TRANSCRIPT
Publishing Observations Data:from ODM to HIS Central
Test bed HISServers
Central HIS servers
ArcGIS
Matlab
IDL
MapWindow
Excel
Programming (Fortran, C, VB)
Desktop clients
Customizable web interface (DASH)
HTML - XMLW
SD
L - SO
AP
Hydrologic Information System Service Oriented Architecture
Modeling (OpenMI)
Global search (Hydroseek)
WaterOneFlow Web Services, WaterML
HIS LiteServers
External data providers
Deployment to test beds
Other popular online clients
ODM DataLoader
Streaming Data Loading
Ontology tagging (Hydrotagger)
WSDL and ODM registration
Data publishing
ODMTools
Server config tools
Hydrologic Information Server
Microsoft SQLServer Relational Database
Observations Data & Catalogs Geospatial Data
GetSites
GetSiteInfo
GetVariableInfo
GetValues
DASH – data access system for hydrologyWaterOneFlow services
ArcGIS Server
SQL Server
ODMs and catalogs. All instancesexposed as ODM (i.e. have standard ODM tables or views: Sites, Variables, SeriesCatalog, etc.)
NWIS-IID
NWIS-DV
ASOS
STORET
TCEQ
BearRiver
. . .
Spatial store
Geodatabase or collection of shapefilesor both
NWIS-IID points
NWIS-DV points
ASOS points
STORET points
TCEQ points
BearRiver points
. . .
My new ODM
My new points
More databases
More synced layers
DASH Web Application
Background layers
(can be in the same or separate spatial store)
WOF services
Web services from a common template
NWIS-IID WS
NWIS-DV WS
ASOS WS
STORET WS
TCEQ WS
BearRiver WS
. . .My new WS
More WS fromODM-WS template
USGS
NCDC
EPA
TCEQ
Web Configuration fileStores information about registered networks
MXDStores information about layers
WSDLs
, web
serv
ice U
RLs Connection
strings
Layer info,
symbology, etc.
ODMDataLoader
2
6
5
3
1
4
WORKGROUPHISSERVERORGANIZATION
STEPS FORREGISTERINGOBSERVATIO
NDATA
New network registration steps (if you publish in HIS Appliance)
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 serviceRegister and test the new service at the HIS Central:
http://hiscentral.cuahsi.org/6
5
4
3
2
1
7
New network registration steps (if you publish in HIS Central)
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
Prepare service abstract, citation, symbology
Register and test the new service at the HIS Central: http://hiscentral.cuahsi.org/
Service is harvested
Tag your variables to the CUAHSI ontology
4
3
2
1
5
6
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: GetVariableInfo•Returns one or more variables
Method:GetValues•Returns a list of data values for a single site and single variable
Method:GetSites•Returns a list of sites, without series informationMethod GetSiteInfo•Returns a single site with series information
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
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