1. Models and Structures of ArcGIS UML and Data Modeling Elements

2. Model / Data Model
Model = representation of something in the real world, of a process in the real world - how the world WORKS
Data Model = representation of data or information ABOUT that something or process - how the world LOOKS
limited representation of reality
a discretization or partitioning of space
constructs for representation in a computer

3. Data Model usually a representation of the data collection process
FIELD … “grid”
OBJECT … “isoline”
FIELD or OBJECT … “geo-relational”
“Delauney triangulation” (alternative)

4. • partition areas based on “influence” of sample points (Thiessen polys)
e.g., trusted elevation benchmarks or VIPs, market area delimitation, rain gauge area assignment, etc.

5. 3 Data Models
geo-relational coverage (object view; from classic ArcInfo)
geo-relational shapefile (object view; from ArcView)
geodatabase (object-oriented; from ArcGIS)

6. Georelational Data Model: “Classic” ArcInfo and ArcView
command line interface
Unix, NT, Windows
ArcView as interface A B

7. Data Structure
the way in which the data model is represented in the GIS
concerned simply with what can be computed and what can’t
not tied to process at all
DEM/raster for field model
coverage/shapefile for ESRI geo-relational (object model)
contour for isoline variation on object model
TIN for Delauney triangulation/Voronoi model
geodatabase for OO geodatabase

8. Data Structures ArcInfo coverages ArcView shapefiles
ArcInfo grids, USGS DEMs
Images (e.g., georeferenced tiffs)
TINs
Geodatabases

9. ESRI Coverage as a Data Structure
Image courtesy of Louisville/Jefferson County Information Consortium, Kentucky

10. ESRI “Shapefile” .shp — shape format; the feature geometry itself
.shx — shape index format; a positional index of the feature geometry to allow seeking forwards and backwards quickly
.dbf — attribute format; columnar attributes for each shape, in dBase III format
.prj — projection format; the coordinate system and projection information, a plain text file describing the projection
.sbn and .sbx – spatial index
.xml — metadata in XML format

11. ArcGIS Icons ( Zeiler, pp. 65-71 )
yellow coverage
green shapefile
gray geodatabase

12. Geodatabase If coverages are apples … and shapefiles are oranges …
The Geodatabase can be your grocery bag…
ESRI Geodatabase Video (3:57 to 11:20)
Slide courtesy of Joe Breman, ESRI

13. Elements of the Geodatabase
Feature Datasets
Feature Classes
Relationship classes
Geometric Networks
Domains
Ranges
Coded Values
Topology
Tables
Metadata
And More!!!

14. Geodatabase Features and attributes as objects
Relationships among features
Validation or editing rules, behaviors
“Container” for
Vector, raster, tabular data
Relationships
Topology
Object Table
MS-Office

15. Relationships for a feature

16. Sharing on Steroids: ESRI Data Models for Geodatabase Templates
Pre-designed schema (skeleton) of
Objects
-Feature classes
-Tables
Relationships
Domains
Rules

17. Why Data Models & Gdb Templates?
Work with users & partners on practical design projects
Build useful ready to load geodatabases
Continue the process with feedback from real projects
Support & encourage standards

18. ArcGIS Data Models Administrative Boundaries Agriculture Basemap
Biodiversity/Conservation
Cadastre 2014
Defense/Intel
Energy Utilities
Environmental Regulated Facilities
Historic Preservation
Hydrographic/Navigation (IHO)
Local Government
Marine
Petroleum
Pipeline
System Architecture
Telecommunications
Transportation
Water Utilities
Water Resources (Hydro, Groundwater)
Forestry
Geology
Land Parcels

20. Arc Marine dusk.geo.orst.edu/djl/arcgis

22. Data Modeling for Spatial Analysis
What is spatial analysis?
"a set of methods whose results change when the locations of the objects being analyzed change"
Methods for working with spatial data
to detect patterns, anomalies
to find answers to questions
to test or confirm theories
deductive reasoning
to generate new theories and generalizations
Inductive reasoning

23. What is Spatial Analysis (cont.)
Methods for adding value to data
in doing scientific research
in trying to convince others
A collaboration between human and machine
How do we set up the framework for spatial analysis?
Data model to data structure

24. 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

25. Purpose of Arc Marine, Arc Hydro and others
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

