GIS Data Models and

Geodatabase

CEB 809 - Lecture 1

Dr. Joeli Varo

Assistant Professor in Urban and Regional Planning
Conten • Quality management of spatial data
ts: • Common Issue
• What is it?
• GIS data models and formats
• ArcGIS Geodatabase and Advantages
• Geodatabase:
• What is it?
• Key Elements of a Geodatabase
• Designing a Geodatabase
• Topology in ArcGIS
• Spatial Adjustment / Data Alignment and Management Overview (Georeferencing
Vector Data)
Common issues
on Lack of
Quality
Management of
Spatial Data Recurring data integrity and management issues
when working with vector data:
• Different data compilation techniques or data
sources used
• Editing methods to help ensure spatial integrity
were not used
• Features created or updated at different points
in time
• Features were created at different map scales
• Different and/or badly defined Map projection
and coordinate system
 GIS: Digital
Representati
on of the
Real World
• In a GIS we can represent/model real
world objects and phenomena in
formats that can be stored, handled
and displayed in a computer.

• The two most commonly used DATA

MODELS for representing the real world
objects are VECTOR and RASTER data
models

• The selection of the model determines

how the real world is modeled in the GIS
and how useful it is for spatial analysis
and mapping
 Raster and
Vector Data
Model
REAL WORLD

GRID RASTER VECTOR

Real world is represented in Real world can be represented and
continuity as a grided matrix. The modelled as homogeneous and
location of each grid cell (pixel) is discrete features. Features can be
defined by row and column with points, lines or polygons
associated attribute value.
GIS Data
Models

• A GIS utilizes a layer-based

geographic information model for
characterizing and describing our
world.

• Each layer has a specified geographic

representation. For example,
individual geographic entities can be
represented as VECTOR features
(such as points, lines, and polygons);
as imagery using rasters; as surfaces
using features, rasters, or TINs; and
as descriptive attributes held in
tables.

• Geographic information layers such

as those described here are
represented in ArcGIS using
specific spatial data formats
 Changes
on Spatial
Data
Manageme • Methods for storing spatial data has changed with time and technology
nt • Many different data formats are used to store and manage spatial data and they
have been developed to work with specific software (Stability Vs Innovation):

 Simple, file based Vs Complex database structures

 Open, community regulated formats Vs Proprietary formats
 Supporting georeferenced coordinate systems Vs Not Georeferenced
 Semantic Depth: Shallow and fixed Vs Flexible and deep
 Topology: Simple Vs Sophisticated
 Desktop-oriented Vs Client-Server based
GIS Data
Formats

VECTOR TABLE
 Text Files.  Plain Text, Comma
 DWG and DXF Formats Delimited files
 DBase Format
 Shape Files
 Excel Worksheets
 File Based, and Personal Geodatabases
 Desktop-Oriented
 Enterprise-Scale Geodatabases
Database Formats
 Web Feature Services
 Enterprise Scale, Server-
Oriented Databases
RASTER
 8-bit Gray Scale Images / Color Mapped Images: GIF, and PNG
 True-Color, Multi-Band Images: TIFF / GeoTIFF
 Compressed Image Formats: Jpg Wavelet Compression, SID files and
JPEG2000
 Deeper Raster Formats: IMG / GRID.
 Image Map Services : (WMS)
 What is a • Organised collection of data/information
Database? • Basic example – excel spreadsheet

• More complicated/larger collections stored

in database management system eg.
• Microsoft Access, MySql etc
• Facilitates searching, queries, sharing

Source: http://www.lightenna.com/sitefiles/lightenna.com/simple-client-server.gif
 What is a • Sets of related tables containing data

Relational • Uses “ primary key” attributes to uniquely

Database? identify each row in a table

• “foreign key” to link to primary keys in other

tables containing related information

• Reduces redundancies and inconsistencies

• Efficient searching and querying Source: http://exonous.typepad.com/mis/relat.gif

Source:
http://www.awi.de/fileadmin/user_upload/Research/Research_Divisions/Geosciences/Marine_Geochemist
Source: http://pubs.usgs.gov/of/2005/1428/richard/fig6.gif ry/Marine_GIS/intern_externe_Daten.gif
 What is a
