ArcGIS Data Models:
Design and Process
Joe Breman
Overview
•
•
•
•
•
•
GIS Design and Process
Data Model Templates and project workflow
Geodatabase Concepts
Case Studies
Tools and methods
Examples
1
Data Models Represent the Real World
GIS Data Model
Description and
Representation
Operational GIS
Analysis and
Presentation
People
Interpretation and
Explanation
Real World
2
Modeling Process
Real World
Objects and Relationships
Physical Model
Database Schema
Business Rules
Conceptual Model
Sketches, Flow Diagrams, etc
Logical Model
Diagram in CASE Tool
ArcCatalog Tools
3
4
Data Model Templates
Geometry Point
Contains M values No
Contains Z values No
Simple feature class
Haul
Allow
Data type nulls
Field name
OBJECTID
SHAPE
HAULJOIN
VESSELCODE
CRUISE
HAUL
STATION_ID
SSTEMP
BOTTOMTEMP
EFFORT
DataSourceID
Object ID
Geometry
Long integer
Long integer
Long integer
Long integer
String
Float
Float
Float
String
Default value
Domain
Precision Scale Length
Yes
No
No
No
No
No
No
No
No
Yes
0
0
0
0
7
0
0
0
0
0
0
50
Table
FishCatch
Relationship class
HaulHasFishCatch
Type Simple
Cardinality One to many
Notification None
Origin feature class
Name Haul
Primary key HAULJOIN
Foreign key HAULJOIN
Forward label FishCatch
Backward label Haul
OBJECTID
HAULJOIN
SPECIESCODE
LATINNAME
COMMONNAME
WEIGHTCPUE
NUMBERCPUE
Destination table
NameFishCatch
No relationship rules defined.
Relationship class
DataSourceHasHaul
Type Simple
Cardinality One to many
Notification None
Origin table
Name DataSource
Primary key DataSourceID
Foreign key DataSourceID
Forward label Haul
Backward label DataSource
NameHaul
No relationship rules defined.
Object ID
Long integer
Long integer
String
String
Double
Double
Default value
Precision Scale Length
Domain
No
No
No
No
No
No
0
0
28
21
0
0
Table
DataSource
Field name
Destination feature class
Allow
Data type nulls
Field name
OBJECTID
DESC_
SOURCE
CONTACT
PREC
CREATE_DATE
LAST_UPDATED
DataSourceID
Allow
Data type nulls
Object ID
String
String
String
String
Long integer
Long integer
String
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Default value
Domain
Precision Scale Length
35
35
20
20
0
0
50
5
0
0
Where to find templates?
•
•
•
•
•
•
•
Available at http://support.esri.com/datamodels.
Can simplify project implementation.
Can be helpful if you are building a product or generic tool.
Provide insight into the design problem.
Developed with industry experts.
Plan for enough time to refine the model.
Budget for the design phase of the work.
6
•http://support.esri.com/datamodels
7
Project Design Methodology
Create
Design
Template
Design
Manage Using
ArcCatalog
Data
Dictionary
Report
Geodatabase Extract Tool
Geometry
Project
Analysis and
Design
Curve
Polycurve
Path
1..*
Complex edge feature class
Polyline
Ring
Road
Polygon
1..*
Field name
UML
Representation
XMI/
Repository
Template Model with
Schema Wizard
Data type
OBJECTID_1
OID
Shape
Yes
Single
Yes
Integer
Yes
ROAD_WORK_ID
Integer
Yes
OBJECTID
Integer
Yes
ENABLED
Integer
Yes
ROADNUMBER
Integer
Yes
Yes
ROADNAME
String
SOURCEYEAR
Integer
Yes
SOURCE
String
Yes
ACCESSSTATUS
String
Yes
PLANNEDCLASS
String
Yes
RECORDEDLE
String
Yes
SURFACE
String
Yes
The system identifier used by the
geodatabase to uniquely identify
the Reference Point.
The decimal representation of the
latitude of the Reference Point.
The decimal representation of the
longitude of the Reference Point.
The accuracy value as a range (+/-)
of the latitude and/or longitude.
The code and associated name
that represents the geometric
entity represented by the
Reference Point.
The code and associated method
that represents the method used to
determine the latitude and
longitude coordinates for the
Reference Point on earth.
The code and associated name
that represents the reference
datum used in determining latitude
and longitude coordinates.
The number that represents the
proportional distance on the
ground for one unit of measure on
the map or photo.
The calendar date (dd-mm-yyyy)
when data were collected.
The code and associated name
that represents the party
responsible for providing the
latitude and longitude coordinates.
The text that provides additional
information about the Reference
Point.
The measure of elevation (i.e. the
altitude), in meters, above or below
a reference datum.
The code and associated text that
describes the method used to
collect the vertical measure of a
Reference Point.
The measure of the accuracy used
to collect the vertical measure (i.e.
the altitude) of a Reference Point.
The code and associated name
that represents the reference
datum to determine the vertical
measure.
The code and associated text that
describes the process used to
verify the latitude and longitude
Longitude
Measure
Horizontal
Accuracy Measure
Geometric Type
Horizontal
Collection Method
Horizontal
Reference Datum
Source Map Scale
Number
Data Collection
Date
Coordinate Data
Source
Location
Comments Text
Vertical Measure
Vertical Collection
Method
Vertical Accuracy
Measure
Vertical Reference
Datum
Verification
Method
0
0
Element
Type
254
0
254
20
20
30
20
Integer
Yes
Single
Yes
120
0
0
0
Shape_Length
Double
Yes
0
0
SUBTYPE
120
List of defined default values and domains for subtypes in this class
Subtype
Code
Subtype
Description
Field name
Default value
Domain
120
Primary
ENABLED
1
EnabledDomain
130
Secondary
ENABLED
1
EnabledDomain
160
Abandoned
ENABLED
1
EnabledDomain
170
Obliterated
ENABLED
1
EnabledDomain
Example
Unique ID
Numeric
Numeric
49.1234, 50.10
112.23456, 135.98
Alphanumeric
+/- 10, +/- 25
Reference
Table (Domain)
001 = point
Reference
Table (Domain)
001 = Address
Matching, 012 =
GPS data
collection
Reference
Table (Domain)
001 = North
American Datum
1927
Reference
Table (Domain)
1:10,000, 1:100,000
Date
17/04/1999
Reference
Table (Domain)
001 = Alabama, 082
= EPA
Headquarters
Alphanumeric
Reference
Table (Domain)
+/- 5, +/- 10
Reference
Table (Domain)
001 = GPS, 010 =
Benchmark
Alphanumeric
Reference
Table (Domain)
001 = North
America Vertical
Datum of 1988
Reference
Table (Domain)
007 = verified to
map features, 010
= unknown
Reuse Existing Designs and/or
Create Tables/Feature Classes
Refine
Design
0
0
Data Elements—Reference Point Feature Class
Element Definition
0
0
EnabledDomain
Subtypes of Road
Geodatabase
Table 4:
Reference Point ID
Latitude Measure
0
1
SUBTYPE
Subtype field
Data Element
Precision Scale Length
Domain
SHAPE_LENG
Default subtype
I.
Allow Default
nulls value
Geometry
LENGTH
ROAD_WORK_
Load Data
I.
Table 4:
Data Elements—Reference Point Feature Class
Data Element
Element Definition
Reference Point ID
The system identifier used by the
geodatabase to uniquely identify
the Reference Point.
The decimal representation of the
latitude of the Reference Point.
The decimal representation of the
longitude of the Reference Point.
The accuracy value as a range (+/-)
of the latitude and/or longitude.
The code and associated name
that represents the geometric
entity represented by the
Reference Point.
The code and associated method
that represents the method used to
determine the latitude and
longitude coordinates for the
Reference Point on earth.
The code and associated name
that represents the reference
datum used in determining latitude
and longitude coordinates.
The number that represents the
proportional distance on the
ground for one unit of measure on
the map or photo.
The calendar date (dd-mm-yyyy)
when data were collected.
The code and associated name
that represents the party
responsible for providing the
latitude and longitude coordinates.
The text that provides additional
information about the Reference
Point.
The measure of elevation (i.e. the
altitude), in meters, above or below
a reference datum.
The code and associated text that
describes the method used to
collect the vertical measure of a
Reference Point.
The measure of the accuracy used
to collect the vertical measure (i.e.
the altitude) of a Reference Point.
The code and associated name
that represents the reference
datum to determine the vertical
measure.
The code and associated text that
describes the process used to
verify the latitude and longitude
Latitude Measure
Longitude
Measure
Horizontal
Accuracy Measure
Geometric Type
Horizontal
Collection Method
Horizontal
Reference Datum
Source Map Scale
Number
Data Collection
Date
Coordinate Data
Source
Location
Comments Text
Vertical Measure
Vertical Collection
Method
Vertical Accuracy
Measure
Vertical Reference
Datum
Verification
Method
Element
Type
Example
Unique ID
Numeric
Numeric
49.1234, 50.10
112.23456, 135.98
Alphanumeric
+/- 10, +/- 25
Reference
Table (Domain)
001 = point
Reference
Table (Domain)
001 = Address
Matching, 012 =
GPS data
collection
Reference
Table (Domain)
001 = North
American Datum
1927
Reference
Table (Domain)
1:10,000, 1:100,000
Date
17/04/1999
Reference
Table (Domain)
001 = Alabama, 082
= EPA
Headquarters
Alphanumeric
Reference
Table (Domain)
+/- 5, +/- 10
Reference
Table (Domain)
001 = GPS, 010 =
Benchmark
Alphanumeric
Reference
Table (Domain)
001 = North
America Vertical
Datum of 1988
Reference
Table (Domain)
007 = verified to
map features, 010
= unknown
Import and export
XML Schema 9.0
8
Implementation Process
Draft
Conceptual Design
Draft
Logical Design
Prototype
Design Engineering
Updated
Conceptual Design
Updated
Logical Design
Pilot Project
Database Engineering
Updated
Conceptual Design
Updated
Logical Design
Production
Deployment/Rollout
…Multipurpose Design
9
Basic GDB data model design
Powerful GDB concepts
–
–
–
–
–
–
–
feature datasets and classes
geometric networks
relationship classes
validation rules/data integrity
raster
Topology
Toolbox model builder
Bottom line: good performance
builds on good (simple but effective)
modeling
10
Tips and Tricks
 The data model team provides a set of