26. Arc Marine Design Strategy
“Generic”
Marine Data Model
Inheritance
User Group
Data Model
User Group
Data Model
User Group
Data Model
As generic as possible… As exhaustive as possible… As temporally dynamic as possible…
Project
Data Model
Project
Data Model
Project
Data Model

27. Geodatabase Concepts Feature class Feature data set
ESRI's new data object-oriented data model
objects, features, behaviors
Geodatabase
collection of feature classes/data sets, rasters, TINs
all data in relational tables
behavior is coupled with features through rules (object-orientation)
Feature data set
Contains feature classes
defines topological role of features
has a coordinate system
Feature class
stored in a relational table
special field for geometric shape
geometric data incorporated into the database
Point, multipoint, segment, path, ring, polyline, polygon

28. Geodatabase Feature Class Geometries

29. ArcMarine Geodatabase
Overall Geodatabase
Feature
Dataset
Feature
Class
Table
Relationship
Class

30. Lists, flow diagrams, etc Objects and relationships
Modeling Process
(1) Conceptual Model
Lists, flow diagrams, etc
Real World
Objects and relationships
(2) Logical Model
Diagram in CASE Tool
(3) Physical Model
Database
Schema
(Object state)
Graphic courtesy of ESRI

31. Data Model Levels Reality Human-oriented Conceptual Model Increasing
Abstraction
Logical Model
Computer-oriented
Physical Model

33. (1) Conceptual - User’s View of Data

34. (1) Conceptual - User’s View of Data

35. Conceptual - cont.

37. (2) Logical - UML Unified Modeling Language
Diagrammatic notation = “visual language”...
For constructing a data model
Drawings, relationships constructed in Visio
Tools to input a drawing to ArcGIS
input data to the data model

38. From (1) Conceptual

39. To (2) Logical

40. UML Notation Zeiler pp. 97-99
a class is shown as a box
top part: name of class
lower part: attributes
methods associated with the class
lines connect boxes, indicate relationships

42. Graphic courtesy of Maidment et al., ArcHydro team

43. UML Notation ( cont. ) Abstract class Feature Class Food
specify subclasses underneath
no new instances
Feature Class
Specify subtypes underneath
Food
Veggies
Meats
Sometimes, a class that you define represents an abstract concept and, as such, should not be instantiated. Take, for example, food in the real world. Have you ever seen an instance of food? No. What you see instead are instances of carrot, apple, and (my favorite) chocolate. Food represents the abstract concept of things that we all can eat. It doesn't make sense for an instance of food to exist.
Similarly in object-oriented programming, you may want to model an abstract concept without being able to create an instance of it. For example, the Number class in the java.lang package represents the abstract concept of numbers. It makes sense to model numbers in a program, but it doesn't make sense to create a generic number object. Instead, the Number class makes sense only as a superclass to classes like Integer and Float , both of which implement specific kinds of numbers. A class such as Number , which represents an abstract concept and should not be instantiated, is called an abstract class . An abstract class is a class that can only be subclassed-- it cannot be instantiated.

44. Relationships Links between classes, shown as lines One to one
One to many
Many to many

45. Relationships (cont.) 1:1 - solid line
one record in Class A linked to one record in Class B
“is married to”
the class of state capitals linked to the class of states
1:n - solid line with * at one end
one record in Class A linked to any number of records in Class B
"owns"
the class of states linked to the class of area codes

46. Graphic courtesy of Maidment et al., ArcHydro team

47. Relationships (Arc Marine example)

48. Relationships (cont.) m:n - solid line with * at both ends
any number of records in Class A linked to any number of records in Class B
"has visited”
"was never married to"
the class of mountain lions linked to the class of wilderness areas

49. Relationships

50. Graphic courtesy of Maidment et al., ArcHydro team

51. Type Inheritance the parts and the whole depend on each other
White triangle
Class B inherits the properties (attributes, methods) of Class A
the class street inherits from the class transportation network
Solid diamond
the parts and the whole depend on each other
lecture
lab

52. Graphic courtesy of Maidment et al., ArcHydro team

