Databases

1
GeoDatabases
Presented by Reza Wahadj University of
California , San Diego (UCSD)
2
Spatial Types OGC Simple Features
Composed
Type
SpatialReferenceSystem
Geometry
Relationship
GeometryCollection
Point
Curve
Surface
Polygon
MultiSurface
MultiCurve
MultiPoint
LineString
Line
LinearRing
MultiPolygon
MultiLineString
3
Overview

• The Geodatabase Data Model
• Designing and Building Geodatabases
• Editing, Long Transactions and Versioning

4
Integration
ArcCatalog / ArcMap / Custom Application
GeoDataObjects
SDE
SDE for Coverages
ArcStorm
Shapefiles Grids TINs Images
MapLibrary
Coverages
5
The ArcInfo 8 Geodatabase

• A new object oriented geographic data model - all
  relational data storage using ArcSDE
• Versioning and long transactions
• Data Access Objects for application software
  developers
• Component based technology (COM)

6
Elements of a Geodatabase
Geometric Network

• Feature Dataset

Relationship Class
Feature Class
Annotation Class
Object Class
The Geodatabase Data Model
7
Elements of a Geodatabase

• Objects , Object Classes
• Features , Feature Classes
• Feature Datasets
• Validation Rules, Domains
• Relationships , Relationship Classes
• Spatial References
• Geometric Networks

The Geodatabase Data Model
8
Objects and Object Classes

• An object is an instance of an object class
• All objects in an object class have the same
  properties and behavior
• An object can be related to other objects via
  relationships

The Geodatabase Data Model
9
The Geodatabase Data Model
10
Features

• Spatial object
• Location
• Attribute of type Geometry
• Spatial relationships
• Instance of a feature class

The Geodatabase Data Model
11
Feature Classes

• Same type of geometry
• Same type of spatial reference system
• Store spatial objects (features)

The Geodatabase Data Model
12
Feature Datasets

• Container
• Same spatial reference
• Analogous to a coverage

The Geodatabase Data Model
13
Object and Feature Behavior

• End users and data modelers can
• Instantiate classes with predefined behavior
• Control the default value and acceptable values
  for any attribute in a class (domains)
• Partition the objects in a class into like groups
  (subtypes)
• Control the general and network relationships in
  which an object can participate
• Rule based, no programming required

The Geodatabase Data Model
14
Controlling and Specifying Object Behavior
Custom Objects
Connectivity Rules
Relationships
Domains and Validation Rules
Subtype Specification
Feature Type Selection
The Geodatabase Data Model
15
Subtypes

• Similar groups of objects
• Lightweight classification mechanism
• same attributes and behavior
• different default values and domains

The Geodatabase Data Model
16
Validation Rules

• Attribute domains
• Connectivity rules
• Relationship rules
• ... are stored in the Geodatabase
• Custom rules
• ... are code based

The Geodatabase Data Model
17
Validation Rules

• The editor in ArcMap provides tools to test
  object validity
• Rules are evaluated, under user control, during
  object editing
• Create a new selection showing all invalid
  objects within a specified area
• Restrict the current selection to invalid objects
  only

The Geodatabase Data Model
18
Domains

• A named set of acceptable values for a field
• Types of domains
• Range
• Coded values
• Can be shared across multiple object classes

The Geodatabase Data Model
19
Domains

• Split policies
• Default value
• Duplicate
• Geometry ratio
• Merge policies
• Default value
• Sum values
• Weighted average

The Geodatabase Data Model
20
Domains in ArcMap

• Attribute editor uses domain values
• Identifies illegal values
• Provides legal value lists

The Geodatabase Data Model
21
Relationships

• Association between two objects
• The Geodatabase maintains the referential
  integrity of relationships when objects are
  deleted
• Related objects can message each other
• eg. move, rotate

The Geodatabase Data Model
22
Pole Attachments
Composite relationship pole to transformer
Select a pole and move it
the transformer follows
The Geodatabase Data Model
23
Relationship Validation Rules

• Subtype combinations
• Type of relationship
• Cardinality ranges

The Geodatabase Data Model
24
Geometric Networks

• Models a network relationship between a set of
  feature classes
• Each feature class has a topological role in the
  network (junction or edge)
• A network may have multiple feature classes in
  the same topological role

