1 / 22

Jeffery S. Horsburgh

Linking HIS and GIS How to support the objective, transparent and robust calculation and publication of SWSI?. Jeffery S. Horsburgh. CUAHSI HIS Sharing hydrologic data. Combining GIS and HIS Demo Dynamic Display of Water Temperature. Physical Implementation. ArcMap Documents.

meira
Download Presentation

Jeffery S. Horsburgh

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Linking HIS and GISHow to support the objective, transparent and robust calculation and publication of SWSI? Jeffery S. Horsburgh CUAHSI HIS Sharing hydrologic data

  2. Combining GIS and HIS DemoDynamic Display of Water Temperature

  3. Physical Implementation ArcMap Documents CUAHSI HIS Server ODM SQL Server View Sensor Network ODM Streaming Data Loader Streaming Data Server

  4. NWIS Potential SWSI System Architecture HIS Server • Data Products and Services • Web Map Based Display of SWSI • WaterOneFlow Web Service(s) for inputs and outputs • GIS Data Services • WMS, WFS, WCS • Digital Watershed • SWSI Results ODM Digital Watershed NHD Plus GetSites GetSiteInfo GetVariableInfo GetValues WaterML HIS Data Services WaterML WaterOneFlow Web Service SNOTEL Data Processing and SWSI Calculation NOAA-NCDC/NWS ASOS

  5. NWIS Potential SWSI System Architecture HIS Server • Data Products and Services • Web Map Based Display of SWSI • WaterOneFlow Web Service(s) for inputs and outputs • GIS Data Services • WMS, WFS, WCS • Digital Watershed • SWSI Results ODM Digital Watershed NHD Plus GetSites GetSiteInfo GetVariableInfo GetValues WaterML HIS Data Services WaterML WaterOneFlow Web Service SNOTEL Data Processing and Index Calculation NOAA-NCDC/NWS ASOS

  6. A Digital Watershed connects geospatial and temporal water resources data Digital Watershed Streamflow NHDPlus Weather Slide from David Maidment

  7. Digital Watershed for Space-Time Data • Conceptual basis/data model for integrating: • Spatial data (watersheds, streams, reservoirs, monitoring sites) NHD Plus • Observations data (streamflow, snowpack, reservoir storage) CUAHSI HIS Data Services • Modeling (creation of space-time datasets)  SWSI Calculation • Tools (visualization and analysis) • Critical infrastructure role as a bridge or framework Digital Watershed Data Retrieval and Management Analysis, Modeling, and Visualization

  8. Digital Representation of WatershedsLinking Observations with Hydrologic Objects • Digital watershed = a structured collection of hydrologic objects (e.g., watersheds, stream reaches, reservoirs, monitoring sites, etc.) on which measurements are made • The relationships between the objects provide the context to facilitate integrated modeling and analysis • NHD Plus is one basis for a digital watershed • Relationships between important hydrologic objects are expressed • CUAHSI HIS provides access to measurements that characterize the hydrologic objects

  9. Digital WatershedDiscrete Space-Time Data Model Time, TSDateTime TSValue Space, FeatureID Variables, TSTypeID Slide From David Maidment

  10. Digital Watershed Services • Once populated, a digital watershed can support: • Data access services • Data retrieval for hydrologic objects (catchments, gages, etc.) • Data analysis/manipulation services • Statistical analyses • Computational/modeling services • Spatial analyses, workflows, models • Presentation services • Map generation, data visualization

  11. NWIS Potential SWSI System Architecture HIS Server • Data Products and Services • Web Map Based Display of SWSI • WaterOneFlow Web Service(s) for inputs and outputs • GIS Data Services • WMS, WFS, WCS • Digital Watershed • SWSI Results ODM Digital Watershed NHD Plus GetSites GetSiteInfo GetVariableInfo GetValues WaterML HIS Data Services WaterML WaterOneFlow Web Service SNOTEL Data Processing and SWSI Calculation NOAA-NCDC/NWS ASOS

  12. HIS Server • Technology/software for serving data • Storage • Loading • Analysis • Publication • Primarily uses free CUAHSI HIS Software • Commercial software packages include: • ESRI ArcGIS Server – publication of spatial datasets • Microsoft SQL Server – publication of observation datasets

  13. HIS Server Internet Data Presentation Point Observations Data ODM Database GetSites GetSiteInfo GetVariableInfo GetValues GIS Data Model Output WaterML WaterOneFlow Web Service Data discovery, visualization, and analysis through Internet enabled applications

  14. NWIS Potential SWSI System Architecture HIS Server • Data Products and Services • Web Map Based Display of SWSI • WaterOneFlow Web Service(s) for inputs and outputs • GIS Data Services (WMS, WFS, WCS) ODM Digital Watershed NHD Plus GetSites GetSiteInfo GetVariableInfo GetValues WaterML HIS Data Services WaterML WaterOneFlow Web Service SNOTEL Data Processing and SWSI Calculation NOAA-NCDC/NWS ASOS

  15. CUAHSI WaterOneFlow Web Services“Getting the Browser Out of the Way” GetSites GetSiteInfo GetVariableInfo GetValues Standard protocols provide platform independent data access WaterML SQL Queries Data Consumer ODM Database Query Response

  16. NWIS Potential SWSI System Architecture HIS Server • Data Products and Services • Web Map Based Display of SWSI • WaterOneFlow Web Service(s) for inputs and outputs • GIS Data Services (WMS, WFS, WCS) ODM Digital Watershed NHD Plus GetSites GetSiteInfo GetVariableInfo GetValues WaterML HIS Data Services WaterML WaterOneFlow Web Service SNOTEL Data Processing and SWSI Calculation NOAA-NCDC/NWS ASOS

  17. Data Processing and SWSI Calculation • Processed/aggregated data (SWSI inputs) stored in the digital watershed • Enables multiple users to access the same data • Hydrologic connectivity of the digital watershed enables us to expose specific inputs underlying SWSI for each watershed • Which gages are used? • Which SNOTEL Sites are within the watershed? • Precipitation sites?

  18. NWIS Potential SWSI System Architecture HIS Server • Data Products and Services • Web Map Based Display of SWSI • WaterOneFlow Web Service(s) for inputs and outputs • GIS Data Services (WMS, WFS, WCS) ODM Digital Watershed NHD Plus GetSites GetSiteInfo GetVariableInfo GetValues WaterML HIS Data Services WaterML WaterOneFlow Web Service SNOTEL Data Processing and SWSI Calculation NOAA-NCDC/NWS ASOS

  19. Potential Data Products and Services • HIS Server Publication of SWSI • ODM Database to store SWSI • Input data used to calculate SWSI • Calculated SWSI values • Published Digital Watershed • WaterML based Web Services for: • Calculated SWSI Values • Inputs used in SWSI calculations • Web Map/Feature/Raster geospatial data services • Map based display of SWSI • Internet map application that presents visualizations • Time Series Analyst display of SWSI time series

  20. Desktop Hydrologic Information System Interactive Definition/Calculation of Custom SWSI Values HIS Server HIS Desktop User-Defined Custom SWSI Digital Watershed GIS Data Services SWSI Values Observations Observation Services

  21. Needs • Robust web services for input datasets • Ensure completeness of existing services (USGS NWIS, NRCS SNOTEL, NCDC, etc.) • Decide how to get data with no Web Services – e.g., reservoir storage • Precise specification of the SWSI calculation process • Inputs • Methods, parameters, weights, etc. • Outputs

  22. Questions for Discussion • How automated should the SWSI calculation be? • How to handle datasets for which no WaterOneFlow Web Services exist (reservoir storage)? • How to handle updates to SWSI calculations that are initially based on provisional data? • Data access and publication agreements/restrictions. • Is it important that the system expose all assumptions and input data (objective calculations)? • How do we make the system objective, transparent, and robust? • What are the requirements for custom SWSI calculation and display?

More Related