53. A full view of the model, a work in progress, approaching beta release, the implementation goals of which include:
production of a common structure, a "geodatabase template", for assembling, managing, and publishing marine data in ArcGIS. Because the Unified Modeling Language code of the model is easily converted to an ArcGIS geodatabase, users can immediately begin populating the geodatabase rather than having to design it from scratch.
users can produce, share, and exchange data in similar formats
unified approaches encourage development teams to extend and improve ArcGIS software
extending the power of marine GIS analyses by providing a framework for incorporating behaviors in data, and dealing more effectively with scale dependencies
• providing a mechanism for the implementation of data content standards, such as the Federal Geographic Data Committee’s Hydrography Data Content Standard for Inland and Coastal Waterways, critical for the Coastal National Spatial Data Infrastructure.

54. Lists, flow diagrams, etc Objects and relationships
Modeling Process
(1) Conceptual Model
Lists, flow diagrams, etc
Real World
Objects and relationships
(2) Logical Model
Diagram in CASE Tool
(3) Physical Model
Database
Schema
(Object state)
Graphic courtesy of ESRI

55. (3) Physical
or XMI file

56. Using a Design Template Schema Wizard reads repository or XMI to create a geodatabase
The ‘Schema wizard’ is the CASE tool in ArcCatalog that is used to move the schema from an xml or a repository to a physical geodatabase. The first step before using this tool is to create an empty Geodatabase, or use an existing database as the starting point into which you will create or add new schema.

57. (3) Physical
or XMI file

58. Data Model Levels Reality Human-oriented Conceptual Model Increasing
Abstraction
Logical Model
Computer-oriented
Physical Model

59. Lists, flow diagrams, etc Objects and relationships
Modeling Process
(1) Conceptual Model
Lists, flow diagrams, etc
Real World
Objects and relationships
(2) Logical Model
Diagram in CASE Tool
(3) Physical Model
Database
Schema
(Object state)
Graphic courtesy of ESRI

60. Arc Marine Data Model Exercise
Exercise and data at
dusk.geo.orst.edu/djl/arcgis/ArcMarine_Tutorial/
What to turn in:
Screen snapshot of what your ArcMap session looks like at the end of Section 4 (including dynseg referencing)
Answers to 2 simple questions at end of Section 4 (which cruise? which vehicle?)
Can put all of the above in a single MS-Word document, labeled with your NAME please!
Due by or dropbox, April 27th, 6:00 p.m.

61. Geoprocessing Models Model Builder diagrams for workflow
Raster in
WGS84
extract_west
Shifted_west
Output
grid name
Extract_east
Extract by
Rectangle (2)
Extent
Shift
Rectangle (3)
Rectangle
Mosaic
Geoprocessing models can be used to create schema, and are most commonly used to store work flow processes. Once you have a data model design that you are happy with, the work flow, or GIS functionality that you employ on the data, it can be preserved in this environment, and more easily shared with others. Notice the toolbox storing the Geoprocessing model can be represented and appended to the Geodatabase itself.

62. Use of a Data Model in an Analysis Model Model Builder geoprocessing diagrams for workflow
Geoprocessing models can be used to create schema, and are most commonly used to store work flow processes. Once you have a data model design that you are happy with, the work flow, or GIS functionality that you employ on the data, it can be preserved in this environment, and more easily shared with others. Notice the toolbox storing the Geoprocessing model can be represented and appended to the Geodatabase itself.

63. Gateway to the Literature
Arctur, D. and Zeiler, M., 2004, Designing Geodatabases, ESRI Press
Lowe, J.W., Flexible data models strut the runway. Geospatial Solutions, 13(2):
Maidment, D.R., Arc Hydro: GIS for Water Resources, ESRI Press, 203 pp. w/CD.
Li, X. and M.E. Hodgson, Vector-field data model and operations. GISci. Rem. Sens., 41(1): 1-24.
Wright, D., Blongewicz, M., Halpin, P., and Breman, J., Arc Marine: GIS for a Blue Planet, Redlands: ESRI Press, 2007.
In Digital Earth or dusk.geo.orst.edu/djl/arcgis/book.html

65. Objects and Features Object (real world) Feature (spatial context)
in ArcGIS an object is non-spatial
it is NOT a point, line, or area
it has no geographic location
it has no shape attribute in its table
Drainage network, ship, vehicle, … customer, lake, house, etc.
Feature (spatial context)
an object that has geographic location
a point, line, area, TIN, raster