Date post: | 18-Jan-2018 |
Category: |
Documents |
Upload: | barnaby-victor-mccarthy |
View: | 220 times |
Download: | 0 times |
1
Arc Hydro Groundwater Data Model
This presentation is adapted from the Groundwater Preconference Seminar presented at the 2008 ESRI User Conference by David
Maidment, Gil Strassberg, and Norman Jones
The research described here is based on the PhD dissertation of Gil Strassberg, which is accessible at:
ftp://ftp.crwr.utexas.edu/pub/outgoing/strassberg/GroundwaterDataModel/Documents/Dissertaion_Strassberg.pdf
2
What is a hydrologic data modelBooch et al. defined a model: “a simplification of reality created to Booch et al. defined a model: “a simplification of reality created to
better understand the system being created”better understand the system being created”
ObjectsObjects
AquiferAquifer
StreamStream
WellWell
VolumeVolumeR.M. Hirsch, USGS
3
Developing a groundwater data modelTake a variety of spatial information and integrate into one geospatial Take a variety of spatial information and integrate into one geospatial database with a common terminologydatabase with a common terminology
• Better communicationBetter communication• Integration of data Integration of data • Base for applicationsBase for applications
Groundwater data modelGroundwater data model(geospatial database)(geospatial database)
Time series observationsTime series observations
Geologic mapsGeologic maps
Borehole dataBorehole data
Geospatial vector layersGeospatial vector layers
Gridded dataGridded dataNumerical modelsNumerical models
Hydrostratigraphy Hydrostratigraphy
4
Network
Components
Framework
Surface water componentsSurface water components
Drainage
Hydrography
Channel
Groundwater componentsGroundwater components
Components can be added to the framework to represent specific Components can be added to the framework to represent specific themes in more detailthemes in more detail
Borehole data
Hydrostratigraphy
Geology
SimulationTemporal (enhanced)
Arc Hydro GW Data Model
5
Watershed
Aquifer Wells
WaterbodyHydroPoints
WaterLines
MonitoringPoint
GeologyArea
GeologyLine
GeologyPoint
1
1..*
BoreholeLog1..*
1..*
1..*
WaterLine
Waterbody
HydroPoint
Watershed
1
1..*
1
1..*
1
1
1..*
1..*
1
Framework data model Wells and boreholes
Time Series
Hydrostratigraphy
SectionLine1
1..*
1..*
1..*
1..*
Geology
1..*
1..*
BoreLine
BorePoint
1
HydroGeologicUnitGeoArea
GeoSection
GeoVolume
GeoRastersTimeSeriesType
1..*
Time Series Datasets
TimeSeries
MonitoringPoint
Well
Aquifer
January 1991
January 1992
January 1993
Feet above mean sea level
UniqueIDTable
1
Boundary
SimulationCell2D 1 1..* Cell3D
Node2D Node3D
11
1..*1 1..*
1..*
Arc Hydro Framework
6
• Basic representation of surface water and groundwater Basic representation of surface water and groundwater • Components can be added to the framework to represent specific Components can be added to the framework to represent specific
themes in more detailthemes in more detail
7
Well• Wells are the most basic features in groundwater databases• Attributes of wells describe its location, depth, water use,
owner, etc.
8
Well• Wells are defined as 2D point features• Only some basic attributes are predefined to describe the
well use, and geometry and relationship with aquifers
Point datasetWell
HydroIDHydroCodeLandElevWellDepthAquiferIDAqCodeHGUIDFType
Wells in the Edwards AquiferWells in the Edwards Aquifer
9
Aquifer features• Polygon features for representing aquifer boundaries and zones Polygon features for representing aquifer boundaries and zones
within themwithin them
• Representation of Aquifer mapsRepresentation of Aquifer maps
10
Aquifer features• An aquifer is defined by one or a set of polygon features• Aquifer features can be grouped by HGUID
Pre Conference Seminar 11
Hydro Features • Key attributes for feature identificationKey attributes for feature identification
• HydroID – Unique ID within the geodatabase (internal relationships)HydroID – Unique ID within the geodatabase (internal relationships)
• HydroCode – Public identifier (external relationships)HydroCode – Public identifier (external relationships)
Pre Conference Seminar 12
HydroID• A new ID assigned to features in a Arc Hydro geodatabaseA new ID assigned to features in a Arc Hydro geodatabase
• Uniquely identifies features with a geodatabaseUniquely identifies features with a geodatabase
• Is used to manage relationships between features and to relate features with Is used to manage relationships between features and to relate features with
tabular data (e.g. time series)tabular data (e.g. time series)
• Custom tool for managing HydroIDsCustom tool for managing HydroIDs
Pre Conference Seminar 13
HydroCode links to external applications• Web interface for groundwater data in TexasWeb interface for groundwater data in Texas• Texas Water Information Integration & Dissemination (WIID)Texas Water Information Integration & Dissemination (WIID)
14
Aquifer and well
*
HydroIDHydroCodeNameHGUIDFType
Aquifer
HydroIDHydroCodeLandElevWellDepthAquiferIDAqCodeHGUIDFType
Well1
• Well features are related to Aquifers: The Well features are related to Aquifers: The AquiferIDAquiferID of a well feature is equal to of a well feature is equal to
the the HydroIDHydroID of an aquifer feature of an aquifer feature
• An aquifer can be associated with one or more wells (1:M relationship)An aquifer can be associated with one or more wells (1:M relationship)
• Can take a different approach to support M:N relationshipCan take a different approach to support M:N relationship
15
Aquifer and well
Well HydroID = 53
16
Wells and TimeSeriesWell features are related with time series (water levels, water Well features are related with time series (water levels, water quality)quality)
San Marcos springs Springs
Sink Creek
San Marcos
Monitoring Well (295443097554201 )
17
MonitoringPoint has time seriesMonitoring points are related with time series (streamflow, water quality, precipitation)
Pre Conference Seminar 18
Integration of surface water and groundwater data
Streamflow Gage at Comal Springs, New
Braunfels Texas
Well in the Edwards Aquifer)
The common framework supports analysis of surface water and groundwater data together
Pre Conference Seminar 19
Surface water groundwater linkageRelationships between surface water and aquifer enable analysis based on spatial and hydrologic relationships
Streams over the outcrop = recharge features
20
Components• Geology - Representation of data from geologic maps
• Wells and Boreholes – Description of well attributes and borehole data
• Hydrostratigraphy – 2D and 3D description of hydrostratigraphy
• Temporal – Representation of time varying data
• Simulation – Representation of groundwater simulation models (focus on MODFLOW)
21
Geologic mapsA geologic map is a cartographic product that portrays information about A geologic map is a cartographic product that portrays information about the geologic character of a specific geographic areathe geologic character of a specific geographic area
• Groundwater features are closely tied to geologyGroundwater features are closely tied to geology
• Geologic maps vary in scale (continental, regional, local)Geologic maps vary in scale (continental, regional, local)
• Provide a simple data structure to support mappingProvide a simple data structure to support mapping
GeologyGeology AquifersAquifers
Maps from the United States National (http://nationalatlas.gov/).
22
Geologic map databases
“A digitally-compiled collection of spatial (geographically referenced) and descriptive geologic information about a specific geographic area” (Geologic Data Subcommittee, Federal Geographic Data Committee 2006)
• Standards for archiving geologic map dataStandards for archiving geologic map data
• Support the development of applications for automating map creationSupport the development of applications for automating map creation
• ComplexComplex
Examples:Examples:
North American Geologic Map Data Model (NADM) North American Geologic Map Data Model (NADM)
National Geologic Map Database (NGMDB)
State geologic map databases (e.g. Geologic Atlas of Texas)
ArcGeology
23
Geologic map databases
Arc Geology: Arc Geology: generic geologic map database implemented within ArcGIS
(figure from Raines et al. 2007
Geodatabase design for storing data from the Geodatabase design for storing data from the Geologic Atlas of Texas Geologic Atlas of Texas ((
http://www.tnris.org/news.aspx?id=244http://www.tnris.org/news.aspx?id=244)
Pre Conference Seminar 24
Geology component
Map modified from: Geologic map of the Edwards Aquifer recharge zone, south-central Texas. U.S. Geological Survey SIM 2873 GeologyPoint
GeologyLine GeologyArea
GeologyLine
HydroIDHydroCodeGeoAbbrevDescriptionHGUIDHGUCodeFTyp
GeologyArea
HydroIDHydroCodeGeoAbbrevDescriptionHGUIDHGUCodeFTyp
GeologyPoint
HydroIDHydroCodeGeoAbbrevDescriptionHGUIDHGUCodeFType
GeologyPoint: Point feature (e.g. springs, caves, sinks, and observation points)
GeologyLine: Line features (e.g. faults, contacts, and dikes)
GeologyArea: Areal features (e.g. rock units and alteration zones)
Pre Conference Seminar 25
Components• Geology - Representation of data from geologic maps
• Wells and Boreholes – Description of well attributes and borehole data
• Hydrostratigraphy – 2D and 3D description of hydrostratigraphy
• Temporal – Representation of time varying data
• Simulation – Representation of groundwater simulation models (focus on MODFLOW)
26
Well databases• Wells are basic features in groundwater databases• Attributes of wells describe its location, depth, water use, owner, etc.• Data are collected from drilling/construction reports and permits
Pre Conference Seminar 27
Well databases• Well databases store information on wells and related data
• Data are related to wells such as construction, water levels, water quality, and stratigraphy
• Usually a central table is used to describe well features and other data are linked to it through key attributes (e.g. state well number)
Relationships in the TWDB groundwater
database
Pre Conference Seminar 28
Well• The Well location is defined as a 2D point in the
Well feature class• In the Arc Hydro model we only predefine a set
of basic attributes Point datasetWell
HydroIDHydroCodeLandElevWellDepthAquiferIDAqCodeHGUIDFType
Wells in the Edwards AquiferWells in the Edwards Aquifer
29
Borehole data• 3D data (screens, completion intervals, stratigraphy) is referenced along the 3D data (screens, completion intervals, stratigraphy) is referenced along the
wellwell
• From depth (top) – To depth (bottom)From depth (top) – To depth (bottom)
30
BoreholeLog table• Used to store 3D borehole data related with well featuresUsed to store 3D borehole data related with well features
• Each row in the table represents a point/interval along a boreholeEach row in the table represents a point/interval along a borehole
• Data are related with a Well feature through the WellID attributeData are related with a Well feature through the WellID attribute
• 3D geometry is defined by the TopElev and BottomElev attributes3D geometry is defined by the TopElev and BottomElev attributes
31
3D features (BorePoints and BoreLines)• Can create 3D features representing data in the BoreholeLog table• BorePoint is a 3D point feature class for representing point locations
along a borehole (e.g. geologic contacts, samplers)• BoreLine is a 3D line feature class for representing intervals along a
borehole
BorePoint
BoreLine
32
Components• Geology - Representation of data from geologic maps
• Wells and Boreholes – Description of well attributes and borehole data
• Hydrostratigraphy – 2D and 3D description of hydrostratigraphy
• Temporal – Representation of time varying data
• Simulation – Representation of groundwater simulation models (focus on MODFLOW)
33
Hydrogeologic units“Hydrogeologic unit is any soil or rock unit or zone which by virtue of its hydraulic properties has a distinct influence on the storage or movement of ground water” (USGS glossary of hydrologic terms)
Hydrogeology can be derived by classifying stratigraphic units
Georgetown Fm. (GTOWN)
Cyclic + Marine member (CYMRN)
Upper confining unit
Leached + collapsed member (LCCLP)
Regional dense member (RGDNS)
Grainstone member (GRNSTN)
Kirschberg evaporite member (KSCH)
Dolomitic member (DOLO)
Upper Glen Rose (UGLRS)
Stratigraphic units Hydrogeologic units
Pearson Fm.
Basal Nodular member (BSNOD)
Kainer Fm.
Georgetown Fm.
Edw
ards
Aq
uife
r
34
Hydrogeologic unit table• HydroGeologicUnit table provides a conceptual description of hydrogeologic units
• Hydrogeologic units are with an AquiferID such that they can be grouped to represent an aquifer
• Spatial features are indexed with a HGUID to relate to the conceptual representation of the units
35
Representations of hydrogeologic units• Different spatial representations of hydrogeologic with 2D and 3D objects• Workflow for creating 3D hydrogeologic models
Cross sections/Fence diagrams
Volume objects representing hydrogeologic units
Cross sections derived from the solid model
Define hydrogeologic units along boreholes
Create surfaces from borehole data and
cross sections
Interpolate and edit cross sections
“Cut” cross sections from the solid model
Surfaces defining the extent of hydrogeologic units
Borehole Stratigraphy
Build volumes between surfaces Create cross sections
based on the surfaces
36
Hydrogeologic unit table• Hydrogeologic units are described with different spatial instances
(outcrops, borehole intervals, surfaces, cross sections, and volumes)• HGUID is the key attribute
1
*
*
*
*
1
GeoVolume
HydroIDHydroCodeHGUIDHGUCodeFType
HGUArea
HydroIDHydroCodeHGUIDHGUCodeFType
GeoRasters
RasterNameDescriptionUnitsHGUIDHGUCodeAquiferIDAqCode
HydrogeologicUnit
HGUIDHGUCodeHGUNameAquiferIDAqCodeDescription
SectionLine
HydroIDHydroCodeSNameFType
HydroIDHydroCodeSectionIDSNameHGUIDHGUCodeFType
GeoSection
*
37
HGUArea
GeoArea feature representing the Kainer hydrogeologic unit
GeologyArea features represent data from
geologic mapsGeologyArea
• 2D polygons defining boundaries of hydrogeologic units2D polygons defining boundaries of hydrogeologic units• HGUArea (conceptual/interpolated boundary) ≠ GeologyArea (mapped outcrop)HGUArea (conceptual/interpolated boundary) ≠ GeologyArea (mapped outcrop)
Data points representing top elevations of the Kainer formation
38
Representation of Cross Sections• SectionLineSectionLine defines the 2D cross section• GeoSectionGeoSection represent 3D sections as 3D polygons represent 3D sections as 3D polygons• SectionIDSectionID of the polygon relates back to the section line of the polygon relates back to the section line
GeoSection 4713HGUID = 3
A
A’B
B’
A
A’
B
B’
Section B-B’(HydroID 4667)
39
Georgetown
Glen RoseKainer
Person
GeoRasters• Raster catalog for storing and indexing raster datasets• Can store top and bottom of formations• Each raster is related with a HGU in the hydrogeologic unit table
40
GeoRasters• GeoRasters also store hydraulic properties such
as transmissivity, conductivity, and specific yield
K (feet/day)
Raster of hydraulic conductivity in the Edwards AquiferRaster of hydraulic conductivity in the Edwards Aquifer
41
GeoVolume• Objects for representing 3D volume objects• Geometry is multipatch
42
GeoVolume• Can create the volumes as a set of 3D triangles• Not real volume – can’t do any 3D operations• Volumes in this example were generated in GMS and
imported to the geodatabase
Georgetown
PersonKainer
Volumes in GMSVolumes in GMS
GeoVolumes in the geodatabaseGeoVolumes in the geodatabase
43
Components• Geology - Representation of data from geologic maps
• Wells and Boreholes – Description of well attributes and borehole data
• Hydrostratigraphy – 2D and 3D description of hydrostratigraphy
• Temporal – Representation of time varying data
• Simulation – Representation of groundwater simulation models (focus on MODFLOW)
44
Types of time varying datasets• Single variable time series – A single variable recorded
at a location, such as stream discharge or groundwater levels
• Multi variable time series – Multiple variables recorded simultaneously at the same location, such as chemical analysis of a water sample
• Time varying surfaces (raster series) – Raster datasets indexed by time. Each rater is a “snapshot” of the environment at a certain time.
• Time varying features (feature series) – A collection of features indexed by time. Each feature in a feature series represents a variable at a single time period.
Pre Conference Seminar 45
Time series • The most basic case is a monitoring device recording
values over time (e.g. monitoring well, streamflow gage)
San Marcos springs Springs
San M
arcos R
iver
Sink Creek
San Marcos
Monitoring Well (295443097554201 )
46
Time series • TimeSeries table is the basic table for storing time series data• Need to support: what, where, and when • Variables table defines variable objects
Time (TsTime)
Space (FeatureID)
Variables (VariableID)
Pre Conference Seminar 47
Time series • By querying the table we can create different data views
2791
TsTime
FeatureID
VariableID
2FeatureID
VariableID
2791 FeatureID
VariableID
2
(a) (b) (c)TsTime TsTime
48
Time series views – create time series graph
Well HydroID = 2791
• FeatureIDFeatureID of the time series = of the time series = HydroIDHydroID of the spatial feature (e.g. Well)of the spatial feature (e.g. Well)
Pre Conference Seminar 49
Time series views – map a variable at a given timeMap a certain variable (e.g. water levels) at a given time (e.g. February 2004)Map a certain variable (e.g. water levels) at a given time (e.g. February 2004)
FeatureID
VariableID
2
TsTime
2/2004 Feet above mean sea level
Pre Conference Seminar 50
• Data are indexed by space (FeatureID) and by time (TsTime) but instead of Data are indexed by space (FeatureID) and by time (TsTime) but instead of one variable we store one variable we store multiple variablesmultiple variables..
• The column heading is the The column heading is the variable key (VarKey)variable key (VarKey)
Variables (VarKey)
Multi-variable time series
51
Multi-variable time series• Data are indexed by space (FeatureID) and by time (TsTime) but instead of Data are indexed by space (FeatureID) and by time (TsTime) but instead of
one variable we store one variable we store multiple variables.multiple variables.• The column heading is the The column heading is the variable key (VarKey)variable key (VarKey)
Variables (VarKey)
52
RasterSeries• Raster datasets indexed by time• Each raster represents a continuous surface describing a
variable for a given time over an area of interest
January 1991
January 1992
January 1993
53
Feature Series• A collection of features indexed by time (e.g. particle tracks)• Features are indexed by VariableID, TsTime.• Features can also be indexed with a GroupID. Each group of
features creates a track over time
54
Components• Geology - Representation of data from geologic maps
• Wells and Boreholes – Description of well attributes and borehole data
• Hydrostratigraphy – 2D and 3D description of hydrostratigraphy
• Temporal – Representation of time varying data
• Simulation – Representation of groundwater simulation models (focus on MODFLOW)
Representing simulation models• GeoreferenceGeoreference model inputs and outputs (in model inputs and outputs (in space and timespace and time))• Focus on Focus on MODFLOWMODFLOW, block centered finite difference grid (nodes are in the , block centered finite difference grid (nodes are in the
center of the cells)center of the cells)• Represent Represent 2D and 3D 2D and 3D modelsmodels
Block-centered finite difference grid
56
Simulation component
Features for representing data from simulation modelsFeatures for representing data from simulation models
Pre Conference Seminar 57
BoundaryPolygon feature class for representing the extent and orientation of a Polygon feature class for representing the extent and orientation of a simulation modelsimulation model
58
Cell2D and Node Cell2D:Cell2D: polygon feature class that represents cells or elements associated with a polygon feature class that represents cells or elements associated with a two-dimensional simulation model or a single layer of a three-dimensional two-dimensional simulation model or a single layer of a three-dimensional modelmodel
Node:Node: point feature class used in combination with Cell2D to represent the point feature class used in combination with Cell2D to represent the model’s mesh/grid. model’s mesh/grid.
Node Features Cell2D Features
(a) (b) (c)
a) Finite element meshb) Mesh centered finite
difference gridc) Cell centered finite
difference grid
59
Cell3D• Multipatch feature class that represents three-dimensional cells and
elements• Used mostly for Used mostly for visualization of 3D modelsvisualization of 3D models