DCEP 1.0 Lecture1

Data Editing,
Collection, and
Production
(Prototype)
Collin Childs
Gary Kabot
Peter Kasianchuk
Keith Mann
Brenda Simmons
Mark Stewart
Copyright 2004 ESRI

All rights reserved.
Course version 1.0. Revised November 2004.
Printed in the United States of America.
The information contained in this document is the exclusive property of ESRI. This work is protected under United States
copyright law and the copyright laws of the given countries of origin and applicable international laws, treaties, and/or
conventions. No part of this work may be reproduced or transmitted in any form or by any means, electronic or mechanical,
including photocopying or recording, or by any information storage or retrieval system, except as expressly permitted in writing by
ESRI. All requests should be sent to Attention: Contracts Manager, ESRI, 380 New York Street, Redlands, CA 92373-8100, USA.
The information contained in this document is subject to change without notice.
U. S. GOVERNMENT RESTRICTED/LIMITED RIGHTS

Any software, documentation, and/or data delivered hereunder is subject to the terms
of the License Agreement. In no event shall the U.S. Government acquire greater
than RESTRICTED/LIMITED RIGHTS. At a minimum, use, duplication, or
disclosure by the U.S. Government is subject to restrictions as set forth in FAR
52.227-14 Alternates I, II, and III (JUN 1987); FAR 52.227-19 (JUN 1987) and/or
FAR 12.211/12.212 (Commercial Technical Data/Computer Software); and DFARS
252.227-7015 (NOV 1995) (Technical Data) and/or DFARS 227.7202 (Computer
Software), as applicable. Contractor/Manufacturer is ESRI, 380 New York Street,
Redlands, CA 92373-8100, USA.
ESRI, ARC/INFO, ArcCAD, ArcGIS, ArcIMS, ArcPad, ArcSDE, ArcView, BusinessMAP, MapObjects, PC ARC/INFO, SDE,
and the ESRI globe logo are trademarks of Environmental Systems Research Institute, Inc., registered in the United States and
certain other countries; registration is pending in the European Community. 3D Analyst, ADF, ArcCOGO, the ArcCOGO logo,
ArcGrid, the ArcGrid logo, the ARC/INFO logo, AML, ArcNetwork, the ArcNetwork logo, ArcNews, ArcTIN, the ArcTIN logo,
ArcInfo, the ArcInfo logo, ArcInfo Librarian, ArcInfoProfessional GIS, ArcInfoThe World's GIS, ArcAtlas, the ArcAtlas
logo, the ArcCAD logo, the ArcCAD WorkBench logo, ArcCatalog, the ArcData logo, the ArcData Online logo, ArcDoc, ArcEdit,
the ArcEdit logo, ArcEurope, the ArcEurope logo, ArcEditor, ArcExplorer, the ArcExplorer logo, ArcExpress, the ArcExpress
logo, ArcFM, the ArcFM logo, ArcFM Viewer, the ArcFM Viewer logo, ArcGlobe, the ArcIMS logo, ArcLocation, ArcLogistics,
the ArcLogistics Route logo, ArcMap, ArcObjects, the ArcPad logo, Arcplot, the Arcplot logo, ArcPress, the ArcPress logo, the
ArcPress for ArcView logo, ArcReader, ArcScan, the ArcScan logo, ArcScene, the ArcScene logo, ArcSchool, the ArcSDE logo,
the ArcSDE CAD Client logo, ArcSdl, ArcStorm, the ArcStorm logo, ArcSurvey, ArcToolbox, ArcTools, the ArcTools logo,
ArcUSA, the ArcUSA logo, ArcUser, the ArcView GIS logo, the ArcView 3D Analyst logo, the ArcView Business Analyst logo,
the ArcView Data Publisher logo, the ArcView Image Analysis logo, the ArcView Internet Map Server logo, the ArcView
Network Analyst logo, the ArcView Spatial Analyst logo, the ArcView StreetMap logo, the ArcView StreetMap 2000 logo, the
ArcView Tracking Analyst logo, ArcVoyager, ArcWorld, the ArcWorld logo, Atlas GIS, the Atlas GIS logo, AtlasWare, Avenue,
the Avenue logo, the BusinessMAP logo, DAK, the DAK logo, Database Integrator, DBI Kit, the Digital Chart of the World logo,
the ESRI Data logo, the ESRI Press logo, ESRITeam GIS, ESRIThe GIS People, FormEdit, Geographic Design System,
Geography Matters, GIS by ESRI, GIS Day, the GIS Day logo, GIS for Everyone, GISData Server, InsiteMAP, MapBeans,
MapCaf, the MapCaf logo, the MapObjects logo, the MapObjects Internet Map Server logo, ModelBuilder, MOLE, the MOLE
logo, NetEngine, the NetEngine logo, the PC ARC/INFO logo, PC ARCEDIT, PC ARCPLOT, PC ARCSHELL, PC DATA
CONVERSION, PC NETWORK, PC OVERLAY, PC STARTER KIT, PC TABLES, the Production Line Tool Set logo,
RouteMAP, the RouteMAP logo, the RouteMAP IMS logo, Spatial Database Engine, the SDE logo, SML, StreetEditor, StreetMap,
TABLES, The World's Leading Desktop GIS, Water Writes, and Your Personal Geographic Information System are trademarks;
and ArcData, ArcOpen, ArcQuest, ArcWatch, ArcWeb, Rent-a-Tech, Geography Network, the Geography Network logo,
www.geographynetwork.com, www.gisday.com, @esri.com, and www.esri.com are service marks of ESRI.
The names of other companies and products herein are trademarks or registered trademarks of their respective trademark owners.
ArcView GIS uses HCL Technologies Ltd. Presenter software under license.
Data Collection, Editing, and

Production
(DCEP)
Copyright 2002 2004 ESRI. All rights reserved.
Building Geodatabases I
Data Collection, Editing and Production
Introduction
1-1
Welcome to Data Collection, Editing and Production
Instructor introduction
Student introductions
Name
Organization
Role
in organization
General
GIS experience
ArcGIS
software
experience
Geodatabase
experience
Goals
and expectations
for this class
1-2
Welcome to Building Geodatabases I.

Prerequisites
This three-day course details the capabilities of the geodatabase and how to migrate existing
data to build a geodatabase for ArcGIS 9. Attendees learn how to create, use, edit, and
manage spatial and attribute data stored in the geodatabase. They learn how to interact with
both a personal and enterprise geodatabase.
Discussion topics include: defining geodatabase schema; loading vector and raster data into
the geodatabase; ArcSDE architecture; connecting to an enterprise geodatabase; maintaining
data integrity through subtypes, attribute domains, and relationship classes; defining
appropriate topology rules for spatial data; the XML schema interchange format; and
geodatabase design concepts.
Introduction
1-2
Logistics
Daily schedule
Start
_______________
Lunch
_______________
Finish
_______________
Facilities
Refreshments
and break area
Restrooms
Telephones
and messages
Internet
access
Student
ID badges
Parking
1-3
Daily schedule
Under normal conditions, the class will begin each day at 8:30 a.m. and continue until
5:00 p.m. There will be at least one break in the morning and one in the afternoon. You will
generally be given one hour for lunch.
Facilities
Your instructor will provide information regarding the facilities.
Internet access
Some training facilities provide Internet access for your use during class. ESRI regards
Internet access as an essential business resource for classroom demos, exercises, arranging
travel, and maintaining contact with your office. Please limit your use of the Internet to
business activities only and, as a courtesy to your classmates, refrain from typing or surfing
during lecture presentations.
Introduction
1-3
Course objectives
Learn Data Workflow and Processes in ArcGIS
Learn to:
Access
data quality
Learn about:
Capture
methods
Conversion
Topology
Editing
tools
Ask questions and participate in discussions
1-4
Course objectives
To learn more about the following topics:
ArcGIS data editor
Tools for editing and managing topologies
Tools for editing and managing networks in a geodatabase
Context menus and shortcut keys for increased productivity
Tools for rubber sheeting, adjusting, and edgematching feature data
Multiuser editing with version management and conflict detection
Remote editing of data checked out from your versioned geodatabase
Editing in projected space
Introduction
1-4
Course timeline
Day 1
Software
GDB
overview
overview
Topology
Data
Assessment
Day 2
Working with legacy data
Creating new GDB features
GPS, XY events & Textfiles
Working
with CAD data
Day 3
Creating features with COGO
Attribues & Tables
Working with Annotation
Working with Raster data
Editing
in a Enterprise GDB
Day 1
Lesson 1:
Introduction
Lesson 2:
Introduction to
geoprocessing
Break
Lesson 3:
Working with
ModelBuilder
Day 3
Lesson 6:
Batch
processing
and advanced
scripting
Lesson 10A:
Geodatabase
raster
Break
Break
Lesson 7:
Advanced
modeling
Lesson 10B:
Geodatabase
XML import
and export
LUNCH
LUNCH
LUNCH
Lesson 4:
Using
Command Line
Lesson 8:
ArcReader and
Publisher
enhancements
Lesson 11
and 12: 3D
symbols and
ArcGlobe
Break
Break
Break
Lesson 5:
Introduction to
scripting
Day 2
Lesson 9:
Labeling and
annotation
enhancements
1-5
Lesson 13:
Developer
overview
Introduction
1-5
ArcGIS overview
Desktop GIS
Embedded GIS
Server GIS
ArcGIS
Desktop
ArcGIS
Engine
ArcGIS
Server
ArcIMS
Create custom
GIS desktop
applications
Comprehensive
server-based
GIS
Publish maps,
data, metadata
on the Web
Mobile GIS
ArcGIS
Mobile
ArcPad
ArcInfo
ArcEditor
ArcView
+ ArcGIS Extensions
ArcMap
ArcCatalog
ArcReader
GIS for field

mapping
applications
ArcObjects
Developer building blocks
ArcSDE
Advanced spatial data server
Geodatabase
File-based
DBMS
XML
1-6
ArcGIS is an integrated collection of GIS software.

ArcGIS Desktop: An integrated, scalable suite of software for compiling, authoring,
analyzing, mapping, and publishing geographic information and knowledge. ArcGIS Desktop
starts with ArcReader and extends to include ArcView, ArcEditor, and ArcInfo, each
component exposing more GIS capabilities. Additional desktop extensions expand GIS
capabilities further.
Embedded GIS: Use ArcGIS Engine to develop custom desktop GIS applications or embed
GIS functionality in existing applications. These focused solutions can then be easily deployed
throughout an organization.
Server GIS: Create and manage server-based GIS applications that share GIS functionality
and data within organizations and to many other users on the Internet.
ArcGIS Server is a central application server that is used to build serverside GIS
applications that run in enterprise and Web computing frameworks.
ArcIMS is a scalable Internet Map Server for publishing maps, data, and metadata over
the Web using standard Internet protocols.
ArcSDE is an advanced spatial data server for accessing geographic information in
relational database management systems.
Mobile GIS: ArcGIS technology can be deployed on a range of mobile systems from PDAs to
laptops and Tablet PCs. ArcPad coupled with a wireless mobile device that is location
enabled is widely used for data collection and GIS information access in the field.
Introduction
1-6
ArcObjects: Libraries of software components form the foundation of ArcGIS. ArcGIS

Desktop, ArcGIS Engine, and ArcGIS Server are all built on top of the ArcObjects libraries.
Geodatabase: An object-oriented data model introduced by ESRI, the geodatabase, which is
hosted inside a relational database management system, represents geographic features,
attributes and relationships as objects.
What is ArcGIS?
The What is ArcGIS book discusses the geographic information system (GIS) concepts and
the components that comprise ArcGIS in a way that is beneficial to both new and practiced
ArcGIS users. This book is included with the ArcGIS Media Kits, and can also be found in the
ESRI Software Documentation Library.
You can learn more about ArcGIS family of products from the ESRI Web site, at:
http://www.esri.com/arcgis.
Introduction
1-7
ESRI Support Center
Online portal to technical

information
http://support.esri.com
Knowledge Base
Technical articles
White papers
System requirements
Downloads
Patches and service packs
Data models
ArcScripts and samples
User forums
Contact ESRI
Request technical support
Discussion groups
Report a bug
E-mail lists
Suggest a software enhancement
1-8
ESRIs primary resource for software support is the ESRI Support Center at
http://support.esri.com.
Knowledge Base
The Knowledge Base is a searchable database of focused technical articles. It includes
answers to frequently asked questions, step-by-step directions for performing common tasks,
and workarounds for known software limitations. The Knowledge Base also contains topicfocused white papers organized by product, system requirement information, and product
documentation.
Downloads
Obtain the latest software correction, software and code samples, utilities, tutorials, user
contributed scripts and sample code (ArcScripts), data models, and evaluation software from
ESRIs download page.
User forums
In the user forums, you can ask questions, provide answers, and exchange ideas with other
ESRI product users. Resources include several discussion forums, and two subscription e-mail
discussion lists moderated by ESRI. ArcView-L is for ArcView users, and ESRI-L is for users
of all other ESRI products.
Contact ESRI
Through the ESRI Support Center, you can contact ESRI to request technical support, report a
software bug, submit a software enhancement request, and learn more about registration,
licensing, and updates.
Introduction
1-8
Additional support resources
ESRI Software
Documentation Library
Digital
versions of
ArcGIS user guides
GIS Dictionary
Collection
of GIS and
ArcGIS terminology
ESRI Data and Maps

Ready-to-use
datasets
1-9
ESRI Software Documentation Library

The ESRI Software Documentation Library is a digital collection of the books that accompany
ArcGIS. This collection is available online at the ESRI Support Center under Product
Documentation for each software type, and is also on a CD in the ArcGIS Media Kit (once
this CD is installed, all books will be available in <installation_directory>\ESRI_Library).
GIS Dictionary
The GIS Dictionary defines terms commonly used in ArcGIS applications and general GIS.
Many terms originate from GIS operations, uses, and contexts; others, from closely allied
fields and major application areas of GIS. The GIS Dictionary is available online at the ESRI
Support Center or through ArcGIS Help.
ESRI Data and Maps
The ESRI Data and Maps CD, included in the ArcGIS Media Kit, contains many types of map
data at many scales of geography. All vector data is in Smart Data Compression (SDC)
format; raster data is in various formats, including ESRI Grid and MrSID image formats. Be
sure to review all information about the data, including redistribution rights and metadata
documentation, before redistributing any of this data.
Introduction
1-9
ESRI Educational Services

http://www.esri.com/training_events.html
Learning options
Instructor-led
Virtual
Campus courses
Training
Web
training
seminars
workshops
Learning Pathways
Focused
training on
particular subject areas
Certificate
of completion
1-10
Depending on which ESRI software your organization has licensed, your skills, and your
plans for upcoming projects, you may benefit from additional training on advanced topics, on
specialized software, or on background topics to refine your understanding of GIS and related
technologies.
Detailed information about Instructor-led and Web-based coursesincluding a list of topics
covered, intended audience, duration, schedules, and pricingis available in the ESRI Course
Catalog. You can access this catalog on the Web at http://www.esri.com/training/index.html.
Web-based courses offer convenience and savings. Also, many ESRI Virtual Campus courses
include a free lesson, called a module. You can create a free account and begin training with
these free modules within minutes at http://campus.esri.com.
In addition to Web-based courses, the Virtual Campus also offers free live training seminars,
training seminars, and Web workshops. Live training seminars are focused lectures on a
variety of GIS topics for all levels of users. Training seminars are free recordings of live
training seminars, viewable at your convenience. Workshops are recordings of live training
seminars, viewable at your convenience, plus printable slides of the presentation, questions
and answers from the live training seminar, a software exercise with accompanying data, an
optional exam to assess understanding, and a certificate for successfully completing the exam.
Learning Pathways
Learning Pathways are collections of instructor-led and Virtual Campus courses organized
to generate job-specific knowledge and skills for particular subjects. There are no extra
fees, and each Learning Pathway ends with a certificate of completion. Learn more about
Learning Pathways at the ESRI Training Web site.
Introduction
1-10
Course materials
Books
Lecture
Exercise
ESRI
CDs
Training Data
Course
data
Topology rules poster
Online course evaluation

http://classeval.esri.com
Requires
Course Identification Number
1-11
Teaching methods
Research indicates that students learn differently. This course maximizes your learning
experience by combining instructor-led lectures and discussions, demonstrations, computerbased exercises, and review questions.
Class materials
Your class materials include lecture and exercise coursebooks. These are yours to take home,
so feel free to write in them.
The class data CD contains all the datasets you will work with during class.
A poster showing all the geodatabase topology rules is also part of the course materials.
Course evaluation
Your feedback improves ESRIs courses. At the end of the week, please evaluate the
following:
Instructor
Course materials
Teaching facilities
Overall course
Introduction
1-11
Exercise typographic conventions

Descriptive
text
Action
9
9
Control
name
Note
Keyboard
input
Warning
Question with hint
1-12
Before you begin your first exercise, you need to recognize the typographic conventions used
in your exercise coursebook.
Descriptive text
This text can provide an overview of the next sequence of actions, a review of actions just
completed, or an interpretation of output on your computer monitor. Descriptive text may
introduce what is about to happen with phrases like Next, create a new map in ArcMap; the
actual instruction follows, indicated by the checkbox symbol.
Action
Actions are taskslike starting an application, clicking a button, or typing a commandthat
you must perform during the exercise. The square checkbox symbol indicates an action; act
only on instructions that are prefaced with the checkbox symbol.
You can mark the checkbox symbol in your exercise coursebook as you complete each task.
This is especially helpful when shifting your attention between your book and your computer
monitor.
Control name
Names of objects on your monitor with which you interact are italicized in your exercise
coursebook. These include windows, menus, and buttons. Many buttons reveal their names
when you hold your mouse pointer over them.
Introduction
1-12
Exercise 1 overview
Install the class database
1-13
Introduction
1-13
1-14
Introduction
1-14
ArcGIS overview
Copyright 2004 ESRI. All rights reserved.
ARCGIS Overview
2-1
Lesson 2 overview
ArcGIS
software
Architecture
Applications
Geoprocessing
2-2
Lesson 2 overview
This lesson introduces the geodatabase (short for geographic database). The geodatabase is a
format for storing spatial and attribute data in a relational database management system
(RDBMS). ESRI introduced the geodatabase with the December 1999 release of ArcInfo 8.
ARCGIS Overview
2-2
ArcGIS Architecture
ArcGIS client products

ArcView,
ArcEditor, ArcInfo
Common applications:
ArcMap
Display, editing and

cartography
ArcCatalog
Creating and managing data

ArcToolbox
Geoprocessing tools
2-3
All ArcGIS products (ArcView, ArcEditor, and ArcInfo) are comprised of the ArcMap and
ArcCatalog applications, both of which contain the Toolbox and Geoprocessing windows.
ArcMap is the application for performing analysis and making maps. ArcCatalog is a tool for
accessing and managing your data. ArcToolbox contains tools for data conversion and
management. The Geoprocessing window allows you to write, import and run scripts and
access individual commands
ArcEditor is a GIS data automation and compilation workstation for the construction and
maintenance of geodatabases, shapefiles, and other geographic information. ArcEditor
provides the ability to create geodatabase behaviors, such as topology, subtypes, domains and
geometric networks.
ArcEditor includes tools that support metadata creation, geographic data exploration and
analysis and mapping. ArcEditor includes advanced tools for multi-user geodatabase editing
and version management. Resolve conflicts, disconnected editing, and history management.
ArcEditor includes all the functionality of ArcView and adds the power to edit topologically
integrated features in a geodatabase or coverage. Additional functionality includes support for
multi-user editing, versioning, custom feature classes, feature-linked annotation, and
dimensioning. ArcEditor allows you to create and edit all ESRI-supported vector data formats.
ARCGIS Overview
2-3
ArcCatalog - create and manage data

Database
exploration tool
Browse your data

Manage your data
Define
GDB schema
Feature datasets
Feature classes
Relationship classes
Domains, Subtypes
Topology
Manage metadata
Create
data documentation
View data documentation
2-4
The ArcCatalog application helps you organize and manage all your GIS data. It includes tools
for browsing and finding geographic information, recording and viewing metadata, quickly
viewing any dataset, and defining the schema structure for your geographic data layers.
ARCGIS Overview
2-4
ArcMap - display, edit and map

Map-based
tasks
Displaying
Editing
Querying
Analyzing
Charting
Reporting
2-5
ArcMap provides tools for creating visual displays of your data, querying, and creating
presentation-quality maps. ArcMap makes it easy to lay out your maps for printing, embedding
in other documents, or electronic publishing. It also includes analysis, charting, reporting
functions, and a comprehensive suite of editing tools for creating and editing geographic data.
When you save a map, all of your layout work, symbols, text, and graphics are automatically
preserved.
ArcMap is the primary ArcGIS application for displaying, querying, editing, creating, and
analyzing data.
ARCGIS Overview
2-5
ArcToolbox Window - geoprocessing functions
Available in ArcCatalog and ArcMap
Geographic processing functions

Data
management, analysis, and

conversion
Tools
vary between ArcGIS products
2-6
The ArcToolbox window provides you with tools for data conversion, managing coordinate
systems, changing map projections, and more. ArcToolbox supports easy-to-use drag-and-drop
operations from ArcCatalog; with ArcMap you need to browse to or type in the variables. For
ArcInfo users, ArcToolbox provides additional and more sophisticated data conversion and
spatial analysis tools.
ARCGIS Overview
2-6
Geoprocessing Functions - Scalability

ArcInfo
Comprehensive GP tools
193 Tools
+ 57 Coverage tools
ArcEditor
ArcView GP tools plus More

93 Tools
ArcView
Basic GP tools
Standard options
87 Tools
Additional Extension Tools

45 3D Analyst Tools
158 Spatial Analyst Tools
1 Geostatistical Analyst Tool
2-7
The following lists the key items present in ArcEditor that ArcView cannot do:
Edit Coverages
Edit enterprise geodatabases (stored in a DBMS - Oracle, MS SQL Server, Informix, IBM
DB2)
Edit geodatabases features participating in Geometric Networks and Relationship classes
Create relationship classes in a personal or enterprise geodatabase
Create multiple versions on an enterprise geodatabase
Edit specific versions on an enterprise geodatabase
Resolve conflicts between versions on an enterprise geodatabase
Create and edit dimension feature classes
Define dimension feature class attributes
Create feature-linked annotation, linking annotation to features in a geodatabase
Load data into an enterprise geodatabase
Load rasters into an enterprise geodatabase
Create subtypes in a geodatabase
ARCGIS Overview
2-7
ArcMap refresher
Title bar
Menu bar
Standard toolbar
Table of Contents
Dockable
Context menu
Display
Display
area
area
Tools
Toolstoolbar
toolbar
Tear-off
Tear-offand
anddockable
dockable
Draw toolbar
Status bar
2-8
Features of the ArcMap interface

The Title bar displays the map name (EuropeOnly.mxd in the example above).
The toolbars are dockable.
The Table of Contents lists the data views and layer legends. The Table of Contents is
dockable and can be resized by horizontally dragging the vertical divider between the Table
of Contents and the display area.
The display area is where the map features draw.
The Status bar, besides reporting the coordinates, displays a description of the selected
buttons and menu items.
ARCGIS Overview
2-8
Data view or Layout view?
Data view
For display, queries, editing, and analysis
Layout view
Can edit data in either data view or layout view
For creating map layouts
Data
DataView
View
Layout
LayoutView
View
2-9
Data view
You will work in Data view if you want to display, query, edit, explore, and analyze data.
Layout view
When you choose to create a hard copy map, you need to move to the Layout view. This view
is where you add all the other map elements, such as the north arrow, legend, scale, title, and
other textual information (e.g., author, data date, map date, projection type). Once the map is
complete, you can send it to a plotter or printer, or export it as a graphic file.
ArcMap provides two different ways to view a map: data view and layout view. Each view lets
you look at and interact with the map in a different way. Data view hides all of the map
elements on the layout such as titles, North arrows, and scalebars. In layout view, youll see a
virtual page upon which you can place and arrange map elements. You can edit your
geographic data in either data view or layout view
ARCGIS Overview
2-9
Managing the Table of Contents (TOC)
Drag layers up or down to change display order

Smart
defaults for layer draw order
Point, lines, or polygons

Layers
draw in the TOC in order
From the bottom up
Rename data frames and layers
Remove layers
Bottom tabs
Display
Source
2-10
Managing the Table of Contents

The Table of Contents (TOC) lists all the data frames and thematic layers on the map and
shows the symbols used to represent the features in each layer. A check box next to a layer
indicates whether it is currently visible on the map. Layers at the top of the TOC draw on top of
layers listed below them. Learning how to manage layers and frames within the TOC will help
you represent your data effectively and efficiently.
The draw order of layers within a data frame is from the bottom to the top, so you will put
those layers that form the background of your map, such as the ocean, at the bottom of the
TOC. ArcMap is smart enough to display a point feature class on top of a polygon feature
class.
To change the order of display, click the layer and drag it up or down the TOC to a new
location.
You can copy and paste layers within the same data frame or into a different data frame.
Layers can be removed by right-clicking on the layer and clicking Remove from the Context
menu.
ARCGIS Overview
2-10
Magnifier and overview windows
See more detail or overview

without changing display
Shows full extent of

data plus extent of
data view
Move over
display like a
magnifying
glass
2-11
Magnifier and overview windows

When you dont want to adjust your map display, but you want to see more detail or get an
overview of an area, open another window. ArcMap provides two additional ways to explore
the spatial data on your map: an overview window and a magnifier window.
The magnifier window works like a magnifying glass; as you pass the window over the data,
you see a magnified view of the location under the window. Moving the window around does
not affect the current map display.
The overview window shows you the full extent of the data. A small box in the overview
window represents the currently displayed area on the map. You can move this box around to
pan the map and shrink or enlarge it to zoom in or out.
Both windows operate only in Data view.
ARCGIS Overview
2-11
Editing in projected space
ArcMap - project on-the-fly capabilities

Edit
layers one coordinate system without need to transform

data.
Scenario:
Data
from variety of sources
Layers
Set
coordinate system for ArcMap data frame
Added
not in same coordinate system

layers automatically transformed to data frame projection.
Thus, edit shapes and attribute layers regardless of

coordinate system it was stored in.
2-12
ARCGIS Overview
2-12
The Editor toolbar
All editing functions are controlled through the toolbar

