Conceptual%20Overview%20of%20ArcMarine:%20The%20ArcGIS%20Marine%20Data%20Model

1
Conceptual Overview of ArcMarineThe ArcGIS
Marine Data Model

• Dawn Wright, Oregon State University
• Pat Halpin, Duke University
• Michael Blongewicz, DHI
• Joe Breman and Steve Grisé, ESRI
• Juergen Schulz-Ohlberg, BSH
• Federal Maritime Hydrographic Agency of Germany

GIS Training for Marine Resource Managers,
Monterey June 15, 2005
dusk.geo.orst.edu/djl/arcgis
2
Session Topics

• General DM Design and Process
• Conceptual Overview of ArcMarine
• Break, questions/discussion
• Paulos ArcMarine Demo Geodatabase Exercise
• Final Questions/Discussion

3
Representing the Real World
Graphic by ESRI
Operational GIS Analysis and Presentation
GIS Data Model Description and Representation
People Interpretation and Explanation
Real World
4
Figure courtesy of Anne Lucas, U. of Bergen,
Norway
5
Marine Data Collection
Image courtesy of PISCO, OrSt
6
Image courtesy of the Neptune Project,
www.neptune.washington.edu, University of
Washington Center for Environmental Visualization
7
Image courtesy of the Neptune Project,
www.neptune.washington.edu, University of
Washington Center for Environmental Visualization
8
Image courtesy of MBARI, www.mbari.org/mars
9
A Georelational to a Geodatabase Model

• coverage and shapefile data structures
• homogenous collections of points, lines, and
  polygons with generic, 1- and 2-dimensional
  "behavior"
• cant distinguish behaviors
• Point for a marker buoy, same as point for OBS
• smart features in a geodatabase
• lighthouse must be on land, marine mammal siting
  must be in ocean

10
Object-Oriented Data Modeling

• Objects in the real world
• Natural rules and relationships
• Rivers flow downstream
• Roads handle levels of traffic
• MPA polys respect use regulations
• How to build this intelligence into data
  structures?

11
Smarter Data Structures

• Arc 7 coverage
• geometric information not stored in database
• Arc 8/Arc 9 geodatabase
• stores geometric information as "shape" attribute
• closer to how we actually think about geographic
  features
• Identity, Inheritance, Encapsulation (Behavior)

12
Microsoft COM( Component Object Model )

• Microsoft standard for re-usable software
  components
• Build software from parts, not from scratch
• Makes software easier to write and reuse
• Provides widest choice in services, tools,
  languages, and applications
• Controls, tools, and server components
• Geographic objects and software objects
• e.g., Word and Excel

13
ArcGIS and Microsoft COM

• 2,000 reusable software objects
• Programmable in Visual Basic for Applications
  (VBA) and Python
• Visual language for representing a data model
• Data modeling with Unified Modeling Language (UML)

14
ArcGIS Custom Data Modelssupport.esri.com/datam
odels
15
ArcGIS Custom Data Models

• Basemap
• Administrative Boundaries
• Utilities
• Parcels
• Transportation
• Imagery
• etc ...

• Conservation/Biodiv
• Hydro
• Groundwater Hydro
• Forestry
• Geology
• Petroleum
• Marine
• IHO-S57
• Atmospheric
• etc ...

16
Purpose of ArcMarine

• basic template for implementing marine GIS
  projects
• input, formatting, geoprocessing, creating maps,
  performing analyses
• simplify project implementation
• basic framework for writing program code and
  maintaining applications
• development of tools for the community
• promote networking and data sharing through
  established standards

17
Why? (cont.)

• Learning, understanding the Geodatabase!
• 2-way educational process users ESRI
• Bear DM in mind when collecting data
• The geodatabase
• Not going away
• Coverages, shapefiles not around forever

18
Implementation Process
Design Engineering
Database Engineering

• Data model template few weeks to months
• Mature data model up to few years
• Since Oct 2001, 3 workshops, 3 ESRI UC sessions
• More info at dusk.geo.orst.edu/djl/arcgis/about.ht
  ml

Deployment/Rollout
19
Modeling Process
Graphic by ESRI
20
Design Strategy
Image modified from original by P. Halpin, Duke
21
Steps in Data Modeling

• (1) Model the user's view of data
• what are the basic features needed to solve the
  problem?

Bathymetry Sidescan sonar/Backscatter Shoreline M
arine boundaries (e.g., MPAs) Geophysical time
series Sub-bottom profiling Magnetics Gravity Seis
mics Sediment transport etc. ...
Marine mammal movement Atmospheric influences Sea
state Wave activity Sea surface
temperature Salinity Sensor calibration
data Current meters Density etc. ...
Image by Joe Breman, ESRI
22
Wright et al., 1995 NOAA PMEL
23
Steve Grisé, ESRI
Userss View of Data
24
(2) Select the geographic representation
(points, lines, areas, rasters, TINs, etc.)
Pat Halpin, Duke
25
(No Transcript)
26
ArcMarine Thematic Layers
27
ArcMarine Thematic Layers
28
Steps in Data Modeling (cont.)

• (3) Define objects and relationships
• draw a UML diagram
• (4) Match to geodatabase elements
• specify relationships, behaviors
• (5) Organize geodatabase structure

29
(No Transcript)
30
InstantaneousPoint (ex CTD)
Michael Blongewicz
X
TimeStamp
Y
Measurement
MeasuringDevice
Z
31
(No Transcript)
32
Organize and finally USE that Gdb!
Graphic by ESRI
33
Implications (1)

• Inputting Formatting Data
• Starting point, a gdb template
• Provides common data structures
• Allows control of required data fields from
  collection through analysis phases

Pat Halpin, Duke
34
DHI TimeSeries Manager
Arc Atmosphere
Arc Hydro
Arc Marine
Geodatabase
TimeSeries Manager
Data Access Bridges
dfs0
35
Implications (2)

• Data models linked to geoprocessing models
• One package for data and process workflow
• New tools provide rapid prototyping for a project

36
Implications (3)
Pat Halpin, Duke

• Data Sharing
• Within / Between Projects
• Internet Map Services (Geography Network, NSDI,
  OBIS)
• Internet Map Services data conflation tools

Distributed Generic Information Retrieval
Distributed Oceanographic Data System
Web Mapping Services
37
ArcMarine is Ongoing

• Case studies , tool development
• Interested participants via web site
• 300 people, 32 countries
• Approaching final UML - feature classes,
  attributes, rules/behaviors
• 2005 ESRI UC technical workshop
• 2006 ESRI Press book
• Agency buy-in
• Publicizing and publishing
• Tie-in w/ other model efforts

38
More information

• dusk.geo.orst.edu/djl/arcgis
• inc. downloads, tutorial
• support.esri.com/datamodels