CUAHSI Hydrologic Information System Status Review, July 28, 2004 PowerPoint PPT Presentation

presentation player overlay
1 / 57
About This Presentation
Transcript and Presenter's Notes

Title: CUAHSI Hydrologic Information System Status Review, July 28, 2004


1
CUAHSI Hydrologic Information SystemStatus
Review, July 28, 2004
2
Agenda
  • Review the work of the five project partners
  • CUAHSI (Rick Hooper, Jon Duncan)
  • San Diego Supercomputer Center (John Helly, .)
  • University of Texas (David Maidment, )
  • University of Illinois (Praveen Kumar .)
  • Drexel University (Michael Piasecki)
  • Involving the collaborators V. Lakshmi, X.
    Liang, Y. Liang, U. Lall, L. Poff, K. Reckhow, D.
    Tarboton, I. Zaslavsky, C. Zheng
  • HIS review meetings
  • SDSC (August 12-13) technical detail
  • Logan (August 23) user needs assessment

3
Agenda
  • Review the work of the five project partners
  • CUAHSI (Rick Hooper, Jon Duncan) meeting with
    NSF today
  • San Diego Supercomputer Center (John Helly, .)
  • University of Texas (David Maidment, )
  • University of Illinois (Praveen Kumar,...)
  • Drexel University (Michael Piasecki,)

4
Agenda
  • Review the work of the five project partners
  • CUAHSI (Rick Hooper, Jon Duncan) Neuse HO
    report status
  • San Diego Supercomputer Center (John Helly, .)
  • University of Texas (David Maidment, )
  • University of Illinois (Praveen Kumar .)
  • Drexel University (Michael Piasecki)

5
Agenda
  • Review the work of the five project partners
  • CUAHSI (Rick Hooper, Jon Duncan) Neuse HO
    report status
  • San Diego Supercomputer Center (John Helly, .)
  • University of Texas (David Maidment, )
  • University of Illinois (Praveen Kumar .)
  • Drexel University (Michael Piasecki)

6
UT Update
  • General issues
  • Landscape characterization for HO Design
  • Flux algebra for surface water systems
  • XML for interchange of groundwater objects

7
Science Tools Corporation
  • http//sciencetools.com/
  • work with NASA and other institutions integrating
    databases for scientific purposes
  • Chief Scientist is Richard Troy he wants to
    explore potential of working with CUAHSI
  • Commercial system that operates over Oracle,
    SQL/Server,
  • Company is based in Oakland, CA

8
GenScn
  • A tool for generation and analysis of model
    simulation scenarios for watersheds
  • Incorporated in EPA Basins system
  • Produced by AquaTerra in Decatur, GA
  • Handles lots of different time series types

9
Suwannee River Watershed Data
  • Contact from Wendy Graham (former Vice-Chair of
    HIS Committee)
  • Offering data for consideration in HIS data model
  • How to discuss this in Logan?

10
UT Update
  • General issues
  • Landscape characterization for HO Design
  • Flux algebra for surface water systems
  • XML for interchange of groundwater objects

11
Landscape Characterization for HO Design
  • Idea suggested by Larry Band at the end of our
    call on July 14
  • have a set of rules for defining subdivisions of
    the landscape using orders of magnitude of
    catchment size, type of land use, etc
  • need to work with LIDAR as well as regular DEM
  • define points at outlets of these catchments as
    potential gage sites

12
EDNA-Elevation Derivatives for National
Application
13
Pfaffstetter Basins
9 basins divided into 99 basins divided into 999
basins
14
Email from Larry Band
In this case the emphasisis on first retrieving
all catchments of a certain size (or range of gt
sizes) developed by specifying threshold areas or
perhaps other gt criteria for identifying first
order catchments. Likely this would gt actually
be area as we are less interested in knowing
precisely where gt channelized flow begins as
identifying characteristics of catchments gt of
specified drainage areas. In response to a set
of scientific gt questions or hypotheses dealing
with scaling issues, we may specify we gt need to
gauge X streams for each of 5 orders of magnitude
of drainage gt area that satisfy a set of
selection criteria. You're correct that gt the
procedure would select the set of candidate
sites, from which a gt final set would need to be
chosen. gt gt The rules can be quite simple, such
as 1. all catchments with gt 20 gt impervious
cover (assuming we have an impervious surface
layer), or gt more complex such as 2. all
catchments with gt 80 forest in a gt specified
riparian buffer. It could also include
topographic gt characteristics including extent
and development of floodplain using gt some of
the indices John Gallant has recently introduced.
You're also gt correct that this can be a
complex problem specifically with lidar gt data
due to the size of the dataset and also the lack
of elevation gt data in open water, and the
potential apparent drainage disruption due gt to
infrastructure. My impression is that most or at
least many gt hydrologists who can carry out this
type of activity with standard USGS DEM would
have difficulty gt handling the lidar data.
Most software packages cannot handle the gt data
volumes. I raised this as a question regarding
whether this gt would be an efficient use of the
HIS groups time and abilities, or gt whether this
is too specific an application and should be left
to the gt individual HO. Their ability to handle
these and similar problems may gt be a good
attribute to consider in the proposals.
15
UT Update
  • General issues
  • Landscape characterization for HO Design
  • Flux algebra for surface water systems
  • XML for interchange of groundwater objects