Edit
EditTool
Tool
Sketch
SketchTool
Tool
Split
SplitTool
Tool Rotate
RotateTool
Tool
Target
Targetlayer
layer
Attribute
Attribute
dialog
dialog
Sketch
Sketch
Properties
Properties
Task
Tasklist
list
Edit
Editsession
session
commands
commands
2-13
Navigating the Editor toolbar

In ArcMap, editing operations are controlled through the editing toolbar. The toolbar contains
several important controls:
Editor menu: This menu contains the commands for beginning, ending, and saving edit
sessions. It also provides access to several editing operations, snapping controls, and
editing options.
Edit Tool: This tool is used to select features for editing.
Sketch Tool: This is the primary tool for editing spatial features. It allows you to digitize in
new features or modify the shape of existing features. The actual operation the tool will
perform is controlled by the Task list.
Task list: You choose your desired editing operation from this dropdown list.
Target layer: This control allows you to select the layer you want to edit.
Split Tool: Allows you to divide a select feature into two features.
Rotate Tool: Allows you to interactively rotate selected features using the mouse or an
angular measurement.
Attribute dialog: This window allows you to edit the attribute values of selected features.
Sketch Properties: Allows you to edit the vertices of a sketch.
ARCGIS Overview
2-13
Map Cache
Employed to speed up
common ArcMap tasks
Temporary storage of
features in current display
extent on local machine's
memory
Improves performance of
edit session
Reduces the load on the

server in a multiuser
environment.
2-14
If youre working with data stored in a personal or ArcSDE geodatabase, building a map cache can
often speed up editing as well as selecting, labeling, and drawing features.
The map cache improves the performance of your edit session and also reduces the load on the server
itself in a multiuser environment.
In general, when editing data in a geodatabase, especially network data, you should use the map
cache. The map cache places features in the current display extent into memory on your local
machine. The features can be accessed much faster from memory than from the server.
The auto-cache can be useful if you are going to be working in a series of different geographic areas
and you dont want to rebuild the cache for each area.
It is also convenient when you dont know the exact bounds of the area you want to cache. Since autocaching may hinder performance, you should set an auto-cache minimum scale.
you're working with data stored in a geodatabase, building the map cache can often speed up common
ArcMap tasks. The map cache allows you to temporarily store the features in the current map display
extent in ArcMap in your local machine's memory. Because retrieving the features from local memory
is a fast operation, using the map cache will often result in performance improvements.
The map cache only stores features in geodatabases, so no data from rasters, coverages, or
shapefiles is cached. The map cache is most useful when you will be working within a specific area of
a map.
For example, if you are working with data in a multiuser geodatabase that serves features over a
network, features in the current extent must be retrieved from the source database each time your
display is updated. Building a map cache, however, can reduce the load on your network and the
geodatabase since ArcMap accesses this information from your computer's RAM. Since features are
cached on the client, it reduces the number of queries the client needs to execute on the server.
Drawing large or complex datasets, labeling, editing, selecting features, retrieving the same features
for multiple layers on a map, and drawing features using a definition query are some of the activities
that can often benefit from a map cache. Labeling, for example, can be a slow and costly process for
the geodatabase, requiring multiple roundtrips to the geodatabase as the label engine attempts to
place the maximum number of labels on the map
ARCGIS Overview
2-14
Managing edit sessions
Starting a session
Within
one data frame at a time
Within
one geodatabase at a time
Within
one directory at a time
Saving edits
During
At
the edit session
the end of the edit session
Ending a session
2-15
Starting an edit session

If you have started an edit session in a map document where the layers come from more than
one storage location (I.e. more than one personal geodatabase or network file directory), you
will be prompted to select the single data source which will be edited.
A personal geodatabase may only have one editor at a time; this does not mean one user, but
rather one application. For example, if you have started an edit session in ArcMap, and move
to ArcCatalog to delete or add fields to a table or feature class within the same personal
geodatabase, you will not be allowed to make your changes. This is because the first
application to access the personal geodatabase puts a schema lock on the entire geodatabase.
Managing edit sessions
In ArcMap you begin, end, and save edit sessions using the Editor menu on the Editor toolbar.
When ending an edit session, ArcMap will prompt you to save your edits. If you do not save,
your edits will not be committed back to the edit layer.
ARCGIS Overview
2-15
What is a sketch?
Sketch:
Shape you draw that performs various tasks when editing

Adding new features, modifying features,reshaping features
Tasks:
Actions listed in the Task dropdown list.
Must create a sketch in order to complete a task.
Example- Create New Feature task uses sketch to make the new feature.
2-16
ARCGIS Overview
2-16
Setting ArcMap options
Control default behaviors

Application
startup screens
When
resizing window
Table
fonts
Layout
rulers and grid spacing
Raster
display
DGN
compliance for CAD files
Table
of Contents appearance
Geoprocessing
environment settings
2-17
Setting ArcMap Options

You can adjust a number of default settings for ArcMap behaviors. For example, you might
change the text size and font of your tables so that they are easier to read. You might also want
to change the shape of the lines and patches that represent the features on a map in your Table
of Contents. As shown on the slide above, you can add an additional tab to the bottom of your
Table of Contents; the Selection Tab provides you with another method of turning selectable
layers on or off (see also slide 4-10). Other settings include:
Layout View: setting snapping to grids or guides, turning on/off rulers and scrollbars
Raster: set default display colors for different bands from a wide variety of raster formats
(particularly useful for remotely-sensed or false color imagery)
Geoprocessing: set default disk storage locations or spatial reference for new data
ARCGIS Overview
2-17
ArcCatalog - refresher
Provides a uniform view of all your data
Define or modify table and feature class

definitions
Manage data: Copy, Rename, Delete

Additional
data management tools with the

ArcToolbox window
2-18
Using ArcCatalog
ArcCatalog is the application where you create and manage connections to all the data you
need to use. When you create a connection, you access the data to which it is linked, whether it
is located on a local disk or a database on the network. Together, your connections create a
catalog of geographic data sources.
Within ArcCatalog you can move, copy, rename, and delete geographic data. You can create,
manage, and edit associated metadata, and you can perform some modifications to the data,
such as adding fields to tables, defining subtypes, creating domains, and building table
relationships.
By adding the ArcToolbox window, you can also access all of the data management tools
contained within the various toolboxes.
ARCGIS Overview
2-18
Contents and Preview tab
Contents tab
Lists catalog tree content

Folders
Geodatabases
Feature datasets
Preview tab
Previews
selected items
Geographic
Tabular data
2-19
The Contents tab

The Contents tab lists the items contained in any item you select in the Catalog tree, such as
folders, geodatabases, or feature datasets. In the Contents tab you can look at the data listed in
four different ways:
Large icons: All items are represented by a large icon graphic in the main display window.
List: The items are shown in a simple list with small icons to the left of the file names.
Details: The items are shown in a simple list with small icons to the left of the file names
(similar to the list view option), but additional information is also given, such as each files
data type.
Thumbnails: All items are represented by thumbnail images in the main display window.
The thumbnails are snapshots of the data at the time the thumbnail was created. Therefore,
the thumbnail images can quickly become outdated and should be updated frequently.
By default, thumbnails are automatically generated for map documents. For other items, a
thumbnail must be created manually. If a thumbnail has not been created for an item, an icon
describing the data type and name of the item will appear in place of the thumbnail.
The Preview tab
When an item is selected in the Catalog tree, the Preview tab will preview the selected items
geographic or tabular data. At the bottom of the tab there is a dropdown list that allows users to
select which view they would like to see (either geography or table). Geography is the default
view, where the data is displayed with a random color and/or symbol set. The table view option
displays the attribute data associated with the selected feature class in tabular form.
A third preview option, 3D view, is also possible if the 3D Analyst Extension has been added.
You can build your own custom views if these three options do not meet the needs of your
organization.
ARCGIS Overview
2-19
Metadata - data about data.
Descriptive information
about data source
Metadata Toolbar
Create
FGDC
FGDC Classic
Classic
and edit content
Stylesheets
FGDC_ESRI
FGDC_ESRI
Metadata tab
XML
XML
ISO
ISO
Description
Spatial
Attributes
2-20
Introducing metadata
Often the definition given for metadata is data about data. While this definition is not incorrect, it not very
informative. More precisely, metadata supports descriptive information about data. Text written on the back of a
photograph telling you the photograph's date and subject, and nutrition labels on food containers are common examples
of everyday metadata. For spatial data metadata includes descriptive information such as date, creator, geographic
extent, coordinate system, and attribute domains. Metadata gives your data credibility, and in many situations your data
may be impossible to interpret or use without it.
The Metadata tab in ArcCatalog displays the metadata for a selected dataset. If metadata doesn't exist for the selected
dataset, ArcCatalog will create as much metadata as it can from the existing information. For the FGDC ESRI
stylesheet, the Metadata tab is divided into three categories, each with an active tab:
Description - contains the basic narrative information about the dataset, including source, organization, date, uses,
and restrictions.
Spatial - contains the coordinate information and geographic extent of the dataset.
Attributes - includes fields, attribute domains, and related tabular information.
You can create, edit, import, and export the metadata for any given dataset. Because metadata information is stored in
XML format, you can use it with other software that can read XML documents.
Viewing metadata
You can view metadata in ArcCatalog by selecting an item in the Catalog tree, then clicking the Metadata tab in the
display area. There are a number of stylesheets available in ArcCatalog to view metadata. Stylesheets format data from
a database and present the results as a report. Metadata is stored as an Extensible Markup Language (XML) file, and the
stylesheets define how XML data is presented. Stylesheets are written using Extended Stylesheet Language (XSL). The
stylesheets in ArcCatalog represent common standards for metadata. However, you can create your own customized
stylesheet for displaying metadata in ArcCatalog using XSL.
The Federal Geographic Data Committee (FGDC) is an organization established by the United States Federal Office of
Management and Budget responsible for the coordination of development, use, sharing, and dissemination of
surveying, mapping, and related spatial data. It is composed of representatives from several federal agencies and GIS
vendors. The FGDC defines spatial metadata standards in its Content Standards for Spatial Metadata, and it coordinates
the development of the National Spatial Data Infrastructure (NSDI).
ISO, the International Organization for Standardization is another common standard for collecting metadata on spatial
data.
ARCGIS Overview
2-20
Connecting to Folders and Databases

Connect
Any
to Folder
folder in your network
Disconnect
Supports
Uniform Naming
Convention (UNC) paths
Available
on many dialogs
Connect
to Database
Enterprise
Tabular
GDB via ArcSDE
database via OLE DB
2-21
Connecting to folders
Unlike Windows Explorer, ArcCatalog does not list all files stored on disk, so when you look
in a folder, it might appear to be empty. By default, ArcCatalog only lists geographic data files.
By default, ArcCatalog can access several types of geographic data (e.g., shapefiles,
coverages). To enable ArcCatalog to access a new type of data, both spatial and non-spatial
types, you need to specify the data type in the File Types list in the Options dialog.
When you first start ArcCatalog, it contains folder connections that let you access your local
computers hard disks along with other folders called top level directories (e.g. Coordinate
Systems, Address Locators). You can add additional folder connections that access specific
folders or directories on a local disk, shared folders on the network, or the contents of a floppy
or CD-ROM drive when needed. You can also connect through Network Neighborhood to store
a Uniform Naming Convention (UNC) path. You can use UNC for layer files or map
documents to reference a layers source data. Lastly, you can remove folder connections and
hide other folders that you do not need.
ARCGIS Overview
2-21
ArcCatalog options
Turn default data types

on or off
Add new file types
Add non-spatial data formats
Import File Types from Windows registry
Add New Types not in registry
Define Contents columns
Choose Metadata default style
Define Table appearance
Raster display defaults
Geoprocessor environment settings
2-22
ArcCatalog Options Tabs

The Options tabs allow you to re-define ArcCatalogs default parameters for various functions.
General - select which top level entries (I.e. entries in the Catalog Tree such as Search
Results, or GIS Servers) are displayed by default, and which types of data you want the
Catalog to show.
File Types add new file types which are not contained within the list supplied in the
General tab.
Contents define which standard and/or metadata columns will be displayed with data rows
within the Contents View.
Metadata define the default metadata stylesheet, Metadata Editor, and toggle on/off
whether ArcCatalog will automatically create and/or update metadata files.
Geoprocessing set default global environment settings such as preferred location for
storing new feature classes
Tables Choose how tables will appear by default.
Raster select which raster formats ArcCatalog will recognize, define how various raster
formats will be displayed, and ArcCatalog will build pyramids to facilitate faster raster
display.
CAD you can choose whether ArcCatalog will or will not check all file extensions for
DGN compliance. It is recommended that users leave this off, in order to speed up
ArcCatalog initialization and searches.
ARCGIS Overview
2-22
Arctoolbox window
Geoprocessing tools for:
Data management
Conversion
Analysis
Container for tools and toolsets
Deployed in ArcCatalog and

ArcMap
Toolbox
Toolbox
System
System tool
tool
Toolset
Toolset
Script
Script
Organized into:
Toolboxes
Toolset: Logical container of tools
Tool: Single geoprocessing
Model
Model
operation
2-23
Core toolbox
Analysis
Geoprocessing for feature classes
Conversion
CAD tools, conversion tools
Data Management
Field and workspace tools
Coverage *Workstation install
Geoprocessing for coverages
Linear Referencing
Creating routes, locations
Geocoding
Building locators, table matching
Cartography
Masking annotation, features
Spatial Statistics
Analyzing patterns, distributions
Analysis Tools
Contains a wide variety of geoprocessing tools used to solve spatial or statistical problems.
These tools work on feature classes (shapefiles and feature classes from a geodatabase) for a
wide array of spatial analysis.
Conversion Tools
Contains tools for performing conversions between various data formats, such as CAD to
Raster.
ARCGIS Overview
feature
or DEM to
Data Collection,
Editingclass
and Production
Coverage Tools
2-23
ArcEditor Geoprocessing tools

Data Management Toolbox
51 Tools
Tools to develop, manage, and
manipulate feature classes and datasets
Feature Class Toolse
Features Toolset
Fields Toolset
Analysis Toolbox
5 Tools
Geoprocessing tools used to solve spatial
or statistical problems
Extract Toolset
Overlay Toolset
Proximity Toolset
General Toolset
Generalization Toolset
Layers and Table Views Toolset
Projections & Transformations
Toolset
Feature (Projections and
Transformations) Toolset
Raster (Projections and
Transformations) Toolset
Conversion Toolbox
20 Tools
Tools to convert data into various formats.
From Raster Toolset
To dBASE Toolset
Geodatabase Toolset
To Raster Toolset
To Shapefile Toolset
Raster Toolset
Table Toolset
Geocoding Toolbox - 7 Tools

Linear Referencing Toolbox - 3 Tools

Spatial Statistics Toolbox - 18 Tools
2-24
ARCGIS Overview
2-24
Geoprocessing framework
Command Line
ModelBuilder
Tool
Scripts
2-25
With ArcGIS 9, ESRI is introducing the geoprocessing framework. The framework includes a
series of tools that can run from numerous locations. For example, the Select tool in the
ArcToolbox window can be executed directly from ArcToolbox as a dialog, from the command
line, from a model, or from a script. The ability to run these tools from multiple locations is
what makes the geoprocessing environment so powerful.
ARCGIS Overview
2-25
Setting the geoprocessing environment

Workspaces
Spatial Reference
Extent
Coverage Settings
2-26
The ArcGIS geoprocessor has one integrated dialog that sets processing environments for all
outputs; shapefiles, rasters, geodatabase feature classes, and so forth.. The environments
control how data is created using the ArcToolbox tools, the command line, scripts, and models.
For Spatial Analyst tools, you normally need to make settings under the General Settings and
Raster Analysis Settings pull-down controls.
Note that the geoprocessing environments do not control outputs created with the Spatial
Analyst toolbar.
Opening the dialog
Right-click anywhere in the ArcToolbox (in ArcMap or ArcCatalog) and choose Environments
from the context menu that appears. Additionally, each ArcToolbox tool has a control to open
the Environment Settings dialog, as does a models property dialog.
Saving the environment
In ArcCatalog, the geoprocessing environments persist between sessions. That is, if you make a
setting, then close and re-open ArcCatalog, the setting will still be in effect.
In ArcMap, the geoprocessing environments are reset to their defaults between sessions. That
is, if you make a setting, then close and re-open ArcMap, the setting will be the default.
However, if you save a map or template the settings are preserved in the .MXD or .MXT file.
You may save and re-load the environments in both ArcMap and ArcCatalog. Right-click in
the ArcToolbox and choose Save Settings or Load Settings from the context menu.
Getting help
The Show Help button on the Environment Settings dialog exposes or hides the help area,
which displays a brief description of the currently selected control in the dialog. Also see the
ArcGIS Desktop Help under Geoprocessing > Geoprocessing in the ArcGIS environment.
ARCGIS Overview
2-26
Using a Tool
Provides dialog interface for tools
Hints and
link to help
Status window
Uses geoprocessing environments

(right-click to set)
2-27
Tools can be executed by either double-clicking on the tool, or right-clicking on the tool and
choosing Open. In either instance, a dialog will appear prompting you for all the needed
parameters. The parameters that are required are things such as the input data being processed,
new output data that may be created, and any other information needed to execute the tool,
such as a buffer distance. In some cases there may be optional parameters. These can be left
blank. In the example above, the Cluster Tolerance parameter is optional for the Clip tool, and
is indicated with the word optional in parentheses.
Once all the appropriate parameters have been filled in, press the OK button to execute the
tool. During the execution of the tool, messages are written to a progress dialog (bottom right
graphic in this slide), a new feature in ArcGIS 9. These dialogs will appear every time any tool
executes, and will remain open until the tool has completed executing. These dialogs also will
indicate whether or not the execution of the tool was successful and how long it took. You can
either manually close the progress dialog or choose to have it automatically close upon
completion.
The messages written in the progress dialog can also appear in the Command Line window
(bottom left graphic), also new to ArcGIS 9. The Command Line window is a dockable
window which you can have visible. If you choose to have it visible, it provides a good
historical view of messages from all tools executed in a session. More on the Command Line
window and its additional features will be discussed later in this course.
ARCGIS Overview
2-27
Using command line

Opens Command Line
Provides command interface for tools
Supports code
completion
Shows
processing
status
2-28
The Command Line window may be used to run any geoprocessing tool even those you have
written and added to the ArcToolbox. You type the tools command name and parameters and
then execute the tool when you press Enter, or you may drag and drop a tool from ArcToolbox
into the Command Line window, which is a quick way to discover a tools command name
(tool names and command names are usually different).
The Command Line window
You open the Command Line window in either ArcCatalog or ArcMap by clicking its button
on the Standard toolbar. The Command Line window contains two sections: a command input
line and a message section. You type a geoprocessing command and its parameters in the input
line. Messages are displayed as the command runs.
Using the Command Line window
The Command Line window has several convenient features. You may:
Obtain a list of available tools and environment settings.
View the syntax for tools to see the parameters that you must specify, and in some cases,
choose appropriate parameter values from pulldown lists (this is code completion).
Set values for environment settings.
Create variables for parameter values that you may save and reuse.
View the messages from previously ran tools.
Open the dialog for a previously ran tool, edit its parameters, and rerun it.
ARCGIS Overview
2-28
Using ModelBuilder
Graphical modeling environment
Automate and manage a geoprocessing work flow
May contain a number of interrelated processes
Run, save or export model
Drag data
Drag tools
2-29
Spatial Analyst and the Model Builder

Building a model helps you to automate and manage a geoprocessing work flow. A complex
model may contain a number of interrelated processes. With the Model Builder, you may
change existing models (e.g., to replace old datasets with newer ones, to change environments,
to add processes, to delete processes, or to change tool parameters).
Using the Model Builder
You open the Model Builder window either by adding a new model to the ArcToolbox (rightclick in a toolbox) or by editing an existing model (right-click on a model in the ArcToolbox).
You add tools including other models and scripts to the model by dragging and dropping
them from the ArcToolbox onto the open Model Builder window. In order to set a tools
parameters, you open its dialog by double-clicking the tool icon in the window. You add data
to the model in several ways, like by dragging from either ArcCatalog, from the ArcMap Table
of Contents, or by setting input/output parameters in a tool dialog. You use the Model Builder
toolbar for a variety of tasks, including setting the model properties and parameters, controlling
the model layout and symbology, and running the model. You may run a model by doubleclicking it in ArcToolbox.
Exporting models to scripts
In the Model Builder window, click Model > Export > To Script to export your model to
Python, JavaScript, or VB script. In addition to many other uses, this is a wonderful way to
learn how to write geoprocessing scripts in these languages.
ARCGIS Overview
2-29
Using Scripts
Automate simple or complex tasks

Many
languages supported (Python shown)
Object-oriented
Implement
May
(But easy!)
geoprocessor tools, environments
add scripts as tools to Toolsets in Toolboxes
May use scripts in models
2-30
Spatial Analyst and scripts

Scripts can automate simple or complex tasks using any of the ArcGIS geoprocessing tools and
can be written so that they are data independent so they may be reused. You may add your
scripts to the ArcToolbox, where they are used like any other tool. Writing scripts is easy, and
you should have no trouble mastering the simple skills you need to get started.
Supported scripting languages
You will probably write geoprocessing scripts using one of the popular languages, like Python,
VB Script, JScript, or Perlalthough any language that is COM compliant and implements the
IDispatch interface is supported. Scripts are usually text files, although some languages can
compile scripts into binary executables.
Python
ESRI provides script samples in Python because it is easy to learn, has the capabilities of a
complete developer language, has a convenient development environment (PythonWin), and
can run on many platforms including UNIX, Linux, and Windows. And, it is free. In fact,
several of the tools in the ArcToolbox are actually Python scripts. For more information, visit
www.python.org on the Web.
How it works
An ArcObject called the geoprocessor provides a single access point and environment for the
execution of any of the more than 400 ArcGIS geoprocessing tools, including extensions. In the
example above, these lines create the geoprocessor object and use it to run the Slope command:
Gp = win32com.client.Dispatch("esriGeoprocessing.GpDispatch.1")
.
.
Gp.Slope_sa(InElev, OutSlp, "DEGREE", "1")
ARCGIS Overview
2-30
Getting help
Tabs
Contents
Index
Search
Favorites
Other help
Whats this?
Tool tips
Online Support
2-31
The ArcGIS Desktop Help provides several methods for finding the help you need to use the
software most productively. The Contents tab lets you search for information by topic. The
Index tab lets you search for topics containing words from the Help index, such as Layer or
Table. The Search tab lets you search the Help document for a word you specify. The Favorites
tab lets you store your favorite help topics so you can easily access them when needed. Your
word does not have to be in the index in order to search the document for it, but the search will
take longer if it's not in the index.
In ArcCatalog, ArcMap, and ArcToolbox, button and tool names are displayed when you move
the mouse over them (these are called tool tips). You can also click the Whats This? tool in
ArcMap or ArcCatalog, then click on a button or tool to access additional help about it (this is
called context-sensitive help). For applications like ArcMap that have graphical user interfaces,
context-sensitive help is useful for finding out what all the various buttons and tools do.
Selecting the ESRI Support Center link will connect you with a wealth of additional on-line
resources. The website URL is http://support.esri.com
ARCGIS Overview
2-31
Lesson 2 Summary
2-32
ARCGIS Overview
2-32
Exercise 2
2-33
ARCGIS Overview
2-33
2-34
ARCGIS Overview
2-34
GDB and topology
GDB & Topology
3-1
Lesson 3A overview
Geodatabase
Advantages
Personal GDB vs. enterprise GDB
GDB constructs
Behavior
Spatial & Attribute validation
GDB topology
Creating a topology
Properties of a topology
Cluster tolerance
Ranks
Rules
Dirty areas
Errors
Exceptions
107
107
Vectors
Dimensions
Topology
Surveys
ABC
Networks
Rasters
Annotation
37464 78787
78874 45545
Attributes
3D Objects
27 Main St.
CAD
Addresses
Terrain
3-2
Lesson 9 overview
When you model geographic features, you will most likely need to model some features that
have spatial relationships with other features around them. This lessons introduces you to
geodatabase topology by describing how features share geometry, and by explaining the
mechanisms for establishing and maintaining topological relationships between features.
A topology is stored as a special class in a geodatabase. You create a topology in ArcCatalog
between a set of feature classes in a feature dataset. You use a topology in ArcMap when you
edit the feature classes.
GDB & Topology
3-2
ESRI spatial data formats
Storing spatial data has changed with time and

technology
Different formats have their advantages and

disadvantages
Data formats are used to represent real-world objects

Shapefile
Grid
ArcInfo LIBRARIAN
TIN
SDE
Geodatabase (1999)
(1999)
ArcStorm
Image Catalog
Coverage (1983)
(1983)
3-3
ESRI Spatial data file formats

ArcGIS offers you many choices for storing spatial and attribute data, and each format has its
strengths and limitations. Some issues to consider when choosing data formats are:
Topology
Coverages store polygon and line topology. The geodatabase, at present, can model both
polygon and line spatial relationships but physically stores line topology as a series of
tables (called a Geometric Network). Shapefiles do not store topology.
Discrete versus continuous data
Raster format is especially suited to data without clear boundaries (continuous data) such
as temperature, land use, and elevation. Vector formats store discrete lines, so they are
more suited to discrete data such as streets and parcel boundaries.
Consistency
The formats you choose should be standardized within your organization, and easily
converted if necessary.
ESRI has developed many spatial storage structures to represent real-world features. You
must understand the various formats available and the advantages and disadvantages of these
formats in order to select the appropriate storage format for your data. When selecting a
spatial data format there are many considerations, including:
Is your data better represented as discrete x,y coordinates or in a grid of cells?
Do you need to share data among many users?
Do you have many users who will be editing the data at the same time?
GDB & Topology
3-3
What is the Geodatabase ?
A container for spatial and attribute data

CAD
CAD files
files
Shapefiles
Shapefiles
Coverages
Coverages
Raster
Raster
GIS
data stored in a relational database (RDBMS)
Scalable
solutions (personal GDB or enterprise GDB)
Supports
Tools
Geodatabase
Geodatabase
data integrity with rules
to migrate existing GIS data
3-4
Introducing the geodatabase

