Transcript No Slide Title

Introducing the
ArcGIS Marine Data Model
Marine Special Interest Group Meeting
ESRI User Conference
July 9, 2002
dusk.geo.orst.edu/djl/arcgis 1
ArcGIS “Custom” Data Models
• Basemap
• Administrative
Boundaries
• Utilities
• Parcels
• Tranportation
• Imagery
etc ...
• Conservation/Biodiv
• Hydro
• Groundwater Hydro
• Forestry
• Geology
• Petroleum
• Marine
• IHO S-S57
etc ...
2
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"
• can’t 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
3
4
Figure courtesy of Anne Lucas, U. of Bergen, Norway
Marine Data
Collection
Image courtesy of PISCO, OSU
5
Overall Process
Draft
Model
Review,
Projects
Final Model
• Data model template – few weeks to months
• Mature data model – up to few years
• more info at dusk.geo.orst.edu/djl/arcgis/about.html
6
Project Milestones
• Oct. 4-5, 2001: Initial Working Group
Analysis Diagram, UMLs, Data Structures
– Steve Grisé, Joe Breman, Simon Evans
– Dawn Wright, OrSt
– Pat Halpin and Eric Treml, Duke
– Jason Marshall, NOAA CSC
• Nov. 2001: Draft Conceptual FW Document
–
7
Project Milestones (cont.)
• Early 2002: Review & Case Study Teams
• Interested Participants via web site
~150 people
29 countries & USVI
• June 7-8, 2002: Second workshop
• Tonight’s Marine SIG Meeting at ESRI UC
8
Purpose of Marine Data Model
• basic template for implementing GIS projects
– input, formatting, geoprocessing, creating maps,
performing analyses
• basic framework for writing program code and
maintaining applications
– development of tools for the community
• promote networking and data sharing through
established standards
9
Why? (cont.)
• Learning, understanding ArcGIS!
• 2-way educational process: users & ESRI
• Bear DM in mind when collecting data
• The geodatabase
– Not going away
– Coverages, shapefiles not around forever
10
Transition to ArcGIS 8?
• How and when to do it?
• How well are marine application domain
requirements met in the geodatabase
structure now?
• Understanding the technology and identifying
requirements
• Potential benefits
11
ArcView 8 vs. ArcInfo 8
• Need AI to fully use data model
– Users vs. power users (CD-R vs. CD-RW)
• ArcView and ArcReader can view DM dBs
– Features classes, simple analysis
• ArcView 3D Analyst - set of pts. with z as
attribute
12
Steps in Data Modeling
(1) Model the user's view of data
– what are the basic features needed to solve
the problem?
(2) Select the geographic representation
– points, lines, areas, rasters, TINs
Bathymetry
Marine mammal movement
Sidescan sonar/Backscatter
Atmospheric influences
Shoreline
Sea state
Marine boundaries (e.g., MPAs)
Wave activity
Geophysical time series
Sea surface temperature
Sub-bottom profiling
Salinity
Magnetics
Sensor calibration data
Gravity
Current meters
Seismics
Density
Sediment transport
etc. ...
etc. ...
13
14
Users’s View
of Data
15
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
16
Core Themes of Objects & Features
17
Synthesis, Analysis, Interpretation
18
19
More information,
downloads, or join MDM listserv
dusk.geo.orst.edu/djl/arcgis
20
21
Some Issues
• Coastal vs. deepsea balance
• General Data Structures
– Your data may not immediately fall into present schema categories
– Shouldn’t be a problem with the structure
– Still hard to input raw data
• 3D
– Many use other software for true 3D analysis (Fledermaus, Rockware,
etc.)
– import, conversion to Arc
– Geology, geophysics, phys. oceanography software
• How does the model handle TIME?
– especially same feature in different locations over time?
– Hydro model time series may not be good equivalent after all
• Change in value (flow) for a fixed feature (channel, gauge)
22