16
Mass Balancing
A South Florida Basin
Flow In
Rain
ET
Flow Out
Flow Out
What volume of water is stored within this basin?
17
Process
Horizontal Inflow
Horizontal Outflow 1
Horizontal Outflow 2
Select Time Series Related to Basin
Vertical Inflow
Vertical Outflow
Hydrologic Data Model
Add to Calculate a Net Flow
Net Horizontal Inflow
Net Vertical Inflow
Net Total Inflow
Cumulative Horizontal Storage
Cumulative Vertical Storage
Cumulative Total Storage
Integrate To Calculate A Storage
18
Daily Averaged Vertical Fluxes
19
Daily Averaged Horizontal Flow Rates
20
Daily Averaged Net Flow Rates
21
Cumulative Storage Since Nov. 1, 2001
22
Complications to Process
Extracting time series
Need ability to query a large database to extract
relevant time series for one or more discrete
watersheds
Dimensions Conversions
Need spatial and temporal integration
Units Conversions
Need unit conversions
Discrete-Continuous Time
Need a spatiotemporal referencing system (TGIS)
23
UT Update
  • General issues
  • Landscape characterization for HO Design
  • Flux algebra for surface water systems
  • XML for interchange of groundwater objects

24
Creating a 3D model of the subsurface
Stratigraphy from the North Carolina database
(tabular), imported into ArcGIS
25
Importing borehole data to GMS
Data is imported from GIS into GMS (Groundwater
Modeling System)
26
Solid model
Solids are generated in GMS using the Horizons
method Contacts are assigned horizons (from
bottom to top) and then solids are created by
interpolating a surface for each horizon
extruding downward.
27
Solid model in GIS
The solid model is read back into ArcGIS through
an XML file
28
Transfer of the solid model via XML
  • Solids can be represented as a set of vertices
    and triangles
  • Each vertex has a x, y, and z coordinates
  • Each triangle is constructed of three vertices

29
Storing solids in an XML file
Solids represented as a set of vertices and
triangles
Vertices
Triangles
30
Full process
Interpolation in external software (for example
GMS)
Stratigraphy information in a spatial database
Store solids in XML
Back to spatial database
31
Agenda
  • Review the work of the five project partners
  • CUAHSI (Rick Hooper, Jon Duncan) Neuse HO
    report status
  • San Diego Supercomputer Center (John Helly, .)
  • University of Texas (David Maidment, )
  • University of Illinois (Praveen Kumar .)
    Praveen is overseas
  • Drexel University (Michael Piasecki)

32
The Modelshed Framework
  • Update July 28, 04

33
What is a Modelshed?
  • A volumetric spatial (GeoVolume?) model unit,
    registered in three dimensions by a GIS, with
    which time-varying data, model fluxes, spatial
    relationships and descriptive metadata are
    associated

34
What can the Modelshed Framework do?
  • Store data for diverse spatio-temporal
    applications phenomena
  • A generalized 4D data model for environmental
    science
  • Addresses issues of scale, heterogeneity, and
    resolution
  • Build on top of existing data models (e.g.
    ArcHydro) to leverage existing data structures
    and tools
  • Establish new relationships
  • Models environmental fluxes
  • Connects raster data and numerical models with
    object-relational data models

35
Modelshed UML
36
Timeseries UML
37
Flux UML
38
AreaLink UML
39
OrthogonalLink UML
40
Applications Helping Raster Vector Talk
  • How can continuous data in rasters be related to
    database objects?
  • Summarize the data using statistics, aggregated
    by overlapping Modelshed areas
  • Statistics are stored as indexed data records
  • Modelsheds can be physically meaningful, like
    watersheds
  • This process can be automated for a large number
    of rasters