A geodatabase is a relational database that stores GIS data as a collection of tables that contain
vector and raster data and their attributes. Users interact with geodatabase data in much the
same way as they interact with file-based data (like shapefiles) through ArcGIS clients like
ArcMap. However, the geodatabase centralizes the GIS data for improved data administration
and allows the creation of rules to help prevent errors from being introduced into the data.
Scalability
Geodatabases come in two variants: personal and multiuser. Personal geodatabases are stored
in a Microsoft Access database and are intended for use by a single user (while many users
may read the personal geodatabase, only one may edit it). For large enterprises, you may
choose to implement the geodatabase in a more powerful RDBMS that is served by ArcSDE,
which allows multiple simultaneous edit sessions, larger data volumes, and faster transactions.
Data integrity
Regardless of implementation, the geodatabase supports a variety of rules to help enforce data
integrity. Attribute domains may be applied to fields to help prevent illegal attribute
assignment, relationship rules may be used to help prevent illegal thematic relationships (e.g.,
putting a warehouse on a residential property), and topology rules may be implemented to find
errors between spatial features (e.g., bus routes that are not coincident with a city street).
Custom behavior
The geodatabase architecture is based on object-oriented technology. This means that
developers can extend the geodatabase object classes to allow custom behavior like specialized
attribute editors and validation rules.
GDB & Topology
3-4
Storing the geodatabase
Personal geodatabase
Built
on Microsoft Jet Engine
Microsoft
Access file
ArcSDE
Enterprise geodatabase
Stored
within an RDBMS
Requires
ArcGIS
ArcSDE
The difference
Personal
Personal
Geodatabase
GDB size limit: 2GB
Enterprise
GDB allows multiuser editing

and versioning
Enterprise
Geodatabase
IBM DB2
Informix
Oracle
SQL Server
Use same ArcGIS tools with either storage type
3-5
The geodatabase can be stores in an MDB file or in a relational database. If the geodatabase
exists in a MDB file, it is called a personal geodatabase. If a geodatabase exists in a relational
database, it is called a enterprise geodatabase and requires ArcSDE.
Personal geodatabase
Using ArcGIS, you are able to create and work directly with a personal geodatabase. The
Microsoft Jet Engine has been incorporated into ArcGIS and allows you to create and
manipulate a Microsoft Access file. All spatial and attribute data is stored in the same MDB
file. The personal geodatabase can only support one editor at a time but more than one session
of ArcGIS may view and query the data.
Enterprise geodatabase
Multiple users can view and edit data in an enterprise database at the same time. Because
building and managing a shared geodatabase for multiple users require a GIS and a RDBMS,
ArcGIS and ArcSDE are delivered together as a single solution. You use ArcGIS with ArcSDE
to implement your database design, specify feature behavior, add and edit geodatabase
contents, and manage geodatabases in a multi-user setting.
ArcSDE
ArcSDE is software installed on the server along with an RDBMS (DB2, Informix, Oracle,
SQL Server) and facilitates the management of the geodatabase. It allows you to centrally
manage and share your organizations large, multi-user geodatabase, or geodatabases. In a
typical client/server configuration, the ArcSDE server is located with the centralized database
on the network. ArcGIS can establish connections over the network to work with the contents
of the geodatabase. Requests come from the client, ArcGIS, to ArcSDE, then from ArcSDE to
the database. ArcSDE handles all queries on the server machine and serves the result to the
client.
GDB & Topology
3-5
Elements within the geodatabase

Geodatabase
Tables
Feature dataset
Raster datasets
Spatial reference
Raster catalogs
Feature classes
Polygon
Line
Point
Annotation
Route
Dimension
Relationship classes
Survey datasets
Survey folder
Survey
Toolboxes
Tool
Model
Geometric networks
Data Integrity rules
Topology
Attribute defaults
Attribute domains
Split/Merge policy
Script
Connectivity rules
Relationship rules
Topology rules
3-6
Inside the geodatabase

The geodatabase is a container of geographic data objects and is often referred to as a
workspace. The various types of objects it contains are discussed below.
Tables store non-spatial objects like parcel owners or work order information.
Feature classes are collections of lines, points, or polygons. Specialized feature classes are
used to store annotation and dimension features.
Subtypes are optional groupings of objects within a table or feature class that have specific
rules assigned to them, like attribute domains or topology rules.
Feature datasets are containers for feature classes (never tables) that share a common spatial
reference (projection and coordinate system). They are required for networks and topologies.
Raster datasets are gridded data derived from a variety of source formats (IMG, JPG, etc.).
Raster catalogs are tables that reference a collection of raster image files
Relationship classes manage thematic relationships between feature classes, tables, or a
combination. They enforce referential integrity between the origin and destination classes.
Geometric networks are specialized topological relationships between line and point feature
classes that are used to perform certain types of analysis, like a shortest-path trace.
Toolboxes hold geoprocessing tools used in the ArcGIS geoprocessing framework.
Topologies are spatial relationships within or between feature classes that are used to find and
fix spatial errors, like parcels that overlap one another or that are not within a county.
Rules may be created to define legal attribute values, thematic relationships between classes,
topological relationships between features, and connections between network features. Rules
may be assigned to subtypes of objects in tables or feature classes.
GDB & Topology
3-6
Feature geometry
x,y coordinates are required

Define
All
vertex position in 2D space
vertices have them
z values are optional

Normally
Must
used for elevation

X
set Contains z values
m values are optional
Normally
used for linear

referencing measures
Must
set Contains m values

Accident
Accident at
at mile
mile 10.64
10.64
3-7
Feature coordinates
The geodatabase may store x, y, z, and m coordinates for every vertex that makes up a feature.
All coordinates may be set or changed by editing the vertex coordinates in ArcMap.
x,y coordinates: All vertices must have x and y coordinates to locate them in 2D space. You do
not do anything special to enable x,y coordinates. The values may be positive or negative, in
geographic units (longitude and latitude as decimal degrees, minutes or seconds), or in map
projection units (feet, meters, etc.). The x,y coordinate values are set by importing, loading, or
digitizing features.
z coordinates: Z coordinates are normally used to store values like elevation or rainfall for a
vertex. If you want z coordinates, you must set the Contains Z values property to True for the
feature classes shape field; you cannot change either the Z or M storage after you have created
the feature class. The values may be positive or negative, and in any appropriate units (feet,
meters, etc.). Z coordinate values are set by importing or loading a 3D shapefile, or by draping
a feature class over a surface.
m coordinates: M coordinates are normally used to store a linear measure from a defined origin
for a vertex in a line. They are used by the linear referencing tools in ArcMap to locate events
along a line, like a car accident that occurred at mile 10.64 on the freeway. If you want m
coordinates, you must set the Contains M values property to True for the feature classes
shape field. The values may be positive or negative, and in any appropriate units (miles,
minutes, etc.). M coordinate values are set by importing or loading a coverage route system, or
by using the linear referencing tools in ArcMap.
GDB & Topology
3-7
Features may be multipart
Points, lines, and polygons may be single or multipart

All
part coordinates are stored in the same SHAPE field
Feature
Feature with
with many
many parts
parts
One
One record
record in
in feature
feature class
class table
table
Enclosed polygons are multipart features

Outside
Outside is
is part
part 11
GRASS
LAKE
GRASS
Add
Add the
the lake
lake as
as
another
another polygon
polygon
Hole
Hole is
is part
part 22
3-8
Features may be multipart

Feature classes can store multipart features. A multipart feature has more than one shape but
only references one record (and set of attributes) in the database. In the example, the polygon
shapes representing the seven major islands of Hawaii are grouped into a single feature.
ArcMap has tools for adding multipart features, merging selected features into a multipart
feature, and exploding multipart features into their constituent parts.
Multipart points
If you want to store multipart points (like multiple wells making up a well field), you must set
the Geometry Type field property for the Shape field to Multipoint. This is because the
geodatabase stores single and multipart points differently. However, all line and polygon
feature classes automatically support multipart features.
Holes in polygons
Multipart polygons must be used to represent areas that are completely contained within
another area. For example, a soil polygon may have a lake in the middle of it. In an ArcMap
edit session, you would digitize the outline of the soil polygon as the first part, then the hole
for the lake as the second part. You would then digitize a separate lake polygon to fill in the
hole. Parts may be nested as deeply as you want. To continue the example, the lake may have
an island, which in turn has a lake, and so forth. Conversion of polygons in shapefile or
coverage format automatically creates multipart polygons when needed.
Not supported for networks
Geometric networks do not support multipart lines; traces do not properly traverse them. A
warning is issued if they are found in an input line feature class while building the network, but
the multipart lines will remain intact. The ArcMap Network Editing toolbar has tools to find
multipart lines, and the Advanced Editing toolbar has tools to explode them.
GDB & Topology
3-8
Spatial reference
Property of a feature class or feature dataset
Defines feature class coordinates

Required
for standalone feature classes and feature datasets
Consists of:
Geographic coordinate
system
Projected coordinate
system
Shape of the earth

Radius, spheroid, etc.
NAD83, HPGN, etc.
You may change
3D earth to 2D map
Origin, units, etc.
Lambert, Albers, etc.
You may change
Coordinate domains for

x/y, z and m
Y
X
Controls coordinate storage
Precision
Extent
You may not change
3-9
The spatial reference

The spatial reference is a collection of properties that define the coordinates used to store
feature geometry. It is required for standalone feature classes and for feature datasets.
Geographic coordinate system (GCS)
The GCS documents the shape of the earth: the datum (NAD27, HPGN, etc.), the lengths of the
axis of the spheroid, and so forth. You should set the GCS if you store your data in latitude and
longitude. ArcGIS supports about 350 GCSs, each of which is optimized for a specific location
on the earth (Africa, North America, etc.).
Projected coordinate system (PCS)
The PCS documents how the positions on the earths surface are translated into 2D positions on
a map. A PCS defines the projection (Lambert, UTM, etc.), the coordinate units, and other
parameters. It also includes a GCS; for example, an Albers projection for the United States may
be based on NAD27 or NAD83. ArcGIS supports about 1,700 PCSs.
Coordinate domainsvery important
The precision and extent properties of the coordinate domains are used to scale and shift your
datas coordinates for storage as integers in the features Shape field. As such, these are very
important settings, and you must determine them before you create any feature classes or
feature datasets for a new geodatabase. The following slides show you how.
Changing the spatial reference
The GCS and PCS document your data and may be changed. For example, if you set the wrong
PCS when you define a feature dataset, you may change it in ArcCatalog (this will NOT reproject the data, just change the description). However, the coordinate domains control the
actual storage of the coordinates and cannot be changed; if you get it wrong, you must create a
new feature class and transfer the old data into it.
GDB & Topology
3-9
Four ways to build geodatabase schema

Database design
What data?
Spatial reference?
Classes & subtypes?
Relationships?
Networks?
Rules?
Create schema
with ArcCatalog
wizards
Import data
Set data integrity

rules
Domains
Connectivity
Relationship
Topology
Build subtypes
Build networks
Create schema
with CASE tools
Create schema
in geoprocessing
framework
Load data
(set topology rules)
3-10
Four ways to build geodatabase schema

Schema refers not to the data it contains but to the structure of a database: the database tables,
their names, their fields, field data types, and so on. The schema of a geodatabase is its tables,
feature datasets, feature classes, subtypes, relationships, and more.
Once you have designed your geodatabase, ArcGIS provides four ways to build its schema:
Create schema with ArcCatalog: ArcCatalog has wizards to help you create everything that
the geodatabase can contain. If you cannot do it with ArcCatalog, it cannot be done.
Create schema by importing data: The process of importing tables, coverages, shapefiles, and
so on creates the schema for the corresponding geodatabase tables or feature classes. The
ArcCatalog and ArcToolbox wizards allow you to modify the schema as part of the import
process. Importing data creates schema only for a table or feature class; you must use the
ArcCatalog wizards to create other elements, like relationship classes, networks, and rules.
Create schema with CASE tools: You may choose to define the content and structure of a
geodatabase using third-party Computer Aided Software Engineering (CASE) tools like
Microsoft Visio or Rational Rose. You use these tools to create a visual UML (Unified
Modeling Language) diagram, or model, of the database, then use the ArcCatalog Schema
Wizard to read the model and generate the corresponding geodatabase elements from it. The
CASE tools cannot create certain types of geodatabase elements, like annotation feature classes
and raster datasets. However, they may be used to manage the database over time; for example,
you can add new tables or feature classes to the model, then re-apply the model to an existing
geodatabase to create the new elements.
Create schema in the geoprocessing framework: You may also decide to generate the schema
of a geodatabase using the various geoprocessing tools available in ArcGIS geoprocessing
framework. You could use several different methods: i) ArcToolbox tool dialogs; ii) command
line; iii) ModelBuilder environment; and or iv) scripting environment.
GDB & Topology
3-10
Feature datasets
Contain feature classes

All
share the same spatial reference
Never
tables - no geometry
Required to model spatial relationships

Geodatabase
Geometric
topology
network
Optional for organization

Group
feature classes for management

(behave like folders in ArcCatalog)
3-11
Feature datasets
Feature datasets are containers for feature classes that impose the same spatial reference on all
the contained feature classes. That is, all the feature classes have the exact same projection,
coordinate system, and coordinate domains.
Required for networks and topologies
A common spatial reference is required for creating spatial relationships between feature
classes, like topologies or networks. Feature datasets enforce this requirement.
Optional for organization
Feature datasets behave like folders in ArcCatalog, and may be used to organize thematically
related feature classes for ease of use. For example, you could create a Hydrology feature
dataset to contain feature classes for lakes, wetlands, springs, and rivers.
Feature datasets and feature class names
Geodatabase tables and feature classes are really just tables in an RDBMS, and feature datasets
are really just associations between feature classes and the defined spatial references, which are
stored as rows within another internal table. In other words, a feature dataset is not really a
container at the physical database level. For this reason, all feature classes (and tables) in a
geodatabase must have unique names, whether they are in a feature dataset or not.
Feature datasets and other classes
Tables do not have geometry and cannot participate in spatial relationships, so they cannot be
created in a feature dataset. However, networks and topologies are stored in the same feature
dataset that contains the participating feature classes, and relationship classes are also stored in
a feature dataset if the feature dataset contains both the origin and destination feature classes.
GDB & Topology
3-11
Feature classes
Table that also stores shapes for features

Each
row represents a feature and its attributes
Stores
features with one type of geometry (point, line, polygon)
Allows for x, y, z, and m coordinates

Has
an associated spatial reference
Projection, coordinate system, and spatial extents
3-12
A table that has a geometry column is called a feature class. The feature class contains a
grouping, or collection, of homogeneous spatial geometry. In other words, you can group all
your similar features together into a geodatabase feature class: all the water valves in the city
become a feature class of points, and all the water laterals become a feature class of lines. Each
feature class uses the same attribute columns to describe the features, and all features share a
common spatial reference. When you think about it, it would not make sense to store some of
the valves in one coordinate system and other valves in another coordinate system. Another
important issue is that all features contained in a feature class can have behavior rules
associated with them such as relationships to objects in another table, topology rules, and
attribute validation rules.
Behavior
The geodatabase lets you apply attribute validation rules to ensure data integrity. As with object
classes, you can apply attribute validation rules with subtypes, domains, and more to feature
classes.
GDB & Topology
3-12
Geodatabase tables
Collections of rows and columns

Non-spatial
element
Containers
for attribute data, addresses,

x/y locations, route events, etc.
May have column behavior

Subtypes
of rows
Attribute
default values
Attribute
domains
May participate in
relationships
3-13
Geodatabase tables
A table is a collection of rows that represent non-spatial data, like parcel owners or zoning code
descriptions. Each row represents a single object (an owner), and the columns (fields) on the
row describe an attribute of the object (e.g., name, address, etc.). Tables from a variety of
formats (INFO, dBASE, delimited ASCII, etc.) may be loaded into the geodatabase.
Column behavior
You may create rules that govern the behavior of the columns. You may assign default values
to automatically populate the columns for new rows, or you may assign attribute domains to the
columns to constrain their legal values, like a list of legal land use codes or pipe diameters.
Subtypes
You may group rows into subtypes based on an attribute, like an owner type of private or
institutional. Different rules may be assigned to columns based on the rows subtype.
Relationships
Tables may participate in relationships with other tables or feature classes.
GDB & Topology
3-13
Rasters in the geodatabase
Images and grids

Image
formats (IMG, TIFF, BMP, many others

supported)
Grids
(ArcInfo Workstation native raster format)
Geodatabase stores as:

Raster
dataset
May mosaic during loading

Raster
catalogs
Personal GDB: Managed or unmanaged

Enterprise GDB: Embedded or referenced
Raster
attribute
Attribute field data type
3-14
Rasters in the geodatabase

Many raster formats are supported in the geodatabase, including TIFF, MrSID, GIF, and GRID
(ESRIs native raster format).
Raster datasets can be large, and it is common to have many rasters that make up an area of
interest, like many high-resolution aerial photographs that cover a city. You may choose to
store the rasters separately, or you may choose to create a raster catalog from them. A raster
catalog is made up of multiple rasters (which may be of different formats), but it displays in
ArcCatalog and ArcMap as one image. The rasters that make up a catalog may be stored in the
ArcSDE geodatabase, or the ArcSDE table may store the path to the file-based raster images.
Raster catalogs are tables in the geodatabase that reference a collection of raster image files.
Each record in the table would store information on one raster dataset. All the rasters in the
catalog must have the same spatial reference.
A raster attribute is a new attribute field data type available within the geodatabase. Each table
in the geodatabase can have one attribute field of data type raster, essentially it can
store/reference a raster image. It acts like a hyperlink.
If you have an existing raster in ArcSDE and are loading a second raster with the same pixel
size, you can mosaic the raster you are loading to the existing raster. You can optionally apply
lossless (LZ77) compression to integer raster data that you import into an ArcSDE
geodatabase.
When many users need to access rasters at the same time, a properly tuned ArcSDE
geodatabase can yield significant performance improvements over a corresponding file-based
system.
GDB & Topology
3-14
Maintaining data integrity

Geodatabase
Attribute
using
offers -
integrity
Subtypes
Domains
Relationship
Rules
Valid attibutes (domains)

Default values (subtypes)
Default
Values
GDB
Connectivity
Rules
Attribute categorization
(subtypes)
Attribute dependencies
(relationships)
Spatial
integrity using
Topologies
Geometric Networks
3-15
GDB & Topology
3-15
Spatial integrity
Topology - spatial Integrity rules

Planarity
Parcel Must not have gaps
Tax parcels cannot overlap one another

Fault lines cannot intersect one another
Connectivity
Contour lines must be connected at both ends

Streams must be connected to 2 or more
streams
Adjacency
LotLine Must not have dangles
Boundary of Voting districts must be coincident

with census block boundaries
Geometric network - Spatial

relationships between points and
lines
3-16
GDB & Topology
3-16
Attribute Integrity
Domains
Coded value or Range domains

Valid set of values for a field or Valid range of values
Split and merge policies
Subtypes
Groups of objects within a class
Different behavior rules may be applied to

different groups
Default values
Relationship rules
Refine cardinality and compatibility between

subtypes
Attribute dependencies
Street
Parcel
Smith
Building
Name
3-17
GDB & Topology
3-17
Lesson 3A summary
3-18
GDB & Topology
3-18
Exercise 3A
3-19
GDB & Topology
3-19
Lesson 3B Topology fundamentals
Introduce GDB topology
Creating a geodatabase topology

Cluster
tolerance
Ranks
Topology
rules
Dirty areas
Validating a topology
Managing errors and exceptions
3-20
When you model geographic features in a GIS, you will most likely need to model some
features that have spatial relationships with other features around them. This lessons introduces
you to geodatabase topology by describing how features share geometry, and by explaining the
A topology is stored as a special element in a geodatabase. You create a topology in
ArcCatalog or within the geoprocessing framework between a set of feature classes in a feature
dataset. You use a topology to ensure spatial data integrity in ArcMap when you edit the
feature classes.
GDB & Topology
3-20
Topology in the geodatabase
Helps to ensure spatial integrity of data
Finds topology errors
Monuments
(user sets the rules)
Lot lines
Fix with edit and topology tools
Parcels
Coincidence based topology
Snaps feature vertices
Zoning
(user prioritizes)
Single or multiple feature classes
Feature topology is not stored
Only properties, errors, and exceptions are stored
Feature topology is discovered on-the-fly by ArcMap
3-21
The purpose of geodatabase topology is to ensure the spatial data integrity of features in one or
more feature classes. Features that are supposed to be spatially coincident, like bus routes that
follow streets, or the common edges between parcels of land; are snapped together to ensure
that they really are coincident within the precision of coordinate storage. You control how far
coordinates may move when they are snapped, and you set the relative importance of the
feature classes to specify how the coordinates are snapped to each other. For example, you can
force low-accuracy, digitized parcel boundaries to move to high-accuracy, surveyed lot lines.
Enables a topological editing environment
In a GIS database, many features may be wholly or partially coincident. For example, lot lines,
parcel boundaries, census tract boundaries, and land use boundaries may superimpose one
another. A geodatabase topology integrates coincident features into a common editing
environment in ArcMap, so that if you change one shared feature (like a parcel boundary), you
automatically change all the coincident features too.
Topology rules help find and fix spatial errors
You may choose to set dozens of optional topology rules between the feature classes in a
topology to define the valid spatial relationships between them. The geodatabase topology finds
the errors, and ArcMap has tools to display and fix them.
Feature topology is not stored
Explicit topological relationships between features are not stored in the geodatabase, as they
are in the ArcInfo Workstation coverage model (where the arc features record their from- and
to-nodes, and their left and right polygons). Rather, feature topology is discovered on-the-fly
by clients of the geodatabase, like ArcMap. The benefit is that the data structure is stable, so
that all mapping, analysis, and editing operations may be performed without cleaning the
data.
GDB & Topology
3-21
Topology manages spatial integrity
With tools for editing coincident geometry between

features and/or between feature classes
With tools for finding and fixing errors
Move
Move aa parcel
parcel boundary
boundary
Rule:
Rule: Soil
Soil polygons
polygons must
must not
not overlap
overlap
Find
error
Fix
error
Rule:
Rule: Streets
Streets must
must not
not cross
cross
Fix
error
ai
M
ai
M
t
1s
n
ai
M
t
1s
Find
error
t
1s
t
1s
n
ai
M
3-22
Editing with a topology

Topology allows you to manage the spatial integrity of your data with tools for editing
coincident geometry between feature classes.
Multiple feature classes can be edited simultaneously if they contain coincident geometry. For
example, it is possible that a parcel can share a common boundary with polygons from the
zoning, land use, and subdivision layers. Using the ArcMap topology editing tools to change a
shared boundary, will automatically update all your feature classes at once, or you can select
which individual shared features will be updated.
Editing with topology rules
Spatial integrity is managed by a set of rules that you define to help you find and fix
topological errors. For example, you may decide to implement a rule that soil polygons must
not overlap one another. The topology finds an error and stores it as a special polygon feature,
which you display in ArcMap. Most errors have automatic fixes which you apply through the
ArcMap edit and topology tools. To continue the example, you would select the overlap error,
then choose an option from a context menu to delete the overlap area: to merge it into one of
the soil polygons, or to create a new soil polygon for it.
Feature construction
You can use topology tools to make new features from existing ones. In ArcCatalog, you can
create a new polygon feature class from an input set of line features. In ArcMap, you can
construct new polygon features from a set of selected lines; or create new line features by
splitting selected line features where they cross; or create new line features from the edges of
selected polygons.
GDB & Topology
3-22
Geodatabase topology
Topology properties
Participating feature classes
Cluster tolerance
Ranks
Topology rules
Stores errors, exceptions, and dirty areas
As specialized point, line, and polygon geometries
Creates and enforces topological relationships
Snaps feature vertices during validation
3-23
The geodatabase topology element

A topology is a specialized element in the geodatabase. Like all elements, it stores properties,
but it also stores specialized point, line, and polygon features that are used to locate rule
violations and to identify dirty areas (areas not validated). Instead of storing topological
information with the feature classes, the topology discovers those relationships when the
information is requested, such as when you are editing with the ArcMap topology editing tools.
Creating a topology
You can create a topology in ArcCatalog or within the geoprocessing framework. A topology
element is always located in the same feature dataset that contains the participating feature
classes. You give the topology a name, set a cluster tolerance, and specify which feature
classes participate in the topology and their relative rank, or importance. You may also set
optional rules for the topology.
Feature behavior
Unlike a geometric network, there is no change to the behavior of the simple point, line, and
polygon feature classes that participate in a topology. Note that a given feature class may only
participate in one topology (or geometric network), and that only simple point, line, and
polygon feature classes may be included in a topology (no annotation or dimension feature
classes).
A new topology environment since ArcGIS 8.3
The geodatabase topology released with version 8.3 of ArcGIS replaces all prior
implementations of topology in ArcGIS. That is, the ArcMap Shared Edit and Integrate
commands have been replaced with new tools, and the old limitations on the number of feature
classes in a feature dataset no longer apply.
GDB & Topology
3-23
Topology workflow
User may stop at any point in the process

Edit
Edit
features
features
Create
Create
topology
topology
Cluster
Cluster
tolerance
tolerance
Dirty
Dirty
areas
areas
Rules
Rules
Ranks
Ranks
Validate
Validate
topology
topology
Errors
Errors
Make
Make
exception
exception
Fix
Fix
errors
errors
Exceptions
Exceptions
3-24
The topology process

You create a topology in ArcCatalog or in the geoprocessing framework. You may choose to
validate it in either ArcCatalog or ArcMap (validation is when coordinates are snapped). You
edit the participating feature classes in ArcMap, which creates dirty (unvalidated) areas. While
editing, you use the topology to find errors (rule violations; without rules, there can be no
errors) and fix them using the ArcMap edit and topology tools. Or you may choose to mark an
error as an exception. You may validate your work in ArcMap to find any errors you may have
made and to eliminate any dirty areas from the topology.
Validation is not required
No ArcGIS capabilities are disabled if a topology has not been validated or if it contains errors.
You may still use the participating feature classes in queries, overlays, and so forth.
Geodatabase versus coverage topology
Working with a geodatabase topology is much more flexible than working with coverages,
because once the topology has been created, you can stop at any point in the process. Any
modifications or additions to the features in a coverage require that the topology be rebuilt
before it can be used in query or analysis operations.
With coverages, the workflow was primarily driven by the data model:
Edit coverage > build topology > perform analysis
With geodatabase topology, new features can be added and errors can exist in the topology
the data is still fully available for viewing, querying, or analysis operations. So topology in a
geodatabase lets you structure your workflow on your business model instead of your data.
GDB & Topology
3-24
Creating a topology
ArcCatalog context menu wizard
Only simple feature classes (no annotation, dimensions, etc.)
A feature class may only participate in one topology or