Geodataba
se?
At its most basic level, an ArcGIS geodatabase is a
collection of geographic datasets of various types
held in a common file system folder, a Microsoft
Access database, or a multiuser relational DBMS
(such as Oracle, Microsoft SQL Server, PostgreSQL,
Informix, or IBM DB2).
Geodatabas
e
 ESRI
Geodataba
se
• Core ArcGIS data model

A comprehensive model for representing

and managing GIS data

• A physical store of geographic data Geodatabas

 Scalable storage model supported on
e
different platforms

• Efficient managing, access, and storage of

spatial data
 Types of 1. Personal Geodatabase

Geodatabases • Single user editing ArcGIS

in ArcGIS
• Stored in MS Access

• Size limit of 2 GB

2. File Geodatabase

• 1 TB per table Personal

File Enterprise
Geodatabase
Geodatabase Geodatabase
• Cross platform

3. Enterprise Geodatabase Oracle

SQL Server
• Stored in an enterprise DBMS DB2
Informix
PostgreSQL
• Supports multi-user editing via versioning

• Large complex datasets

 Types of
Geodatabses
in ArcGIS

* By default; option to have 256 TB per

table
 Slide Title

Advantage • Essentially no size limitations: vector and raster

s of Using stored in same geodatabase.
a • Centralized data storage
Geodataba • Support for advanced feature geometry
se
• Accurate data entry and editing through the use
of subtypes, attribute domains, and validation The geodatabase is built on an
rules extended relational database:
• Base relational model
• Geodatabases can be created and managed
easily using the standard tools in • Relational integrity
ArcCatalog, and ArcMap provides simple •Base short transaction
. tools to work with geodatabases
model
• Integrated data management policy covering all •Supports continuous, large
data datasets
• Simplify support and maintenance, and reduce •Reliability, Flexibility,
costs. Scalability
 Slide Title
Geodatabase:
Data
Management
Approach Editing and data compilation
• Rich set of editing tools

• Maintain spatial and attribute integrity

Versioning workflows
• Undo and redo edits

• Multiple users editing the same data

Archiving

• Distributed data management

Robust, customizable
framework
• Build and manage your own specific
GIS solution
Overview of
Geodatabas • The geodatabase contains three primary dataset types:
es • Feature Dataset

• Features Classes / Rasters

• Tables (Object Classes)

• Geodatabase is a collection of datasets

• Within a geodatabase it is possible to

organize these datasets using advanced tools
to model GIS behavior (to maintain data
integrity, and work with spatial relationships)
such as:

• Topology,
• Networks, domains, subtypes
and relationship classes
• Annotation, Dimension
What is an
object in a

geodataba
se?
 How do
objects
relate in a
geodataba
se?
What is an
attribute
table?

Record
 Slide Title
Key
•
Elements of Data Formats:
• Spatial and non-spatial information
a (with or without geometry)
• Vector, Raster, Table
Geodatabas • Vector Data can be:
• Points
e • Lines
• Polygons
• Annotation
• Elements:
• Feature and Raster Datasets
• Feature Classes (“Layers”)
• Subtypes
• Attribute Fields
• Domains
• Behaviours defining rules and
relationships between elements:
• Relationship classes
• Geometric networks
• Topology
• Network datasets
• Toolboxes
• Tools
• Models
• Scripts
 Slide Title
Key
Elements of
a
Geodatabas
e
 Key
elements of
a
Geodatabas
e:
EXAMPLE 1
– Groceries
Store
 Key
elements of
a
Geodatabas
e:
EXAMPLE 2
– Land Use
 Slide Title

Spatial and • Feature class tables have one or more

non-spatial columns that store feature geometry.
attribute
• Nonspatial tables contain only attribute data
tables
(no feature geometry) and display in
ArcCatalog with the table icon . They can
exist in a geodatabase as stand-alone
tables, or they can be related to other tables
or feature classes.

A feature class table : each row has a geographic column

 Slide Title

Feature Classes
and Feature
Datasets Feature
• A feature class is a geographic feature including Dataset
points, lines, polygons, and annotation feature class.

• Feature classes may exist independently in a

geodatabase as stand-alone feature classes or you Feature
can group them into feature datasets Class

• A feature dataset is composed of feature classes