documents that help navigate the steps
involved between architecture, design, and
implementation of a geodatabase. These are
supporting guides to elements of the software
that are useful to data modelers.
 Also available for download on the data
models website.
11
What about Spatial Reference?
• Managed at the Feature Data Set level or
individually for stand alone feature classes.
• Once you create a Geodatabase the Spatial
reference is set and locked
• This is a part of database design
• Establishes integrity, and can solve projection
issues common to shapefile and coverage
integration.
What if I want to “unlock” it?
12
Geoprocessing Models
• Where does version 9.0 lead the data models?
• Geoprocessing models and data models.
• One package for data and process workflow…
13
Rasters in the Geodatabase
14
Raster Catalogs
15
A Tutorial for New Users of the
Marine Data Model
Alyssa Aaby, Dawn Wright
Oregon State University
Tutorial Purpose
• Assist in simple data entry into MDM
– Starting point for project work or specific database
design.
– Personalize MDM to fit your needs
• Support for Case Studies
• Laboratory exercise or module
• General publicizing
17
Entry Point on Web
dusk.geo.orst.edu/djl/arcgis
18
19
Tutorial Setup
• Tutorial divided into four sections
–
–
–
–
Basics
Setting Up the Geodatabase
Loading Data into the MDM Geodatabase
Adding the Geodatabase Features to your ArcMap
Project
20
(1) Basics
• Introduction to the ArcGIS MDM
– Why created
– Intro to geodatabases
– Helpful links
• Tutorial Objectives
– Apply, prepare and load
• Computer and Data Requirements
– Tested using ArcGIS 8.3 and 9.0
– Need MDM schema, Tutuila Island and XYBottle
shapefiles, Pago Pago 5m grid and XYBottle data
tables.
21
(1a) Views of Data
22
(2) Setting up the Geodatabase
• Downloading the MDM Geodatabase
• Downloading the Data
• Applying the MDM Model Schema to the
Geodatabase
23
(2a) Downloading the MDM Geodatabase
24
(2a) Downloading the MDM Geodatabase
• Tip #1: ArcCatalog does not always refresh
automatically. If you do not see the
ArcGISMarineReposit.mdb file in the Samoa
folder after you extract it, refresh ArcCatalog
by going to View-->Refresh.
25
(2b) Downloading the Data
(if additional test data sets needed)
26
The MDM Repository and Test Data
• All data contained in a
feature dataset must
have the same
coordinate system and
fit within the set spatial
extent
• Tutorial used: WGS
1984 UTM Zone 2S
27
(2c) Applying the MDM Model Schema to
the Geodatabase
• Use Schema Tool in
ArcCatalog
• Select coordinate
system and spatial
extent
• Tutorial used XYBottle
Data
28
(2c) Applying the MDM Model
Schema to the Geodatabase
• Tip #2: Use Import option and select a
shapefile/coverage with the largest extent
needed and desired coordinate system
• Tip #3: Make sure that the schema and your
data match exactly
29
(3) Loading Data into the MDM
Geodatabase
• Assess Your Data and Determine Your
Database Setup
• Personalizing the MDM to Fit the Data
• Loading Vector Data into the MDM
• Creating a Relationship
• Loading Raster Data into the MDM
30
(3a) Assess Your Data and
Determine Your Database Setup
• Most important, but also most time
consuming step
• Important things to consider:
– Which feature classes should the data go into?
– What are the attributes of each data set?
– Do you want to relate any of your data? If so,
through what key fields?
31
(3a.1) Matching Data with Feature Classes
32
(3a.2) Matching Spatial with Non-Spatial
XYBottle Spatial Data
– Feature class:
InstantaneousPt
– Attributes:
• RefID (Long Integer)
• Cast (Text, 50
Characters)
• Lat (Double)
• Long (Double)
• MaxDepth (Double)
– Will create a 1-to-1
relationship class
between the RefID
XYBottle Non-Spatial Data
– Table: create new
– Attributes:
•
•
•
•
•
•
•
RefID (Long Integer)
Cast (Text, 50 Characters)
MMDDYYYY (Date)
Temperature (Double)
Oxygen (Double)
Salinity (Double)
Phosphate (Double)
33
(3a) Determine the Database Setup
• Tip #4: Relationships between data columns
can only be established if attribute data type
is Long Integer
34
(3b) Personalizing the MDM to
Fit the Data
• Feature class
personalized to fit
XYBottle Data
• Field names were
added to the
InstantaneousPT
feature class
• Can add additional field
names later, but cannot
modify once data have
been added to those
fields
35
(3b) Personalizing the MDM to
Fit Your Data
• Tip #5: Make sure data types match up
exactly, or your data will not load
36
(3c) Loading Vector Data into the MDM
• Load data into feature class/table
• Match field names and data types
37
(3d) Creating a Relationship
38
(3e) Loading Raster Data into the MDM
• To add raster data (without ArcSDE):
– Can add standalone grid
– Or can convert grid to shapefile
• Convert Pago 5m grid to 3D shapefile
• Loaded data into MeshPoint feature class
39
(4) Adding the Geodatabase
Features to your ArcMap Project
• How to add the data in ArcMap
• How to query the data in ArcMap
40
(4a) How to add the data
1. Add the three
feature classes:
FeatureArea,
InstantaneousPoint
and MeshPoint,
from the
geodatabase.
2. Add the
Measurement
table.
3. Now you are ready
to query for
information through
the tables.
41
(4) How to query the data
• Sample query: How many points have a temperature of
30 °C ? (Larger issue: Effect of global warming on coral reefs)
42
Sample Result of query
• 423 (in orange) out of 4780
43
Summary:
Important Things to Consider
•
•
•
•
•
Coordinate system and spatial extent
Identifying any possible differences between
the schema and your data
Which feature classes should the data go
into?
What are the attributes of each data set?
Do you want to relate any of your data? If
so, through what key fields?
44
Summary of “Tips and Tricks”
• Tip #1: ArcCatalog does not always refresh
automatically. If you do not see the
ArcGISMarineReposit.mdb file in the Samoa folder
after you extract it, refresh ArcCatalog
• Tip #2: Use Import option and select a shapefile/
coverage with the largest extent needed and desired
coordinate system
• Tip #3: Make sure that the schema and your data
match exactly
– Ex: M value for MeshGrid feature class
• Tip #4: Relationships between data columns can
only be established if attribute data type is Long
Integer
• Tip #5: Make sure data types match up exactly,
otherwise, your data will not load
45
dusk.geo.orst.edu/djl/arcgis
46
Marine Animal Analysis
Applications
Marine Data Model
Pat Halpin, Ben Best, Ei Fujioka and
Michael Coyne
Duke University
Overview
• The role of a data model for Marine Animal
Analysis
• Applications
– Animal Tracking (telemetry location series)
– At-Sea Survey (observations & effort)
– Shore Surveys (beach counts & time)
• AnalysisTools
– Import
– Analysis
– Visualization
48
OBIS•SEAMAP
OBIS-SEAMAP
mapping marine megavertebrates
http://seamap.env.duke.edu
Ocean Biogeographic Information System - Spatial Ecological
Analysis of Megavertebrate Animal Populations
Historical-MAP
Field Projects
Ocean Biogeographic Information System
OBIS-SEAMAP
Future-MAP
sponsors
49
OBIS•SEAMAP
Current
OBIS-SEAMAP
Data Status
mapping marine megavertebrates
http://seamap.env.duke.edu
64 datasets - 280,243 records (1947 – 2004)
50
OBIS•SEAMAP
Current
OBIS-SEAMAP
Data Status
mapping marine megavertebrates
http://seamap.env.duke.edu
Internet Data Services
• Metadata
• Species profiles
• Download text (CSV)
• Download Shapefile
Future:
Geodatabase support
for desktop tool
development
51
Marine Animal Tracking
GIS Data Challenges
• 3 dimensional, moving observations are difficult
to relate to dynamic environmental variables
using available GIS data structures (~4D GIS…).
• Data sharing and internet applications are
limited by a lack of standardization.
• The development of new analytical tools and
extensions are limited by common data formats
and relationships.
52
Marine GIS Data Model
Implementation
Implementation of common data models is
enhanced when tool development makes the
benefit / cost worthwhile to the user.
Example: ArcHydro Data Model usage has
been enhanced with the development of
the ArcHydro Tools.
53
Marine GIS Data Model Implementation
Hierarchy
User Group
Data Model
Project
Data Model
User Group
Data Model
Project
Data Model
Inheritance
“Generic”
Marine Data Model
Marine
User
Group
Animal User
Data
Model
Group
Project
Data Model
54
Overview
• The role of a data model for Marine Animal
Analysis
• Applications
– Animal Tracking (telemetry location series)
– At-Sea Survey (observations & effort)
– Shore Surveys (beach counts & time)
• AnalysisTools
– Import
– Analysis
– Visualization
55
Example Research Application: 1
Animal Tracking (telemetry location series)
Sea Turtle Tracks (Caretta caretta)
Sea Surface Temperature (WCR)
Source: http://www.po.gso.uri.edu/SST/
Source: http://obis.env.duke.edu/datasets/ (Read & McClellan2004)
56
Marine Management Application
Optimizing fisheries closures in space and time.
Spatial optimization algorithms used to
select potential locations to reduce sea
turtle bycatch in the Atlantic swordfish
fishery.
D’Agrosa, C., A.J. Read, P. N. Halpin, M.A. Hall. (2004 - in prep.) Reducing the ecological
cost of the US Atlantic swordfish longline fleet: Tools for incorporating spatial distribution into
time-area closure design.
57
Animal Tracking (telemetry location series)
Turtles: Cayman Islands
T
Z
m mm
X
Y
Dive Profiles:
~4D Data (X,Y,Z,T m…m)
58
Marine GIS
Data Model
Can be thought
of as a
conceptual
“extension” of
GIS features to
better fit marine
applications…
Time Series
Location Series
Telemetry tracking
example…
59
Marine Data Model – Data Types
60
(Temperature or depth sensor…)
LocationSeriesPoint
(example: animal telemetry data)
(Temperature / Depth…)
(Value…)
61
Overview
• The role of a data model for Marine Animal
Analysis
• Applications
– Animal Tracking (telemetry location series)
– At-Sea Survey (observations & effort)
– Shore Surveys (beach counts & time)
• AnalysisTools
– Import
– Analysis
– Visualization
62
Example Research Application: 2
Marine Mammal Habitat Modeling
Sperm Whale: Physeter macrocephalus
Physeter macrocephalus
0 - 100% probability range
No threshold set for habitat
.vs non-habitat
Model output calculated for: oceanographic
conditions, August 5-12 1998
Data Sources: NEFSC & SEFSC
63
Example Research Application: 2
Marine Mammal Habitat Modeling
At-Sea
Surveys
Observations
Effort
InstantaneousPoints
TimeDurationLines
Data Sources: NEFSC & SEFSC
64
Example Research Application: 2
Marine Mammal Habitat Modeling
Sample points
vs. random points
InstantaneousPoints
(sampled along effort track…)
Data Sources: NEFSC & SEFSC
65
Example Research Application: 2
Marine Mammal Habitat Modeling
Relating spatio-temporal environment
66
Marine Data Model – Data Types
67
(Temperature or depth sensor…)
InstantaneousPoint
(example: At-Sea Survey Obs.)
(Temperature / Depth…)
(Value…)
68
(length / duration of effort)
(Temperature or depth sensor…)
TimeDurationLine
(Cruise/Run)
(Temperature / Depth…)
(ex: Beaufort Sea-State)
(example: At-Sea Survey Effort)
69
Relating InstantaneousPoints - TimeDurationLines
70
Overview
• The role of a data model for Marine Animal
Analysis
• Applications
– Animal Tracking (telemetry location series)
– Animal Survey (observations & effort)
– Shore Surveys (beach counts & time)
• AnalysisTools
– Import
– Analysis
– Visualization
71
Example Research Application: 3
SWoT
Turtle Nesting Beach Surveys
Site re-surveys over time…
Time
72
Marine Data Model – Data Types
73
TimeSeriesPoint
(ex: nesting beach resurveys)
(Value…)
74
Overview
• The role of a data model for Marine Animal
Analysis
• Applications
– Animal Tracking (telemetry location series)
– At-Sea Survey (observations & effort)
– Shore Surveys (beach counts & time)
• AnalysisTools
– Import
– Analysis
– Visualization
75
ArcGIS 9.x Developments
• ModelBuilder
• Geodatabase
Raster Support
• Python Scripting
76
Import Tools – Survey Data
Transfer
Data Manager(s)
Shapefiles for
OBIS-SEAMAP
Datasets
(Text)
OBIS Staff
Datasets Utility
Surveyors
Validation
Raw
data
Import
File
Sighting
Effort
Export
Import
Generate
Import
Shapefile
Populate
OBISOBIS-SEAMAP
Views for
SEFSC
Source: Ei Fujioka
Duke University & SEFSC
Shapefiles for
SEFSC
Oracle
Shared Folder
Users
(General Public)
Researchers
77
Analysis: Telemetry Data Filter
Enforces spatio-temporal rules
Speed, distance, depth, hours,
angle
(similar to topology rules…)
Ex: M. Coyne, Duke University & Seaturtle.org
78
Analysis – Data Extraction Tools
Models to automatically extract environmental data
layers for spatio-temporal analysis
Model: Get-SST
AML to Modeler conversion at ArcGIS 9.x
79
Visualization – Date Synchronization
80
Tools
Our goal…
Release a bundle of marine animal analysis
tools and model collections as soon as
possible…
http://seamap.env.duke.edu
81
Summary
• The role of a data model for Marine Animal
Analysis
• Applications
– Animal Tracking (telemetry location series)
– At-Sea Survey (observations & effort)
– Shore Surveys (beach counts & time)
• AnalysisTools
– Import
– Analysis
– Visualization
82
Marine GIS Data Model
Marine Animal Applications
Implications:
Allows explicit spatial & temporal relationships
to be used in geoprocessing and analysis
Allows for advanced tool development
83
OBIS•SEAMAP
mapping marine megavertebrates
http://seamap.env.duke.edu
Next…
84
Implementing Time Series with the
Marine Data Model
Michael J. Blongewicz
GIS Specialist
DHI Water & Environment
Portland, Oregon
mjb@dhi.us
www.dhi.dk
www.dhisoftware.com
86
Introduction
DHI Modeling Software
Water Resources - MIKE 11, MIKE SHE, MIKE Basin
Marine - LITPACK, MIKE 21, MIKE 3
Urban - MIKE Urban
87
Marine Data Model
• Presented a different kind of challenge.
– Multiple features
• Multiple depths
– Multiple Measuring devices
» Measuring multiple variables
– Example:
• Moored buoy with a CTD cable with multiple sensors at
every 10 m. At each depth one sensor is measuring
temperature and salinity and a second sensor is
measuring current speed and direction
88
Marine Data Model
X
TimeSeriesPoints
MarineID
1
2
3
Y
MarineCode
AAA
BBB
CCC
MarineID = 1
- 3.5
Measurement
MeasureID
1
2
3
4
5
MarineID
1
1
1
1
1
FeatureClass
TimeSeriesPoint
TimeSeriesPoint
TimeSeriesPoint
TimeSeriesPoint
TimeSeriesPoint
ZLoc
-3.5
-10.0
-13.0
-17.5
-21.5
Xloc
Yloc
- 10.0
- 13.0
Measuring Device
- 17.5
Measurement
- 21.5
Z
TimeSeries
FeatureID
3
3
3
3
3
TSType
TSTypeID
4
4
4
4
4
TSDateTime
12:00:00
12:20:00
12:40:00
13:00:00
13:20:00
TSValue
16.7
14.0
21.9
11.2
12.4
TSTypeID
1
2
3
4
5
Variable
CurrentSpeed
Salinity
Wave Height
Temperature
Wave Direction
Units
89
Marine Data Model
MarineFeature
FeatureClass:
TimeSeriesPoint
-MarineID : esriFieldTypeInteger
-MarineCode : esriFieldTypeString
-CruiseID : esriFieldTypeInteger
MarinePoint
ObjectClass:
Measurement
Measurement
-MeasureID : esriFieldTypeInteger
-FeatureID : esriFieldTypeInteger
-FeatureClass : esriFieldTypeString
-ZLocation : esriFieldTypeDouble
-XLocation : esriFieldTypeDouble
-YLocation : esriFieldTypeDouble
MeasurementPoint
TimeSeriesPoint
{GeometryType = esriGeometryPoint}
*
*
90
Marine Data Model
ObjectClass:
TSType
ObjectClass:
TimeSeries
TSType
-TSTypeID : esriFieldTypeInteger
-Variable : esriFieldTypeString
-Units : esriFieldTypeString
-IsRegular : DBoolean
-TSInterval : TSIntervalType
-DataType : TSDataType
-Origin : TSOrigins
TimeSeries
1
*
-FeatureID : esriFieldTypeInteger
-TSTypeID : esriFieldTypeInteger
-TSDateTime : esriFieldTypeDate
-TSValue : esriFieldTypeDouble
91
Marine Data Model
ObjectClass:
TSType
ObjectClass:
TimeSeries
TSType
-TSTypeID : esriFieldTypeInteger
-Variable : esriFieldTypeString
-Units : esriFieldTypeString
-IsRegular : DBoolean
-TSInterval : TSIntervalType
-DataType : TSDataType
-Origin : TSOrigins
TimeSeries
1
*
-FeatureID : esriFieldTypeInteger
-TSTypeID : esriFieldTypeInteger
-TSDateTime : esriFieldTypeDate
-TSValue : esriFieldTypeDouble
*
1
Measurement
ObjectClass:
Measurement
-MeasureID : esriFieldTypeInteger
-FeatureID : esriFieldTypeInteger
-FeatureClass : esriFieldTypeString
-ZLocation : esriFieldTypeDouble
-XLocation : esriFieldTypeDouble
-YLocation : esriFieldTypeDouble
92
DHI TimeSeries Manager
TS Editor
TS Plot
TS Tabular
Data
Access
Component
Data
Access
Bridges
Data Access Bridges
dfs
TimeSeries Controls
TS Object
ASCII
TS Toolbox
Gap
Gap
Filling
Filling
Gap
Filling
Transform
Regression
Double
Mass
Timeseries
Data
DB
......
Extrapolate
XML
Functionality
93
DHI TimeSeries Manager
Data
Access
Bridges
dfs
ASCII
DB
GeoDatabase Bridge
...
GDB
...
XML
94
DHI TimeSeries Manager
Arc Atmosphere
Arc Hydro
MIKE 21
MIKE GIS
Data Access Bridges
MIKE 11
TimeSeries Manager
ArcGIS
Arc Marine
Geodatabase
dfs0
MIKE Basin
95
Summary
• An organized GIS design and process results
in a successful implementation.
• Templates provide a starting point that we
simplify for project driven solutions.
• New tools provide rapid prototyping for your
project.
• New techniques, but basic GIS design
principles remain.
96