geometric network
Geoprocessing framework Create Topology tool

ArcToolbox > Data Management Tools toolbox > Topology toolset
ArcCatalog
ArcCatalog
3-25
There are two ways to create a geodatabase topology:

1. Using the ArcCatalog context menu wizard: right-click a feature dataset and choose New >
Topology to start the New Topology wizard. In the wizard, set the topology properties:
Name
Cluster tolerance
Participating feature classes
Ranks of feature classes
Topology Rules
2. Within one of the geoprocessing framework environments, you execute the Create Topology
tool. This tool allows you to set the same properties for a topology as you would within the
New Topology wizard. It is located in the Data Management Tools toolbox > Topology toolset.
Some guidelines
Here are the rules you must follow when you create a topology:
A topology may be created only inside a feature dataset.
Many topologies may be created within the same feature dataset.
All participating feature classes must be in the same feature dataset.
A given feature class may participate in only one topology or geometric network.
Only simple feature classes may participate in a topology no geometric network feature
classes, annotation feature classes, dimension feature classes, or custom feature classes are
allowed.
GDB & Topology
3-25
Cluster tolerance
A distance within which all geometry is considered

coincident, or identical in location
Not a limit on how far vertices may move
Value limits are based on the coordinate precision
Minimum: Approx. (1 / precision) X 2 (the default)
Maximum: Approx. (Minimum) X 100,000
Set cluster about 1/10th of coordinate accuracy
But within the minimummaximum range
3-26
If vertices or point features are found to be within a specified distance of one another, then they
are moved so that they have the exact same coordinate values. This distance is the cluster
tolerance.
The cluster tolerance is not a limit on how far a given coordinate can move, however, because
the clustering process is iterative. That is, two vertices could be moved to an average location,
then that new location is found to be within the cluster tolerance of another vertex so they are
moved again, and so forth. In fact, the cluster tolerance simply states that after the data is
validated, no two vertices will be closer together than the cluster tolerance.
Precision limits the cluster tolerance
The geodatabase imposes limits on the cluster tolerance you may set based on the precision of
the feature dataset. The minimum is about 2 times the inverse of the precision. For example, if
the precision is 100, then the minimum cluster tolerance would be about 1/100 * 2, or 0.02,
which is how the suggested default is calculated. The maximum you may set is about 100,000
times the minimum. In the example, this would be about 0.02 * 100,000, or 2000.
So given a precision of 100, you could set a cluster tolerance between about 0.02 and 2000.
These numbers are in the same units as your coordinates, such as feet or meters.
Consider your coordinate accuracy
The cluster tolerance you set should be about 1/10th the positional accuracy of the coordinates,
provided that the value is within the range imposed by the precision. For example, if your data
was digitized from a 1:24,000 scale map and your units are feet, then the positional accuracy of
the coordinates cannot be better than approximately 5 feet (about the width of a narrow line on
the 1:24,000 scale map). You should choose a cluster tolerance about one tenth of that, or about
0.5 feet. This value is well within the 0.02 to 2000 foot range imposed by the coordinate
precision of 100 used in the example.
GDB & Topology
3-26
Ranks
Control how vertices move during validation
Lower-ranked vertices move to higher-ranked vertices

Ranks:
1 (highest) to 50 (lowest)
Set
ranks between feature classes

(not subtypes or individual features)
Endpoints
Endpoints move
move to
to
average
average location
location
LL line
line moves
moves to
to H
H line
line
H
Equal
Equal ranks
ranks
Cluster
Cluster tolerance
tolerance
L
L
Unequal
Unequal ranks
ranks
Crackpoints
Crackpoints move
move
to
to endpoints
endpoints
H = Highest rank
L = Lowest rank
3-27
Ranks allow you to control how vertices move during the validation process. You determine
the number of ranks (up to 50; 1 is the highest, and 50 is the lowest) based on your data, and
the priority of the rank of each feature class in the topology. This allows you to integrate lessaccurate data to match data of higher accuracy.
Crack points
Crack points are created as part of the topology validation process, where vertices are created
at the intersection of feature edges.
When feature classes have EQUAL ranks:
1. Crack points move to end points.
2. Multiple endpoints are moved to an average location.
When feature classes have UNEQUAL ranks:
1. Endpoints, crack points, or both of lower ranked (higher numbers) features move to match
endpoints/crack points of higher ranked (lower numbers) features.
2. Low quality feature classes are snapped to high quality feature classes.
Example
For example, if you had parcel lines and zoning feature classes, and the parcel lines were
entered using COGO measurements from a plat, you would want to set this feature class with a
rank of 1. If the zoning data was digitized with a tablet, you would want to set its rank lower
(e.g., rank = 2), so the zoning boundaries would snap during the validation procedure to match
the parcel lines.
GDB & Topology
3-27
Topology rules
Define valid spatial relationships

Between
features on a single feature class
Between
feature classes
Between
subtypes
Set as properties of the topology, 25 rules available
Applied to dataset during validation
3-28
There are approximately two dozen pre-defined topology rules that you may optionally set to
define the topological relationships between features. Rules may be applied to feature classes
and to subtypes of feature classes. Some involve a single feature class while others involve two
feature classes of the same or differing geometries. Some examples are listed belo
Parcels Must not have gaps
States Area boundary must be covered by boundary of Counties
Streets Must not self intersect
BusRoutes Must be covered by feature class of Streets
Valves Must be covered by endpoint of Pipes
The rules you specify are tested when you validate the topology, and the errors are stored in the
topology for use in ArcMap which has special tools for locating and correcting them. Note
that if you do not set any rules, there will be no errors.
Setting rules
Topology rules may be set when you create a new topology. You may add and delete rules by
editing the properties of an existing topology, in which case you must re-validate the topology.
You may save the rules to a file and reload them if you need to delete and re-create a topology.
GDB & Topology
3-28
Dirty areas
Areas in the dataset that have not been validated
Entire extent is dirty when topology is first created
May contain existing or undiscovered errors
Edits create dirty areas

Before
Before
Edit
Edit session
session
Insert vertex
Dirty area created
Only dirty areas are validated

3-29
A dirty area is any part of the topology that has been edited since the last validation. That is, the
coordinates have not been adjusted and the topology rules have not been applied in that area. A
topology may have several dirty areas.
When you initially create a topology, the whole extent of the dataset is a dirty area. After you
validate it, there are no dirty areas. In subsequent edit sessions, each time you edit a coordinate,
a dirty area is created around the features involved in the edit. Subsequent validations are only
applied to the dirty area, not the whole extent of the topology, which saves processing time.
It is also possible to create dirty areas by changing feature subtypes; by modifying the topology
rules; or by changing the cluster tolerance property of the topology. You should re-validate the
topology after making any of these changes.
Creation optimizations
The dirty areas are used to optimize the validation process by limiting the extent of data for
which spatial relationships need to be evaluated by ArcGIS. If features are moved, a dirty area
is created for both the original extent and the new extent of the features.
Three states of a topology
Not Validated: The topology has not been validated and one or more dirty areas exist. Errors
may or may not be present.
ValidatedErrors exist: The topology has been validated. There are no dirty areas and errors
have been found.
ValidatedNo Errors: The topology has been validated. There are no dirty areas and no errors
have been found.
GDB & Topology
3-29
Validating a topology
Execute in ArcCatalog or in ArcMap
Snaps coordinates using cluster tolerance and ranks
Cracking: Adding vertices to lines
Clustering: Snapping or averaging vertices
Ranks: Lower-ranked feature vertices move to higher-ranked

Before
Before
After
After
Cracking
Clustering
No new features are created
Finds violations of topology rules

3-30
Validation is the process of moving feature coordinates to ensure they are the same if they are
within the cluster tolerance of each other. It also applies the specified topology rules to the
resulting features to find topology errors. You may choose to validate a topology: in
ArcCatalog; in an ArcMap edit session (where you may undo the validation); or within the
geoprocessing framework.
Cracking and clustering
In the first stage of validation, features are tested to see whether they are within the cluster
tolerance of another feature by checking the vertices. If necessary, new vertices are created
(cracking) on lines and polygons where they are within the cluster tolerance of one another.
Then the vertices are either clustered together (are moved to an averaged location) or are
snapped to one another (one moves to the location of the other). This process never creates new
features; it simply makes existing features coincident with one another.
Snapping versus clustering
Line ends are considered to be more important than line vertices. Here are the rules that govern
how line ends and line vertices are moved (this behavior is modified by feature ranks):
Two line ends will be clustered together
Two line vertices will be clustered together
A line vertex will snap to a line end
Rules and errors
In the second stage of validation, the adjusted features are tested to see whether they violate
any of the topology rules (dangling lines, overlapping polygons, etc.). Errors are recorded as
specialized point, line, and polygon features in the topology element for display in ArcMap.
GDB & Topology
3-30
Topology errors
Found during validation

Rule
If
there are no rules, there can be no errors
Stored in topology as specialized geometries

Use
violations: dangles, overlaps, etc.
to locate errors in ArcMap
Error properties
What
rule was violated
Which
feature(s) caused
the error
Where
the error is
located
3-31
Topology rules are tested when a topology is validated. If a violation is found, then an error
feature is created in the topology with attributes that identify the rule that was violated; the
feature(s) that caused the error; and its location. The ArcMap topological editing tools read this
information to enable the automatic fixes that are available in some of the tools.
To display the topology errors, you add the topology to the ArcMap Table of Contents. You
can control the symbology of the error features.
Error features
Error features may be points, lines, or polygons, depending on the nature of the error. You
cannot directly delete or work with an error feature from the topology. You can only correct the
underlying problem with the feature geometry that caused the error. Once a problem is solved,
the topology automatically deletes its own error features.
One problem may cause many errors
A single problem with the feature geometry may violate multiple rules and cause multiple
errors. For example, you may have a rule that states that a lot line cannot have dangles, and
another that states that parcel polygon boundaries must be covered by lot lines. A single
dangling lot line would then violate both rules; not only is it a dangle, it is also leaving a
portion of a parcel boundary uncovered.
GDB & Topology
3-31
Managing errors
User options
Fix the error use edit and topology tools in ArcMap
Mark as an exception state is stored in the topology
Ignore the error data can still be used
Errors cannot be deleted
Only fixed or marked as exceptions
Integrate error management into your workflow
Who is responsible for finding and fixing errors?
When are they fixed?
Who performs final Quality Assurance tests?
3-32
The presence of a topology error does not prevent any other ArcGIS operations, such as:
drawing, queries, or analysis. This gives you the freedom to integrate your quality control
process into your business practices in any way you want.
This is superior to the ArcInfo Workstation coverage data model, where the data is not usable
until the coverage topology is error free.
Your options
You may use the ArcMap edit and topology tools to fix the error. You may also mark an error
as an exception to its rule, or you may choose to ignore any topology errors.
Workflow considerations
Your organization should incorporate quality control into your workflow so that it is clear
which group or individual has the responsibility to determine the topology rules, to find errors,
and to fix errors.
GDB & Topology
3-32
Lesson 3B summary
Topology is an element in the geodatabase

Helps
to ensure spatial integrity of data
Enforces
coincidence based geometry
Properties
Cluster tolerance
Ranks
Topology rules
After topology is defined, apply to data through

validation to check for errors in dataset
3-33
GDB & Topology
3-33
Exercise 3B
3-34
GDB & Topology
3-34
Data editing workflow
The Data Editing Work Flow
4-1
Lesson 4a overview
Data Editing Work flow:
What is a work flow process?
The Editing Process
Setting up the editing

environment
Figuring out where you

fit into the work flow process
What is a work order?
Organizing workspaces for

data editing
4-2
4-2
What is a workflow process?
An organization's
established processes
for design, construction,
and maintenance of
facilities or Data
Common workflow
processes usually
progress in discrete
stages
How projects or
work orders transpire
over time
4-3
Whether youre building GDBs or maintaining them, there are logical & physical
design considerations.
In the case of GDB maintenance, logical design incorporates the flow of work
whereas the physical design describes the flow of data.
Every organization maintains their GIS database differently
Varies greatly from organization to organization and throughout each sector of the
business community
Work flow design also depends on data, staff, deliverables, equipment, software
licenses, management structure, etc
Another definition: How projects or work orders transpire over time
At each stage, different requirements or business rules may be enforced.
4-3
Where do you fit into the workflow?
Your
responsibilities
may be only a
small part of the
overall workflow
Or, you do
everything
Or, your workflow

is something
completely
different
4-4
Your organizations work flow can be multi-layered, complicated and even convoluted
and GIS data maintenance may only represent a small portion of the work flow.
Stages of data maintenance can be divided into broad categories (assessment,
maintenance & reconciliation)
Assessment yields a description of the problem, data issues, & possible solutions (all of
which can be captured in a work order)
The work order is given to someone (you) and you perform the required maintenance
(modifying the project data in some way)
When finished, you work is then reconciled back into the primary database and validated.
Its possible that validation may reveal more errors (work to do) and so the maintenance
reconciliation stages can be cyclical.
Data maintenance workflows generally break down into several categories (as-built
editing, data collection, and data conversion).
With as-built editing, youre usually required to modify portions of an existing database
with validation rules set (change the boundary line of a feature class).
With data collection, the new data you require is captured using GPS or derived from
tabular or text-based files. You must integrate the new data into the primary database
and usually modify features and attributes to satisfy validation rules.
With data conversion, youre working with legacy data formats or data from other
organizations or even vendor data. You may be required to modify it, either in its native
format or in a scratch GDB, before integrating it into the primary GDB.
A logical workflow design can also reflect the stages of work or, more specifically the
status of the work order. Typically, during each stage of the process, the project or work
order is associated by a named stage. For example, common stages include "proposed",
"accepted", " under construction", and "as built". The process is essentially cyclical.
4-4
Setting up your project workspaces
Physical design of a workflow involves organizing

system folders and GIS workspaces (geodatabases)
4-5
The physical design of a work flow involves system folders and GIS workspaces
(geodatabases)
In a data maintenance work flow you want to design a workspace to hold the
original project data (in its native format) and a workspace for that reflects the final
data format and schema, complete with validation rules. This is the model were
using for this course.
1st animation: instead of just loading or importing raw data into the project GDB,
its a good idea to impose some quality control on it, fix any major errors, add and
delete fields, etc.
2nd animation: ArcGIS certainly has many tools to help convert and extract data in
many formats to the geodatabase but were suggesting that you insert quality
control workspace inbetween the raw data and the final data.
The results of initial data conversions and any intermediate data should go to a
scratch GDB.
This allows you to keep your project or operational GDB uncluttered.
This quality control workspace and scratch GDB can be used to scrub and prepare
data before its loaded into the project GDB.
There can be more than one scratch GDB.
3rd animation: once the converted data is properly prepared, it can be loaded into
the project GDB. Validation and additional editing may be required in the project
GDB in order to meet all the validation rules but it will be far less if you use the
scratch GDB first.
Data Collection,
th Editing and Production
Data Editing Work Flow