that have been grouped together so they can  Builds on the Relational Model
participate in topological relationships with each  A feature is an instance of a
other. All the feature classes in a feature dataset
feature class (spatial object)
must share the same spatial reference (or coordinate
system). Feature datasets also contain geometric  Extended the relational model
networks, topologies, terrains, etc… (Geometry attribute type)
 Slide Title

Raster • V. efficient storage and access

Datasets
• Support for many raster formats

 Tiff, bmp, GRID, among others

• Attribute field in a table

 Scalable storage model supported on different

platforms

• Mosaic dataset

 Data model for managing raster collections

 Stored as a catalog, viewed as a mosaic

 Advanced querying and processing

 Slide Title

Domains and • Subtypes and domains are used to categorize and control the integrity of new
Subtypes data attributes entered into the geodatabase

• Subtype: subset of a field type in a feature class – If there are entry points in your
database that share similar characteristics you can group them in subtype. For
example, if object A and B have the same values/codes for Field x, y, and z,
group them in the same subtype.

• Domains: rules that describe the legal values of a field type or subtype (coded or range values)
Domain
Subtype
Highway
Field Type
Primary
Major
Arterial
Road_Type
Secondary Minor
Arterial

Local
Tertiary

Track, Etc..
 21

Domains • Describe the legal values of a field type

• Used to ensure attribute integrity

• Defined at the geodatabase level

• Types of domains:

• Range:

• Valid values between a min / max

range

• A tree can have a height between 0

and 300 feet

• A road can have between one and eight lanes

• Coded Value

• Valid values chosen from a set list

• A tree can be of type oak, redwood, or plain

• A road can be made of dirt, asphalt, or

concrete
Subtypes
• Categorize objects or features into groups

• Share the same attributes

• Defined at the class level

• Select a field to base the subtype on:

• Short or long integer field

• Can have different default values and domains for

each field

• Can define behavior rules between subtypes

 Slide Title

Spatial • In the geodatabase, the relationship between two object classes is stored in a
Relationship relationship class.

• Relationship classes allow you to create an association between two tables

based on common field values.

1 to 1

1 to Many

Many to Many
 Accuracy Accuracy in the Data: 1:1000 ± 50 cm
1:2,500 ± 1.25 m
and • Scale of source map determines accuracy 1:5,000 ± 2.5 m
Precision in 1:25,000
1:50,000
± 12.5 m
± 25 m
a Precision: 1:250,000 ± 125 m

Geodatabas • Ability to store the accuracy into a database. The Precision is a “multiplier”
e to provide digits of precision after the decimal place for the coordinates:

Significant digits
Geodatabase 0-10 precise digits

Cluster Tolerance:
• Distance that determines the range in which features are made coincident

 ArcGIS calculates the minimum value as default

 Minimum depends on precision of Feature Dataset spatial reference
 Units are same as Feature Dataset
 Errors smaller than tolerance are not reported
 Slide Title

Geodatabase: • A comprehensive model for representing and managing GIS data

Summary
• Main Advantages:

 Control the default value and acceptable values for any

attribute. (Domains)
 Partition the objects into like groups. (Subtypes)
 Instantiate classes with predefined behavior. (Dimensions and
Annotation)
 Control the general relationships in which an object can
participate. (Relationship Classes)
Geodatabas
e: Summary Feature

Classes

Domain

Topolog Tabl
y Raster e

Feature Persona
Subtypes
Dataset l Gdb
s
Geodatab
•
ase Effective GIS implementation requires good database design

Design • Design is the process where:

 Goals are defined
 Design alternatives are identified, analyzed and evaluated
 Implementation plan is agreed upon

• A functional, well-organized database:

 Satisfies objectives and supports organization
requirements
 Contains all data but not redundant data
?
 Organizes data so that different users access the same
data
 Accommodates different views of data
 Appropriately represents, codes and organizes geographic
features
How to develop a • Designing a geodatabase model or schema is probably
geodatabase? the most important activity to start the implementation
of any GIS analysis and/or GIS project.

• A database model basically says what different

elements (data) it will have and how they will relate to
each other (rules).

• It is an iterative process
 Slide Title

Design Conceptual Design of a Database Model:

Phases 1. Identify information products and/or “need to know” questions (what
and 10 data are available, which products will be produced, etc..)
2. Identify the key thematic layers and feature classes based on
steps information requirements
3. Detail all feature classes
4. Group feature classes into datasets (logical collections)

Logical Design of a Database Model :

5. Define attribute database structure and behaviour for descriptive
attributes, (e.g. (feature types, table, raster, subtypes, domains,
relationships, etc …)
6. Define spatial properties of datasets, e.g. using rules
7. Propose a database design / schema

Learn more about

the ten steps of the Physical Design of a Database Model:
Geodatabase
Design Process: 8. Implement, prototype, review and refine schema design
https://desktop.arcgis.com/
en/arcmap/latest/manage-d 9. Design workflows for building and maintaining each layer
ata/geodatabases/geodatab
ase-design-steps.htm 10. Document design using appropriate methods

Source: Washington University: Geodatabase Design Process – Ten Steps

 Slide Title

Design Conceptual data modeling or conceptual database design is the

first step to build a geodatabase. It includes the following tasks:
Phase 1:
Conceptual 1. Identify information products and/or “need to know”
Data questions: Clarify the “why” it is being created – what are the
Modelling objectives or decisions it will support, which information
products are expected, and questions that need to be
answered.
2. Identify knowledge sources: for example, through collection
of existing geodatabase models that can be replicated, review
of academic articles and reports, and interviews with experts.

What is a geodatabase schema?

Watch this video

Available ESRI Geodatabase Data Models Templates:

http://support.esri.com/en/knowledgebase/techarticles/detail/40585
https://support.esri.com/en/technical-article/000011644
 Slide Title

Design Documenting Geodatabase Design and Schema

Phase 1:
Make data layers and patterns visually clear
Conceptual (many methods):
Data
Modelling • Whiteboard, paper drawings
• Database design document
• Classic layer diagrams
• UML Models (ESRI CASE, ArcGIS
Diagrammer,etc..)

:
 Design After a few consultations with experts in phase 1, it should
Phase 2: have an agreement on all the data it should have in the Example of a geodatabase ER diagram
schema.
Logical
Design The next step is to design an Entity-Relationship
Diagram (E-R Diagram). In this diagram “Entities” or
Feature Classes are represented in boxes and the
relations between them or “relationship classes” are
represented through arrows.

Microsoft Visio is a software that can be used to design

ER Diagrams

Learn more about logical design and E-R

Diagram:
https://www.youtube.com/watch?v=ZBgXb6
6Ckz0&list=PLCjqksNpDZje9yUNxmOpcvC
tvFw0kjpOo&index=15&t=0s
Source:
https://desktop.arcgis.com/en/arcmap/latest/manage-data/using-sql-
with-gdbs/overview-geodatabase-system-tables.htm
 Design patterns

Geodatabas
e design
involves a
• Suitable data model for your organization’s
series of requirements
trade-offs
• Right balance in the model for data integrity, cartographic production, and
information access

• Data model effectiveness is also often driven by budgetary constrains and the
use of existing data
 Your Turn:
Thinking in
Layers
Look at this image and try to identify possible layers
or feature classes

Guiding Questions:
•What are the main physical elements you see in this satellite image? (example:
roads, rivers, etc)
•What is the information present in the space? What are the non-visible
elements? (example: Educational background of households, health, pollution,
etc)
•What are the different “events” that can happen in this space? (Example: natural
disasters, congestion, etc)
 Your Turn:
Thinking in
Define Feature Datasets and Feature Classes
Layers • Identify thematic layers
• Group these different elements into “layers” or “feature classes” and “datasets”–
for example “transportation”, “water”, “land use”
• Fill Table 1 with the identified datasets and feature classes

Table 1: Geodatabase Conceptual Design 1

Feature Datasets Feature Classes (Layers)
1.

2.

3.
Topolog
• Topology expresses the spatial relationships
y between connecting adjacent or coincident
vector features (points, polylines, and
polygons)

• Topology is necessary to ensure data integrity

(e.g. no gaps and/or no overlapping between
polygons) for carrying out spatial analysis and
queries.

• Two primary types of topology in ArcGIS:

• Map topology: editing simple features

(.shp) that overlap or touch each other in
ArcMap. It is temporary and only lasts for
the duration of your edit session

• Geodatabase topology: defines a set of

behaviours and rules (32 rules) about the
relationships between feature classes in a
feature dataset.
Topology Examples
Errors • Topology errors represent violations of topology rules.
Need to edit the features to remove the topology errors
(e.g. two lines in a roads vector layer that do not meet
perfectly at an intersection).

• Topological errors can be grouped according to whether

the vector feature types are polygons or polylines:

• Polygon features can include unclosed

polygons, gaps between polygon borders Undershoots (1) occur when digitised vector lines
(silvers) or overlapping polygon borders. that should connect to each other don't quite touch.
Overshoots (2) happen if a line ends beyond the line
• Polyline features that do not meet perfectly at a it should connect to.
point (node) – Undershoots & Overshoots. These
errors are called 'dangling nodes' at the end of
the lines. Dangling nodes are acceptable in
special cases, for example if they are attached to
dead-end streets.

• Topological errors break the relationship between

features. These errors need to be fixed in order to be
able to perform spatial analysis
Slivers (3) occur when the vertices of
two polygons do not match up on their borders
Topology Examples
Errors • Topology errors represent violations of topology rules.
Need to edit the features to remove the topology errors
(e.g. two lines in a roads vector layer that do not meet
perfectly at an intersection).

• Topological errors can be grouped according to whether

the vector feature types are polygons or polylines:

• Polygon features can include unclosed

polygons, gaps between polygon borders
(1)Topological editing to detect shared boundaries, when
(silvers) or overlapping polygon borders. moving vertices. When moving a vertex, all features that
share that vertex are updated.
• Polyline features that do not meet perfectly at a
point (node) – Undershoots & Overshoots. These
errors are called 'dangling nodes' at the end of
the lines. Dangling nodes are acceptable in
special cases, for example if they are attached to
dead-end streets.

• Topological errors break the relationship between

features. These errors need to be fixed in order to be
able to perform spatial analysis
(2) To avoid polygon overlaps, when a new polygon is digitised
(shown in red) it is clipped to avoid overlapping neighbouring
areas.
Topology
Examples
Tools
• ArcGIS provides a number of tools for defining,
creating and fixing topology.

• First you need to create and define topology

rules inside your geodatabase (ArcCatalog).
This step normally implies defining rules and
which features will participate in the topology .
(1)Topology toolbar in ArcMap

• When your set of topology rules are validated

you can edit your features and fix topology (2)Topology toolbar in ArcMap

errors in ArcMap by using the topology errors in

ArcMap by using the topology toolbar. You can
also use geoprocessing tools (ArcToolbox) or
building, analyzing, managing, and validating
topologies.

(3) Geprocessing tools (ArcToolbox).

Adjustment
Process
Create Link
Elements
• Create Links
Set Adjustment
• Set Adjust source Source

• Set Adjustment Method Set Adjustment

Method
• Preview

• Adjust

Preview

Adjustment

Adjust

data
Adjustment Methods:
Transformations

Shift data between coordinate systems and/or in coordinate space

• Shift data between coordinate systems: Project GP tool

• Digitize coordinates to real world

• CAD coordinates to real world

 Affine: min. 3 displacement links, can scale, skew,

rotate and translate data

 Similarity: min. 2 displacement links, can scale,,

rotate and translate data but will not introduce

skew or rescale the axis
 Projective (most complex): iincludes the

approximate scale, the RMS error, and the

equation parameters
 Adjustment
Methods:
Rubbersheet
• Aligns local data: the surface is literally stretched by moving the feature in
a piecewise transformation that preserve straight lines
• Integrating data from different scales and sources

• Integrate 250K Hydro features into 50K data

• Align Tiger lines with local roads

Adjustment
Methods:
Edge Snap
• Aligns features along the edge of one layer to features along an
adjoining layer
• It ensures that all features along shared boarders of layers have the
same edge locations
 To keep your
data aligned:
Know what the
basic tools are • Snapping environment
and how to use • Basic snapping
• “Classic” snapping
them • Snap to feature

• Auto-Complete (polygon and freehand)

• Trace construction tool
• Extend and Trim tools
• Auxiliary anchor (Rotate and Scale tools)
Thank you!
 Acknowledgement

UNITAR (2021) Training of Trainers.