The Modelshed Framework Praveen Kumar and Ben Ruddell, CUAHSI HIS Update July 28, 04.
-
Upload
juliana-richards -
Category
Documents
-
view
215 -
download
0
Transcript of The Modelshed Framework Praveen Kumar and Ben Ruddell, CUAHSI HIS Update July 28, 04.
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
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
Modelshed UML
-HydroID : esriFieldTypeInteger-HydroCode : esriFieldTypeString
Hydrography::HydroFeature
-ModelshedTypeID : esriFieldTypeInteger
Modelshed
Modelshed::ModelPoint
Modelshed::ModelLine
Modelshed::ModelArea
-ModelShedTypeID : esriFieldTypeInteger-FeatureID : esriFieldTypeInteger-TSTypeID : esriFieldTypeInteger-ZLayerID : esriFieldTypeInteger-TSDateTime : esriFieldTypeDate-TS_MEAN : esriFieldTypeDouble-TS_MEDIAN : esriFieldTypeDouble-TS_MAJORITY : esriFieldTypeDouble-TS_COUNT : esriFieldTypeDouble-TS_MIN : esriFieldTypeDouble-TS_MAX : esriFieldTypeDouble-TS_STD : esriFieldTypeDouble-TS_SUM : esriFieldTypeDouble-TS_SKEWNESS : esriFieldTypeDouble-TS_KURTOSIS : esriFieldTypeDouble-TS_ERROR : esriFieldTypeDouble = 0.0
StatisticalTS
1
1
*
1
-ModelshedTypeID : esriFieldTypeInteger-ModelshedClass : ModelshedClass-Description : esriFieldTypeString
ModelshedType
1
*
Timeseries UML
-FeatureID : esriFieldTypeInteger-TSTypeID : esriFieldTypeInteger-TSDateTime : esriFieldTypeDate-TSValue : esriFieldTypeDouble
TimeSeries -TSTypeID : esriFieldTypeInteger-Variable : esriFieldTypeString-Units : esriFieldTypeString-IsRegular : AHBoolean-TSInterval : TSIntervalType-DataType : TSDataType-Origin : TSOrigins
TSType
1* TSTypeHasTimeSeries
-ModelShedTypeID : esriFieldTypeInteger-FeatureID : esriFieldTypeInteger-TSTypeID : esriFieldTypeInteger-ZLayerID : esriFieldTypeInteger-TSDateTime : esriFieldTypeDate-TS_MEAN : esriFieldTypeDouble-TS_MEDIAN : esriFieldTypeDouble-TS_MAJORITY : esriFieldTypeDouble-TS_COUNT : esriFieldTypeDouble-TS_MIN : esriFieldTypeDouble-TS_MAX : esriFieldTypeDouble-TS_STD : esriFieldTypeDouble-TS_SUM : esriFieldTypeDouble-TS_SKEWNESS : esriFieldTypeDouble-TS_KURTOSIS : esriFieldTypeDouble-TS_ERROR : esriFieldTypeDouble = 0.0
StatisticalTS
1
* TSTypeHasStatisticalTS
-ModelshedTypeID : esriFieldTypeInteger-ModelshedClass : ModelshedClass-Description : esriFieldTypeString
ModelshedType1*
-ZLayerID : esriFieldTypeInteger-AltitudeUnits : esriFieldTypeString-AltitudeDatum : esriFieldTypeString-Description : esriFieldTypeString-LayerBottomAltitude : esriFieldTypeDouble-LayerTopAltitude : esriFieldTypeDouble-ZLayerAboveID : esriFieldTypeInteger-ZLayerBelowID : esriFieldTypeInteger
ZLayer1
*
Flux UML
Modelshed::ModelArea Modelshed::ModelLine Modelshed::ModelPoint
-FluxTypeID : esriFieldTypeInteger-FluxLinkID : esriFieldTypeInteger-FromFeatureID : esriFieldTypeInteger-ToFeatureID : esriFieldTypeInteger-FromZLayerID : esriFieldTypeInteger-ToZLayerID : esriFieldTypeInteger-FromModelShedTypeID : esriFieldTypeInteger-ToModelShedTypeID : esriFieldTypeInteger-TSTypeID : esriFieldTypeInteger
FluxLink
-FluxLinkID : esriFieldTypeInteger-DateTime : esriFieldTypeDate-Value : esriFieldTypeDouble
FluxRecord
-FluxTypeID : esriFieldTypeInteger-Description : esriFieldTypeString
FluxType
1 11
1
1
*
1
*
-ModelshedTypeID : esriFieldTypeInteger-ModelshedClass : ModelshedClass-Description : esriFieldTypeString
ModelshedType
-ZLayerID : esriFieldTypeInteger-AltitudeUnits : esriFieldTypeString-AltitudeDatum : esriFieldTypeString-Description : esriFieldTypeString-LayerBottomAltitude : esriFieldTypeDouble-LayerTopAltitude : esriFieldTypeDouble-ZLayerAboveID : esriFieldTypeInteger-ZLayerBelowID : esriFieldTypeInteger
ZLayer
ArcHydro NativeImplementation Classes1 *
1
*
1 *
1
*
AreaLink UML
Modelshed::ModelArea1
*
1
*
-Area1FeatureID : esriFieldTypeInteger-Area2FeatureID : esriFieldTypeInteger-ModelshedClass1 : ModelshedClass-ModelshedClass2 : ModelshedClass-FractionOf1In2 : esriFieldTypeDouble
AreaLink
-ModelshedTypeID : esriFieldTypeInteger-ModelshedClass : ModelshedClass-Description : esriFieldTypeString
ModelshedType
1
*
1
*
ArcHydro NativeImplementation Classes
OrthogonalLink UML
-ModelShedTypeID : esriFieldTypeInteger-FeatureID : esriFieldTypeInteger-posYFeatureID : esriFieldTypeInteger-posXFeatureID : esriFieldTypeInteger-negYFeatureID : esriFieldTypeInteger-negXFeatureID : esriFieldTypeInteger-posXposYFeatureID : esriFieldTypeInteger-posXnegYFeatureID : esriFieldTypeInteger-negXnegYFeatureID : esriFieldTypeInteger-negXposYFeatureID : esriFieldTypeInteger
OrthogonalLink
Modelshed::ModelArea
-ModelshedTypeID : esriFieldTypeInteger-ModelshedClass : ModelshedClass-Description : esriFieldTypeString
ModelshedType
1
*
1
1
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
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
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
11
1
*
1
-DynamicFeatureID-ZLayerID-TSDateTime
DynamicFeature
DynamicPoint{GeometryType = esriGeometryPoint}
DynamicArea{GeometryType = esriGeometryPolygon}
DynamicLine{GeometryType = esriGeometryPolyline}
Modelshed::Modelshed-HydroID-HydroCode
Hydrography::HydroFeature
-DynamicFeatureID-Description-ModelshedTypeID
Objects::DynamicFeatureIndex
*
1
*
*
-ModelshedTypeID-FeatureID-TSTypeID-ZLayerID-TSDateTime-TS_MEAN-TS_MEDIAN-TS_MAJORITY-TS_COUNT-TS_MIN-TS_MAX-TS_STD-TS_SUM-TS_SKEWNESS-TS_KURTOSIS-TS_ERROR = 0.0
Objects::StatisticalTS
1
*1
1
-FluxTypeID-FluxLinkID-FromFeatureID-ToFeatureID-FromZLayerID-ToZLayerID-FromModelshedTypeID-ToModelshedTypeID
Objects::FluxLink
11
-Area1FeatureID-Area2FeatureID-ModelshedTypeID1-ModelshedTypeID2-FractionOf1In2
Objects::AreaLink
1
*
1
*
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
SALT
SPOON
KANKAKEE
IROQUOIS
UPPER FOX
LOWER ILLINOIS
LA MOINE
DES PLAINES
VERMILION
MACKINAW
MACOUPIN
LOWER FOX
UPPER SANGAMON
CHICAGO
UPPER ILLINOISLOWER ILLINOIS-SENACHWINE LAKE
LOWER SANGAMON
SOUTH FORK SANGAMON
LOWER ILLINOIS-LAKE CHAUTAUQUA
Illinois River Basin Database (ILRDB)
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