(ArcSDE),
the
4 animation: if your organization maintains an enterprise GDBThe
project dataset can be reconciled with it (Note: this may not be part of your work
4-5
Tracking location & progress with maps
Study Area(s)
Administrative Areas
Work Areas
Symbolized
& color coded for:
Status of work
Type of work
Customer
Associated
with work request
Work order #25
4-6
4-6
What is a work order?
One specific task that

proceeds through each
stage of an organizations
workflow process,
including design,
acceptance, and
construction in the field.
Work orders are used for:

Tracking
& approving work
Assigning
work
Describing
Capturing
work
comments
4-7
Some organizations used work orders to track the progress of work in the work
flow.
Typically, work orders help you and your organization to track requests, approve
projects, specify the details of the work, as well as locate the work.
Work orders contain tracking information like a work order number, source of the
request, dates, approval status, etc.
Work orders contain location information like administrative areas, addresses, and
maps.
Work orders contain a description of the work.
Work orders contain information for the GIS staff like who will do the work and
comments technicians.
You may experience work orders as casual requests or formal documents. For
some organizations, work orders are automated forms generated within a work
management system (WMS), see example next slide.
4-7
Work orders can be automated
Custom forms help

automate the
work request
Can be accessed by
the manager, the
technician in the
office or in-the-field
4-8
4-8
Demo
Creating project workspaces
4-9
4-9
Lesson 4a summary
Data
Editing Work flow:
The
work flow process?
The Editing Process
The
editing environment
Work
orders
Organizing workspaces
4-10
4-10
Lesson 4b
Data assessment
4-11
Lesson4b overview
The
basics of data assessment
Data
Location
Where is the data located on your system?

Data
Type
What are the different types of data available?

Data
Quality
Does the data meet the standards for your

organization or purpose?
Spatial
& Attribute Suitability
Is the data geographically correct?

Is the attribute information useful?
4-12
4-12
Assessment techniques
Browse the Catalog
Preview the data
Evaluate Metadata
Review dataset Properties
Do a Visual comparison
4-13
4-13
Browsing the Catalog & Previewing the data
Manage data Connections

Is
the data local or somewhere on the network?
Determine Data Types

GDB
feature class, shapefile, coverage, raster
Create & manage Workspaces

System
Assemble Datasets
Copy,
Paste, Rename, Import, Export, etc.
Explore the geometry

Zoom,
folders or geodatabases
pan, query
Assess the attributes

Sort
values, freeze columns, calculate statistics
4-14
4-14
Evaluating metadata (if there is metadata)
Which Stylesheets do you use?
FGDC, ISO, XML
What should you look for in

metadata?
Where
Who
did it come from?
is the data provider?
What
is the data format?
When
was it produced?
Why
was the data produced?
How
was the data checked?
What
data?
scale was used to create the
4-15
Metadata can come in many formats including text files and HTML
Federal Geographic Data Committee (FGDC)
International Organization for Standardization (ISO)
Extensible Markup Language (XML)
4-15
Reviewing dataset properties
What is the feature class Geometry?
Are there feature class Subtypes?
Coordinate system, extent & precision
What type of attribute Fields are there?
Domain name, type & policies
What is the Spatial reference information?
Subtype field, code & default value
Are there geodatabase Domains?
Line, Multi-point, Point, Polygon
Field names & types
Are there Relationships I should know about?
4-16
What about annotation
4-16
Visual comparison of spatial features
Is the Scale appropriate?
Are the features Generalized?
Are there a sufficient number of points or vertices lines to describe the the features or
phenomenon?
Is the Temporal state of the data useful?
Are points, lines & polygons in the correct position and shape?
Are the Density of observations adequate?
Are lines & polygons arranged together as they should be?
Do feature locations appear Accurate?
Have lines lost their essential shape because of a reduction of vertices or,in the case of
raster data, the enlargement or resampling of cells?
Do the features Align properly?
Does the relationship between a distance or area on a map correspond to the distance or
area on the ground?
Is the data out of date?
Does the data appear to be Complete?
Are features truncated or missing?
4-17
4-17
Preview of work requests (by lesson)
Lesson 5
Lesson 6
Lesson 7
Digitizing & editing features
Data capture
Lesson 8
Data conversion
Working with CAD data
Lesson 9
Creating features using COGO
Lesson 10
Lesson 11
Lesson 12
Working with Tables
Annotation and dimensions
Working with Raster
4-18
4-18
Data conversion
Migrating Shapefiles to the

Geodatabase
Migrating Coverage to the

Geodatabase
Migrating Region features
Topology & Spatial Data

validation
4-19
4-19
Digitizing & editing features
The Editing process
Constructing new features
Editing existing features
Editing attributes
Editing topology
4-20
4-20
Data capture
Text files
GPS log files
Data from ArcPad
Data from TabletPC
Capturing data using a

digitizing tablet
4-21
4-21
Working with CAD data
CAD data organization and

representation in ArcGIS
Tools supporting CAD

related operations
Workflows of common CAD

related tasks
4-22
4-22
Creating features using COGO
Overview of COGO data
Preparing the COGO editing

environment
Adding traverses
Creating polygons from line

features
Tools
that work with COGO
data
Editing COGO features
4-23
4-23
Working with Tables
Tables and fields
Table editing tools
The Field Calculator
Find and Replace
4-24
4-24
Annotation and dimensions
Differences between labels vs.

annotation
Labeling toolbar
Maplex extension
Annotation
Storage options for annotation
Methods to create annotation
Editing annotation
Dimensions
Types and properties
Dimension style properties
Creating dimension features
4-25
4-25
Working with Raster
Exploring raster data
Raster data storage in the

GDB
Raster
dataset
Raster
catalog
Raster
attribute
4-26
4-26
Lesson4b exercise overview
4-27
4-27
4-28
4-28
Converting/Migrating
Converting/Migrating Legacy Data
5-1
Lesson 5 Overview
Migrating Shapefiles to the Geodatabase
Migrating Coverage to the Geodatabase
Migrating Region features
Topology & Spatial Data validation
5-2
5-2
ESRI shapefile data format
Shapefile
Single
feature class
Attributes
Made
Can
stored in dBASE table
up of separate files
create and edit with ArcGIS or ArcView 3.x
Use only ArcCatalog to manage

shapefiles
5-3
Data format: Shapefile

Shapefiles can only contain one feature class. Therefore, a donut shop point feature class
(representing the buildings point location) must be stored in a different shapefile as a donut
shop polygon feature class (representing the buildings footprint).
Regardless of feature type, a shapefiles default attribute table is stored in dBASE format and
is named shapefile.dbf (e.g., donut.dbf). You can access this table in ArcGIS applications or
dBASE. Additionally, shapefiles are the native format for ArcView 3.x, so you can view,
display, and edit both the spatial and attribute data in ArcView 3.x.
Shapefiles are a vector file structure for storing the location and attribute information of points,
lines, or areas. Each shapefile consists of at least three files: <name>.shp, <name>.shx, and
<name>.dbf (e.g., donut.shp, donut.shx, and donut.dbf). However, there may be other files
associated with the shapefile, which you might not recognize and therefore miss if you tried to
copy or move the shapefile using your computer operating system. This is why you should only
use ArcCatalog to copy, move, or rename shapefiles.
5-3
ESRI coverage data format
Coverage
Multiple
geometry types
Attributes
Can
only be stored in an ArcGIS Workspace
Edited
stored in INFO table
only with ArcInfo Workstation
Use only ArcCatalog to manage

coverages
5-4
Data format: Coverage

A coverage is the ArcInfo Workstation native vector format. It is stored as a folder containing
both the locational data files and the descriptive data files for features in a given geographic
area. It is a collection mechanism that may contain one or more feature classes. For example, a
landuse coverage may contain both an area feature class representing contiguous landuse
boundaries and a line feature class used to model the exact transitional location between
landuse types. Area and line feature classes have separate attribute tables, but it is important to
note that they share the same geometry. You can have points and lines (with attributes) in the
same coverage, but they do not share the same geometry. The only limitation is that you cannot
have both point and polygon attributes within the same coverage.
ArcInfo coverage organization
An ArcInfo workspace is simply an operating system folder with a subfolder named info. The
info folder stores and manages the info format attribute tables for the coverages in the
workspace. In addition to coverages, workspaces may also store any other type of geographic
data (e.g., shapefiles, geodatabases, GRIDs), as well as related files, such as documentation or
graphics files.
It is very important to use only ArcGIS tools to manage and manipulate coverages and
workspaces. ArcGIS tools are designed to preserve the link between the files stored in the
coverage directory and the files stored in the info directory. Operating system file management
tools are unaware of this link.
Coverage files are stored in two folders: the coverage folder and the INFO folder. Files in both
folders are required to reconstruct a coverages spatial and attribute information.
5-4
Coverage regions
A set polygons that

Have
Are
the same attributes and shared geometry
organized into subclasses the same attributes
Represent complex area features

Nested
or contain voids
Hawaii
Forest fire
Owl habitat
Multi-part
Overlap
Lake
Goose habitat
Beaver habitat
5-5
5-5
Coverage and Geodatabase equivalents

Geodatabase
Notes
Workspace
Coverage
Coverage
Geodatabase
Feature dataset
RDBMS that contains GIS data

Contains topologically related feature classes
Feature class
Tic
Bnd
Feature class
N/A
N/A
Contains features of same geometry

GDB does not use; may import as points
Extent is a property of the spatial reference
Arc
Node
Line
Point
Lines may be multi-part, like routes

Point
Polygon
Polygon Label
Point
Polygon
N/A
Points may be multi-part

Polygons are simple, not chains of arcs
Route
Region
Line
Polygon
Lines with M (measure) coordinates

Polygons may be multi-part, like regions
Annotation
N/A
Annotation
Dimension
Feature-linked or not
A type of graphical annotation
Network
Topology
Network
Topology
Topologically related lines and points

A set of rules defining spatial relationships
5-6
5-6
Migrate coverage to geodatabase

Coverages
Logical Design
Geodatabase
Boundaries
Lots
Parcels
PLSS Monuments
PLSS Quarter
PLSS Section
PLSS Township
Boundaries hold COGO

information
Coverage polygons
only exist for regions
5-7
Examine existing data

Often you are not starting to design your geodatabase completely from scratch. Perhaps your
organization is working with GIS applications that are supported by data in coverage, shapefile,
CAD, raster, VPF, or other GIS data format. If that data is meeting your requirements you can
document how best to migrate your existing data to take advantage of the geodatabase. There
may be an existing data model that partly or wholly suits your needs. Adopting an existing
design can give you a headstart in creating a geodatabase. Consider using an industry-standard
data model as a template to bridge existing data with current technology.
A parcel example
The example above shows land records held in multiple coverages. You can decompose a
given coverage feature class into multiple geodatabase feature classes, or aggregate features
from multiple coverages into a single geodatabase feature class.
Most projects benefit from careful planning before any data is imported. When you design a
geodatabase, you determine the feature datasets, feature classes, tables, attributes, and other
items it should contain. You can incorporate items from an existing data model or design the
geodatabase from scratch.
5-7
Prepare coverages for migration
Some tasks are best done in Workstation:

BUILD
/ CLEAN for clean topology
JOINITEM
tables to FATs
Minimize relationships!
Use attribute domains for LUTs
Create
.PRJ files
Document spatial reference

MAPJOIN
/ APPEND to create layers
DISSOLVE
Make
to drop edges
routes and/or regions
Defines GDB feature classes
5-8
5-8
Regions in coverages and the GDB
Regions in coverages:
Are
complex features regions are made up of polygons
Enforced
topology between polygons and regions
Regions in the geodatabase:

Are
simple polygons (may be multi-part)
GDB
Polygon-to-Region relationships set by topology rules:
Overlap
Contained
Cover
Gap
Migration:
Coverage
polygons migrate to GDB polygons
Coverage
regions migrate to GDB polygons
5-9
5-9
Comparing coverage and GDB topology

Geodatabase
Coverage
Integrate in the
coverage
Need topology to use

polygons vs. polygons exist
with or without topology
Discovers
relationships onthe-fly
Fixed set of rules
For non overlapping soil areas,

build poly topology vs. define
Must not overlap rule
You define rules
Basic tools for

finding errors
Labelerrors, nodeerrors,
intersecterr, editplot vs.
Validate, Fix Topology Error,
Error Inspector
Powerful validation
tools
Label and node errors corrupt

integrity vs. known errors can
be marked and accepted
Exceptions can
exist
CLEAN and BUILD vs. ranks,

cluster tolerances, and area
selection for validation
Specify dirty
areas for validation
Errors resolved
before building
topology
All geometry
participates in
building topology
5-10
5-10
QC Coverage migration
Use geodatabase topology rules to validate

Polygons
must not have gaps
Polygons
must be covered by coverage polygon

boundary lines
Lines
must not have dangles
Points
Lines
must be on the end of lines
must have points at ends
Use topology edit tools to

Construct
polygons where coverage boundary lines

had dangles
5-11
5-11
QC shapefile migration
Use tools from geoprocessing framework

Check
Use geodatabase topology rules

Polygons
should not overlap
Polygons
should not have gaps
Points
and repair geometry
should be at the end of lines
Use topology edit tools

Create
missing polygons or lines when shapefile

geometry was corrupt
5-12
5-12
QC migration of coverage regions
Use tools from geoprocessing framework

To
explode multi-part features to single-part
Topology rules to consider for region features

Polygon
class must not have gaps
Polygons
must not overlap
Polygons
must be covered by polygon feature class
Polygons
must cover each other
Polygons
must be covered by polygons
Polygons
must not overlap with polygons
5-13
5-13
Lesson 5 exercise overview
Work Order GIS-6789

Check
and repair shapefile geometry
Import
shapefile and coverage polygons to the working

geodatabase
Build
geodatabase topologies to QC the new feature classes
Work Order GIS-6790

Migrate
a region coverage to a geodatabase feature class
Explode
multi-part features to single-part features
Challenge:
Migrate a table to a geodatabase domain and apply it

to an attribute of the Zoning feature class
5-14
5-14
Creating new features
Creating New Features
6-1
Lesson 6 Overview
The Editing process
Constructing new features
Editing attributes
Editing topology
6-2
6-2
The Edit Session (workflow)

1.
Start ArcMap
2.
Open a map document
3.
Add data
4.
Add the Editor toolbar
5.
Start Editing
6.
Create or modify features

& attributes
7.
Stop editing & Save
6-3
6-3
Start Editing
1.
Start an Edit Session
2.
Set Edit Options
3.
Set Snapping
Environment
4.
Set Selectable Layers
5.
Set Task and Target
6.
Build & finish a Sketch
6-4
6-4
Setting Editing Options
Setting the number of

decimal places used for
displaying measurements
Snapping tolerance
Sticky move tolerance
Stream mode
Stream
Group
tolerance
points together
when streaming
6-5
6-5
Setting the Snapping Environment
Layer snapping properties
Sketch snapping properties
Topology snapping properties
Snapping is used to establish

exact locations relative to
features and other geometries.
Two types of snapping;

Feature
snapping to vertices,
edges and endpoints
Sketch
and topology snapping
6-6
What about snapping order?
6-6
Setting Selectable Layers
Selectable Layers dialog
Selection tab
6-7
6-7
Setting a Task and a Target
Create Tasks these

tasks create a new
features in the target
feature class.
Modify Tasks require

one or more selected
features, do not consider
the target feature class.
Topology Tasks work

with the topological
elements to modify
vertically integrated
features.
Other Tasks Select

features from the
selectable layers using an
edit sketch.
6-8
When you're creating a new feature, the target layer determines the layer where a
new feature will be stored. After copying a feature, the target layer is also the layer
you will be pasting into. When you're editing existing features, the target layer is
the one you will be modifying, cutting, or reshaping.
The Target layer dropdown list contains the names of all the layers in the datasets
with which you're working. Subtypes are also listed, if applicable. For instance, if
you set the target layer to Buildings: Commercial, any features you create will be
part of the Commercial subtype of the Buildings layer.
You must set the target layer whenever you create new featureswhether you're
creating them with the Sketch tool, by copying and pasting, or by buffering
another feature. It is also important to set the target layer when you are editing
existing features, so you can modify the features in the correct layer.
6-8
Building a sketch (workflow)
1.
Select a Task
2.
Select a Target
3.
Select a sketch Tool
4.
Build the sketch in the

map (vertices and
segments, the Sketch
context menu)
5.
Finish the sketch
6-9
You can create three main types of features with the Editor toolbar: points, lines,
and polygons.
To create a line or polygon, you must first create a sketch. A sketch is composed
of all the vertices and segments of the feature. Vertices are the points at which the
sketch changes direction, such as corners; segments are the lines that connect
the vertices.
You can create a sketch by creating the vertices and segments that make up the
features. Vertices are marked in green, with the last vertex added marked in red.
The Sketch tool is the tool you will use most often to create a sketch. It has an
accompanying context menu that helps you place vertices and segments more
accurately.
6-9
Sketch properties
Remove parts of a mult-part

feature
Insert and delete vertices
6-10
What about digitizing multi-part features?
6-10
Digitizing new features
The basic tools for interactive

digitizing include;
Edit
tool: Used for selecting and

moving features.
Sketch
tools: Work with the

current task.
Current
Task: An editing task is

used to perform a specific edit
operation.
Current
Target: The map layer

that new features will be added
in.
Other
commands that work on

selected features
6-11
6-11
6-12
6-12
Editing attributes
The attributes dialog box
6-13
6-13
Editing topology workflow
Create a topology
Validating (full or partial extent)
Topology toolbar
Start editing
Error Inspector
Investigate errors
Fix errors or make exceptions
Use pre-existing fix or editing tools/tasks
6-14
6-14
Editing Topology
Edges and nodes
Geometric sharing
The Topology toolbar
Show Shared Features
6-15
6-15
Selecting & unselecting features
With the Edit Tool
Using Tasks and sketches

Select
Features Using a Line
Select
Features Using an Area
6-16
6-16
Keyboard shortcuts for editing
6-17
6-17
Managing the map cache
The map cache places features

in the current display extent
into memory on your local
machine
The Map Cache toolbar

Build
map cache
Show
map cache
Empty
map cache
Show
extent of map cache
Zoom
to extent of map cache
6-18
6-18
Demo
Interactive Digitizing from Orthoimagery
6-19
6-19
Demo
Creating Street Centerlines from Existing Features
6-20
6-20
Lesson 6 Exercise overview
Create new features
6-21
6-21
6-22
6-22
Data capture
Data Capture
7-1
Lesson 7 overview
Text files
GPS log files
Data from ArcPad
Data from TabletPC
Capturing data using a

digitizing tablet
7-2
Data Capture
7-2
Add X,Y coordinate data to the map
Create a layer based on x and y

columns from an input table
The table must contain two

fields: one for the x-coordinate
and one for the y-coordinate.
The values in the fields may

represent any coordinate system
and units
The fields must be numeric
7-3
Data Capture
7-3
Create XY Events from text files
Add the text file to ArcMap
Create an XY Events layer
Export to shapefile or
geodatabase feature class
7-4
Data Capture
7-4
ArcMap GPS toolbar
Simple GPS Support
Display
Variety
options
of symbology
Altitude,
Speed
and Direction-based
rendering
Snapping
positions
to selected Feature
Layers
Auto
Panning
Position logging
7-5
A global positioning system ( GPS) device allows you to quickly find your position
to within several meters. To display and save positions reported by a GPS device
in ArcMap using ArcMap GPS Support, the GPS device must have an input/output
(I/O) interface and be National Marine and Electronics Association ( NMEA)
compliant. You also need a GPS compatible cable that connects to a computer.
Refer to the GPS device documentation or contact the GPS manufacturer if you're
uncertain whether your device meets these requirements.
The Display Options dialog box allows you to customize the look of the GPS
positions. You can decide whether to show estimated positions if the GPS signal
is lost, or change how often a new position is displayed. You can add a pointbased or linear trail to show previous positions and better see the path of the GPS
device. The positions can be snapped to features. You can also vary the current
position or trail symbols by the direction, speed, or altitude of the position.
You can use an existing dataset in place of a connection to a GPS device. A
simulated connection is useful if you're giving a demonstration or are working
with previously collected data. The shapefile or feature class must have point or
line features; you can't use point or line coverages for the simulation.
Data Capture
7-5
Capture GPS data in a GPS log file
The GPS log file is a shapefile or

geodatabase feature class
You can log individual points or

stream data.
The log has the same spatial

reference as the GPS device
You can store related information
7-6
You can save the information from a GPS device to a shapefile or personal
geodatabase feature class. You can write individual points to the log or stream
data. When streaming data, you can also filter the data by properties such as
time or distance. To write data to a log, you must first either create a new log or
open an existing log and append locations to it.
The log has the same spatial reference as the GPS device. Besides the actual
coordinate values, you can save related information to the logs attribute table.
1. The sampling rate is time based. The default is to log a position every second.
2. The units of the minimum sampling distance between points are set in the
Display Options dialog box.
3. The minimum deflection angle is the absolute difference between the direction
of the new position and the direction of the previous position. The direction is
the azimuth from north as calculated between two positions. A new position is
stored if the change in direction is greater than the minimum deflection angle.
Data Capture
7-6
Capture data using ArcPad
Software devised
ArcPad
for handheld units

Microsoft
ActiveSync required
on PC for synchronization
Desktop PC
Microsoft
ActiveSync
Field component to
ArcGIS solution
Real-time
ArcGIS
Desktop
mapping
and GIS
Field-based
GIS tasks
Data files
ArcSDE
7-7
More information about ArcPad

ArcPad supports the Windows CE operating system, which has a similar interface and file
system to the desktop versions of Windows, but also has many differences. Windows CE is an
operating system that is designed to run on embedded and mobile devices. Mobile devices
include palm-size, pocket PC, and handheld computers and cell phones. ArcPad should run on
any Windows CE device that uses a supported processor chip, runs a supported version of
Windows CE, and meets the minimum requirements for memory and VBScript. ArcPad also
supports the following Windows operating systems on desktop PCs: 95, 98, ME, NT, 2000, and
XP. For even more detailed information on what ArcPad supports, see the Using ArcPad
documentation book.
The primary software used for connecting Windows CE devices to the desktop PC is Microsoft
ActiveSync*. ActiveSync is preinstalled in ROM on the Windows CE devices, and a CD
containing ActiveSync for desktop PCs is shipped with every Windows CE device. As of this
writing, the current version of ActiveSync is 3.7. ActiveSync serves four major purposes: data
synchronization, file management, file backup, and software installation. An ActiveSync
connection between your WindowsCE device and your desktop PC is required to install ArcPad
on your Windows CE device.
*Microsoft ActiveSync 3.7 is the latest and significantly improved synchronization

software for Microsoft Windows Powered Pocket PCs. ActiveSync 3.7 is easy to install and
use, and offers the best levels of reliability yet. ActiveSync 3.7 also brings you up to date with
compatibility to Microsoft Office XP and Windows XP.
Data Capture
7-7
ArcPad toolbar
Add from ArcMap View menu
Functionality
Get
data for ArcPad
Check
in edits
from ArcPad
Get
Get
data
data
Check
Checkin
in
edits
edits
Undo
Undo
check
check
out
out
Undo
checkout
for editing
Application
Check
out
layers to
shapefiles
for use with
ArcPad
7-8
ArcPad toolbar in ArcMap

You will add the ArcPad toolbar to your interface in ArcMap. From the View menu, choose
Toolbars and click the ArcPad toolbar. The toolbar has one superior purpose to let you manage
transactions between ArcPad and ArcGIS. The toolbar has three tools on it: Get Data For
ArcPad, Check In Edits From ArcPad, and Undo Check Out For Editing.
The only vector data that ArcPad can edit is shapefiles. The purpose of the ArcPad toolbar is to
allow editing of shapefiles converted from geodatabase feature classes (both personal and
enterprise) with ArcPad. You will use the Get Data Wizard to extract data for use with ArcPad,
check data out of a geodatabase for editing, or both. You can also use the Get Data Wizard to
extract maps onto a mobile device for use in the ArcPad application. The Check In Edits From
ArcPad button, allows you to update your geodatabase with the changes you made in ArcPad.
The Undo Check Out For Editing button lets you remove unwanted checkouts from the
transaction log.
Data Capture
7-8
Editing data in ArcPad
Symbology limited with ArcPad
Make sure font is in Windows font

folder
Labeling limited in ArcPad
Geometry editing
ArcPad only supports editing

shapefiles
ArcPad Export tools create

shapefile representations
of GDB features
Shapefiles do not support true

curve geometries
True curves represented as

densified straight line segments
7-9
Concerns when checking out data

ArcPad supports a subset of the layer properties and symbology supported by ArcMap. For
point, line, and polygon layers, ArcPad supports the following symbols: single symbol, unique
values, graduated colors, and symbols. For point layers, both True Type font symbols and
raster symbols are supported. Composite or color symbols are not. The True Type fonts must
be loaded onto your mobile device. For line layers, the line color, style, thickness, and symbol
reference scale are supported. For polygon layers, simple raster and bitmap fills are supported.
Transparency is implied if no background color is specified. For more information on
symbology, see the Using ArcPad book.
Labeling is limited in ArcPad. ArcPad was not designed for creating maps. You specify your
label field and properties in the Layer Properties dialog on the Labels tab. You also turn on
your labels in this dialog.
In ArcPad, when editing the geometry of your shapefiles that have been created via the Get
Data Wizard, it is important to note a couple of things. Shapefiles do not support true curve
geometry. The geodatabase does support true curve geometry. When you use the Get Data
Wizard, you are converting your geodatabase features to shapefile features. Because of this
process, the geometry of the original true curve in the geodatabase will be affected. You are
creating shapefile representations of your geodatabase features. If you do edit the geometry of
a true curve in ArcPad version 6.0.3, upon check-in back to the geodatabase, the true curves
will be represented as densified straight line segments. If, however, you only edit the attributes
of the feature, true curve geometry will be maintained inside the geodatabase.
Data Capture
7-9
Synchronization folders
Microsoft ActiveSync required

Creates
partnership between mobile

device and desktop computer
Partnership enables folder

creation and synchronization
Put Checkout folder in

synchronization folder
Synchronization
Synchronizationfolder
folder
Desktop computer
Checkout
folder
Information
up-to-date
on both devices
Mobile device
Checkout
folder
7-10
Synchronization
Microsoft ActiveSync, synchronization software for Microsoft Windows Powered Pocket PCs,
allows you to create a partnership between your mobile device and desktop computer. The
partnership is just a file that enables a device to synchronize with a desktop computer. This file
contains the synchronization and file conversion setting you select on both your mobile device
and your desktop computer. This file is stored on your desktop computer. An additional file
that enables your desktop computer to recognize your device is stored on your mobile device.
An ActiveSync connection between your Windows CE device and desktop PC is required to
install ArcPad on your Windows CE device. Once you have established an ActiveSync
connection, you can use Windows Explorer on your desktop PC to transfer files to and from
your Windows CE device.
Synchronization allows you to create a folder on your desktop that is automatically
synchronized with a folder on your mobile device. You can use synchronization to keep
information and files up-to-date on both computers. It also enables you to share information
between your personal computer and device. If you make a change on one computer, the next
time you synchronize, the change is automatically made to the corresponding information on
the other computer.
In order to synchronize files, you must keep the files in a specific folder. There will be a
specific folder both on your desktop and on your mobile device. If you want to maintain
different file versions, you can drag and drop your file into a different folder. It is always a
good idea to store your data under a My Documents folder.
Data Capture
7-10
Check In Edits From ArcPad
Add GDB feature class(es) you edited in

ArcPad to ArcMap
Must be in ArcMap edit session
Specify which data you want to check

back into geodatabase
Process
Process
1
Add
AddFC
FC
to
toArcMap
ArcMap
Edit
Edit
session
session
Check
Checkin
in
edits
edits
Choose
Choose
data
datato
to
check
checkin
in
7-11
You will use the Check In Edits From ArcPad button to update your geodatabase with the field
edits that were made using ArcPad. The Check In Edits From ArcPad process requires that you
start an editing session on the same geodatabase (and version of SDE) that you checked data
out of.
Once you start editing in ArcMap, click the Check In Edits From ArcPad button to choose
which layers you want to check in. The Check In Edits From ArcPad dialog lists each of the
checkouts that were made to the geodatabase you are editing, and only lists the layers from the
geodatabase that are in the map. The feature class must also be in the map.
After you click each layer that you want to check in updates for, click the Check In Edits From
ArcPad button. All updates from the selected layers will be checked into your edit session. If
there were no updates to check in, you will be notified.
When you complete the check-in process, the transaction is complete. You can click Undo to
roll back the edits that have been added to your edit session; however, the transaction is still
complete and cannot be redone.
Data Capture
7-11
Undo Check Out For Editing
Check box for feature class, and click Undo
Feature class cannot be checked out for

editing in ArcPad
Checkout
folder and created shapefile not deleted
7-12
You will use the Undo Check Out For Editing to remove unwanted checkouts from the
transaction log file. Once you click the Undo Check Out For Editing button, a list of the current
checkouts for all geodatabases in the map will be listed. Click on the specific layers that you
want to undo the checkout for, and click undo. The checked-out data is not removed from your
disk when you click Undo; only the record of the transaction is deleted.
Data Capture
7-12
Capture data using TabletPC
Drawing tablets
Sketching
Tracing
Visualization
Applications
Field
surveying
Red-lining
Requirements
Advanced
Full
editing tools
data model
Close
integration with
enterprise GIS
Same desktop / field UI
Disconnected editing
High-end
devices
7-13
With the addition of the Tablet PC, ArcGIS is now a mobile computing solution for
GIS. ArcGIS users can now update their enterprise GIS geodatabases in the field
using the same tools and applications, such as ArcMap and ArcCatalog, that are
used in the office.
The Windows XP Tablet PC Edition is an operating system from Microsoft that is
based on the existing Windows XP Professional operating system. Windows XPcompliant applications are fully supported by the Tablet PC Edition of Windows
XP. For this reason, ArcGIS is certified and fully supported with the Tablet PC
Edition.
ArcGIS applications work on Tablet PC devices. Since all Windows XP-compliant
applications are fully supported, all COM-based extensions to the ArcGIS
architecture will work. This enables developers of GIS applications to build
ArcObjects based mobile extensions to ArcGIS.
The digital pen can be used to click buttons on toolbars in ArcGIS and to draw on
the map. Essentially, the pen takes over the movement of the pointer and acts as a
mouse.
With Tablet PC speech recognition technology, you can use your voice instead of
a mouse, keyboard, or pen to control applications. The speech recognition
functionality is embedded within the Tablet PC Input Panel and can be used with
ArcGIS as it is used with other applications. Because of our custom menu
implementation, standard speech recognition commands will not work. However,
dictation does work.
Data Capture
With the Windows XP Tablet PC Edition comes the introduction of digital ink
technology Ink is drawn on the tablet using a pen and is stored as a series of
7-13
Capture data using a digitizing tablet
Large format digitizers

Full-size
CAD
drawings (plat maps)
Large
patterns
Highly
maps (USGS quads)
accurate
Rollup digitizers
Portable
digitizing device
7-14
Data Capture
7-14
Anatomy of a digitizing tablet
Digitizing surface
Menus
Built-in
Detached
Puck or stylus
Cables
USB
Serial
7-15
Data Capture
7-15
Using a digitizer with ArcGIS
Steps for setting up a digitizer:

Connect
the digitizer to your computer
Install the digitizer driver
Configure
the puck or stylus buttons
0 button = left click, 1 button = left drag, 2 button = right click

Register
digitizer.dll
From Command prompt:
Getting started in ArcMap

Start
an edit session,
Open
the Edit Options dialog
Click
Digitizer tab.
7-16
Data Capture
7-16
Registering a paper map with ArcMap
Secure paper map within the

digitizing area on the digitizer
Register the paper map

Digitize
control points
RMS
error (.004 max.)
Save
registration file
7-17
Data Capture
7-17
Lesson Summary
Display and generate features

from a text file containing
coordinate information
Connect ArcMap with GPS via

the GPS toolbar
Create and manage ArcPad

data via the ArcPad toolbar
Use the Tablet toolbar to work

with TabletPC technology
Digitize features using a

digitizer tablet
7-18
Data Capture
7-18
Digitize new spatial features
7-19
Data Capture
7-19
7-20
Data Capture
7-20
Working with CAD
Working with CAD Data
8-1
Lesson 8 Overview
Explain how CAD data is organized and represented in

ArcGIS
Describe the tools that support CAD related operations
Show workflows of common CAD related tasks
8-2
8-2
CAD Integration Scenarios
Cartography
CAD
Database Integration
CAD
feature classes interact with other GIS layers
Editing
CAD
feature attributes link with other databases
Spatial Analysis
CAD
layer serves as a background map element
features serve as reference for new features, snapping
Translation
CAD
and GIS feature classes exchanged between systems
8-3
8-3
CAD data support in ArcGIS
Two most common CAD file formats:

AutoCAD
ArcGIS 9.0 updated to support the latest versions:

AutoCAD
2004 and MicroStation V8
DWG/DXF support:
AutoCAD
DWG, MicroStation DGN
R12 to AutoCAD 2004
DGN support:
MicroStation
5.x 8.x (95/SE/J/V8)
8-4
8-4
CAD data organization in ArcGIS
Two ways that ArcGIS organizes CAD data:

CAD
Drawing Datasets - 1 map layer
CAD
Feature Datasets - 5 map layers
Both representations only reference one CAD file
CAD Drawing Datasets vs. CAD Feature Datasets

Which
What
one should you use?
are the differences?
8-5
8-5
CAD Drawing Datasets
Represented as a single data

source
ArcCatalog Tree = white icon
ArcMap = single layer file with no

symbology
Display is similar to how CAD

program the drawing
No ArcMap symbology control
Complex entity representation is

preserved (i.e., inserts, cells)
Typically used for display purposes

as background element
8-6
8-6
CAD Feature Datasets
Represented as a folder
ArcCatalog = blue icon
ArcMap = selected layers with symbols
CAD Feature Classes are organized by

geometry types:
Annotation
Point
Polyline
Polygon
Multipatch
Rendered as simple features
ArcMap can change symbols
Used for query, analysis, and

conversion operations
8-7
8-7
CAD Data Properties in ArcCatalog
Same for CAD Drawing Dataset

and CAD Feature Dataset
General Panel
Drawing
layer information
Visible/Invisible
Feature
counts
Categorize
Useful
layers
by geometry type
for evaluating data
8-8
8-8
CAD Data Properties in ArcCatalog
Spatial Reference Panel

World
File Name
Enable/Disable
Projection
Import existing
8-9
8-9
Spatial Reference and CAD Data
World Files
File
based two-point transformation
Uses
the .wld file extension
Simple
text file containing two lines:
<From X1, From Y1> <To X1, To Y1>

<From X2, From Y2> <To X2, To Y2>
Projections/Coordinate Systems
Associated
Must
with CAD Data by means of a projection file (.prj)
use Save As option to create .prj file
8-10
8-10
CAD Layer display in ArcMap
Drawing layer management

Enable/Disable
Custom Symbolization
Change
symbols; Render by Categories, Quantities
Attribute based labeling

Fields,
drawing layers
Expressions
Display Effects (CAD Drawing Datasets only)

Transparency
8-11
8-11
CAD Layer Properties
Supports all feature class

property tabs
CAD-specific tabs:
Drawing
Layers
Manage layers drawn

Transformations
8-12
8-12
ArcToolbox and CAD Data
CAD-Specific
Feature
Class to Feature Class
Import
CAD Annotation
Import
from CAD
Export
to CAD
Supports conversion tools for

several data formats
8-13
8-13
Converting CAD Data
Feature Class to Feature Class

One-to-one
conversion
Feature
Class to Geodatabase
supports multiple layers (i.e., batch)
Can
use an expression to isolate

subset of feature class
8-14
8-14
Preparing CAD Data for ArcGIS
Organize levels intelligently
Create data in real-world coordinate locations
Use entities/elements that are supported by ArcGIS
Use blocks or cells for attributing objects (i.e., points

inside polygons)
Use unique symbols to represent different objects

Use
unique text symbols for different text objects
Separate cartographic objects (i.e., title, blocks,

legends, etc.) from geometry
8-15
8-15
Import from CAD tool
Creates a Staging Geodatabase
Optimized representation of the

CAD drawing file(s) as a
geodatabase
Reformats the CAD data into

predefined highly normalized
tables and feature classes.
Flattened out structure, that

allows it to be joined by key
fields. (User Defined)
8-16
8-16
When to use Import from CAD
Many CAD files are being processed at one time
Attribute Tags as points (rather than the block insertion point)
Extended Entity Data (EED/XData)
Layer Properties (In addition to the ENTITY layer property.)
CAD Document file Properties (i.e. Drawing path spatial extents)
Tool provides means for user to select a spatial reference
Tool automatically appends multiple files of mixed CAD versions in

a single pass
8-17
8-17
GIS to CAD Users
Can output GIS feature classes to Native CAD format
DGN V8
DWG / DXF R14
DWG / DXF R2004
Export to CAD can be a simple export or tightly

controlled
Export CAD tool will generate well formatted CAD

drawings with explicit symbology according to
attributes in the input feature layers.
8-18
8-18
Add CAD Fields
Tool adds CAD-specific

fields
ArcInfo
only
Adds same fields that

Import From CAD adds
Prepares geodatabase
feature class for export to
a CAD file
New fields recognized by

the Export to CAD tool.
8-19
8-19
Set CAD Alias
Sets alias name for a field that will

be recognized by Export to CAD
Matches columns from the input

table with a list of CAD specific
fields
Contained in dropdown list
Replace Add CAD Fields before

export, instead use Set CAD Alias
tool to name existing fields
8-20
8-20
Convert CAD data
8-21
8-21
8-22
8-22
Creating and editing

COGO features
Lesson title
2-1
Lesson 9 overview
Overview of COGO data
Preparing the COGO editing environment
Adding traverses
Editing COGO features
Creating polygons from line features
9-2
Lesson 11 overview
The geodatabase makes no special provision for feature classes that store COGO (coordinate
geometry) data or that are used as the reference data for geocoding (address matching); they
are simply point, line, or polygon feature classes with special attributes. However, because
these are data structures of general interest, this lesson has been included to address them.
COGO
Coordinate geometry, or COGO as it is often called, is the capture and automation of survey
data to create features. Coordinate geometry involves the creation of lines using a set of survey
measurements collected in the field. COGO data may be in the form of directions and
distances, angles and distances, curves, or tangent curves, measured from a known point. This
lesson covers the ArcCatalog and ArcMap tools used to create COGO features.
Geocoding
Many geographic data are spatially located by some form of address. For example, you may
provide someone with your street address so they may visit you or mail you a document. But to
display these data on a map, these locators must be converted to map coordinates.
Geocoding is the process of matching data with locators against a set of map features that have
the same locational information stored as attributes. For example, your street address may be
matched against a street map, and a position for your house may be interpolated based on the
range of house numbers on your street. The result of geocoding is a set of points that have the
attributes of the input data (that is, your address and name). This lesson covers the ArcCatalog
and ArcMap tools used perform geocoding.
Lesson title
2-2
Coordinate geometry (COGO) overview
Capture survey data to create ArcGIS data
Used in applications
requiring accurate/precise
coordinate geometry
Survey data consists of

Angles
(directions) and
distance measurements
9-3
Coordinate geometry (COGO) overview

Coordinate geometry, or COGO as it is often referred to, is the capture and automation of
survey data to create ArcGIS data. It stores line and curve dimensions along with x,y
coordinate values. Often these dimensions are extremely accurate and precise and can be used
for a variety of applications. These data store attribute values that pertain to angles or
directions and distance measurements. The graphic above shows line features that are labeled
according to direction and distance information. The directions are represented in quadrant
bearing using degrees, minutes, and seconds. To satisfy the requirement that the recorded
measurements that were entered by the user are persisted in the GIS database, a COGO line
feature class is required with specific attributes.
Lesson title
2-3
COGO line feature class
Standard line feature class containing required fields
Straight lines
-0E
5-0 81
4
N
6.7
12
Curves
Circular
Field
Direction *
Distance
Radius
Tangent (Length)
ArcLength
Tangent
Side
9-4
Lesson title
2-4
The Create COGO Fields tool
Automatically adds the required COGO fields to a table
Add from Customize Dialog Box in ArcCatalog
9-5
Lesson title
2-5
COGO support in ArcMap
Create and maintain COGO lines and attributes

Create 2-Point Line Features edit task
Sketch tools
Advanced Editing toolbar

Rectangle
Copy Extend
Traverse
Generalize Tool
Features
Proportion
Edit
Fillet
Annotation
Smooth
Inverse
Trim
Explode
Circle
Tool
9-6
Advanced Editing toolbar

The Advanced Editing toolbar contains many editing tools for creating and modifying
geometric features. The toolbar is available with all levels of licensing. Several of the tools it
contains are used specifically to create and edit features that have COGO attributes.
Create 2-Point Line Feature task
This edit task forces the creation of two-point lines, which are required for COGO features.
Traverse tool
The Traverse tool lets you create edit sketch geometry from a wide variety of traverse
measurements. Once you have started a traverse, you can add segments or curves to the edit
sketch using DirectionDistance, AngleDistance, Curve, and Tangent Curve methods.
Inverse tool
The Inverse tool calculates the direction and length of a two-point line feature, as well as curve
parameters for curved two-point lines. It populates the attributes of the feature with COGO
attributes for Direction, Distance, Radius, Delta, Tangent, Arclength, and Side.
Fillet and Proportion
These are geometric construction tools that also populate the COGO attributes for two-point
lines.
Sketch tools
Many of the sketch tools may be used to construct two-point lines. The Inverse tool may then
be used to compute the COGO attributes for them.
Lesson title
2-6
Create 2-Point Line Features task
2-Point lines are required

for COGO attributes
Use with many construction tools

The Create New Feature task
One line, three segments
The Create 2-Point Line Features task

Three lines, one segment each
(each click makes a new 2-Point line)
9-7
Create 2-Point Line Feature task

In COGO, only single-part, or single-segment polylines, made of either two-point lines or
curves, can be supported by COGO attributes. To create this type of geometry, there is a Create
2-Point Line Features task.
Traditionally, when new features are created, every segment and vertex that is produced is a
part of that one line. When features are created using the Create 2-Point Line Features task,
every segment added between two vertices is an independent feature.
COGO attributes
Only some of the construction tools assign COGO attributes to the 2-Point line they create or
update. For these lines, you populate the COGO attributes with the Inverse tool. Just select the
line and click the tool. If the feature class lacks COGO attributes, the Inverse command will
display a warning message.
Lesson title
2-7
Traverse overview
survey plat, deed
Values
entered manually or loaded from a
text file
Straight
Takeoff
point
or curved segments
Closed traverse is adjusted

Compass
N30
-0
12 0-0
4.7 0-E
3
From
distances, directions, and angles
Rule, Transit, Crandall
There is a ground to grid conversion
Closed
Closedtraverse
traverse
-0
012
4.7 00-E
3
Precise
Open
Opentraverse
traverse
Constructed from segments (courses)
N30
Takeoff
point
Closure error
Tie
point
9-8
Traverse tool
The Traverse tool is a productivity tool that allows you to enter segments of a line or polygon
boundary edit sketch by using precise distances, directions, and angles that come from survey
measurements gathered in the field. You can generate straight lines as well as tangent and nontangent curves using this tool. Values can be entered into the traverse course table by either
manually typing in the survey measurements, or by loading in a text file containing COGO
attributes.
There are three types of traverses: open, closed, and looped. All traverses begin at a specified
x,y coordinate, known as a take-off point. An open traverse is a traverse that has a take-off
point, and the segments or courses that follow, end where they may. A closed traverse has two
points; a take-off point and a tie point. A tie point is a known x,y coordinate for the endpoint
of a traverse. When a traverse is closed, it is possible to examine the calculated difference
(closure error) between the specified endpoint and the traversed endpoint by viewing the
closure report. Lastly, a looped traverse has the same take-off and endpoint.
If a traverse is closed, it should be adjusted. Adjusting a traverse involves modifying the
segments to distribute systematic error in the directions and distances. The supported
adjustments include Compass Rule, Transit, and Crandall.
Compass Rule is the adjustment most often used when there is an error in closure. It assumes
that the closure errors are a result of errors in both observed directions and measured distances.
Each direction and distance of each line in the traverse will be adjusted to close the traverse.
The adjustment for each direction and distance will reflect the total closure error of the
traverse.
Lesson title
2-8
Traverse tool
Enter traverse courses

Straight
lines or curves
Supports
many direction
and angle formats
Open or closed
Provides
closure
adjustment tools
Creates 2-Point lines

Sets
COGO attributes
9-9
Traverse tool
The Traverse tool is used to enter the properties of the courses that define a traverse. Each
course becomes a 2-Point line feature with COGO attributes detailing the direction, distance
and curve information of the course. Traverse information may be read from a text file instead
of typed. The example shows a traverse being entered to construct a new subdivision.
Direction and distance formats
The tool accepts directions and distances in a variety of formats. Directions may be entered as
North Azimuth, South Azimuth, Polar, or Quadrant Bearings. Distances may be entered as
radians, decimal degrees, degrees-minutes-seconds, gradians, or gons. The units are set in the
Editing Options dialog under the Units tab.
Lines and curves
Courses may be entered as straight lines (just a direction and distance), or as tangent or nontangent curves. You provide any two of the curve parameters (chord length, arc length, angle,
or radius) to the tool to construct the curve.
Open and closed traverses
Traverses may be open or closed. All traverses begin at a specified x,y coordinate, known as a
take-off point. An open traverse is a traverse that has a take-off point, and the courses that
follow end where they may. A closed traverse has two points: a take-off point and a tie point. A
tie point is a known x,y coordinate for the endpoint of a traverse. When a traverse is closed, it
is possible to examine the calculated difference (closure error) between the specified endpoint
and the traversed endpoint by viewing the closure report. Lastly, a looped traverse has the same
take-off and endpoint. Closed traverses should be adjusted with one of the supported
adjustments (Compass Rule, Transit, or Crandall) to distribute the closure error back to the
course directions, the distances, or both.
Lesson title
2-9
COGO direction types
Quadrant Bearings
North
0
Azimuths
Polar
Angles
Degrees
0
North
N45-0-0E
45-0-0-4
N45-0-0
90
270
45.0000-3
0
South
S315-0-0
180
Grads
0
South
100
300
200
9-10
Lesson title
2-10
Circular curve computations

Geometric elements
Orientation
Solution
Two of these
One of these
And this = The information

necessary to
calculate the
endpoint of a
circular arc from
any given starting
point
Tangent curves do not
require orientation
9-11
Defining circular curves

There are a variety of methods to define a circular curve using different combinations of the
curves geometric elements and orientation.
Lesson title
2-11
Traverse file format
Sample traverse file:

DT
DU
SP
EP
DD
AD
TC
NC
QB
(Direction Type Quadrant Bearing)
DMS (Direction Units Degrees Minutes Seconds)
454868.9 298986.09 (Start Point)
454868.9 298986.09 (End Point)
N90-0-0E 105 (Direction and Distance)
45-0-0 100 (Angle and Distance)
C 45 D 100-0-0 L (Tangent Curve)
C 45 D 100-0-0 C N45-0-0E R (Non-tangent Curve)
9-12
Lesson title
2-12
Traverse corrections
Closure report
Compass, transit, or Crandall corrections
9-13
Traverse correction techniques

Three standard traverse correction techniques are available when using the closed Traverse
tool.
Compass correction
The compass correction technique specifies that the misclosure, or difference in x and y
between the resulting endpoint and the desired endpoint, are equally distributed among the
individual two-point arcs and curves that make up the traverse. This is done by adjusting
the location and distance of each arc proportional to the difference in closure. The compass
correction technique is the technique most often used to resolve errors in misclosure. It
assumes that the errors are related to both errors in the direction measurements as well as
the distance measurements. Thus, the corrections are reflected in each distance and
direction value. This technique is also known as the Bowditch rule.
Transit correction
Much like the compass correction technique, the transit correction method specifies that
the misclosure is equally distributed among the individual two-point arcs and curves that
make up the traverse. However, this technique favors the direction measurements over the
distance measurements. In determining the location change required of each arc, the
proportion assigned to each arc is proportional to the total x or y values of all the arcs. This
results in changes that will affect both the direction and the distance of each arc, but will
alter the distance to a greater extent.
Crandall correction
The Crandall correction technique is used when the direction values are assumed to be
precise and accurate, and that any misclosure is due solely to errors in distance
measurements. This adjustment will preserve all of the direction measurements and will
alter only the distance measurements to eliminate the closure error.
Lesson title
2-13
Proportion tool
Split selected line feature into new features

You
set lengths of the parts

260
Original line
260
Split by specified lengths

Sets
50
50
50
COGO attributes for new lines
Distributes
100
error if length of parts not equal to whole
Many other ArcMap editing tools support COGO data
9-14
Proportion tool
The Proportion tool splits an existing line feature into several new features or segments based
on specified lengths. Sometimes the task can be complicated by measuring errors. For example,
the length of the line in a GIS database might not be exactly equal to the total length of the
segments as measured in the field. If this is the case, the error between the GIS feature length
and the entered lengths is automatically calculated and distributed to each segment.
The command is enabled if a single line feature is selected. If the line feature is from a COGO
feature class, the new features will populate the distance and direction fields. The direction
value will actually be copied from the original direction value. The Distance field will report
the length of the segment entered into the Proportion tool, while the Shape_Length field will
report the actual length of the feature.
Lesson title
2-14
Managing undershoots and overshoots
Extend undershoots to selected feature
Trim overshoots to selected feature
9-15
Managing undershoots and overshoots

In previous releases of ArcGIS, the ability to trim or extend a feature was dependent on the
creation of a virtual sketch. Line features either extended to this sketch or were trimmed back
to it. The tools on the Advanced Editing toolbar for dealing with overshoots and undershoots
work a little differently, though the outcome is the same. Features are extended or trimmed
back to an existing feature. The Extend tool extends a line to touch another line or polygon
boundary that is selected. The Trim tool removes the portion of a line that crosses a selected
line or polygon boundary. The tool is interactive; you simply click on the line you want to
extend or trim. Another difference between the Extend and Trim tools and the Extend/Trim
task, is that the task allows you to extend or trim multiple line features at once. These new tools
work on a single feature.
Lesson title
2-15
ArcMap topology toolbar
Topology toolbar contains editing tools

Constructing features
Topology to edit
Validation
Editing coincident geometry
9-16
Editing topologies in ArcMap

The Topology toolbar provides tools for editing and managing coincident geometry in ArcMap.
There are two types of topologies that can be edited with ArcMap: geodatabase topology and
map topology.
Geodatabase topology
Regardless of whether a topology is based upon a feature class in a personal geodatabase or an
ArcSDE geodatabase, an ArcEditor license is required to create the topology and edit the
topology or the layers that participate in a topology. Recall that a geodatabase topology consists
of a fixed set of user-defined rules and properties that are applied to your data.
Lesson title
2-16
Fix topology error tool
Select an error, apply a standard fix

Similar
to the Error Inspector, but more visual
Select an error
Right-click
9-17
The Fix Topology Error tool

The Fix Topology Error tool provides the same standard fixes as the Error Inspector, but it
behaves like a tool. Use it to select one or more errors, then right-click to raise a context menu
to select the fix for the errors.
This tool is useful when you are solving complicated errors, like several errors that
superimpose one another or are very close together. You have more visual control over the
error you are selecting and the fix you are applying to it. The tool works whether the Error
Inspector is open or closed.
Controlling selection
Open the Layer Properties for the topology and click the Selection tab. The check boxes control
the types of errors that the tool can select.
Lesson title
2-17
Error Inspector edit tools
Has standard fixes for some rule violations

Choices
depend on the error
Select errors
and right-click
Five dangles
Choose a fix
from menu
All are fixed
9-18
Error Inspector edit tools

The Error Inspector has built-in tools for fixing common, simple topology errors.
Select one or more errors of the same type (like Must not have dangles, as shown above), rightclick to raise the context menu, then choose a fix. Only fixes that are appropriate for the
selected error are available. For example:
Dangling line: Extend or trim the line
Intersecting or overlapping lines: Split at the intersection, or subtract the overlap
Overlapping polygons: Subtract or merge the overlap, or create a polygon from it
Polygon gaps: Create a polygon to fill the gap
Must be covered by: Create a covering line or polygon feature. Or delete a feature
No fixes are available if you have errors of different types selected.
You must be careful when selecting multiple errors, because the same fix is applied to all of
them (perhaps some dangles should be extended, and others trimmed).
Exceptions
Not all rule violations may be errors. For example, you may have set the dangle rule for street
centerlines knowing that most streets connect to other streets. But there are a few exceptions,
like cul-de-sacs. For these, you may mark the error as an exception.
Other options
The context menu also allows you to zoom or pan to errors, select the features involved in the
error, and show the description of the rule being violated (same as in the Add Rule dialog).
Lesson title
2-18
Creating parcels from line work

Create/Delete Polygons
Construct Features tool uses selected lines
Creates new feature in Target layer
Can consider existing features
Split
Splitpolygons
polygons
Append
Appendpolygons
polygons
ArcCatalog tool for processing whole datasets

9-19
The Construct Features command on the Topology toolbar, provides a way to generate new
polygon features from a selection containing lines, polygons, or both. When the option to
consider existing features is chosen, selected line features can be used to split or append
polygon features in the target layer. This can be extremely beneficial for parcel maintenance
applications, where it is necessary to maintain coincident parcel lines and parcel polygons.
Digitize, trace (ArcScan), or traverse the parcel lines and use them to construct (split or
append) parcel polygon features.
You can also create polygons from lines within ArcCatalog. The Polygon Feature Class from
Lines tool takes one or more existing line or polygon feature classes in a feature dataset and
creates new polygon features from the closed shapes that are defined by the intersection of all
the lines or polygon edges. A polygon feature class can be created using a line feature class to
supply the boundary lines and an optional point feature class to supply the attributes. The input
and output layers are required to be from within the same geodatabase.
Lesson title
2-19
Exercise overview
Add COGO fields to a line feature class
Load a traverse file
Manually enter traverses
Fix spatial errors using Error Inspector tools
Create Parcels from line features
9-20
Lesson title
2-20
Attributes, tables and

relationships
Attributes, Tables & Relationships
10-1
Lesson 10 overview
Tables and fields
Table editing tools
Find and Replace
10-2
Lesson 9 overview
When you model geographic features, you will most likely need to model some features that
have spatial relationships with other features around them. This lessons introduces you to
geodatabase topology by describing how features share geometry, and by explaining the
A topology is stored as a special class in a geodatabase. You create a topology in ArcCatalog
between a set of feature classes in a feature dataset. You use a topology in ArcMap when you
edit the feature classes.
10-2
Supported table types
ArcGIS supports four types of tables

INFO
- All have the same

look and feel in ArcGIS.
dBase
- All behave the same

in ArcGIS*
Geodatabase
(Oracle, etc.)
* Except Delimited Text
Delimited
Text
A
10-3
10-3
Supported field types
The geodatabase supports eight field data types

Data type
Bytes
Short Integer
Long Integer
Float
Range / format / notes
2 -32,768 to +32,767
4 -2,147,483,648 to +2,147,483,647
4 About 3.4e38 to +1.2e38 (~7 significant digits)
Double
Text
8 About 2.2e308 to +1.8e308 (~14 significant digits)

varies Up to ~64,000 characters
Date
BLOB
Raster
8 mm/dd/yyyy hh:mm:ss am/pm

varies Store large binary content or other multimedia
varies Store images
Supported field data types are generic

Data
types specific to an RDBMS are not supported
10-4
10-4
Creating a new geodatabase table
With ArcCatalog tools
With ArcToolbox tools
10-5
10-5
Creating a geodatabase table with ArcCatalog
Use the New Table wizard

Name
the table
Define
the fields
Name
Type
Type Properties
Or,
import field
definitions from
another table
Can not change

after you "Finish"
10-6
10-6
Loading records into a table
Use the ArcCatalog "Simple Data Loader"

ArcToolbox,
too: Conversion Tools > To Geodatabase
10-7
10-7
Adding records to a table
In ArcMap, in an Edit session

Open
the table
Move
to last record and type into it
Click
the button next to a record to select it (or by attribute)
Press
"Delete" to delete selected records
10-8
10-8
Table editing tools

Field Options (right-click field name)
Delete Field, Calculate Values, Summarize
Table Options (Click Options)

Add Field, Find & Replace, Export
10-9
10-9
Find and replace
Replace all occurrences of one string with another

For
a selected field or for all fields
Very
fast, very useful
Joe
Blow
Joe Blow
10-10
10-10
The most powerful table edit tool
Use in or out of an edit session
In: Slower, but can Undo
Out:
Faster, but can not Undo
Build an expression
Click fields
Click operators
Click Visual Basic functions

Number, String and Date
You may type, too
Apply expression to the field
For the selected records
10-11
10-11
Using Visual Basic functions
Many are exposed in the Field Calculator

Any
others may be used, too
Must open Visual Basic Editor to get function help
10-12
10-12
Advanced field calculations
You can write VB scripts in the Field Calculator

Click
the Advanced button
Type
the Pre-Logic VBA Script Code
Or,
Load one of the scripts from http://arcscripts.esri.com
10-13
10-13
Exercise 10 overview
Create a new, empty Geodatabase table

Load
Add
records with ArcCatalog
records with ArcMap
Use table editing tools

Add
fields
Delete
fields
Manually
edit data
Use the Field Calculator

Parse
strings
Calculate
polygon centroids
10-14
10-14
Labels, annotation, and

dimensions
Labels, Annotation & Dimensions
11-1
Lecture 11 overview
Review differences between labels vs. annotation
Labeling toolbar
Maplex extension
Annotation
Storage
options for annotation
Methods
Editing
to create annotation
annotation
Dimensions
Types
and properties
Dimension
Creating
style properties
dimension features
11-2
In this lesson, you will learn about two custom feature classes that can exist in the geodatabase:
annotations and dimensions. Both are types of map text that help cartographers convey more
information in maps. Topics in this section include: how they are stored in the geodatabase and
how to create, edit, and manage them in ArcGIS.
11-2
Labels vs. annotation
Text elements in ArcGIS can be stored as:

Labels
Annotation
Dynamically placed by
software
Static manually positioned by

user
Managed as a group
Managed individually
Stored in map document or

layer file
Stored in map document or

geodatabase
Always linked to feature
May or may not be linked to

feature
11-3
In ArcGIS, there are two feature labeling options for placing textual information on a map:
labels and annotation. This slide summarizes the main differences between the two.
Labels
A label is text that displays dynamically on your map document. When you zoom and pan
around your map, labels are re-positioned and re-sized based on the current display scale.
Labels are always managed as a group. For example, you cannot move an individual label or
change the color of an individual label. Label properties (e.g., color, size, or position) are
stored as properties of the map document or in a layer file. Labels are always linked to the
feature they represent. For example, if you delete a feature, the label is deleted as well.
Annotation
Annotation is different from labels in that each annotation stores its position, text string, and
display properties. Unlike labels, individual pieces of annotation can be selected and edited in
ArcMap. Annotation is also static; when you pan and zoom around the map, annotation does
not re-position or re-size. You must change their position manually. In addition, annotation can
be managed individually. For example, you can change the position or color of each individual
annotation. Annotation can be stored in three ways: (1) as a graphic in your map document, (2)
as a feature class in the geodatabase, or (3) as a feature-linked feature class in the geodatabase.
11-3
Label manager
Access to labels for layers in active data frame
11-4
The Label Manager allows you to display and set all labeling properties for each layer in the
active data frame. To make a change to a label class, select if from the Label Managers Table
of Contents. All properties for that label class will be displayed on the right. Through the Label
Manager, you can change label expressions, text symbols, placement properties, and so on. The
same labeling properties are available with ArcGIS 8.x through the layers properties dialog.
11-4
Label Priority and Weight Ranking
Annotation not listed

11-5
You can set label priority and label weight rankings between labels and other labels and
between labels and features.
Label Priority Ranking
This button can be used to set which label class will have the highest label priority ranking
and which will be the lowest. You are thus creating a hierarchy of relative importance
between your labels which will appear in different visual levels helping the map reader to
read your labels in accordance with their relative importance.
Label Weight Ranking
This button can be used to set weights that controls which labels will be placed when there
are potential conflicts or overlaps between the features and the labels. Sometimes you
might want features to have a high weight (i.e., you might not want any label to overlap
the features).
11-5
Lock labels
Locks size and position of labels in current extent
Useful for:
Moving
Zoom
around map without waiting for labels to redraw
in on cluttered area without changing label placement
Use with the magnification window
No label movement
when zoomed in
11-6
The Lock Labels tool enables you to lock the labels for the current extent. When you lock the
labels, you are locking the size and the position of the labels. Therefore, as you navigate
around the map, labels do not change in size or position. This is useful if you want to move
around the map without waiting for the label placements to be recalculated. You can also use
this functionality to zoom in on a cluttered area to see the labels more clearly. Your labels will
not redraw or resize with the new scale. If you want to zoom in on labels, but do not want to
modify your current view extent, you can use the locking labeling functionality in conjunction
with the Magnification window.
11-6
Viewing unplaced labels
Draws labels that could not be placed due to conflicts
Unplaced labels draw in different color (default is red)
11-7
Often there is not enough room to place the labels for all the features on your map. The View
Unplaced Labels button shows all the labels that are not currently placed, due to some conflict
(e.g., you have set a rule that states that no two labels can overlap). The unplaced labels are
drawn on the map in a different color - the default is red. You can change this color through the
Labeling toolbars Labeling > Options button.
11-7
Polygon placement options
Horizontal
Straight
Try horizontal first, then straight
11-8
With ArcGIS 8.x, there are no polygon placement options. Every polygon label is horizontal.
With ArcGIS 9, you have three polygon placement options: horizontal; straight; and try
horizontal first, then try straight. Straight means that each label will be placed so that it follows
the longest direction of the polygon being labeled. In the dialog on the slide, the preview on the
left changes according to which radio button option you click on the right.
11-8
Maplex for ArcGIS
Advanced rules-based label

placement to simplify map creation
Highlights
Stacking
Font
labels
reduction
Abbreviation
dictionary
11-9
June 23, 2004 Change: Replaced the Labeling toolbar with the final version that was shipped with ArcGIS 9. Old toolbar
was being used.
Basics: Introducing the new Maplex for ArcGIS Extension
Details: This is an optional extension to that uses a set of rules to determine how and where to place labels in order to
create standardized maps with complicated data and labeling requirements.
Script: ______ showed the Maplex Labeling Extension for ArcGIS-- we cant overstate the value of this sophisticated
but easy to use advanced text-placement product. It handles complicated, intricate annotation data in large volumes in
a batch process. It eliminates the very tedious and time consuming task of creating highly readable, complex
cartographic products.
The Maplex Labeling Extension, an optional extension, adds high-quality cartographic text placement, labeling, and
conflict resolution to ArcView, ArcEditor, and ArcInfo. A detailed set of rules enables users to control text placement
and properties such as abbreviations, stacking, font reduction, overflow, and much more. Maplex for ArcGIS can be
used to generate text that is saved as labels in map documents or as in an annotation layer in the geodatabase. Maplex
for ArcGIS greatly reduces map production time and enhances cartographic quality.
<or>
Maplex for ArcGIS adds advanced label placement and conflict detection to ArcMap. Maplex for ArcGIS can be used to
generate text that is saved with map documents as well as annotation that can be incorporated into comprehensive
annotation layers in the geodatabase.
Using Maplex for ArcGIS can save significant production time. Case studies have shown that Maplex for ArcGIS can
shave at least 50 percent, and often more, off the time spent on map labeling tasks. Because Maplex for ArcGIS
provides better text rendering and print-quality text placement, it is an essential tool for GIS-based cartography. Any
GIS site that makes maps should consider having at least one copy of Maplex for ArcGIS.
11-9
Stacking labels
Complete control without VBScript code

Justification,
stacking character, line break options
11-10
Label fitting strategies

A common challenge when labeling a map is to fit many labels into a small area. Using
Maplex, there are several strategies for fitting labels to maximize the number of labeled
features:
Stacking labels to reduce their overall length
Reducing the font size of labels
Abbreviating certain words in labels
Stacking labels
When a label does not fit in the available space, Maplex can split it into two or more parts and
stack it to reduce the horizontal length. You can change the stacking parameters to fit your
map. For example, you can control how the stacked label text is justified; what characters are
used to indicate where the text should be split; whether and where these characters should
appear in the label; and whether all labels should be split at the stacking character, or just when
there is not enough room. To accomplish the same result with the ESRI Standard Label Engine
(or the ESRI Label Engine at 8.x), you would have to write a VBScript or JScript.
There are three check boxes that help you control the behavior of the split:
Visible: If checked, the split character will appear on the map.
Stack after: If checked, the split will happen after the stacking character, otherwise it will
occur before the character.
Forced split: If checked, a split will always happen at the character and stacking will
always occur, otherwise stacking is determined by the Maplex Label Engine.
Example on slide
In the example on the slide, the forward slash (/) is added as a stacking character. Every time
11-10
Font reduction
Reduces label size so it can be placed on the map

Can
specify minimum font size and stepping interval
* Exaggerated example
11-11
Another strategy for fitting labels into small areas is to reduce the size of the label text.
Reducing the font size reduces the overall size of labels in areas where there are size
constraints. When you allow the Maplex Label Engine to reduce the font size, you have control
over the lower limit font size and the step interval that specifies the font size variants for the
label engine.
For example, for a label with a base font of 12 points, you might set a lower limit of 6 points
and a step interval of 2 points. Maplex will first try to place each label at 12 points, then at
10 points, then at 8 points, then at 6 points. If a label will not fit within a polygon, along a line,
or around a point at 6 points, then the label is not placed.
11-11
Abbreviation Dictionary
11-12
Abbreviation dictionary
The Maplex Label Engine can automatically shorten words in order to fit a given label on the
map. You need to specify the word and the abbreviation in an abbreviation dictionary, and then
apply that abbreviation dictionary to a label class.
There are three types of abbreviation dictionary entries: keywords, endings, and translations.
Keywords and endings are only applied to words when the original string cannot be placed
because of labeling conflicts. Translation entries are always applied to all matching words.
Keywords: Can be applied to all words in a string except the last word (e.g., Interstate 10 will
become Int 10, but 10 Interstate will remain 10 Interstate). Keywords are useful for
abbreviations such as Mount to Mt., or International to Intl.
Endings: Are only applied to the last word of a string (e.g., Interstate 10 will remain
Interstate 10, but 10 Interstate will become 10 Int.) Endings are useful for abbreviations such
as Street to St, or Road to Rd.
Translations: Are always applied to all words in a string. Translations may be useful when you
translate a map into another language, when you wish to remove words from a label string, or
when you want all occurrences of a word to be abbreviated.
Abbreviation dictionaries can be saved to a .dic file, and loaded into other ArcMap sessions.
Example on slide
In the example above, the word HIGHWAY is abbreviated to HWY, regardless of where the
word occurs in the text string. The word INTERSTATE is abbreviated to INT, when space is
needed.
11-12
Preparing labels for conversion
Take advantage of label formatting options in ArcMap
Choose symbol, font, color, etc.
Choose placement schema
Label with an expression
Create label classes
Set the reference scale before converting to annotation
Scale at which text is displayed at its font size
11-13
The primary method for creating annotation is to convert ArcMap labels to annotation features.
The annotation may be stored in the map document or in a geodatabase feature class.
The new annotation features will have the same properties as the labels from which they are
derived. You should set the label symbols, fonts, sizes, colors, placement options, and so forth,
before you convert the labels into annotation features.
Setting the reference scale
The reference scale is the map scale at which label text appears at the specified font size. For
example, you may want your annotation to appear at 8 point type at 1:24,000 scale. When you
set a reference scale, label text appears at the specified font size when the map is drawn at that
scale, and becomes larger or smaller as you zoom in or out on the map. If the reference scale
has not been set, the point size remains constant regardless of the map scale (e.g., the text is
drawn at 8 points at all scales).
Setting the reference scale is a preparatory step for creating annotation from your labels.
Annotation features have a reference scale built into their data structures. So when you add
annotation to your map, you do not need to set the reference scale, because those features
already have a reference scale. Determining the correct reference scale for your labels is
important so that when you create annotation from the labels you know how the annotation will
appear at specific scales.
11-13
Creating annotation from labels in ArcMap
ArcMap data layer context menu
Decide how annotation will be stored
Label properties become attributes to annotation features
Label classes become annotation classes
Set
Set properties
properties
11-14
To convert labels for one data layer, right-click the data layer in the ArcMap Table of Contents
and click Convert Labels to Annotation. The Convert Labels to Annotation dialog has options
for: annotation storage (map or geodatabase), filtering (all features, features in the current
extent, or selected features), and whether or not to convert unplaced labels.
If you decide to create geodatabase annotation, you can choose to store the annotation as
standard or feature-linked. If you store the annotation as standard, you have the option to
browse to the output geodatabase that will store the new annotation feature class. If you store
the annotation as feature-linked, the annotation must be stored in the same geodatabase as the
underlying feature class.
If the layers labels have numerous classes, each class will become an annotation class in the
annotation feature class. Annotation classes are analogous to subtypes.
Remember that annotation stores its own reference scale. When you create annotation, the
current scale will be used as the reference scale for this annotation. This can be confusing if
you are zoomed out to the full extent or if you are zoomed in on the map; your annotation may
not turn out the way you expect. Before converting to annotation, set the reference scale for
your labels and make sure they display the way you want them to appear.
11-14
Annotation in ArcGIS
Annotation can be stored as
Map document graphics

Annotation stored as graphic text within map document
Property of the Data Frame
Feature classes in the geodatabase

Standard annotation feature class
Featurelinked annotation feature class
Annotation can include graphic shapes
E.g., Boxes, arrows, or highway shields
11-15
Annotation in ArcGIS can be stored as:

Map document graphics The annotation is saved as a part of the map document. The
annotation is stored as a graphics map layer and can be accessed via the Data Frame properties.
Multiple annotation groups can exist within a map and each has its own properties such as:
reference scale, symbology, and so forth. This might be a good option if you only have a few
pieces of text and you do not want to use your text in many maps.
Geodatabase feature classes The annotation is stored as its own specialized feature class in
the geodatabase. This option is good if the annotation will be reused in multiple maps. There
are two types of annotation feature classes: standard and feature-linked. In the former,
annotation features are independent text features in the map. In the latter, annotation features
are related and affected by the feature objects they are labeling this is a type of composite
relationship class. For example, if the feature is moved or deleted, then the corresponding
annotation moves or is deleted as well.
Annotation is typically text, but may also include graphic shapes like boxes, arrows, and
highway shields.
11-15
Geodatabase annotation
Feature class that contains specialized text features
Properties include reference scale and symbology
May change properties of individual annotation features
May have multiple annotation

classes (subtypes)
Two types
Standard: standalone text
Featurelinked: text from a related

features attributes
C2
C2
R1
R1
Feature-linked
Feature-linked annotation
annotation
Updated, moved, rotated, and/or deleted

with the related feature
Uses a composite relationship class
11-16
The geodatabase allows you to store both textual labels and graphics in a special annotation
feature class. Individual pieces of annotation can be selected and edited in ArcMap, just like
any other feature. Like other feature classes in the geodatabase, all features in an annotation
feature class have a geographic location and attributes. They can be stored inside a feature
dataset or as stand-alone feature classes.
Compared to simple feature classes (e.g., point, line, or polygon), annotation is unique, because
each annotation feature has associated symbology. Text symbology includes properties like:
font, size, color, and alignment. These symbology properties are saved as attributes in the
annotation feature class. Which allows you to use the attributes in queries. Being able to query
symbology properties gives cartographers numerous options for customizing maps.
11-16
Methods to create annotation
Convert labels to annotation

ArcMap:
Easiest
label features, then convert them to annotation
and most common method used
Create a new, empty annotation feature class
ArcCatalog: similar to creating other feature classes
Customized to store annotation features
Import existing annotation into the geodatabase
Convert coverage or CAD annotation

Geodatabase
11-17
Three methods for creating annotation

1. Since dynamic labels constantly reposition themselves in the best location, they might not
always appear where you want them. To assign each piece of text to a specific location, you
may consider converting your labels to annotation. This procedure takes advantage of the
labeling engine functionality in ArcMap, and is the easiest and most common method used to
generate annotation.
2. Alternatively, you could create a new, empty annotation feature class in ArcCatalog. Then
add new annotation features to that feature class in an ArcMap edit session.
3. There are two geoprocessing tools for converting coverage and CAD annotation to
geodatabase annotation. They are located under the Conversion Tools toolbox > To
Geodatabase toolset. These tools allow you to set reference scale and symbol properties when
generating the output annotation feature class.
11-17
Annotation classes
One annotation feature class may have multiple

annotation classes
Each
annotation class has its own symbology properties
E.g., Symbol, expression, and placement properties

Improved
performance over multiple annotation feature classes
Annotation
Annotation
classes
classes
Convert
Convert labels
labels
to
to annotation
annotation
11-18
Classes for geodatabase annotation

A standard or feature-linked geodatabase annotation feature class can contain one or more
annotation classes. Each annotation class contains properties that determine how a subset of
annotation in the feature class displays, including the default symbology and the visible scale
range. In other words, annotation classes are like subtypes. For example, if you have an
annotation feature class for roads, you could have annotation classes of varying text sizes and
scale ranges for highways, major, and minor roads all managed within a single annotation
feature class. Annotation classes save you from having to define and maintain multiple
annotation feature classes.
If you have an ArcEditor or ArcInfo license of ArcGIS, you can create and modify annotation
classes. You create annotation classes when you convert labels to annotation; each label class
converts to an annotation class. Or you create annotation classes when you create an empty
annotation feature class in ArcCatalog. Annotation classes can be defined in the Feature Class
Properties dialog box. To create new annotation for an annotation class, choose the class as the
target in the Editing toolbar.
Support for annotation classes is limited within ArcView license of ArcGIS. You can create an
annotation feature class with one annotation class and edit its annotation. However, if an
annotation feature class has more than one annotation class, you can only display its
annotation. The ArcEditor or ArcInfo licenses of ArcGIS are required to add annotation
classes.
11-18
Creating annotation feature classes
ArcCatalog context menus

Use
New Feature Class wizard
Specify that it will store annotation features

Set
properties
Standard or feature-linked
Reference scale
Symbology
Fields
Annotation can be loaded

or added manually
11-19
Creating an annotation feature class in ArcCatalog

You create a new geodatabase annotation feature class as you would any other feature class:
right-click the geodatabase or a feature dataset, then click New > Feature Class to start the
wizard. Check the box indicating that the feature class will store a custom feature and choose
ESRI Annotation Feature from the dropdown list. If the annotation class will be feature-linked,
select the related feature class. The wizard will have additional panels for setting the reference
scale and default symbology properties for the annotation features.
Creating annotation features
Like all new feature classes, the new annotation feature class is empty. You may add new
annotation features to the feature class in ArcMap using any of the following:
Standard annotation
Manually add annotation features using the tools on the Annotation toolbar.
Use the Convert Labels to Annotation command to create annotation features from labels.
Load annotation features into the feature class by importing existing coverage or CAD
annotation.
Feature-linked annotation
An annotation feature is automatically created when you add a feature to the related
feature class.
Select features in the related feature class and use the Annotate Selected Features
command to create annotation features for them.
11-19
Importing annotation into the geodatabase
ArcGIS provides tools to import coverage or CAD

annotation into the GDB
Convert
each coverage annotation layer or CAD drawing layer

into individual annotation feature classes in the GDB
ArcToolbox > Conversion Tools toolbox > To Geodatabase toolset
Required
inputs include
Standard or feature-linked
Reference scale
Symbology
11-20
Converting coverage or CAD annotation into the geodatabase

You can import coverage annotation feature classes with the Import Coverage Annotation tool.
Similarly, you can import CAD annotation feature classes with the Import CAD Annotation
tool. Both tools import into a new standard or feature-linked annotation feature class they
create in the process. Importing from these formats into a feature-linked annotation feature
class does not automatically link annotation to features.
Values stored in regular text attributes in the annotation feature classes you import are carried
over to the new feature classes.
Coverage and CAD annotation import into the geodatabase as they appear in ArcMap. For this
reason, you should carefully set up the display of the annotation before you import. If you are
importing several tiled annotation feature classes at the same time, you only need to set up
symbology for the first annotation feature class listed in the Import Coverage Annotation or
Import CAD Annotation tool. The tools allow you to apply the same symbology to all the other
feature classes you import.
Preparing coverage annotation for conversion
In both ArcMap and ArcInfo Workstation, the display of coverage annotation is driven by
special attributes in the annotations attribute table called pseudo items. These include
$ALIGN, $SIZE, and $JUSTIFY. The $SIZE pseudo item is especially important; it stores the
text size in map units, like 100 feet. ArcMap translates the $SIZE values into points
automatically during the conversion. However, you cannot use ArcMap to change the size of
coverage annotation features that have a $SIZE value, so you should consider using ArcInfo
Workstation to change the $SIZE value to zero before the conversion.
11-20
Editing annotation in ArcMap
Use Annotation toolbar to:

Create
Edit
new annotation features
existing annotation
Integrated with feature editing environment

Places
new annotation in Editor toolbar target layer
Edit
Edit Annotation
Annotation
tool
tool
Determine
Determine
construction
construction type
type
Unplaced
Unplaced Annotation
Annotation
window
window
Text
Text for
for next
next
construction
construction
Predefined
Predefined text
text
symbols
symbols
11-21
Editing geodatabase annotation

All feature editing is performed in an ArcMap edit session, this includes editing annotation.
The Edit Annotation tool is found on the Annotation toolbar. You use it to select, move, rotate,
and delete annotation features. The tools context menu has multiple options for forcing
annotation to follow selected features and other operations. The tool also lets you change the
curvature of your annotation text. Choose from horizontal, straight, or curved. For curved
annotation, you can modify the shape of the annotation by editing the annotations baseline.
Finally, you can add and remove leader lines for selected annotation, and stack and un-stack
annotation text.
The attribute editor for annotation features also has additional options for setting the annotation
symbology.
The Edit Annotation Tool is used for editing annotation features; the rest of the tools are used
for creating new annotation. The Unplaced Annotation Window tool manages unplaced
geodatabase annotation.
All of the tools on the Annotation toolbar work in conjunction with the Editor toolbar. For
example, if you want to create a new piece of annotation, the new annotation will be placed in
the Editor toolbars current target layer.
11-21
Creating new annotation features

1.
1. Select
Select construction
construction type
type
2.
2. Type
Type in
in text
text or
or use
use text
text
from
from label
label field
field (hover
(hover over
over
feature
feature and
and press
press Ctrl
Ctrl +W)
+W)
3.
3. Pick
Pick aa symbol
symbol
11-22
Most of the tools on the Annotation toolbar are used for creating new annotation. These tools
consist of constructors, input text, and symbology.
Constructors
The first thing you do before you add a new piece of annotation to an existing annotation
feature class is pick a constructor. There are five constructors to choose from: Horizontal,
Straight, Curved, Leader Line, and Follow Feature. The horizontal, straight, and leader line
options can be accessed through shortcut buttons on the Annotation toolbar. In addition to
setting the current constructor, the one-touch tools set the current task and make the Sketch tool
the current tool.
Text
Once you have picked a constructor, you need to decide what text will be placed into the new
annotation. You can manually type in a value for the text or you can use the text from the label
field. To use the text from the label field, hover over the feature and press the Ctrl + W key on
your keyboard.
If you choose to use the text from a field, the value returned will be different depending on if
the annotation is standard annotation or feature-linked annotation. Standard annotation will use
the field value from the current label field. Feature-linked annotation will use the field value
from the label field that the annotation is based on.
Symbol
Once you have picked a constructor and the text, you need to pick a symbol. By default, you
will have one symbol for each annotation class. You can add additional symbols to your
annotation feature class in ArcCatalog.
11-22
Editing annotation
Select one or multiple annotation features to edit
Real
Real preview
preview
Properties
Properties stored
stored
in
in attribute
attribute table
table
11-23
If you select a piece of annotation to edit, then click the Attributes Editor button on the Editor
toolbar, you will have access to both the Annotation and Attributes tabs.
Annotation tab
The Annotation tab allows you to format an individual piece of annotation or if you have
multiple pieces of annotation selected, you may format them all at once. You can also preview
the annotation symbology before you click the Apply button.
Attributes tab
All of the annotations properties are stored in the annotation feature class. For example, the
annotation feature class has the following fields: Bold, Italic, Angle, X Offset, Y Offset, and so
forth. Since all of these properties are stored in the feature class, you can perform queries using
these attributes. For example, you can select all of the annotation that has a 90 degree angle and
reset the angle to 45 degrees. When modifying these attributes, you have a series of dropdown
options to pick from. The dropdown list forces you to choose from one of the listed options,
preventing user error.
11-23
Unplaced annotation
Unplaced map (graphic) annotation

Examine
and manage with the

Overflow window
View
menu > Overflow Annotation
Stored
within .MXD
Unplaced geodatabase annotation

Written
to annotation feature class
View
and manage with

Unplaced Annotation
window
Stored
as Status attribute
11-24
When you convert labels to annotation, you can store them with the map as a graphics layer or
as an annotation feature class in the geodatabase.
Unplaced map (graphic) annotation
Unplaced labels that are converted to map (graphic) annotation are stored in the Overflow
Annotation window of the map document. The unplaced annotation can be viewed and
managed within this dialog. By right-clicking a selected piece of annotation in the window, you
can access a variety of options including: selecting the feature, zooming to it in the map, and so
forth.
Unplaced geodatabase annotation
If you create geodatabase annotation, all unplaced labels are stored with the annotation feature
class. A column called Status is added to the annotation feature class and each piece of
annotation receives a value of Placed or Unplaced. In addition, there is a dialog window, called
the Unplaced Annotation window, which lets you manage all of the unplaced annotation for
each annotation feature class. The unplaced annotation for each annotation feature class is
available every time you add that annotation feature class to a map.
11-24
Dimensions
A special kind of annotation for displaying

measurements on a map
Two types
25.5
Aligned
Run parallel to baseline of feature
Aligned
Aligned
Represents true distance between two points
Linear
Run horizontal, vertical, or rotated to baseline of feature
Represents horizontal, vertical, or rotated difference between two
points
Horizontal
Horizontal
Vertical
Vertical
10
11
10
10
Rotated
Rotated
11-25
A dimension is a special kind of map annotation for showing specific lengths or distances on a
map. A dimension may indicate the length of a side of a building or land parcel, or the distance
between two features, such as a fire hydrant and the corner of a building.
ArcGIS supports two types of dimensions: aligned dimensions and linear dimensions. Aligned
dimensions run parallel to the baseline and represent the true distance between the begin and
end dimension points.
Unlike aligned dimensions, linear dimensions do not represent the true distance between the
begin and end dimension points. Linear dimensions can be horizontal, vertical, or rotated. A
horizontal linear dimensions line represents the horizontal distance between the begin and end
dimension points. A vertical dimensions line represents the vertical distance between the begin
and end dimension points. A rotated linear dimension is a dimension whose line is at some
angle to the baseline, and whose length represents the length of the dimension line itself, not
the baseline.
11-25
Creating dimension feature classes
ArcCatalog
Create
new Feature Class
Reference
Style
scale and units
specifies drawing properties
Can
be oriented either outward or

inward
Option
to change style while editing

in ArcMap
120 ft
Outward
Outward
120 ft
Inward
Inward
11-26
Dimension feature class

In the geodatabase, dimensions are stored in dimension feature classes and can be either inside
or outside of a feature dataset. Like other feature classes in the geodatabase, all features in a
dimension feature class have a geographic location and attributes. Similarly to annotation
features, dimension features are smart; they act within the parameters of a predefined style,
and are able to determine their own symbology and how the dimension features should be
drawn.
A collection of dimension styles is associated with a dimension feature class. A dimension
features style describes its symbology, the parts that are drawn, and how it is drawn. Every
time you create a new dimension feature, it is assigned a particular style. All dimension
features of a particular style share certain characteristics, some of which can be changed on a
feature-by-feature basis. Styles for a dimension feature class are created, copied, and managed
using ArcCatalog. Using the editing capabilities in ArcMap, styles are then assigned to
individual dimension features.
Once a style is created in a dimension class, it cannot be modified. If you want to modify the
properties of an existing dimension style, you must create a new style with new properties. You
can create new styles based on the properties of an existing style, or you can import styles from
other dimension feature classes.
All dimensions can be oriented either outward or inward. Outward dimensions have dimension
lines pointing to the outside of the feature and represent the distance being measured between
the two boundaries. Inward dimensions have arrows pointing in from the outside of the feature
and measure the distance between these two arrows. Whether a dimension is outward or inward
is determined by the distance that the dimension represents and whether that distance on the
map is sufficient to display all the elements of the dimension between the extension lines.
11-26
Dimension style properties
Controls appearance of dimension features
Styles have many properties

Categories: Lines and arrows, Text, and Fitting
138.2
Arrowhead
Extension
Extension line
line
(1)
(1) Overshoot
Overshoot
(2)
(2) Height
Height
(3)
(3) Offset
Offset
(1)
(2)
Dimension line
(5)
Annotation
Dimension
Dimension line
line angle
angle
(4)
(4) Oblique
Oblique
(5)
(5) Rotated
Rotated linear
linear
(4)
Extension line
(3)
Begin
dimension line
Leader
line
Baseline
End
dimension line
11-27
A dimension feature is composed of many parts. Each dimension feature can represent each
part differently by using different symbology and placement rules.
A dimension style describes how a dimension feature is displayed including its symbology,
label font, and label text. Each dimension feature class has at least one style. Dimension
features within a dimension class are associated with a particular style. All dimension features
of a particular style have certain characteristics that are the same, while other characteristics
can be overridden on a feature-by-feature basis.
Dimension styles are created and managed in ArcCatalog in the Feature Class Properties
dialog. You can create, delete, rename, and import dimension styles, and you can specify the
default style for a dimension feature class.
The dimension styles properties are defined in the Dimension Style Property dialog. This
dialog has three tabs: Lines and Arrows, Text, and Fit. The Lines and Arrows tab allows you to
set the properties for the dimension lines, line arrows, and extension lines. The Text tab allows
you to control the content of the dimension text as well as its symbology. The Fit tab allows
you to define how the dimension and dimension text adjust when the dimensions length is too
short to display the arrows and text between the extension lines.
11-27
Creating dimension features
In an ArcMap edit session

Use
Dimensioning toolbar with Editor toolbar

1
2
Determine
Determine
construction
construction type
type
Select
Select style
style
Two ways to create dimensions

Based
on segment of a feature
Create new dimension using Sketch tool

Based
on an existing dimension feature
4
3
AutoDimension
AutoDimension tools:
tools:
1.
1. Dimension
Dimension edge
edge
2.
2. Baseline
Baseline dimension
dimension
3.
3. Continue
Continue dimension
dimension
4.
4. Perpendicular
Perpendicular
dimensions
dimensions
Select a dimension, then use dimensioning tools

11-28
Creating dimensions
Dimension features, unlike simple features, know how they are created. A dimension feature
requires a specific number of points to be entered into the edit sketch to describe its geometry.
The standard edit tools can be used to manually input the points required for these construction
methods. In addition to the manual construction methods, there are several tools that allow you
to create new dimension features from existing dimension features and other features. These
tools are collectively called the Auto-dimension tools.
You can assign a style to a dimension feature when you create it or change an existing
dimension features style. Dimension features draw and symbolize themselves based on the
properties of their assigned style.
The Autodimension tool palette contains four tools for automatically creating dimension
features: Dimension Edge, Baseline Dimension, Continue Dimension, and Perpendicular
Dimensions. Using these tools, you can create new dimension features based on existing
dimension features as well as other features.
Dimension Edge works on any type of feature. It will automatically create a dimension whose
baseline is described by a line segment of an existing feature. It only creates horizontal and
vertical linear dimension features.
Baseline Dimension and Continue Dimension are both used only on existing dimension
features. Baseline Dimension creates a new dimension feature whose begin dimension point is
the same as the existing dimension feature that is being baselined. The Continue Dimension
tool creates a new dimension feature whose begin dimension point is the same as the end
dimension point of the existing dimension feature being continued. Both tools create the same
type of dimension as the existing dimension they are applied to and assign it the style selected
in the Style dropdown list in the Dimensioning toolbar.
The Perpendicular Dimensions tool creates two dimension features which are perpendicular to
each other. This tool can be used to create dimensions for the supposed intersection of two
features in space, such as the edge of one building and the corner of another.
11-28
Exercise 11 Overview
11-29
11-29
11-30
11-30
Rasters and images
Rasters & Images
12-1
Lesson overview
Raster data storage in the GDB

Raster
dataset
Raster
catalog
Raster
attribute
12-2
This lesson discusses how raster data can be stored in the geodatabase. First, it will briefly
review the basics of raster data and the methods to load rasters into the geodatabase. Then it
examines how raster data can be stored within the geodatabase; rasters can be stored either as a
raster dataset, in a raster catalog, or as an attribute of type raster. Additional topics include:
how raster data is managed in the geodatabase and how raster data is retrieved by ArcSDE
from an enterprise geodatabase.
Rasters & Images
12-2
Geodatabase can manage/store raster

data
Data
stored as pixels
1000 rows
Each
pixel has a numeric value
Pixels
are arranged in columns

and rows
May
have one or more value/bands
Each pixel is independent

No
Pixel
discrete features or attributes
1000 columns
Raster data types

Discrete
data indicates a quality of a variable
Continuous
variable
data indicates a quantity of a
12-3
Raster data
When working with GIS spatial data, you can either work with raster data or vector data.
Raster data is composed entirely of pixels, which is the smallest unit of raster storage. Each
pixel represents a small, square patch of geographic space. All pixels in a raster share the
same dimensions and align to one master grid in a series of regular columns and rows.
Each pixel is represented by a numeric value in the database. These values may be either
floating point or integer, and usually record one property of a geographic phenomenon
occurring over the patch of space it covers.
The values stored in a raster will either represent discrete or continuous data. Discrete raster
data represents geographic features that have definable boundaries. Discrete geographic
features include: buildings, wells, land parcels, rivers, and lakes. Continuous raster data
represents geographic phenomena that can vary at every location, like elevation, temperature,
or radio signal strength. Continuous geographic phenomena do not have distinct boundaries.
With raster data, each pixel is independent of the other pixels, recording information only
about the area it covers. For example, a pixel does not know that the pixel beside it might be
part of the same tree or building.
Every raster is made up of at least one band. A raster with one band (e.g., a TIFF) is called a
single-band raster, meaning that each pixel only has one value for a given pixel location.
Rasters that have multiple bands are called multi-band rasters, meaning that for each pixel
location there are several values; each value is stored in a separate band. A good example of a
multi-band raster is a Thematic Mapper (TM) image. TM images generally have seven values
which represent different spectral readings. Each value is placed into one band.
Rasters & Images
12-3
Raster bands
Layer of pixel values for one variable

Band
Single-band rasters
One
depth determines resolution of values
variable is stored
Multi-band rasters
Multiple
variables
are stored
Aerial
Aerial
Photo
Photo
Each
band covers
same geographic area
Stored
together in
one raster dataset
Up
to three bands can

be displayed together
Satellite
Satellite
Image
Image
12-4
Raster data can consist of a single-band or have multiple-bands; the term band is a reference
to how many values are assigned to a pixel in the raster. If a pixel has one value, it is a single
band raster; if it has several values, it is a multi-band raster. Typically, bands refer to the
amount of spectral information that is stored in the raster, where each band is represented as a
layer of information stored within a pixel.
In single-band rasters, only one value is stored within the pixel; this would typically be an
aerial photo or discrete image.
In multi-band rasters, multiple values are stored within the pixels, where each value would
represent the spectral information for a particular wavelength of the electromagnetic
spectrum. An example of a multi-band raster is a LandSat TM satellite image; it has seven
bands (Red, Green, Blue, Near-Infrared, Mid-Infrared, Thermal, and Near-Infrared II spectral
wavelengths).
Rasters & Images
12-4
Raster data in the geodatabase
Raster dataset
Any
valid raster format that

organizes data into bands
Includes
mosaics
Raster catalog
A
collection of raster datasets

stored in a table
Attribute of type raster

An
attribute to a feature that is

of type raster
12-5
Types of raster data in the geodatabase

There are three types of raster data that can be stored in a geodatabase:
A raster dataset
A raster catalog
An attribute of type raster
Having the ability to store raster data in a personal geodatabase is new at ArcGIS 9. However,
you have been able to store raster datasets and raster catalogs in an enterprise geodatabase
since ArcGIS 8.1.
Rasters & Images
12-5
Tools for loading raster data into the GDB
Raster toolset geoprocessing tools

Contains
several tools for creating

and loading raster data into the GDB
ArcCatalog context menu
Import tool
Raster to GDB script tool

Same as above to access
Applicable for personal GDB

and enterprise GDB
Geodatabase
12-6
Raster data loading options

ArcGIS provides numerous tools for loading raster data into the geodatabase. The two basic
options are: to access the collection of raster geoprocessing tools in the Raster toolset, or to use
the Raster to Geodatabase import tool. Both options are accessible through ArcCatalogs
context menus or within the geoprocessing framework.
Raster toolset geoprocessing tools: This toolset contains all the geoprocessing tools that you
would need to create, edit, and manage raster data in ArcGIS. Six of the tools are particularly
useful for loading raster data into the geodatabase:
Copy Raster
Create Raster Dataset
Mosaic
Mosiac to New Raster
Copy Raster Catalog Items, and
Create Raster Catalog
You will explore these tools in more depth later in this lecture.
Import tool: The Conversion Tools toolbox > To Geodatabase toolset > Raster to Geodatabase
script tool is a useful tool for loading rasters in the geodatabase. This tool is a Python script that
enables you to directly import a raster into the geodatabase. You simply specify the input
raster, the output geodatabase, and optionally a storage configuration keyword.
Any of these options can be used to load raster data into both a personal and enterprise
geodatabase.
Rasters & Images
12-6
Raster toolset and Raster to GDB tool
ArcCatalog context menu
ArcToolbox > Data Management Tools toolbox > Raster toolset
Geoprocessing
Geoprocessing
Framework
Framework
ArcCatalog
ArcCatalog
Both methods also access Raster to GDB script tool

12-7
Loading raster data

There are two ways to load raster data into the geodatabase:
Using the ArcCatalog context menu wizard: right-click the geodatabase and click New >
Raster Catalog or New > Raster Dataset to access their respective geoprocessing tools.
You can use the same method to access the Raster to Geodatabase tool, however, in this
case you would right-click the geodatabase and click Import, then click Raster Datasets or
Raster Dataset (mosiac). The first option will load a new raster into the geodatabase, the
latter will append a new raster into an existing raster dataset in the geodatabase.
Within one of the geoprocessing framework environments, you can access any of the
geoprocessing tools to load rasters into the geodatabase. The tools are located in the Data
Management Tools toolbox > Raster toolset.
Both methods access the same raster data geoprocessing tools.
Rasters & Images
12-7
Geoprocessing tools for raster datasets
Copy Raster
Converts to GRID, IMG, TIFF, or GDB format
Loads raster datasets into a raster catalog
Create Raster Dataset
Creates an empty raster dataset element
Mosaic
Mosaics raster datasets into an existing

raster dataset
Overlapping pixel options: first, last, blend, mean, max, or min
Mosaic To New Raster
Mosaics raster datasets into a new raster dataset
Same overlapping pixel options
12-8
There are a number of specific geoprocessing tools that allow you to work with raster datasets.
The Copy Raster tool can be used for two different operations. It converts a raster into a
GRID, IMG, TIFF, or geodatabase raster dataset. It can also be used to load raster datasets
into a raster catalog. All of the properties for the original raster (e.g., the coordinate
system) will be copied, unless you have assigned environment settings. Environment
settings will override the properties of the input raster.
The Create Raster Dataset tool creates an empty raster dataset. During creation, you can
set the cell size, the pixel type, the coordinate system, and the number of bands. If you are
creating the raster dataset in an enterprise geodatabase, you can also specify the storage
configuration keyword, the type of pyramids, the tile size, and the type of compression.
The new raster dataset is empty and can be used to contain one raster dataset or many
mosaicked raster datasets. You can mosaic or load one or more raster datasets into this
new raster dataset, or you can use this dataset with Spatial Analyst tools to store output
results.
The Mosaic tool will mosaic multiple raster datasets into one raster dataset. There are
numerous options for handling overlapping areas: first, last, blend, mean, minimum, and
maximum. This is an improvement from ArcGIS 8.x, where pixels are always overwritten
by incoming pixels. There are also colormap options so you can choose which colormap
from the input rasters will be applied to the mosaicked output: first, last, match, and reject.
The Mosaic To New Raster tool allows you to mosaic multiple raster datasets into a new
single raster dataset. First, a new raster dataset is created, then the input raster datasets are
mosaicked into the new raster dataset. If you would like to mosaic into an existing raster
dataset, use the Mosaic tool. The Mosaic To New Raster tool also supports the overlapping
pixel and colormap options.
Rasters & Images
12-8
Raster datasets
An element in the GDB for images

E.g.,
GRID, IMG, TIFF, etc.
Fast display at any scale
Can mosaic multiple images

together
Image1
Image1
Image2
Image2
Append
into one continuous raster

dataset in the GDB
Inputs
are typically adjacent
Multiple options to address overlapping

pixels
Gaps are allowed
Partial
pyramid building when inserting

or updating area of raster dataset
Mosaic
Mosaic
12-9
In general, raster dataset refers to any ArcGIS-supported raster; it is not really a format. In this
context, raster dataset refers to a raster that is being stored or managed by a geodatabase. There
are advantages to storing rasters in a geodatabase. For example, the geodatabase provides data
management for rasters and makes them more accessible to users; and it stores the rasters
efficiently by converting them to a common, compressed format.
Personal geodatabase storage
A personal geodatabase raster dataset is actually a reference to an externally stored raster, not
the raster itself. This is because rasters may be very large and a Microsoft Access file is limited
to a size of approximately 2 GB. Regardless, they appear to be stored in the geodatabase to
users.
Rasters are converted to ERDAS IMG format (which supports grid attributes) and are stored in
an Image Data Base (IDB) folder. The IDB folder is named after the geodatabase (name.idb)
and is created at the same directory level as the geodatabase. The IDB folder is not visible in
ArcCatalog or ArcMap, but is visible to operating system tools like Windows Explorer.
Enterprise geodatabase storage
Rasters are converted to ArcSDE raster format (no grid attribute support) and are stored in the
host RDBMS as you load them into the raster dataset. ArcSDE offers more data management
options (like security, backup, and recoverability) and has the ability to handle very large raster
datasets.
Mosaics
Raster datasets can be mosaicked into a single raster dataset. Mosaicking allows you to take
two or more raster datasets and combine them into an existing raster dataset to create a single,
seamless raster dataset. Mosaicking creates a raster dataset that is no different in schema from
any other raster dataset. Once mosaicked, all input raster datasets will have the same set of
properties (e.g., same number of bands, same cell size, and same spatial reference).
Rasters & Images
12-9
Raster catalogs
A collection of raster
datasets
Raster datasets stored

in a table format
One
record for each

raster dataset
Each raster dataset keeps its

own properties
Can mosaic rasters within each

raster dataset
Footprint for each raster dataset

Used
for spatial searching
Footprints
Footprints stored
stored as
as
vector
vector data
data in
in SHAPE
SHAPE field
field
12-10
A raster catalog is a collection of individual raster datasets. They are most often used to display
multiple raster datasets without having to mosaic them into one large raster dataset. The raster
datasets may be adjacent, have gaps between them, or overlap one another.
Raster catalog structure
A raster catalog is really a table in any supported format from delimited ASCII to geodatabase.
Each record defines a participating raster dataset with its name, a reference to the raster dataset,
and its extent. In addition, each raster dataset stores a vector footprint that represents the
envelope of the raster dataset.
A raster dataset inside a raster catalog behaves in the same way as a stand-alone raster dataset.
Therefore, you can mosaic raster data into a raster dataset that resides in a raster catalog. You
may query the table and only display the selected raster datasets. The raster datasets are drawn
in the order they appear in the table, first row to last.
The raster datasets in a raster catalog may have different data types and formats, like different
bit depths (e.g., 8-bit integer or 32-bit floating) and cell sizes.
Personal geodatabase storage
You define a raster catalog to be either managed or unmanaged when you create it by
setting a property of the Raster field. In a managed catalog, the individual rasters are converted
to IMG format, are stored in the hidden IDB folder as you add them, and are referenced by
number in the catalog tables Raster field. An unmanaged catalog just stores the path (full or
UNC) to the source raster dataset; the source raster is not converted or moved.
Enterprise geodatabase storage
Raster datasets are converted to ArcSDE raster format and are stored in the host RDMBS as
you add them to the raster catalog.
Rasters & Images
12-10
Managing raster catalogs in ArcCatalog
Contents tab
Properties,
Geography, Metadata, and Bands preview options
Wireframe
Wireframe
preview
preview
Query
Query builder
builder
Preview
Preview dropdown
dropdown
A
12-11
In ArcCatalog, tools are provided for browsing and managing raster catalogs. When you
select a raster catalog in ArcCatalog, you can view its contents using the Contents, Preview,
or Metadata tabs. The Contents tab displays a list of all the raster datasets in the raster
catalog. The Preview tab displays the geographic or table view of the entire raster catalog.
From the table view you can add new fields, delete existing fields, sort the fields, and export
the table. The Metadata tab provides all of the metadata for the entire raster catalog.
To view the properties of individual raster datasets, expand the data view (overview and
selection tabs shown on the right side of the application window above). Note: The data
view is only accessible from the Contents tab. In the data view you can view the properties,
geography, metadata, and bands for the selected raster datasets. You can also view a
wireframe preview (showing the vector footprints of all the raster datasets) of the entire
raster catalog. You can select raster datasets by clicking rows from the Contents tab or by
performing attribute queries through the query window. These windows facilitate
management, display, and query of very large raster catalogs.
Rasters & Images
12-11
Raster catalog selection environment
Raster data can be used for spatial analysis in ArcMap
Rasters can be queried based on their footprints

Select
by attributes
Select
by location
Select
tool
12-12
Querying with vector footprints

Since vector footprints are stored with the raster dataset, they can be easily displayed and
queried. It is possible to perform spatial queries and selections for data management, corridor
analysis, display, and so forth. You can open the attribute table of a raster catalog layer and
work with these footprints like any other feature. Vector footprints make it very easy to
perform subsetting of raster catalogs. In ArcMap, after several footprints are selected, you can
right-click a raster catalog layer and click Export Data. The Export Data dialog box lets you
create a new raster catalog from some or all of the rasters.
In the example above, a select by location operation is used to select all the raster datasets
(from the Rensselear County Catalog) that intersect the Main Highway feature class.
Rasters & Images
12-12
Geoprocessing tools for raster catalogs
Copy Raster Catalog Items

Makes
a copy of a raster catalog
Create Raster Catalog

Creates
Load
an empty raster catalog
data using
Copy Raster tool

Catalogs context menu
Delete Raster Catalog Items

Deletes
The
datasets from the catalog
catalog schema is not deleted
12-13
There are a number of specific geoprocessing tools that allow you to work with raster catalogs.
The Copy Raster Catalog Items tool makes a copy of the entire raster catalog, including its
contents.
The Create Raster Catalog tool creates an empty raster catalog. You assign properties to
the raster catalog when you create it (e.g., the coordinate system and whether it is
managed or not-managed). To load raster datasets into a raster catalog, right-click the
raster catalog in the ArcCatalog tree, and click Load Data or use the Copy Raster tool.
The Delete Raster Catalog Items tool deletes all raster datasets in a raster catalog.
However, the catalog schema is not deleted.
Rasters & Images
12-13
Raster attributes
Raster column data type
One raster column per table

Multiple
rasters can be supported through related tables
Personal GDB, can be managed or not-managed

Managed
data converted to IMG format; managed by GDB
Not-managed
analogous to a hyperlink
Enterprise GDB - rasters converted to ArcSDE raster
12-14
Geodatabase feature classes and standalone tables can contain fields of type raster. A raster
type field can contain any supported image or raster dataset, such as: a digital photo of a
feature, a scanned floor plan, and so forth. Raster fields are defined in ArcCatalog when you
create a table or feature class in a geodatabase or add fields to it after it has been created. Only
one raster field can be defined for a particular table or feature class. If more than one field of
type raster is needed a related table can be used.
When you define a new raster field in a table or feature class in a personal geodatabase, the
raster field's data is not actually stored inside the geodatabase like it is when you define it in an
enterprise geodatabase. Instead when you define a raster field in a personal geodatabase, you
choose whether the data will be managed or not-managed by the personal geodatabase. You
make this choice by setting the 'Managed By GDB' property on the raster field to either Yes or
No.
If the raster field's data is managed by the personal geodatabase, the rasters in the field will be
automatically stored locally as IMG files in a folder named after, and located in the same folder
as, the personal geodatabase. This folder is managed directly by the geodatabase and does not
appear in ArcCatalog to the user.
If the raster field's data is not-managed by the personal geodatabase, the rasters in the field will
be automatically referenced from the geodatabase to their disk location, linked by their
pathname.
In an enterprise geodatabase, all rasters are converted to an ArcSDE raster format and are
stored within the enterprise geodatabase.
Rasters & Images
12-14
Using raster attributes
Load rasters within an ArcMap edit session
Use Identify tool to view raster attributes
12-15
Creating and using raster attributes

Once you have defined a raster field, you can add data into the field in an ArcMap edit session.
Select the feature you want to add a raster to, click the Attributes button in the Editor toolbar to
open the Attributes widow and then click the > button next to the raster field. In the empty
popup window that appears, right-click and click the Load command. This will open a dialog
that lets you choose the raster to load. This is also how you replace an existing raster with a
different one. To delete a raster, click the Clear command.
When you identify a feature containing a raster field, you will see a small button next to the
raster field if a picture exists for the record. Click that button to see the raster in a small popup
window. Right-click in the popup window to see more options. Click the View command (or
just left-click in the pop-up window) to view the raster in a floating resizable window. In this
window, you have the option to zoom, pan, or view the rasters properties.
Rasters & Images
12-15
Raster data in the personal geodatabase
Raster data seemingly stored in the geodatabase
However, all data stored externally from geodatabase

Two
management types
Managed by the GDB

Not-managed by the GDB
Advantages
Organization
through common location
Raster
catalogs provide a selection

environment
Personal
Geodatabase
12-16
Storing raster data in a personal geodatabase

Raster data is stored very differently in a personal geodatabase than in an enterprise
geodatabase. In the next several slides you will learn about how raster data is stored in both
types of geodatabases.
In a personal geodatabase, the raster data is only seemingly stored in the database. In other
words, if you look at a personal geodatabase in ArcCatalog, it will look like the raster data is
stored in the geodatabase. However, the actual data is stored in a separate location outside of
the geodatabase. Therefore, all of the data is actually stored externally from the geodatabase. A
personal geodatabase has a 2GB size limitation, so storing raster data in the geodatabase is not
a feasible option.
How the geodatabase references and manages the raster data can vary. The raster data can
either be managed or not-managed by the personal geodatabase. In the next two slides you will
learn the differences between the two.
There are two main advantages to managing your raster data in a personal geodatabase:
You can manage and view all of your data (raster and vector) from a central location.
If you place your data into a raster catalog, you will have a selection environment. The
selection environment is not be available if rasters are stored completely outside of the
geodatabase (e.g., ArcGIS does not associate the rasters with the geodatabase).
Rasters & Images
12-16
Managed geodatabase raster
Rasters are managed by

the geodatabase
Stored
in folder at same
directory level as the personal
GDB
Raster
data is converted to
IMG format
over 2GB will use IMG
and IGE files for storage
C:\
Student
Manhattan.mdb
MillerRanch
MillerDRG
Data
Raster datasets must be

managed
Raster catalogs can be

managed
Manhattan.idb
c1
m_1.img
c2
m_1.img
12-17
When you load raster data into a personal geodatabase, a folder is created at the same directory
level as the geodatabase. The folder has the same name as the geodatabase and gets an .idb
(image database) extension. In the example above, the USA.idb folder gets created when raster
data is loaded into the Manhattan.mdb.
When you load raster data into a personal geodatabase, the rasters automatically get converted
to an ERDAS Imagine (IMG) format and are stored in a new folder under the .idb folder. This
duplicates your data. You still have the original raster on your machine, and now you have the
new ERDAS Imagine raster in the .idb folder.
IMG files have a 2GB size limit, so if your raster exceeds 2GB, additional IGE files are created
to store that raster dataset. ArcGIS creates these IGE files automatically. The IGE file is an
ERDAS format that has been developed to handle large rasters. When loading a raster that is
larger than 2 GB, the IMG file will be created to store the header information and the IGE file
will store the imagery itself.
Raster datasets must be managed by a personal geodatabase, whereas raster catalogs can either
be managed or not-managed. To have raster data managed by the geodatabase means that
ArcCatalog will take care of all the data management for you. For example, if you delete a
raster dataset from the geodatabase, the IMG file will automatically be deleted from the .idb
folder. If you move the geodatabase to a new location the .idb folder will follow.
Rasters & Images
12-17
Not-managed geodatabase raster
Not managed by the

geodatabase
C:\
Student
Raster
data is referenced
through NAME field
No
Riley.mdb
Riley_catalog
loading of raster data
Pathname
1
2
3
is used to find a
raster file
Only raster catalogs can

be not-managed
No recreation of data
Fast to create
F:\Images\R01.sid
F:\Images\R02.tiff
F:\Images\R03.img
Riley.idb
F:\
Images
R01.sid, R02.tiff,
R03.img
12-18
With not-managed raster catalogs, there is a pointer connecting the individual raster dataset to
the raster data on disk. The raster data is referenced through the NAME field in the raster
catalog table and the pathname is used to find the raster file.
Unlike the managed scenario, there is no conversion of the raster data. The raster stays in its
original format and is not placed into the .idb folder. Therefore, if you delete a raster dataset
from the raster catalog, the corresponding raster does not get deleted. If you move the
geodatabase to a new location, the raster data does not follow. Raster catalogs containing notmanaged rasters are similar to traditional image catalogs, where the raster is managed by the
user and not the database.
Since there is no conversion of the data, it is much quicker to load not-managed raster data into
a personal geodatabase.
Rasters & Images
12-18
Personal GDB storage considerations

Managed
Not-managed
Description:
Data converted into IMG

and stored in a folder
Files are referenced by the

geodatabase (no data
conversion)
Raster types:
Raster datasets
Raster catalogs
Raster catalogs
Raster attributes
Raster attributes
Geodatabase maintains and

administers the IMG files
No data duplication
Data stored in a common

format
Fast to create
Data duplication
Slower to create as data

is converted to IMG format
User needs to maintain and

administer the raster files
Cannot create raster datasets
Advantages:
Disadvantages:
12-19
There are both advantages and disadvantages to storing rasters in the personal geodatabase as
managed or not-managed, illustrated by the chart above. Which method to use will depend on
your particular needs.
Rasters & Images
12-19
Lesson summary
Raster data can be stored in the geodatabase as

Raster
dataset (includes mosaics)
Raster
catalog
Attribute
of type raster
In a personal GDB, rasters can be

Managed
by the GDB
Not-managed
by the GDB
In an enterprise GDB,stored in the RDBMs
Additional parameters available

Storage configuration keyword, pyramids, tiles, and compression
type
12-20
Rasters & Images
12-20
Exercise 12 overview
Exploring raster data in GDB
Creating a raster dataset
Georeferencing a raster
Creating a raster catalog
Exploring field type raster
Creating and populating a raster field
12-21
Rasters & Images
12-21
12-22
Rasters & Images
12-22
Bringing it all together
Data Collection, Editing, and Production
13-1
Lesson 13 overview
We need your feedback !!!!!
Versioning and Enterprise GDB

OR
Customization and creating used defined edit tools,

toolbars and scripts ect.
13-2
13-2
Versioning
Versioning models can help you manage data

integrity
Mark
the Default version as Protected and have User

Master versions
Design 1
Work A
Design 2
Joe
Work B
Default
Anne
Work A
Design 1
Design 1
13-3
13-3
Topology and Versioning

ArcGIS
Topology fully supported in the

versioned environment
multiple
simultaneous editors of same feature
Topology
errors and exceptions are part of reconcile and post
Reconcile
will require validation in the child version
process
Validate
features
May
can result in new vertices inserted in adjacent
result in unexpected conflicts
13-4
13-4
Versioning Example
Common
Ancestor
Version 2 (child of version 1)
Version 1
Split
Validate
Reconcile
13-5
13-5
Topology and geodatabase versions
Merging versions can create topology errors

1 Create Child version
2 Edit DEFAULT; create
new polygon P3
P2
DEFAULT
version
P1
P2
P2
Child
version
P1
P2
P2
Child version
after reconcile
P1
P3
3 Validate new dirty

area in DEFAULT
4 Edit polygon P2
in Child
5 Validate new dirty
area Child
6 Reconcile Child
with DEFAULT
7 Validate dirty area;
error detected
A
P3
13-6
Topology and geodatabase versions

Geodatabase topology is fully supported with versioned enterprise geodatabases. Versions are
alternative representations of the database. It is possible that reconciling (merging) two
topologically clean versions can create topology errors, as the animated sequence on the
slide above illustrates.
13-6
Multi User editing

Two versions
Project begins
Edits merged
Edit versions
add new features
Default version
MultiMulti-user editing
Year 3
Year 2
Year 1
Deleted
Unchanged
Inserted
Historical Archive
13-7
13-7
GDB manages change

History Management
Long
Transactions
T1
T2
T3
Base
Versions
Simultaneous
Edits
13-8
13-8
Distributed Data
Multiple Replication (9.1)
Disconnected Editing
National
Editor
State
. . . Using a MultiMulti-State Database

13-9
13-9
13-10
13-10

DCEP 1.0 Lecture1

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

DCEP 1.0 Lecture1

Uploaded by

Copyright:

Available Formats

Data Editing,

Copyright 2004 ESRI

The information contained in this document is subject to change without notice.

U. S. GOVERNMENT RESTRICTED/LIMITED RIGHTS

Data Collection, Editing, and

Copyright 2002 2004 ESRI. All rights reserved.

Data Collection, Editing and Production

Welcome to Data Collection, Editing and Production

Copyright 2002 2004 ESRI. All rights reserved.

Data Collection, Editing and Production

Welcome to Building Geodatabases I.

and break area

Copyright 2002 2004 ESRI. All rights reserved.

Data Collection, Editing and Production

Learn Data Workflow and Processes in ArcGIS

Ask questions and participate in discussions

Copyright 2002 2004 ESRI. All rights reserved.

Data Collection, Editing and Production

Creating new GDB features

GPS, XY events & Textfiles

with CAD data

Attribues & Tables

Working with Annotation

Working with Raster data

Copyright 2002 2004 ESRI. All rights reserved.

GIS for field

Developer building blocks

Copyright 2002 2004 ESRI. All rights reserved.

ArcGIS is an integrated collection of GIS software.

ArcObjects: Libraries of software components form the foundation of ArcGIS. ArcGIS

ESRI Support Center

Online portal to technical

Patches and service packs

ArcScripts and samples

Request technical support

Suggest a software enhancement

Copyright 2002 2004 ESRI. All rights reserved.

Data Collection, Editing and Production

Additional support resources

ESRI Data and Maps

Copyright 2002 2004 ESRI. All rights reserved.

Data Collection, Editing and Production

ESRI Software Documentation Library

ESRI Educational Services

Copyright 2002 2004 ESRI. All rights reserved.

Data Collection, Editing and Production

Topology rules poster

Online course evaluation

Course Identification Number

Data Collection, Editing and Production

Copyright 2002 2004 ESRI. All rights reserved.

Exercise typographic conventions

Data Collection, Editing and Production

Install the class database

Copyright 2002 2004 ESRI. All rights reserved.

Data Collection, Editing and Production

Copyright 2002 2004 ESRI. All rights reserved.

Data Collection, Editing and Production

Copyright 2004 ESRI. All rights reserved.

Data Collection, Editing and Production

Data Collection, Editing and Production

Copyright 2004 ESRI. All rights reserved.

Data Collection, Editing and Production