The Geodatabase Data Model
25
Geometric Networks
Valve
Geometric Network
Feature Classes
Service
Feed
Lateral
Main
The Geodatabase Data Model
26
Geometric Networks

• A geometric network and its feature classes must
  all belong to the same feature dataset

The Geodatabase Data Model
27
Feature Datasets and Geometric Networks
FD
FD Feature Dataset GN Geometric Network FC
FeatureClass OC Object Class J Junction E
Edge
Water
GN
Water
FC
FC
FC
FC
FC
Feed
Main
Lateral
Service
Valve
J
E
E
E
J
The Geodatabase Data Model
28
Network Model

• A geometric network has an associated logical
  network
• Network features are associated with logical
  network elements

The Geodatabase Data Model
29
Geometry and Connectivity

• Geometric network contains features and geometry
• Logical network contains elements and
  connectivity
• Connectivity established via geometric
  coincidence

The Geodatabase Data Model
30
Network Analysis

• Connectivity tracing
• Cycle detection
• Establishment of flow directions
• Upstream and downstream tracing
• Isolation tracing
• Trouble call tracing

The Geodatabase Data Model
31
Multiple Approaches Possible

• The Build Using Existing Data approach
• The Define in ArcCatalog approach
• The Define Using CASE and UML approach

Designing and Building GeoDatabases
32
Build Using Existing Data Approach

• Use ArcCatalog and ArcToolbox to load coverages
  and shapefiles
• Use ArcCatalog to refine and extend loaded
  feature classes
• build network topology
• add domains and rules

Designing and Building GeoDatabases
33
Define in ArcCatalog Approach

• Use ArcCatalog to define new empty object
  classes.
• Define validation rules.
• Use the object editor and object loaders (in
  ArcMap) to populate your feature classes.

Designing and Building GeoDatabases
34
Define Using UML / Case Tools Approach
Supports the systematic design of large systems

• Use UML to define your domain object model, based
  on the generic Geodatabase object model.
• Use a UML Case Tool - eg. Visio, Rational Rose to
  specify the UML model.

Designing and Building GeoDatabases
35
Versions

• Named state of the database
• Multiple coexisting versions
• Differ in row state

Editing, Long Transaction and Versioning
36
Versioning
Default As Built
Electric Net

• Default version
• A user can work with any version

Editing, Long Transaction and Versioning
37
Multi User Editing

• Versioned Geodatabase
• Modify any version
• Only see your own changes
• Temporary child version
• When the Edit Session is saved the temporary
  version is posted

Editing, Long Transaction and Versioning
38
Direct Multi User Editing
Editor B
Editor A
Editor C
Editing, Long Transaction and Versioning
39
Conflict Resolution
Conflicts are automatically detected
Conflicting FeatureClass
Options to resolve conflict
Conflicting feature(s)
Versions
Conflicting field
Editing, Long Transaction and Versioning
40

• CASE and UML
• Using CASE and UML for design and building a
  Geodatabase
• Custom Object Development
• Using ESRI code generation and schema wizards for
  building custom objects
• Application Development
• Using ESRI Geodatabase Access Objects

41
Detailed Sessions

• Using ArcCatalog to design and manage
  Geodatabases
• Working with versions in ArcInfo 8
• Working with networks in ArcInfo 8

42
Detailed Sessions

• Tuesday 14.00 Uhr C122
• Tina Kapka, ESRI Redlands An Overview of
  ArcInfo 8 Geodatabase
• Wednesday 14.00 Uhr C122
• Tina Kapka, ESRI Redlands Object Concepts What
  ESRI users should know

43
Spatial Relations

• Equals same geometries
• Disjoint geometries share common point
• Intersects geometries intersect
• Touches geometries intersect at common boundary
• Crosses geometries overlap
• Within geometry within
• Contains geometry completely contains
• Overlaps geometries of same dimension overlap
• Relate intersection between interior, boundary
  or exterior

44
Contains Relation
45
Touches Relation
46
Spatial Methods

• Distance shortest distance
• Buffer geometric buffer
• ConvexHull smallest convex polygon geometry
• Intersection points common to two geometries
• Union all points in geometries
• Difference points different between two
  geometries
• SymDifference points in either, but not both of
  input geometries

47
Convex Hull and Difference Methods
48
Grid Index (multi-level)
49
Point and Region Quadtrees
50
R-tree
51
Minimum Bounding Rectangle