41
Applications Helping Raster Vector Talk
42
Applications Automating data management with the
Modelshed Tools
  • The ModelShed Tools automate some database tasks
  • Adding new descriptive indexes
  • Building the index of raster datasets
  • Automatically processing a timeseries of raster
    datasets based on areas in the database, and
    ingesting the statistical data into the database
  • Building AreaLink tables
  • ModelShed Tools are an extension to ArcGIS 8, and
    use ArcGIS Spatial Analyst geoprocessing routines

43
Dynamic Features
  • Supports database features that move and change
    in time
  • The full range of Modelshed features are still
    supported, including vertical indexing, flux
    links, and area links.
  • A parallel UML structure for static and dynamic
    features

44
Dynamic Features in Time
45
(No Transcript)
46
Applications 2 ILRDB
  • A prototype geodatabase of the Illinois River
    Basin using the Modelshed geodata model
  • Combining base hydrography from the NHD /
    ArcHydroUSA database with supercomputer-generated
    regional climate data, remote sensing data, land
    use data, and multi-layer soils data
  • A proof of concept for study using a much more
    extensive multi-disciplinary integrated database

47
Illinois River Basin Database (ILRDB)
48
(No Transcript)
49
Studying the relationships between large-scale
phenomena and hydrology using the ILRDB
  • Climate simulation precipitation and humidity
    data is modeled along with NDVI vegetation and
    surface hydrology
  • Query-based analysis is used to analyze the
    relationships between these datasets

50
(No Transcript)
51
Agenda
  • Review the work of the five project partners
  • CUAHSI (Rick Hooper, Jon Duncan) Neuse HO
    report status
  • San Diego Supercomputer Center (John Helly, .)
  • University of Texas (David Maidment, )
  • University of Illinois (Praveen Kumar .)
    Praveen is overseas
  • Drexel University (Michael Piasecki)

52
Drexel ProgressCUAHSI
  • July 28 2004

53
Controlled Vocabulary for the Neuse River Basin
ONTOLOGIES Stream Gauges Datums Site
Types Counties Agencies
Soil Types Municipal Wells Units
http//loki.cae.drexel.edu/how/cuahsi/2004/07/neu
se-station.owl
In progress
54
MTF and MIF files based on ISO-19115
MTF Available in the Web Version 01 based on
ISO19115 http//loki.cae.drexel.edu/how/cuahsi/2
004/07/cuahsi_v01.mtf
Example for municipal wells end of this week.
Controlled vocabularies will be used to annotate
the values
55
Agenda
  • Review the work of the five project partners
  • CUAHSI (Rick Hooper, Jon Duncan)
  • San Diego Supercomputer Center (John Helly, .)
  • University of Texas (David Maidment, )
  • University of Illinois (Praveen Kumar .)
  • Drexel University (Michael Piasecki)
  • Involving the collaborators V. Lakshmi, X.
    Liang, Y. Liang, U. Lall, L. Poff, K. Reckhow, D.
    Tarboton, I. Zaslavsky, C. Zheng
  • HIS review meetings
  • SDSC (August 12-13) technical detail
  • Logan (August 24) user needs assessment

56
Agenda
  • Involving the collaborators V. Lakshmi, X.
    Liang, Y. Liang, U. Lall, L. Poff, K. Reckhow, D.
    Tarboton, I. Zaslavsky, C. Zheng
  • Development of concept papers for particular
    areas of HIS
  • LeRoy Poff an assessment of needs for an HIS to
    support aquatic ecology
  • Manu Lall a survey of methodology for
    statistical space-time interpretation of data
  • We have a draft of a written scopes for Manus
    paper and it has been reviewed by the group

57
Agenda
  • HIS review meetings
  • SDSC (Thursday, Friday, August 12-13) technical
    detail on HIS development especially on metadata
    definition http//cuahsi.sdsc.edu/
  • Logan (Monday, August 23) Status report on HIS
    project and assessment of user needs for HIS in
    the hydrologic observatories http//www.usu.edu/wa
    ter/cuahsi
  • CUAHSI will provide travel funds for HIS project
    PIs and collaborators to travel to one of these
    meetings
Write a Comment
User Comments (0)
About PowerShow.com