ArcGIS Marine Data Model
Technical Session
Joe Breman, Michael Blongewicz,
Pat Halpin, Dawn Wright
Agenda
•
•
•
•
•
•
Data Model Purpose
Thematic content
Demonstration
Detailed design discussion
Implications
Q&A
For Sample Database and Design Documents
See Data Models at
support.esri.com/datamodels
2
ArcGIS Data Modeling
• The Marine Data Model
– Designing a geodatabase to best fit marine data
– Coastal and Marine Managers, Educators
Researchers, and Professionals
– Use and implementation
3
Marine Data Model Purpose
• To support marine data management
• Template Includes
–
–
–
–
Marine Points, lines and polygons
Multiple dimensional and dynamic data
Relationships between the features and tables
Implementing multiple z, and time attributed data
• Leverage other existing practices/standards
• Approaches to managing marine data
4
Marine Thematic Layers
Basemap
Marine Points
Coastal and Boundary Lines
Time and Depth Measurements
Water Column Data
Bathymetry
Substrate
5
Demonstration
• Important feature classes, relationships, and
attributes of the marine data model
• In the process of design planning consider
tools and final result as part of the process
6
Web Site 1
• Content
• Case study,
template
• Geodatabase
diagrammer tools
on arcscripts
7
Web Site 2
dusk.geo.orst.edu/djl/arcgis
• Background
• Additional
content
• Mirror of UML,
gdb, etc.
• Related links
• MDM-only user
forum
8
Marine Template
• Provide a structure for relationships between
complex multidimensional dynamic data
• Consideration to method of data collection
• Provide a basis
for describing marine
data types
9
Metadata Documentation
• Important to document the details about
the data collection and attributes
10
Extending the model with 3-4D
A Method:
• Creating a fishnet
• Converting to polygon
• Joining to points
• Extrusion
Some design questions:
When to implement z
aware data (PointZM)?
When to relationship
classes and how?
How to best include time
series and duration
measurements?
11
TimeSeriesPoint
TimeSeriesPoints
MarineID
1
2
3
MarineCode
AAA
BBB
CCC
Z
MeasuringDevice
Measurement
MeasureID
1
2
3
4
5
MarineID
1
1
1
2
2
Measurement
ZLoc
-0.8
-1.5
-3.5
-0.8
-1.5
Xloc
Yloc
ServiceTrip
SeviceDesc
X
MeasuringDevice
MDeviceID
1
2
3
4
5
Name
Type
MeasurementID
1
1
1
2
2
Y
TimeSeries3
FeatureID
TimeSeriesTurnTable
FeatureID
1
1
2
2
2
TSTypeID
1
2
3
4
5
TSType
TSTypeID
1
2
3
4
5
Variable
CurrentSpeed
Salinity
CurrentSpeed
Temperature
Salinity
Units
TSTypeID
TSDateTime
TSValue
1
12:00:00
16.7
TimeSeries2
1
12:20:00
14.0
FeatureID
TSTypeID 1 TSDateTime
TSValue 21.9
12:40:00
1
1 12:00:00 13:00:0016.7
11.2
TimeSeries1
1
1 12:20:00 13:20:0014.0
12.4
1
12:40:00
21.9
FeatureID
TSTypeID
TSDateTime
TSValue
1
13:00:0012:00:00 11.2 16.7
1
1
13:20:0012:20:00 12.4 14.0
1
1
1
1
12:40:00
13:00:00
13:20:00
21.9
11.2
12.4
13
Marine GIS Data Model
Implications of a marine data model?
An data model provides a basic template for:
1. Inputting / formatting data
2. Geoprocessing / analyzing data
3. Sharing data
For developers, it provides a basic framework for
writing program code and maintaining
applications
Marine GIS Data Model
Building a template…
Strategy:
 As generic as possible…
 As exhaustive as possible…
 As temporally dynamic as possible…
Marine GIS
Data Model
Building a
template…
An extension of
GIS features to
better fit marine
applications…
Time Series
Location Series
Marine GIS Data Model
Strategy:
 As generic as possible…
 As exhaustive as possible…
 As temporally dynamic as possible…
Resulting Issues:
 Too generic for unmodified use…
 Usefulness will vary with applications…
 Some common marine data types (rasters)
do not directly benefit from relational UML
model…
Marine Data Model – Data Types
Marine GIS Data Model
“Generic”
Marine Data Model
User Group
Data Model
Project
Data Model
User Group
Data Model
Project
Data Model
User Group
Data Model
Inheritance
A data model hierarchy…
Project
Data Model
Marine GIS Data Model
Implications:
Inputting & Formatting Data
 Provides common data structures
 Allows control of required data fields from
collection through analysis phases
Marine GIS Data Model
Implications:
Geoprocessing & Analysis
 Allows explicit spatial & temporal
relationships to be used in geoprocessing and
analysis
Build Better Models / Analysis
GIS Applications
Data Space
Statistical Applications
GIS Applications
Geographic Space
Geographic Space
2. Statistical methods
Redefine Model
Sample Data
1. Sampling
Model Habitat
4. Model validation
3. GIS models
Marine GIS Data Model
Implications:
Data Sharing
 Within / Between Projects
 Internet Map Services (Geography Network, NSDI, OBIS…)
 Internet Map Services: data conflation tools
Data Type:
Tools/Protocols:
vector data
XML
raster data
DODS
metadata
Z39.50
FGDC
map
WMS
Analysis Physical Ocean &
Species
Physical data
Species data
Web Map Service
(WMS)
Implications
– Use the data model as a part of the workflow
– Project implementation
– Industry and Academic cooperation Oregon State,
Duke, NOAA, Fisheries
Use multi-dimensional dynamic data in the
geodatabase to facilitate display, analysis,
queries, and map making for marine
applications.
32
Implications continued…
• Extremely generic
• Coastal vs. deepsea
• Use tutorial, case studies to help w/ data input
– dusk.geo.orst.edu/djl/arcgis/MDM_tutorial
• Feature classes document (glossary) with
– Marine data types graphic
– SIM diagram
• Bear DM in mind when collecting data
• More case studies welcome!!!
33
Crosswalks
• ArcHydro (surface and groundwater)
• IHO S-57 data model
• Possible atmospheric data model
– Focus on temporal, attend ATM SIG
• SciViz (Viz5D, Fledermaus, CTech, etc.)
34
Summary
• More information
– Case Studies / White paper
– Data Model Poster
• To represent the model design
– Metadata Template, Tools
– Stay tuned for news on MDM book
– Join MDM list at dusk.geo.orst.edu/djl/arcgis
• Websites:
support.esri.com/datamodels
dusk.geo.orst.edu/djl/arcgis
• Questions?
35