ArcGIS2 3.0 Lecture1

Title Page
(This page has been included in the page count and is a place holder only)
Copyright 20002003 ESRI All rights reserved. Course version 3.0. Revised February 2003. 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, 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, ARC COGO, the ARC COGO logo, ARC GRID, the ARC GRID logo, the ARC/INFO logo, AML, ARC NETWORK, the ARC NETWORK logo, ArcNews, ARC TIN, the ARC TIN 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, the ArcFM Viewer logo, ArcGIS, ArcIMS, the ArcIMS logo, ArcLogistics, the ArcLogistics Route logo, ArcMap, ArcObjects, ArcPad, the ArcPad logo, ARCPLOT, the ARCPLOT logo, ArcPress, the ArcPress logo, the ArcPress for ArcView logo, ArcScan, the ArcScan logo, ArcScene, the ArcScene logo, ArcSchool, ArcSDE, 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, @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.
C O N T E N T S
Introduction
Welcome Lesson overview Logistics Teaching methods Course overview Course objectives ArcGIS overview GIS in the enterprise Learning paths Software support resources Exercise typographic conventions Exercise 1 overview Exercise 1: Install the class database 1-2 1-3 1-4 1-5 1-6 1-7 1-8 1-9 1-10 1-11 1-12 1-13
Working with ArcCatalog

Lesson overview ArcGIS products ArcGIS extensions Working with geographic data Storing geographic data ArcGIS spatial data formats The geodatabase overview Using ArcCatalog Adding tables from existing sources Setting viewable data Managing file types visible in ArcCatalog Contents options Tables options Raster options Searching for data Exercise 2 overview Exercise 2: Working with data in ArcCatalog 2-2 2-3 2-4 2-5 2-6 2-7 2-8 2-9 2-10 2-11 2-12 2-13 2-14 2-15 2-16 2-17
Copyright 20002003 ESRI
Introduction to ArcGIS II (for ArcView 8, ArcEditor 8, and ArcInfo 8)
Contents
Working with layers and map symbology

Lesson overview Setting Data View options Setting Layout View options Setting Table of Contents (TOC) options Creating quantitative displays Choosing a classification method Using natural breaks Using quantile and equal interval Using standard deviation Excluding features from a classification Normalizing your data Graduated and proportional symbols Showing quantity with dot density Displaying multiple attributes Symbology Stylesheets Using the Style Manager Creating custom symbols Creating custom lines and markers Using the Advanced Drawing Options Ways to create a map Building templates Changing templates Exporting a map Exercise 3 overview Exercise 3: Working with layers and layouts 3-2 3-3 3-4 3-5 3-6 3-7 3-8 3-9 3-10 3-11 3-12 3-13 3-14 3-15 3-16 3-17 3-18 3-19 3-20 3-21 3-22 3-23 3-24 3-25 3-26
Working with labels and annotation

Lesson overview Labeling options Point placement Line placement Label visibility Labeling with an expression Labeling features differently Setting reference scale Creating annotation 4-2 4-3 4-4 4-5 4-6 4-7 4-8 4-9 4-10
ii
Contents
Storing annotation Overflow window Exercise 4 overview Exercise 4: Creating labels and annotation
4-11 4-12 4-13
Displaying locations from tabular data

Lesson overview What is geocoding? The geocoding process Creating a geocoding service in ArcCatalog Field mapping to geocoding style Geocoding services properties Adding a geocoding service in ArcMap Geocoding a table Unmatched records New fields in the output point feature class Finding an address with the Find tool Adding XY data in ArcMap Exercise 5 overview Exercise 5: Geocoding address locations 5-2 5-3 5-4 5-5 5-6 5-7 5-9 5-10 5-11 5-12 5-13 5-14 5-15
Modifying the ArcGIS interface

Lesson overview Why modify the interface? Saving and accessing your customizations Introducing the Customize dialog Instructors demo Exercise 6 overview Exercise 6: Modifying the ArcGIS interface 6-2 6-3 6-4 6-5 6-6 6-7
Designing a GIS database

Lesson overview The database design procedure Assessing needs Conceptual and logical design Determining the data storage format Why the geodatabase? 7-2 7-3 7-4 7-5 7-6 7-7
iii
Contents
Physical design Database schema Choosing a database projection The UTM projection series Automation plan Pilot project Exercise 7A - B overview Exercise 7A: Organizing a GIS database Exercise 7B: Explore the REGIS database Lesson overview Metadata: Documenting your data Types of metadata Viewing metadata Editing metadata documentation Setting metadata properties Metadata import and export Exercise 7C overview Exercise 7C: Exploring the REGIS project metadata in ArcCatalog
7-8 7-9 7-10 7-11 7-12 7-13 7-14
7-15 7-16 7-17 7-18 7-19 7-20 7-21 7-22
Automating data
Lesson overview Many spatial data automation options Creating new data Georeferencing your data Spatial reference Coordinate domain Creating new data Creating a new feature class in ArcCatalog Defining feature class properties Setting the spatial reference Creating feature datasets (FDS) Digitizing in ArcMap Exercise 8A overview Exercise 8A: Digitizing data in ArcMap Lesson overview Converting digital data Building a database from existing data sources Importing data into the geodatabase ArcCatalog Simple Data Loader 8-2 8-3 8-4 8-5 8-6 8-7 8-8 8-9 8-10 8-11 8-12 8-13 8-14 8-15 8-16 8-17 8-18 8-19
iv
Contents
Transferring data from GPS Importing data from the Internet Defining or changing projection Exercise 8B overview Exercise 8B: Bringing existing data to the geodatabase
8-20 8-21 8-22 8-23
Setting geodatabase validation rules

Lesson overview Introducing subtypes and domains Anatomy of a subtype Setting subtypes Editing with subtypes Domains Anatomy of a domain Setting domains Editing coded value domains Range domains in ArcMap Exercise 9A overview Exercise 9A: Attribute validation Lesson overview Topology Topology manages spatial integrity Working with geodatabase topology Creating a topology Cluster Tolerance Ranks Topology rules Three states of a topology Validating a topology Topology errors and their management The Error Inspector The Fix Topology Error tool Exercise 9B overview Exercise 9B: Spatial validation 9-2 9-3 9-4 9-5 9-6 9-7 9-8 9-9 9-10 9-11 9-12 9-13 9-14 9-15 9-16 9-17 9-18 9-19 9-20 9-21 9-22 9-23 9-24 9-25 9-26
10
Editing spatial and attribute data

Lesson overview Editing security 10-2 10-3
Contents
Navigating the Editor Sketches Editing attributes Feature creation tools Split and Divide Buffer Copy Parallel Union and Intersect Merge Editing topologies in ArcMap Coincident geometry Moving coincident geometry Topology Edit Tasks Auto Complete Polygon Create polygons from lines Intersecting lines Map topology Topology functional comparison The Map Topology tools Exercise 10 overview Exercise 10: Editing features and attributes
10-4 10-5 10-6 10-7 10-8 10-9 10-10 10-11 10-12 10-13 10-14 10-15 10-16 10-17 10-18 10-19 10-20 10-21 10-22 10-23
11
Spatial adjustment
Lesson overview Why use Spatial adjustment? Spatial adjustment Transformation Transformation methods Creating displacement links RMS error Rubbersheeting Edge Snap Attribute transfer Aggregating spatial data Exercise 11 overview Exercise 11: Spatial adjustment 11-2 11-3 11-4 11-5 11-6 11-7 11-8 11-9 11-10 11-11 11-12 11-13
vi
Contents
12
Spatial analysis functions

Lesson overview Dissolving features Aggregating spatial data Clipping features The GeoProcessing Wizard Spatial analysis functions Buffering The Buffer Wizard Overlay analysis and geoprocessing overview Overlay analysis functions Union Intersect Spatial join The analytical process Deciding on project data Analysis options Review analysis tools Exercise 12A overview Exercise 12A: Conducting a pilot study Exercise 12B - C overview Exercise 12B: Conducting a pilot study (independent) Exercise 12C: Making a map 12-2 12-3 12-4 12-5 12-6 12-7 12-8 12-9 12-10 12-11 12-12 12-13 12-14 12-15 12-16 12-17 12-18 12-19 12-20
vii
Introduction to ArcGIS for ArcView and ArcInfo II ModuleTitle
Introduction
Welcome Lesson overview Logistics Teaching methods Course overview Course objectives ArcGIS overview GIS in the enterprise Learning paths Software support resources Exercise typographic conventions Exercise 1 overview
1-2 1-3 1-4 1-5 1-6 1-7 1-8 1-9 1-10 1-11 1-12 1-13
contents
Copyright 20002003 ESRI. All rights reserved.
Introduction
1-1
Welcome
Instructor introduction
Name and educational background GIS experience
Introduction to ArcGIS II
Student introductions
Name Organization Role in organization GIS experience Goals and expectations for this class
1-2
Welcome Welcome to Introduction to ArcGIS II (for ArcView, ArcEditor and ArcInfo). Instructor The instructors introduction will include the following information: Name Educational background Geographic Information System (GIS) experience ESRI experience Teaching experience Students Students should introduce themselves by providing the information below: Name and organization Computer operating system experience and software experience GIS and cartographic experience Reasons for taking this course Prerequisites This course builds on basic skills learned in Introduction to ArcGIS I.
Introduction
1-2
Lesson overview
Logistics Teaching methods Course overview and objectives ArcGIS overview GIS in the enterprise Learning paths Software support resources Course exercise conventions Exercise
1-3
Introduction
1-3
Logistics
Daily schedule
Start Lunch Finish
Facilities
Refreshments and break area Restrooms Telephones and messages Student ID badges Parking
Feedback
Copyright 20002003 ESRI. All rights reserved. Introduction to ArcGIS II (for ArcView 8, ArcEditor 8, and ArcInfo 8)
1-4
Logistics Please note the following information. Daily schedule Under normal conditions, the class will begin each morning 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. Lunch time is generally one hour. Facilities Your instructor will provide information regarding the facilities. Feedback Your feedback is used to improve ESRI's courses. At the end of the week, please evaluate the following: Instructor Course materials Teaching facilities Overall course
Introduction
1-4
Teaching methods
Books
Lecture Exercise and review questions
CDs
Course data
Online course evaluation

http://classeval.esri.com Course Identification Number: _______________
Software evaluation
Email enhancement requests to product teams
desktop_comments@esri.com ims_comments@esri.com sde_comments@esri.com
1-5
Teaching methods This course teaches the basics of the ArcGIS desktop applications by using specialized training materials and methods developed by ESRIs GIS professionals. Research indicates that every student is slightly different in their learning styles. To maximize your learning experience, a variety of teaching methods are used: instructor-led lectures and discussions, demonstrations, computer exercises, and review questions. Class materials You will be provided with both lecture and exercise materials. These are yours to take home after the class is completed, so feel free to write your own notes on them as needed. Most students find these materials to be a valuable resource long after the class is over. You also get a CD of all the data necessary to use for the exercises. Evaluation You will evaluate the course using the Internet. The URL is listed above, and your instructor will give the course identification number. Should you have any suggestion for software enhancements, please use the e-mail addresses provided above to speed up the delivery of your contribution to our software developers.
Introduction
1-5
Course overview
Day one
GIS review and ArcCatalog options Cartography with ArcGIS Displaying tabular locations Customizing the interface
Day 1
Day 2
Day two
Designing a GIS database Automating data Setting geodatabase validation rules
Day 3
Day three
Editing spatial and attribute data Spatial adjustment Spatial analysis and final project
1-6
Course overview Day one will focus on a variety of ArcGIS tools. You will examine ArcCatalog tools for managing data and explore different options in ArcMap for symbolizing and labeling data. You will learn to geocode address information and other methods for displaying tabular data in ArcMap. You will also learn to customize the ArcGIS interface, add and delete tools, and create custom toolbars. Day two and three, you will work through a GIS project from the initial design phase of the project database to solving spatial problems. You will examine different methods for creating data, editing spatial and attribute data, and analytical techniques.
Introduction
1-6
Course objectives
Reinforce ArcMap and ArcCatalog concepts Learn advanced cartographic skills Design, create, and implement a GIS project Explore geodatabase rules
Subtypes and domains Topology
Implement advanced editing techniques Perform spatial analysis functions

Proximity Overlay
1-7
Course objectives This course follows Introduction to ArcGIS I (for ArcView 8, ArcEditor 8, and ArcInfo 8) and continues to present important concepts and functionality for successfully working with ArcGIS. With further exploration of ArcMap, ArcCatalog, and ArcToolbox, students focus on spatial analysis, automation of spatial and attribute data, editing, and advanced options for cartographic display and reports. Hands-on exercises teach ArcGIS procedures in the context of solving real-world problems. Examples and exercises use data from a variety of application areas. A portion of the class is reserved for carrying out an analysis project and applying many of the new skills and techniques learned in this course. Students conduct queries, perform spatial analysis, and present their results in a hard-copy map and report. This course covers a variety of topics but may not include specific tools or concepts used in your applications. If you have questions about particular functionality that does not appear to be covered by this class, feel free to ask your instructor.
Introduction
1-7
ArcGIS overview
ArcGIS Server ArcInfo ArcEditor ArcView
Extensions
Web browser Web server RDBMS server
ArcIMS
ArcMap
ArcSDE
ArcObjects
ArcCatalog
Data Personal geodatabase Enterprise geodatabase
Workstation
ArcToolbox Coverage Shapefile Grid TIN Image CAD
1-8
ArcGIS is the name used to identify ESRIs flagship family of GIS products. ArcGIS includes client software, server software, and data components. ArcGIS itself is not a GIS application; rather, it is a system of software products, each servicing a specific need. Software products and applications When someone purchases an ArcGIS system, they license software products which include one or more software applications. Understanding the difference between products and applications is important in understanding how ArcGIS is structured, and how the topics covered in this training class relate to the system as a whole. For example, one group may license the ArcView software product, which includes the ArcMap, ArcCatalog, and ArcToolbox applications. Another group may license the ArcEditor software product, which includes the same three applications. After installing their respective products, both groups would find icons for the ArcMap, ArcCatalog, and ArcToolbox applications in their Start menus; neither would find an ArcView or ArcEditor icon. But upon running the applications, the ArcEditor group would find more button and menu choices than the ArcView group. In another example, a group who licenses the ArcSDE software product may install and use the ArcSDE, ArcSDE CAD Client, and ArcSDE for Coverages applications.
Introduction
1-8
GIS in the enterprise
Advanced modeling and analysis Data editing and maintenance General analysis and visualization Desktop-based map viewing Internet-based map viewing
Developer interface
Data management and distribution
ArcSDE & ArcIMS ArcInfo

Ex te i ns s on
ArcEditor & ArcPad ArcView 8 & ArcView 3 ArcReader Web browser
Number of users
1-9
The graphic above illustrates the number of users in an enterprise environment performing various GIS tasks with ESRI software. Internet-based map viewing Internet-based mapping, enabled by ArcIMS, can share GIS information with traditionally non-GIS users. Using a standard Web browser, people on an intranet or the Internet can display live maps for simple viewing or more sophisticated analysis. Desktop-based map viewing The free ArcReader application enables people to view pre-configured maps published with the ArcReader Publisher extension to ArcMap. Browse data using an ArcMap-like graphic interface while referencing live file, ArcSDE, and ArcIMS data sources. ArcView 8 and ArcView 3 Two ArcView products provide more substantial GIS functionality, including data analysis and advanced cartographic display. ArcView 8, part of the ArcGIS Desktop family, includes the ArcCatalog, ArcMap, and ArcToolbox applications, as well as many optional extensions for specialized tasks such as raster processing, 3D modeling, and network analysis. ArcView 3, its predecessor built on a different software architecture, offers much of the same functionality, including extensions. A large, experienced user community and millions of lines of customized code continue to make ArcView 3 a popular choice for GIS professionals.
Introduction
1-9
Learning paths
Foundation Introduction to ArcGIS I Learning ArcGIS I
Customization / Programming Introduction to Visual Basic for ESRI software Introduction to Programming ArcObjects with VBA (more)
i
Proficiency Introduction to ArcGIS II Learning ArcGIS II: Presenting information
Extensions (more)
Database Design / Development Building Geodatabases I Geodatabase Design Concepts Creating, Editing, and Managing Geodatabases
(more)
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. The diagram above illustrates the position of this training course in the ESRI Education Solutions curriculum, along with its most closely-related companion courses. Courses identified with the i symbol occur in a classroom with an instructor. The W symbol indicates Web-based courses available on the ESRI Virtual Campus at http://campus.esri.com. 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. From this main training page, follow the ESRI Instructor-led Training link, then click the link for the newest course catalog. On the ESRI Training Web site, you can also find information about new courses that have been developed since the course catalog was printed. 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.
Introduction
1-10
Software support resources

Online Support Center is gateway to resources
http://support.esri.com
Downloads
Software upgrades Technical papers ArcScripts
User-to-user resources
Discussion forums Email lists
Technical archives
Knowledge base Documentation System requirements
ESRI Technical Support

Request support online Find phone and fax numbers Available to support subscribers
1-11
ESRIs primary resource for software support is the Online Support Center (OSC) at http://support.esri.com. From the OSC you can request assistance from ESRI Technical Support, interact with other ESRI software users, and even help yourself to technical information and downloads. Support resources are grouped by software product. When you click the name of a software product, a list of available resources expands below the name. In the graphic above, clicking the ArcGIS Desktop product name reveals links to technical articles, downloads, system requirements, and more. Downloads Downloads from the OSC fall into three main categories. Software upgradesalso called service packs, patches, updates, and utilitiesare ESRIprovided enhancements. These upgrades range from handy tools that facilitate common tasks to system wide upgrades that resolve bugs, improve performance, and add support for additional platforms. Unless otherwise stated in their descriptions, software upgrades are fully supported by ESRI Technical Support. In-depth technical papers discuss topics like system design, performance, and integration. Documents available through the Technical papers link are written by ESRI, and the recommendations they make are fully supported by ESRI Technical Support. The ArcScripts site is a repository of software utilities (scripts) supplied by the ESRI user community for the benefit of its peers. Here you will find ArcScripts, as these utilities are called, for most ESRI software products and customization environments, including ArcGIS VBA, Avenue, and AML. Download scripts anonymously, and create a free account to post tools to the archive. ArcScripts are provided as-is and are not supported by ESRI Technical Support. You may, however, purchase technical support for a per-incident fee.
Introduction
1-11
Exercise typographic conventions

Action Descriptive text
Note
Control name
Warning Question with hint
Keyboard input
1-12
Before you begin your first exercise, you need to recognize the typographic conventions your exercise course book will use. 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, but proceed to the actual instruction, indicated by the checkbox symbol, before interacting with your computer. Action Actions are taskslike starting an application, clicking a button, or typing a commandthat you must perform during your exercise. The square checkbox symbol indicates an action; act only on instructions that are prefaced by the checkbox symbol. To help keep your place while you work, you can mark the checkbox symbol in your exercise course book to indicate which tasks you have completed. This is especially useful when shifting your attention between your book and your computer monitor. Note Paragraphs prefaced with Note: provide inconsequential information, such as an optional way to perform an action or platform-specific syntax for a script.
Introduction
1-12
Exercise 1 overview
Load class database
Execute the Setup program on the class CD-ROM Your destination folder is C:\Student
1-13
The class database All the data and documents necessary for the exercises in this class are stored on the class CD-ROM included with your class materials. Load this data on to your personal computer for your use during class: Insert the CD-ROM into your CD drive. Use Windows explorer to navigate to the CD drive. Double-click setup.exe in the CD contents. The install program will prompt you through the installation of the class database. Confirm that your destination folder for copying the data is to your c:\student folder.
Introduction
1-13
Lesson 1 review
1. ArcGIS is comprised of three software products that increase in their level of functionality from ________________ to ______________ to ______________.
2. All of the ArcGIS software packages include what three applications? _______________________ ________________________ _______________________
Introduction
1-14

Lesson overview ArcGIS products ArcGIS extensions Working with geographic data Storing geographic data ArcGIS spatial data formats The geodatabase overview Using ArcCatalog Adding tables from existing sources Setting viewable data Managing file types visible in ArcCatalog Contents options Tables options Raster options Searching for data Exercise 2 overview
2-10 2-11 2-12 2-13 2-14 2-15 2-16 2-17
contents
2-2 2-3 2-4 2-5 2-6 2-7 2-8 2-9
Introduction
2-1
Lesson overview
ArcGIS and other ESRI software products GIS data overview Managing data in ArcCatalog
2-2
Overview This course uses a number of different teaching methods, learning activities, and GIS-related discussions to teach you how to be a skilled GIS user. The following pages provide an overview of some of the material covered in this course.
Introduction
2-2
ArcGIS products
Scalable desktop applications
ArcView ArcView ArcEditor ArcEditor ArcInfo ArcInfo ArcGIS ArcGISextensions extensions
All support data

Creation Creation Management Management Analysis Analysis Storage Storage
2-3
ArcGIS overview ArcGIS is a comprehensive, integrated, scalable system designed to meet the needs of a wide range of GIS users. ArcGIS software includes ArcView, ArcEditor, and ArcInfo. Depending on your organization's requirements, you can employ one or a combination of the ArcGIS components across your network. With ArcView, ArcEditor, and ArcInfo, you can view databases managed or served by ArcSDE or ArcIMS. Only ArcEditor and ArcInfo provide tools for editing ArcSDE databases.
Introduction
2-3
ArcGIS extensions
Extensions that plug into the new applications
3D Analyst ArcPress ArcScan Geostatistical Analyst Publisher Spatial Analyst StreetMap Survey Analyst Tracking Analyst
2-4
ArcGIS extensions There are a number of software extensions that work in conjunction with ArcView, ArcEditor and ArcInfo. These extensions have been created for specific types of applications and analysis. Most extensions are a separate and additional purchase that supplement your current ArcGIS application.
3D Analyst is used for creating, analyzing, and displaying surface data. ArcPress is a PostScript-based Raster Image Processor (RIP) that prints and exports maps. ArcScan is a powerful tool set for importing, correcting, editing, plotting, and exporting scanned raster images. Geostatistical Analyst will allow you to use kriging and other advanced mathematical methods used in the analysis of spatial properties. Publisher allows you to save maps for distribution and sharing with others. Publisher converts ArcMap map documents (.mxd) into the published map format (.pmf) used with ArcReader. Spatial Analyst was created for complex analysis with raster data and to perform integrated vector-raster analysis. StreetMap is an extension product that supports nationwide address geocoding and street map display. Survey Analyst manages survey data and represents survey measurements and observations on a map. Tracking analyst is an extension for mapping objects that move or change status through time.
To load an ArcGIS extension for use in ArcMap, click Extensions from the Tools menu and select the extension or extensions you want to use. Each extension will have a specific toolbar for your use. To activate the toolbar, right-click on the ArcMap interface and select the extensions toolbar from the context menu.
Introduction
2-4
Working with geographic data

Geometry Geometry Attributes Attributes
Validation Validation
Drawing, Drawing,querying, querying,analyzing analyzing
2-5
Components of geographic data There are three general components to geographic information: Geometry represents the geographic features associated with real-world locations. Geographic features are abstracted into points, lines, or areas. Attributes provide descriptive characteristics of the geographic features. Validation means that geographic features can be made to allow certain types of editing, display, or analysis, depending on circumstances that the user defines. Feature validation is most easily implemented in the geodatabase.
Introduction
2-5
Storing geographic data

Two common data structures: Vector and Raster Use the Spatial Analyst extension for raster analysis
Real Realworld world
Vector Vector (points, (points,lines, lines, and andpolygons) polygons)
Raster Raster (grid (gridcells) cells)
2-6
Spatial data structures In general, there are two structures into which you can abstract the real-world: vector and raster. Vector structures In a vector data model, each point is recorded as a single x,y coordinate. Lines are recorded as a series of x,y coordinate pairs. Areas are recorded as a series of x,y coordinate pairs defining line segments that enclose an area; therefore, the term polygon, meaning many-sided figure. Areas have a perimeter and lines have a length. Examples of vector data are ArcInfo coverages and ArcView shapefiles. ArcGIS is well suited for performing analysis with vector datasets. You can perform standard GIS tasks such as feature display, manipulation, and analysis. Raster structures In the raster data model, the earth is treated as one continuous surface, and each location is represented as a cell. Cell values are used to represent a geographic phenomenon. Cells are organized into a matrix of rows and columns called a grid. Cell values are numbers, and can represent discrete data such as land-use classes, or continuous data such as elevation values. The ArcGIS Spatial Analyst extension stores grid themes as directories in the ARC GRID format. This format is the cell-based equivalent of an ArcInfo coverage. If you do not have the Spatial Analyst extension, your grid themes will be treated as images and can be used for display only.
Introduction
2-6
ArcGIS spatial data formats

Data types vary in format and complexity Suited to model different characteristics
Coverage Shapefile Geodatabase
Grid
CAD
Tin
Table
Internet Map Service
2-7
Spatial data formats The ArcGIS applications support a wide range of spatial data formats, allowing you a great deal of flexibility in the data you may use. Each spatial storage format has strengths and limitations, and you can choose the format that best suits your needs. Features stored together with the same type of geometry: point, line, or polygon, are referred to as a feature class. In addition to the same geometry types, a feature class uses the same attribute columns to describe all of its features, and all features share the same spatial reference. Depending on the storage format, feature classes with spatial relationships between them may be grouped together in a feature dataset. This class focuses mainly on the vector data formats of shapefiles, coverages, and geodatabases for modeling spatial features.
Introduction
2-7
The geodatabase overview

Feature classes
Contain points, lines, or polygons
Feature datasets
Contain spatially related FCs
GDB GDB FC FC FDS FDS FC FC FC FC Enterprise EnterpriseGDB GDB (ArcSDE (ArcSDE+ + RDBMS) RDBMS) Personal PersonalGDB GDB (.mdb) (.mdb)
Geodatabase
Scalability Scalability
Attribute Attributevalidation validation

Subtypes Subtypes Domains Domains Relationship Relationshipclasses classes
Spatial Spatialvalidation validation

Topology Topology Geometric Geometricnetwork network
2-8
Validation means that geographic features can be made to allow certain types of editing, display, or analysis, depending on circumstances that the user defines. Feature behavior is most easily implemented in the geodatabase. In the geodatabase, you can set two types of validations: Spatial and attribute. Spatial validation Spatial validation can be used in two ways: Topology or Geometric Networks. Both of these spatial validation types require a feature dataset where dedicated feature classes participate in either the Topology rules or the Geometric Network rules. A single feature class cannot participate in both. Both of these spatial validation are available in ArcEditor and ArcInfo Attribute validation Attribute validation are of three types: Subtypes, Domains, and Relationship classes. These types of validations are necessarily used with tabular data. Both of these validations are required for maintaining data integrity and efficiency during management, display, and editing operations on the geodatabase. Feature classes Feature classes can be placed in a geodatabase either as standalone or under a feature dataset. Feature classes can contain either points, lines, or polygons. Feature datasets Feature datasets are important for maintaining feature classes that are topologically related. Both topology and relationship classes can only be created in a feature dataset.
Introduction
2-8
Using ArcCatalog
Provides a uniform view of all your data
Define or modify table and feature class definitions Manage data: Copy, Rename, Delete
2-9
Using ArcCatalog ArcCatalog is the application where you can assemble connections to all the data you need to use. When you select a connection, you can access the data to which it is linked to, whether it is located on a local disk or a database on the network. Together, your connections create a catalog of geographic data sources. You can browse your data holdings in three different ways in ArcCatalog using three different tabs: the Contents tab, the Preview tab, and the Metadata tab. The Contents tab shows what a selected itemperhaps a folder or database filecontains. The Preview tab will give a preview of the selected items geographic or tabular data. The Metadata tab will show the metadata for a selected item. Within ArcCatalog you can move, copy, rename, and delete geographic data, and create, manage, and edit associated metadata. You can also perform some modifications to the data, such as adding fields to tables, defining subtypes, domains, and table relationships.
Introduction
2-9
Adding tables from existing sources

Direct access for Info, dBASE, and comma delimited text files Accessing remote data
OLE DB connection
2-10
Accessing existing databases You may access existing Info, dBASE or comma delimited text files simply by connecting to the folder that holds them. To access tabular data in other formats, you can use Object Linking and Embedding Database (OLE DB) providers. ArcCatalog communicates through an OLE DB provider which then communicates with a different database. This standard lets you work with data from any database in the Catalog in the same way. Looking in an OLE DB connection in the Catalog, you will see a list of tables in the database. Microsofts OLE DB providers come with ArcCatalog. They let you access Jet (Microsoft Access), SQL Server, and Oracle databases. Another provider communicates with Open Database Communication (ODBC) drivers.
Introduction
2-10
Setting viewable data

Turn all data types on or off
2-11
Setting viewable data You can control what appears in the Catalog tree of ArcCatalog. This can be done by clicking the Tools menu and selecting Options. Within the Options window and in the General tab, you have the choice of deciding which data types to turn on or off. Turning a data type off will result in the data type to not to be listed in the Catalog tree of ArcCatalog. In other words, to ArcCatalog, the data type becomes invisible, unreadable, or both.
Introduction
2-11
Managing file types visible in ArcCatalog

Add AML macros, text files, or other file types
1 2 5 4 3
2-12
Managing file types visible in ArcCatalog By default, not all file types are set to be displayed in the Catalog tree of ArcCatalog. Only the most common types of data are visible in ArcCatalog. In order to enable other file types to be listed in the Catalog tree of ArcCatalog, click the Tools menu, and select Options. Within the Options window, click the File Types tab, then select New Type. In the File Type window, type the file extension of the data type that you want to add (e.g., AML), in the input field. Then complete the Description of Type (e.g., Arc Macro Language for AML) input parameter and click OK. This will add the information about this file type in the Options menu, such that when you exit the menu, all available .aml files that are contained in the database will be listed in the Catalog tree. You can repeat this procedure for other file types, such as text files (.txt), exchange files (.e00), and so on.
Introduction
2-12
Contents options
Display more metadata in contents view
Standard Standardcolumns columns
Metadata Metadatacolumns columns
2-13
Contents options When you start using ArcCatalog, you will see two columns in Details view that show the Name and Type of each item. You can add columns that show additional properties or information stored in the item's metadata. When an individual item is selected in the Catalog tree, the values that would appear for that item in all columns in Details view are listed in the Contents tab. A column may not apply to all items. You can add your own property and metadata columns to the lists in the Options dialog box. To do so, you must type the exact name of the property or metadata element into the Property text box in the Add Standard Column or Add Metadata Column dialog box. The columns that are included in these lists by default appear in the Caption and Property lists in the dialog boxes. If you delete default columns, you can easily add them again later by choosing their caption or name from either the Caption or Property dropdown lists.
Introduction
2-13
Tables options
Modify table appearance Table behavior
Column Column selection selectioncolor color
Text Textfont, font, color, color,size size Behavior Behavior
2-14
Tables options You can change the appearance of tables in the Catalog to make it easier to read their values. For example, you may want to change the size, color, and type of font used. To quickly pick out which columns are selected, the background color of selected columns is set to the highlight color. When you see an asterisk (*) next to a columns name, the values in that column are indexed; indexes can improve the performance of queries. Use the Options dialog box to change the font, highlight color, and index character used in Table view to suit your preferences. These changes affect the way all tables appear in the Catalog.
Introduction
2-14
Raster options
For grids, images
Default Defaultband bandsettings settings Pyramid Pyramidcalculation calculation
Image Imagefiles filesto tosearch searchfor for
Pyramids
Reduced resolution copies for fast display of large raster images
2-15
Raster options You can also control the way raster data is displayed in the Catalog tree and in the display area of ArcCatalog. To access the raster data display properties, click the Tools menu, and click Options. Within the Options window, click the Raster tab. This tab allows you to control the display of both grids and images. You can set the Default RGB Band Combinations depending on the number of bands you have in the source data. You can also assign which band will be displayed by any of the three standard Red, Green, and Blue guns. This combination will dictate the type of false color imagery you are trying to set to help in interpreting the imagery (especially for satellite images). By default, for a three-band data source, band one will be assigned to the Red gun, band two the Green gun, and band three the Blue gun. The default assignment for a data source with four or more bands is: band four (near-infrared reflectance) to the Red gun, band three (red reflectance) the Green gun, and band two (green reflectance) for the Blue gun. Raster data requires a long time to display, especially if it is of high resolution. You can use the Raster Layer Pyramid Calculation option (on the Raster tab) to display the images with reduced resolution (i.e., you can generalize the raster data for faster displays). You can also control which raster file formats will be listed in the Catalog tree of ArcCatalog on the Raster tab.
Introduction
2-15
Searching for data

Search by
Name & Location Geography Date Metadata
Results
Located in the catalog tree Shortcuts point to the data Can be used anywhere data is used
2-16
Searching for data You can use the Search tool in ArcCatalog to search for data meeting a specific criteria: name and location, geography, date, or an entry in the metadata. Once you click Find Now in the Search dialog box, shortcuts to those items that match the search are added to a list in the Search Results folder in the Catalog tree. These shortcuts provide a link to that matching item wherever it is stored. When a shortcut is selected in the Catalog tree, you can preview the items data and metadata in the appropriate tabs as if you were exploring the contents of the item itself. Once you have found the item that you want to use, you can right-click the shortcut and click Go To Target to select the item itself in the Catalog tree. Alternatively, you can work with the shortcut as if you were working with the item itself. You can drag-and-drop a shortcut onto a map or an ArcToolbox tool. You can also double-click a shortcut to open the items Properties dialog box.
Introduction
2-16
Exercise 2 overview
Explore data with ArcCatalog Set catalog properties Search for data
2-17
Introduction
2-17
Lesson 2 review
1. ArcGIS extensions work with all three core software packages. TRUE / FALSE
2. Feature classes that are spatially related should be stored as stand-alone feature classes inside the geodatabase. TRUE / FALSE
3. Grid data can only be viewed in ArcMap if you have the Spatial Analyst extension loaded. TRUE / FALSE
4. Using the Search tool in ArcCatalog, you can search by ___________________, ____________________, ____________________ and ___________________.
5. ArcCatalog can only view spatial data types. TRUE / FALSE
6. How can you make a new file type (and its extension) visible in ArcCatalog?
Introduction
2-18

Lesson overview Setting Data View options Setting Layout View options Setting Table of Contents (TOC) options Creating quantitative displays Choosing a classification method Using natural breaks Using quantile and equal interval Using standard deviation Excluding features from a classification Normalizing your data Graduated and proportional symbols Showing quantity with dot density Displaying multiple attributes Symbology 3-5 3-6 3-7 3-8 3-9 3-10 3-11 3-12 3-13 3-14 3-15 3-16 3-20
3-21 3-22 3-23 3-24 3-25 3-26
contents
3-2 3-3 3-4
Stylesheets Using the Style Manager Creating custom symbols Creating custom lines and markers Using the Advanced Drawing Options Ways to create a map Building templates Changing templates Exporting a map Exercise 3 overview
3-17 3-18 3-19
Working with layers and maps
3-1
Lesson overview
Setting ArcMap options Creating quantitative displays Working with styles Creating new symbols Advanced drawing options Working with templates
3-2
Overview This lesson discusses different options for displaying data and creating map products. You will learn how to set the layer properties that control the display of data in ArcMap. You will explore the softwares extensive resources of symbols, organized into styles, as well as options to create your own custom symbols. Once your data has been properly displayed in ArcMap, map templates can be used to quickly format your map layout.
3-2
Setting Data View options

Control
What to do when window is resized
3-3
Setting ArcMap Options The Data View The Data View options let you control how your map is displayed when the ArcMap display window is resized. The default is for the display to be redrawn whenever the window is resized. This ensures that the same area is displayed as before, but it also causes the scale of the display to change.
3-3
Setting Layout View options

Control
Appearance Ruler units Grid spacing Snapping grid resolution
3-4
Setting ArcMap Options The Layout View The Layout View options let you control design elements helpful in making quality maps, such as the snapping elements, the resolution of the snapping grid, and the units of the rulers. You can use rulers, guides, and grids to align map elements on the virtual page you use in Layout View. The Layout View Options let you control how these design elements perform. Rulers show the size of the page and map elements of the final printed map. Guides are straight lines that you use to align map elements on the page. A Grid is a series of reference point on the layout page that you use to position map elements. You can choose to turn on or off snapping to any or all of these alignment features.
3-4
Setting Table of Contents (TOC) options

Control
Visibility
Display Source Selection
Display appearance
Font Size
Patch
Size Shape
3-5
Setting ArcMap Options The Table of Contents You can adjust the look of the Table of Contents to suit your needs. For example, you might change the text size and font so that it makes a greater visual impact or is easier to read. You might also want to change the shape of the lines and patches that represent the features on a map. The Table of Contents has two default tabs at the bottom: a Display tab and a Source tab. The Display tab shows the drawing order of the layers and allows you to change the order. The Source tab sorts layers by where they are stored on disk, it is also the tab you use if you want to view any non-spatial tables you have added to your map (e.g., DBF or INFO). This is useful during editing, when you edit all layers in a given folder or database. If you are not planning on using your map for editing, you can hide the Source tab. You cannot change the drawing order of layers from the Source tab. Additionally you have a Selection tab which you can activate in the Table of Contents. This will allow for an alternative method of changing the selectable layers while editing.
3-5
Creating quantitative displays
Graduated Graduatedsymbol symbol
Graduated Graduatedcolor color

1 Dot = 50 people
Charts Charts
Proportional Proportionalsymbol symbol
Dot Dotdensity density
Multiple Multipleattributes attributes
Quantitative displays use a type of classification scheme

3-6
Creating Quantitative Displays Quantitative data is data that describes features in terms of a quantitative value measuring some magnitude of the feature. Unlike categorical data, where features are described by a unique attribute value such as a name, quantitative data generally describes counts or amounts, ratios, or ranked values. For example, data representing precipitation, population, and habitat suitability can all be mapped quantitatively. Which quantitative value should you map? Knowing what type of data you have and what you want to show will help you determine what quantitative value to map. In general, you can follow these guidelines: Map counts or amounts if you want to see actual measured values as well as relative magnitude. Use care when mapping counts as the values may be influenced by other factors and could yield a misleading map. For example, when making a map showing the total sales figures of a product by state, the total sales figure is likely to reflect the differences in population among the states. Map ratios if you want to minimize differences based on the size of areas or numbers of features in each area. Ratios are created by dividing two data values and are also referred to as normalizing the data. For example, dividing the 18- to 30-year-old population by the total population yields the percentage of people aged 18-30. Similarly, dividing a value by the area of the feature yields a value per unit area, or density. Map ranks if you are interested in relative measures and actual values are not important. For example, you may know a feature with a rank of 3 is higher than one ranked 2 and lower than a 4, but you cannot tell how much higher or lower.
3-6
Choosing a classification method

Classification places attribute values into groups Six classification methods are available
Natural breaks (default) Manual Equal interval Defined interval Quantile Standard deviation
3-7
Choosing a classification method When you map quantitative data, you can either assign each value its own symbol or group values into classes using a different symbol for each class. If you are only mapping a few values (less than 10), you can assign a unique symbol to each value. This may present a more accurate picture of the data, because you are not predetermining which features are grouped together. More likely, your data values will be too numerous to map individually and you will want to group them in classes, or classify the data. A good example of classified data is a temperature map you might find in a newspaper. Instead of displaying individual temperatures, these maps show temperature bands, where each band represents a given range in temperature. Ways to classify your data How you define the class ranges and breaks (the high and low values that bracket each class) will determine which features fall into each class and thus what the map will look like. By changing the classes you can create very different-looking maps. Generally, the goal is to make sure features with similar values are in the same class. Two key factors for classifying your data are the classification scheme you use and the number of classes you create. If you know your data well, you can manually define your own classes. Alternatively, you can let ArcMap classify your data using standard classification schemes. The four most common schemes are natural breaks, quantile, equal interval, and standard deviation. These are described on the following pages.
3-7
Using natural breaks

Default method Identifies breakpoints between values Shows clusters or concentrations of values
3-8
Using natural breaks Classes are based on natural clusters of data values. ArcMap identifies break lines by looking for groupings and patterns inherent in the data. The features are divided into classes whose boundaries are set where there are relative gaps in the data values.
3-8
Using quantile and equal interval

Quantile Quantile Equal Equal interval interval
Each Eachclass classcontains containsthe the same samenumber numberof offeatures features
Divides Dividesvalues valuesinto into equal equalranges ranges
3-9
Using quantile and equal interval In a quantile classification, each class contains an equal number of features. A quantile classification is well suited to linearly distributed data. Because features are grouped by the number in each class, the resulting map can be misleading. Similar features can be placed in adjacent classes, or features with widely different values can be put in the same class. You can minimize this distortion by increasing the number of classes. The equal interval classification scheme divides the range of attribute values into equal-sized subranges. For example, if features have attribute values ranging from 0 to 300 and you have three classes, each class represents a range of 100 with class ranges of 0-100, 101-200, and 201300. This method emphasizes the amount of an attribute value relative to other values, for example, to show that a store is part of the group of stores that made up the top one-third of all sales. It is best applied to familiar data ranges such as percentages and temperature.
3-9
Using standard deviation

Shows distribution above and below the mean
Mean = 1,173 493 4 3 2 1 0 260 807 1,354 1,900 2,447 -2 -1 +1 +2 +3 947 1,400 1,853 2,307
Standard deviation = 453
3-10
Using standard deviation This classification scheme shows you the amount a features attribute value varies from the mean. ArcMap calculates the mean value and then generates class breaks by successively adding to it or subtracting from it the standard deviation. A two-color ramp helps emphasize values above (shown in blue) and below (shown in red) the mean.
3-10
Excluding features from a classification

Eliminate values that skew the classification
3-11
Excluding features from a classification It is always a good idea to examine your data before you map it. For instance, you may find that you have a few extremely high or low values or null values where no data is available. These values can skew a classification and thus the patterns on the map. Fortunately, you can choose to exclude these values before you classify your data.
3-11
Normalizing your data

Divide one attribute by another to determine a ratio
Population density Total sales by area
A
3-12
Normalizing your data You may also want to normalize your data before you map it. When you normalize data, you divide it by another attribute to come up with a ratio. Often, ratios are easier to understand than the raw data values. For example, dividing total population by area yields the number of people per unit area, or a density. Dividing a stores sales figure by the total sales for all stores yields a percentage of sales at that store.
3-12
Graduated and proportional symbols
Graduated Graduated
Proportional Proportional
Symbol Symbolsize sizereflects reflects class class
Symbol Symbolsize sizereflects reflects actual data actual datavalue value
3-13
Graduated and proportional symbols When you draw features with graduated symbols, the quantitative values are grouped into classes. Within a class, all features are drawn with the same symbol. Thus, you cannot discern the value of individual features; you can only tell that its value is within a certain range. Proportional symbols represent data values more precisely. The size of a proportional symbol reflects the actual data value. For example, you might map earthquakes using proportional circles, where the radius of the circle is based on the magnitude of the quake. The difficulty with proportional symbols arises when you have too many values; the symbols may become indistinguishable. Also, the symbols for high values can become so large as to obscure each other.
3-13
Showing quantity with dot density

Determine dot size and value Good technique for areas of low and high concentrations
3-14
Showing quantity with dot density When creating a dot density map, you specify how many features each dot represents and how big the dots are. You may need to try several combinations of amount and size to see which one best shows the pattern. In general, you should select values that ensure the dots are not so close as to form solid areas that obscure the patterns, or so far apart as to make the variations in density hard to see.
3-14
Displaying multiple attributes

Symbolize features based on more than one attribute
Street type and traffic volume Parcel land use and value
3-15
Displaying multiple attributes Geographic data usually has a number of different attributes that describe the features it contains. While you will commonly use one of the attributes to symbolize the data (e.g., show categories or quantities), you may sometimes want to use more than one. For example, you might display a road network using two attributes: one representing the type of road and the other representing the traffic volume along it. In this case, you could use different line colors to represent the different types of roads and also vary the line width to indicate traffic volume along each road. When you symbolize your data using more than one attribute, you create a multivariate display. Symbolizing your data this way can effectively display more information about the data; however, it can also make your map more difficult to interpret. Sometimes it might be better to create two separate displays than to try to display the information together.
3-15
Symbology
12,000 + symbols Styles
Set of symbols or elements Industry specific
Civic, transportation, environmental, geology, utilities, real estate.
Create your own Style manager for creation and management
3-16
Symbology A style is an organized collection of elements that are used to make maps, complete maps, or do both. Styles include elements such as symbols, scale bars, north arrows, and colors. There are lots of different styles for different feature types. In ArcMap you have styles for point, line, polygon, and text symbols.
3-16
Stylesheets
Each style contains
Symbols Map elements
Styles provide information on

Symbol properties Labels specifications Color schemes Legend and scale bar characteristics Coordinate reference systems
Styles Styles
3-17
Stylesheets ArcMap starts with two default symbol styles: ESRI and a Window-generated symbol set saved under your profile (in the example above the user is makram). To access the location of these symbols, click the Tools pulldown menu > click Styles > click Style Manager. Available symbol styles are displayed and you can select a style, navigate to their location, import new styles, or create a new style.
3-17
Using the Style Manager

Styles populate the palettes in ArcMap Create a new styleset
3-18
Using the Style Manager Styles are managed by a Style Manager which can be accessed from the Tools menu in ArcMap. Click Styles from the Tools menu, then select the Style Manager option. The Style Manager dialog box appears. ArcMap starts with two default styles: ESRI style and the username style (in the example above the user is tom). You can check which styles are loaded by clicking the Styles button. Any other style you select from this list will be loaded for your convenience in that ArcMap session. Notice the specialized styles for different applications. This makes it easy for an ArcMap cartographer to comply with industry standards of symbolization. If the list of styles do not meet your needs, you can create your own styleset. This can be done by picking the Create New option at the bottom of the style list.
3-18
Creating custom symbols

1 Choose Choosetype typeof ofsymbol symbolor ormap mapelement element 4 Edit Editproperties properties
2 Right-click Right-click in indisplay display area area
3-19
Creating custom symbols You can use the Style Manager to create a new symbol from scratch or you can modify an existing symbol. To create a new custom symbol, right-click on any style in the Style Manager, and from the context menu, select New. To modify an existing symbol, right-click on it in the Style Manager and access its properties. Both actions will active the Symbol Property Editor that will allow you to set the type of symbol, the color, style, size, and so forth, for each layer that will comprise the symbol.
3-19
Creating custom lines and markers

Line types
Simple, Cartographic, Hash, Marker Any number of layers may be combined
Marker types
Simple, Arrows, TrueType fonts, Pictures Use your company logo
3-20
Custom lines and markers You may need to create your own custom symbols for a specific application. You can create any custom symbol or map element type. These are examples of creating custom lines and markers. As with any symbol, any number of layers may compose a symbol. Line symbols are used to draw linear data such as transportation networks, water systems, boundaries, zonings, and other connective networks. Lines are also used to outline other features such as polygons, points, and labels. As graphics, lines can be used as borders, leaders for arrows and other annotation, and freehand drawing. The four line types and are: Simple: Fast-drawing, one-pixel lines with a predefined pattern; or solid, wide lines Cartographic: Straight line template patterns and marker decorations Hash: Hachure, template patterns, and marker decorations Marker: Markers, template patterns, and other marker decorations
Marker symbols are used to draw point features, labels, and other map annotation. They can be used in conjunction with other symbols to decorate line symbols and create fill patterns and text backgrounds. As graphics, they can add special cartographic elements. The four marker types are: Simple: Fast-drawing set of basic glyph patterns with an optional mask Character: A glyph from a TrueType font Arrow: A glyph from a TrueType font Picture: A single .bmp (Windows bitmap) or .emf (Windows enhanced metafile) graphic
3-20
Using the Advanced Drawing Options

Control display of complex symbology
A
3-21
Using the Advanced Drawing Options Right-click on the Data frame and use the Advanced Drawing Options to order the drawing sequence of multilevel road networks with complex symbology. You can drag and reorder the drawing sequence, join features drawn with the same multi-layered symbol, and merge features drawn with a variety of multi-layered symbols.
3-21
Ways to create a map

Create Createa amap mapfrom fromscratch scratch Modify Modifyan anexisting existingmap map
Use Usea apredefined predefinedmap maptemplate template
3-22
Ways to create a map There are three ways to create a map in ArcMap: You can create a map from scratch. You can use a user-defined map template and substitute the elements in it. You can modify an existing map.
3-22
Building templates
Standardize map creation Templates are just maps
Contain everything a map contains
Personal Personaltemplates templates
Have an *.mxt extension ArcGIS templates: Arcexe83\Bin\Templates

Add folders to group templates
Personal templates stored in users profile

<user_profile>\Application Data\ArcMap\Templates\Normal.mxt
3-23
Building templates A template is a kind of map document that provides a quick way to create a new map. Templates can contain data, a custom interface, and a predefined layout that arranges map elements, such as North arrows, scale bars, legends, and logos, on the virtual page. They are especially useful when many maps with the same design need to be created. Templates can contain scripts that you might have written on how to structure your layout or certain layers that you want to appear in all your maps. Map templates have an .mxt file extension. You can store your template permanently under the templates folder in either ArcGIS templates: Arcexe83\Bin\Templates (server install), or For Windows NT: C:\Winnt\Profiles\<user>\Application Data\Esri\ArcMap\Templates or For Windows 2000: C:\Documents and Settings\<user>\Application Data\Esri\ArcMap\Templates When you are storing a layout as a map document, make sure you store it with an *.mxd extension.
3-23
Changing templates
Apply different layout or customizations to your map
Choose a new template Map Data Frames
1 3
3-24
Applying different template You may have created your map from scratch or by choosing a template and then adding layers to the map. Later, if you want to change the layout, you can apply a new template. The Change Layout tool on the Layout toolbar will allow you to choose another template to format your map.
3-24
Exporting a map
Export to an image format
3-25
Exporting a map Once you have created a map, you may want to export it from a map document to an image file. The new image could then be inserted into another document (for example, Microsoft Word or PowerPoint). Export a map by choosing Export Map from the File menu. You can export maps as several types of image files. Some of these include EMF, BMP, EPS, PDF, and JPEG. EMF (Enhanced Metafiles) are Windows native vector, or vector and raster graphics. They are useful for embedding in Windows documents because they can be resized without distortion. BMP (bitmap) files are simple, native Windows raster images. They do not scale as well as EMF files. EPS (Encapsulated PostScript) files are primarily used for vector graphics and printing. PDF (Portable Document Format) files are designed to be consistently viewable across different platforms. They are commonly used for distributing documents on the Web. JPEG (Joint Photographic Experts Group) files are compressed image files. They are commonly used for images on the Web because they are more compact than many other file types.
3-25
Exercise 3 overview
Change layer properties Classify data Make a definition query Create and use styles Create a layer file Use a template to create a layout
3-26
3-26
Lesson 3 review
1. Geodatabases, coverages, shapefiles, and ArcSDE layers do not store symbology. TRUE / FALSE
2. The attribute value that appears with a map tip is set by the primary display field. TRUE / FALSE
3. It is not possible to change templates in ArcMap once the data has been added. TRUE / FALSE
4. What file extension do map templates have? __________________
5. What happens when a definition query is created for a specific layer? _________________________________________________________________________________
6. What three ways can you create a map with? _________________________________________________________________________________
7. Templates are stored in what two locations? _________________________________________________________________________________ _________________________________________________________________________________
8. Where can you access more styles in ArcMap? _________________________________________________________________________________ _________________________________________________________________________________
3-27
3-28
3-28

Lesson overview Labeling options Point placement Line placement Label visibility Labeling with an expression Labeling features differently Setting reference scale Creating annotation Storing annotation Overflow window Exercise 4 overview 4-2 4-3 4-4 4-5 4-6 4-7 4-8 4-9 4-10 4-11 4-12 4-13
contents
4-1
Lesson overview
Labeling options Label placement Label visibility Grouping labels Generating annotation
4-2
Lesson overview Labeling is a property of a layer. A large part of this lesson focuses on setting labeling properties. Once the labels are symbolized and positioned correctly, you can convert the labels to annotation. Annotation is stored in the geodatabase as features that can be manipulated in an edit session. Annotation can also be created from scratch or imported from a coverage. The following topics will be discussed: Labeling options Label placement Label visibility Grouping labels Generating annotation
4-2
Labeling options
Labels Labels
Displayed on the fly Stored as a property of the layer
Annotation Annotation
Stored as a feature Stored separately from the source feature class
Graphics layer Geodatabase
4-3
Labeling options You have two feature labeling options on your map: labels or annotation. Labels A label is text that displays dynamically on your map document. When you zoom and pan around your map, the labels re-display themselves with the best placement for the scale at which you are viewing the map. Label placement is based on the properties set up for the layer. Because the labeling properties are a property of the layer, they will travel with the layer whether it is stored in a map document or a layer file. Annotation Unlike labels, annotations can be treated individually regardless of where they are stored. Labels let you set properties that affect the symbology and placement of all the labels on your map, but you cannot change the properties for a single label. However, you can manually change the properties for a single annotation. The annotation size also stays constant relative to the other features on the map. For example, when you zoom out on a feature, that feature will appear smaller on your screen. Because annotation is just another type of feature, when you zoom in and out on annotation, it will act the same as the other features on your map. Labels, on the other hand, will always remain the same point size regardless of your scale. Annotation can be stored as a graphic on the map or as a feature in the geodatabase.
4-3
Point placement
Placement options
Use predefined placement scheme Place label on point Hierarchy of angles
Label on point Predefined scheme
Rules for conflicts

Weights between labels and features
Angles 45 and 225
4-4
Point placement You have three options for placing labels for a point: Use predefined placement scheme A predefined scheme allows you to place the label in one of eight standard positions around the point. Each position is given a number to indicate its priority: 0, 1, 2, or 3 (1 being the highest and 3 being the lowest). The software will try to place the label starting with the highest priority position (1) and finish with the lowest priority (3). A position with a value of 0 means that that position is off limits and no label will be placed at that position. Place label on point Labeling on the point means that the label is centered on top of the point. Hierarchy of angles Labeling with specified angles allows you to specify a hierarchy of angles around a point where labels will be placed. The angles start at 0, which is to the right of the point, and continue in a counter-clockwise direction. Conflict detection rules are available for all the label placement options. Weights between labels and features Weights can be set for the labels and features. Objects assigned a high weight will not be obstructed and given priority above other objects in the same layer and other layers in the display. Buffer ratio A buffer ratio is the amount of space reserved around the label. You can use the buffer ratio to ensure labels are not placed too close to other labels or features.
Introduction to ArcGIS II (for ArcView 8, ArcEditor 8, and ArcInfo 8) Working with labels and annotation 4-4
Line placement
Constraints
Based on orientation
Above Aboveor orto tothe theright right Below Belowor orto tothe theleft left
Position on line
On start point or endpoint Along line Map units offset
At Atthe theendpoint endpoint
Angle Make labels follow the curve of the line

Following Followingthe thecurve curveof ofthe theline line
4-5
Line placement Label placement for a line is first based on whether the label is oriented to the page or to the line. If the label is line-oriented, it can be placed to the left or to the right of the line based on the lines direction. You can determine a lines direction by symbolizing it with one of the arrow options, which are located at the bottom of the symbology list. If your label orientation is based on the page, your labels can be placed above or below the line. There is also an option for ignoring orientation and placing the label on top of the line. Line labels can also be placed at the beginning of a line, at the end of a line, or best-fit along a line. You can make the text curve parallel to the curvature of the line. An offset between the label and the line, in map units, can be applied for more aesthetic calligraphy. In addition, you can also control the angle of the text relative to the line, i.e., along the line, horizontal, or vertical.
4-5
Label visibility
Scale ranges
Independent of layer
Labels Labelsare aredisplayed displayed between betweenthese thesescales scales
45,000 0
1:1
1:45,000
1:75,000
1:100,000
Label scale range Feature scale range
4-6
Label visibility By default, the visibility of labels is controlled by the visibility of the features in the layer. If you zoom in on your map and a layer appears (i.e., the features in the layer appear), the labels for that layer will appear as well. Alternatively, you can choose to set a scale range for the labels independent of the features in the layer. For example, imagine you are zooming in on a city. When you reach a scale of 1:24,000 the streets appear, but the labels do not. However, when you reach 1:12,000, the labels for the streets appear.
4-6
Labeling with an expression

Visual Basic Script or JavaScript Simple concatenation
+ JavaScript & Visual Basic Script
Logical expressions
Click Advanced If...Then
[Name] [Name]& &vbNewLine vbNewLine& &[POPULATION] [POPULATION]
New line
\n JavaScript vbNewLine Visual Basic Script
4-7
Labeling with an expression By default, labels consist of single field values. You can also label features with an expression built using Visual Basic Script or JavaScript. You can use an expression to label with multiple fields in a concatenated format, and further format those fields with descriptive text. Concatenation is done using specific characters. For Java scripts, use the + sign for concatenation and for Visual Basic scripts use the & sign for concatenation. Logical expressions can also be used to set conditions for labeling the same features differently. For example, you might label capital cities with their names and populations, but label all other cities with just their names. Logical expressions can be syntaxed with If Then statements. While concatenating you may want to stack the information that comes from the different fields. This can be done as follows depending which programming language you are using. \n JavaScript Use \n for stacking when writing Java scripts for your logical expression. vbNewLine Visual Basic Script Use vbNewLine for stacking when writing Visual Basic scripts for your logical expression.
Note: Microsoft provides more detailed information and documentation on scripting languages at http://msdn.microsoft.com/scripting.
4-7
Labeling features differently

Label using advanced options
Classes are groups of features labeled the same way (e.g., larger cities displayed with larger text) Can create multiple classes SQL expression defines the features in a class
4-8
Labeling features differently You can select the Label using advanced options from the Method input dropdown list in the Layer properties dialog box and fill in the options. These options let you create groups of features that are labeled differently with classes. A class represents a group of features with the same labeling properties. The group of features represented by a class is defined with a SQL expression. All the labeling properties discussed up to this point in the lesson also apply to a class. With classes, you can change labeling properties for different groups of features. For example, if you labeled capital cities with larger text than the other cities, you would have a class representing the capitals and a class representing the other cities. The group of features represented by a class is defined with a SQL expression. This option can be accessed by clicking the SQL Query button.
4-8
Setting reference scale

For a data frame Text scales with the map features
Zoom Zoomwith withreference referencescale scaleset set
Set Setreference referencescale scale
Zoom Zoomwith withreference referencescale scaleoff off
4-9
Setting reference scale Setting the reference scale lets you fix the size of the labels relative to the other features in the map at a specific scale. When you set the reference scale, the labels will remain at their current size in map units. The reference scale is set to control the entire data frame. Once the reference scale is set, the text appears larger when you zoom in and smaller as you zoom out. When the reference scale is not set, the point size is maintained as you zoom in and out so that labels appear to be the same size relative to your screen 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; when you add annotation to your map, you do not need to set the reference scale because those features will already have a reference scale. Determining the correct reference scale for your labels is useful when you create annotation from those labels, because you will know how the annotation will appear at certain scales.
4-9
Creating annotation
Convert labels to annotation
Current scale is used as the reference scale Options for storage
Define an annotation feature class in ArcCatalog

Feature linked Annotation is added with new feature
Convert from coverage annotation

Tool in Labels category of the Customize dialog box
4-10
Creating annotation When zooming in and out of the map display, labels will constantly reposition themselves at the best location when re-rendered, and they might not always appear where you want them. To assign each piece of text to a specific location, you must convert your labels to annotation. 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. In addition to converting your labels to annotation, you can create a new annotation feature class in ArcCatalog. After creating the annotation feature class, add the new annotation features to that feature class. Then the annotation will be feature linked. You can then add these new annotation features individually with the Text tool while you are editing a map. You can also load the annotation from a coverage. The coverage annotation is treated like labels that are being converted to annotation. The new annotation will include a reference scale that you set when you create that annotation feature class in ArcCatalog. You can add these new annotation features using the Convert Coverage Annotation tool in the Label category of the Customize dialog box.
4-10
Storing annotation
In a graphics layer contained in .mxd As geodatabase features
When the source feature moves, the annotation does not move
As feature-linked geodatabase features in ArcInfo

When the source feature moves, so does the annotation
7646 7646
7646
4-11
Storing annotation Annotation can be stored in one of three ways: as graphics, as geodatabase features, and as geodatabase features that are linked to the features they are annotating. In a graphics layer: The annotation graphics are stored in a graphics layer in your map. You would store annotation in a graphics layer if this annotation is only applicable to that particular map. This could make the size of your map very large, but if you give this map to someone else, the annotation will automatically come with the map. As geodatabase feature: This stores your annotation in the geodatabase as features that are not related to any other features. If you move the features denoted by this annotation, the annotation does not move. Also, if you change the text in the field that generated the annotation, the annotation is not affected. You would store unlinked annotation if you want your annotation to be a historic record of a specific time. For example, perhaps your annotation represents the names of the streets in 1995. In this case, you would not want the annotation to update when the feature updates because you would want it to store the names for that feature as it was at a specific time. As feature-linked geodatabase features: This stores your annotation in the geodatabase with a relationship to the features that the annotation was created from. When you move the original feature, the annotation moves with it, and when you update the text value that the annotation is created from, the annotation text automatically updates. You would use linked annotation when you want your annotation to reflect the current state of your features.
4-11
Overflow window
List of labels that could not be placed
Options
4-12
Overflow window When you convert your labels to annotation, some of the labels may possibly not be converted because they cannot be displayed at the reference scale based on your placement rules. All the labels that could not be converted to annotation will be placed in an overflow window. You can right-click each of these features in the overflow window and zoom in on them. When you view the feature, you may decide to add that label as annotation and place it yourselfjust right-click on the feature in the overflow window and select Add Label.
4-12
Exercise 4 overview
Turn on layer labels Change the label symbol Change label placement and visibility Display the population with the city name Label the capitals with a different symbol Manage label priority Create and edit annotation
4-13
4-13
Lesson 4 review
1. Labels are a property of a layer. TRUE / FALSE
2. By default, labels have a reference scale associated with them. TRUE / FALSE
3. All labels that cannot be converted to annotation and placed are lost forever. TRUE / FALSE
4. Annotation remains the same point size as you zoom in and out. TRUE / FALSE
5. The visibility of labels can be set independent of the layers visibility. TRUE / FALSE
6. How can annotation be stored? _________________________________________________________________________________
7. Give an example of when you would set scale ranges for labels. _________________________________________________________________________________
8. What scripting languages can be used to label features using multiple fields? _________________________________________________________________________________
9. What happens when annotation is feature linked? _________________________________________________________________________________ _________________________________________________________________________________
10. What placement options are there for labels associated with point features? _________________________________________________________________________________ _________________________________________________________________________________
4-14

Lesson overview What is geocoding? The geocoding process Creating a geocoding service in ArcCatalog Field mapping to geocoding style Geocoding services properties Adding a geocoding service in ArcMap Geocoding a table Unmatched records New fields in the output point feature class Finding an address with the Find tool Adding XY data in ArcMap Exercise 5 overview 5-5 5-6 5-7 5-9 5-10 5-11 5-12 5-13 5-14 5-15
contents
5-2 5-3 5-4
5-1
Lesson overview
Geocoding addresses Displaying XY data
5-2
5-2
What is geocoding?
Linking an address to a geographic location Address is matched to address range on street data A real-world location is assigned to each address
5-3
What is geocoding? A feature is an object that has geometry. In most cases, this geometry is captured by digitizing or scanning paper maps. In many cases, however, geographic data exists that indirectly captures geometry by describing locations such as street addresses, city names, or even telephone numbers. While you understand what these descriptions mean and how they relate to locations on the earths surface, computers do not. In order to display these locations on a map and perform analysis with them, a computer must be given geometric representations (such as point features) of these locations. Geocoding, also known as address matching, is the process of creating geometric representations for descriptions of locations. A geocoding service defines the process for converting these descriptions into geometric shapes. You can use a geocoding service to find individual addresses and to geocode tables of addresses. You can also review and rematch the feature classes and shapefiles that you create through geocoding.
5-3
The geocoding process

Create a geocoding service in ArcCatalog
Defines how the address will be found
Add the geocoding service to a map Match addresses

Individual addresses Addresses stored in a table
Re-match unmatched addresses
5-4
The geocoding process The first step in the geocoding process is to create a geocoding service in ArcCatalog. Geocoding services use a specific set of steps to find a match for an address. First, the geocoding service standardizes the address. Second, the geocoding service searches the geocoding reference data to find potential candidates. Next, each potential candidate is assigned a score based on how closely it matches the address. Finally, the address is matched to the candidate with the best score. Once you have added a geocoding service to an ArcMap document, you can begin geocoding addresses with it. You can geocode a whole table of addresses or use the Find tool to search for individual addresses. After you have geocoded a table of addresses, you will want to review the results. If you are unhappy with the results, you may want to modify the geocoding services settings and try to geocode the table again. This process is known as rematching.
5-4
Creating a geocoding service in ArcCatalog

Choose an address style
Method for finding addresses
Set Reference data

Field mapping to geocoding style
Additional properties
Matching options
5-5
Creating a geocoding service A geocoding service defines a process for converting address descriptions of locations into geometric shapes. Geocoding services are created and maintained in ArcCatalog and enable you to geocode in either ArcCatalog or ArcMap. The geocoding service defines paths to reference data, algorithms for standardizing address descriptions and matching them to the reference data, and parameters for reading address data, matching the address data to the reference data, and creating output. Geocoding styles With ArcMap and ArcCatalog, you can geocode addresses against geodatabases and file based data sources such as shapefiles and coverages. ESRI provides numerous geocoding styles for you to choose. Each style has different requirements for the information that tables of addresses must contain in order to be geocoded. If your reference data is a geodatabase, select a style name with (GDB), otherwise use one named with (File). If a style is named with the word AltName, you can use it to specify an additional table that contains alternate names, for instance the former name of street changed to honor a local dignitary, to the primary street records data. Geocoding reference data In order to find the geographic location of an address, a geocoding service must refer to at least one data source that has both address information and spatial information. A feature class is an example of a data source that includes both types of information. When geocoding an address, a geocoding service searches through the features in the reference data feature class to find the feature that most closely matches the address. The geometry of the matching feature is then used to create geometry for the address.
5-5
Field mapping to geocoding style

Styles categorize address data
301 Style Stylecategories categories Source Sourcedata datafields fields 300
301 399 300 398 N New York ST
N New York ST
399 398
5-6
Field mapping to geocoding style ArcGIS comes with several predefined geocoding service styles that you can use immediately to create geocoding services. These styles cover some of the most common styles of addresses that you might want to geocode. Each geocoding service style has specific requirements for the reference data that it can use to match data. You can use StreetMap data, feature classes, and tables as reference data for geocoding services. This data may contain some common pieces of information that can be used for geocoding including a prefix direction and type, the street name and type, a suffix direction, and a zone. The above example is using a geocoding style for U.S. Streets. This geocoding style lets you create geocoding services for U.S. addresses. This style can use feature classes with any type of geometry, but typically uses feature classes with line or polyline geometry. Each feature in the reference data represents a street segment with two ranges of addresses that fall along that street segment, one for each side of the street.
5-6
Geocoding services properties

How to read the address table How to match addresses
Search for aliases Spelling sensitivity Minimum candidate score Minimum match score Intersections
Output information
Offsets Output fields
5-7
Geocoding service settings Geocoding services have a number of settings that allow you to control the geocoding process. These settings control how a geocoding service reads a table of addresses to geocode, how it matches features in the reference data, and what it writes to the geocoded output. Modifying a geocoding services settings will impact how well the geocoding service will be able to match addresses to the reference data, as well as what information the geocoding results will contain. Matching options Place Name Alias Table A place name alias table allows you to geocode addresses by their common names, for example City Hall, instead of by their street addresses. The place name alias table must contain an alias field for storing the common name, in addition to all the required fields for the particular geocoding services style. Spelling sensitivity The Spelling Sensitivity (SS) controls how much variation the geocoding service will allow when it searches for likely matching candidates in the reference data. The spelling sensitivity setting for a geocoding service is a value between 0 and 100. A low value for spelling sensitivity will allow Mane, Maine, and Man to be treated as match candidates for Main. A higher value will restrict candidates to exact matches. The spelling sensitivity does not affect the match score of each candidate, only the number of candidates considered to be a potential match. Default SS is 80.
5-7
Minimum candidate score The Minimum Candidate Score (MCS) is used strictly in conjunction with the interactive review of records in your address table and also with the find tool. The MCS is the minimum score that a record in the reference data must have to be considered a candidate for one of the address records in the address table. Again this score is used for use with the Find dialog and when you use the Find tool to determine where an address is located. You can choose to display all addresses or just addresses that are greater than the minimum candidate score. Default MCS is 30. Minimum match score The Minimum Match Score (MMS) setting lets you control how well addresses have to match their most likely candidate in the reference data to be considered matched. A perfect match yields a score of 100. Default MMS is 60. Intersection connectors Geocoding services that are based on the U.S. One Range, U.S. Streets, and StreetMap styles can geocode street intersections in addition to street addresses.The connectors setting lets you specify all the strings that the geocoding service recognizes as intersections connectors. Output options Some geocoding styles will determine the side of the street an address is located on. For these styles you can set a side offset to place the resulting feature to the left or right of the street. There is also an option to set an end offset for placing geocoded features. This will prevent features that are located at the end of a reference feature from falling on top of other features, for example, a cross street. Output fields You have four options for additional information that can be included in the output feature class. Output fields can be added that store the x,y coordinates of the features, a standardized address, the reference data ID, and the percent along where the address falls on the reference feature.
5-8
Adding a geocoding service in ArcMap

Use Geocoding Services Manager
Any number of geocoding services may be available
5-9
Adding a geocoding service in ArcMap Your ArcMap document can contain any number of geocoding services. You can use the Geocoding Services Manager to manage the set of geocoding services contained in an ArcMap document.
5-9
Geocoding a table
Use geocoding service to create point features Output data as a shapefile or geodatabase feature class
5-10
Geocoding a table When you geocode a table of addresses, you use a geocoding service to create point features that represent the locations of the addresses. You can geocode a table of addresses and save the output as a shapefile or a geodatabase feature class.
5-10
Unmatched records
Statistics Specify records to re-match
Unmatched records Records with low match scores Tied records All records Use a query
Change geocoding options Match interactively or automatically
5-11
Unmatched records There are a number of options for specifying which addresses in a geocoded feature class you want to rematch. You can rematch just the addresses that are unmatched, all of the addresses with a match score less than a certain value, all of the addresses with two or more candidates with the best score, or all the addresses. In addition, you can specify a query to use that defines the set of addresses to rematch. You can change some of the geocoding options, perhaps change the spelling sensitivity, when you rematch addresses. When you are geocoding a table of addresses, modifying the geocoding settings does not change the geocoding service that you are using. Only the settings that are used to geocode this table are modified. These settings are stored with the geocoded feature class. The original geocoding service is not modified.
5-11
New fields in the output point feature class

Status
U = Unmatched T = Tied M = Matched
Score Side ARC_Street
5-12
Attributes in geocoded feature classes When you geocode a table of addresses, a geocoding service creates some special attributes in the output feature class. Status The status field indicated whether or not the address was matched. This attribute has values of M for matched addresses, U for unmatched addresses, and T for addresses where a tie occurred. Score The score field contains the match score of the candidate to which the address was matched. Side The side field contains the side of the street to which an address was matched, if the geocoding service that was used to match the table contains address information for both sides of the street. This attribute has values of L for the left side of the street, R for the right side, or nothing if the geocoding service could not determine the side of the street. ARC_Street The ARC_Street contains the address information that was geocoded.
5-12
Finding an address with the Find tool

Select geocoding service in Addresses tab Enter address Right-click on result
Flash Zoom to Create graphic Set bookmark
4 1 2 3
5-13
Finding an address You can use a geocoding service to find addresses in ArcMap. In order to use a geocoding service in ArcMap, it must be loaded into the document. It is not necessary to load the reference data for a geocoding service into the map document, though doing so will help you choose an appropriate candidate for an address.
5-13
Adding XY data in ArcMap

Add table containing XY fields as a layer Export to shapefile or geodatabase feature class
5-14
Adding x,y data In addition to data sources such as a shapefile, you can also add tabular data that contains geographic locations in the form of x,y coordinates to your map. X- and y-coordinates describe discrete locations on the earths surface such as the location of fire hydrants in a city or the points where soil samples were collected. You can easily collect x,y coordinate data using a global positioning system (GPS) device. In order to add a table of x,y coordinates to your map, the table must contain two fieldsone for the x-coordinate and one for the y-coordinate. The values in the fields may represent any coordinate system and units such as latitude and longitude or meters. Once you have added the data to your map, the layer behaves just like any other feature layer. For instance, you can decide whether or not you want to display it, symbolize it, set the visible scale, or display a subset of features that meet some criteria.
5-14
Exercise 5 overview
Geocoding and XY data
Create a geocoding service Geocode crime locations Rematch addresses Find individual addresses Add XY data for coffee shops in Redlands
5-15
5-15
Lesson 5 review
1. Geocoding styles are specific to the data format. TRUE / FALSE
2. The geocoding service is created in ArcMap. TRUE / FALSE
3. What purpose does the geocoding service serve? ___________________________________________________________________________ ___________________________________________________________________________ ____________________________________________________
4.
Addresses can be located on the fly using __________________ in ArcMap.
5. Match the following with the correct function: I. Place name alias table II. Copyright Spelling sensitivity 20002003 ESRI. All rights reserved. III. Minimum candidate score IV. Minimum match score V. Intersection connectors
5-16
a. Allows you to specify all strings that the geocoding service recognizes as intersections. b. Allows you to geocode addresses by their common names instead of by their street address. c. The threshold value to determine whether or not a potential candidate should be considered. d. Controls how much variation the geocoding service will allow when it searches for match candidates in the reference data. e. Controls how well addresses have to match their most likely candidate in the reference data to be considered matched.
6. What four fields are included in the output point feature class of a geocoding process? ___________________________________________________________________
7. How can you display X, Y coordinate data in ArcMap? ___________________________________________________________________
5-16

6-4 6-5 6-6 6-7
contents
Lesson overview Why modify the interface? Saving and accessing your customizations Introducing the Customize dialog Instructors demo Exercise 6 overview
6-2 6-3
6-1
Lesson overview
Use of the Customize dialog Manage toolbars, buttons, and user interface controls Store and distribute your customizations
6-2
Overview Modifying the ArcGIS interface There is more to the ArcGIS interface than meets the eye. In this lesson, you will learn how to easily manipulate the menus, tools, and shortcut keys to make a custom interface suited to your needs and preferences.
6-2
Why modify the interface?

Personalize the software to fit your needs
Group frequently used tools together Display only commonly used tools Add macros for common tasks Tools Macros
Shortcuts
6-3
Why modify the interface? There is a lot more to ArcMap and ArcCatalog than immediately meets the eye. Many tools exist within the applications that are not available on the default toolbars. Through the Customize dialog, you are able to add these tools to existing or new toolbars in ArcMap or ArcCatalog. You can also program shortcut keys and add Visual Basic for Applications macros to perform common tasks more efficiently. This ability lets you customize an ArcGIS interface for a user or specific project.
6-3
Saving and accessing your customizations

Interface changes can be saved in a map document or a template file
.mxd .mxt extension Normal.mxt is the default template (stored in user profile)
6-4
Saving and accessing your customizations Modifications made to the ArcMap interface can be saved in a map document, in a template file with a .mxt extension, or in the Normal template. Modifications made to the ArcCatalog interface can only be saved in the Normal template. To create a new template file by use the Save As command from the File pulldown menu. For ArcMap, the default template file is Normal.mxt. If you want your modifications to appear as soon as you bring up the application, then save them to Normal.mxt.
6-4
Introducing the Customize dialog

Graphical interface for customization and development
Right-click Right-clickon oninterface interface
6-5
The Customize dialog Using the Customize dialog, you can expand the default menus and tools, create your own toolbars, and program shortcut keys. These types of basic modifications make you more productive and do not require any programming. The Customize dialog is available through the Tools menu or by right-clicking on the interface. The Customize dialog has three general tabs Toolbars This tab allows you to create new toolbars and controls which toolbars appear on the interface. Commands This tab provides access to all of the ArcGIS commands that can be clicked and dragged onto a toolbar or menu. The commands are organized by their functional category. Options This tab allows you to control certain security and access issues such as locking the interface from modifications and determining the level of security for working with outside macros.
6-5
Instructors demo
Turn toolbars on or off Create new toolbars Create new controls Add, delete, and move controls
To toolbars To context menus
Program a shortcut key Lock customization
6-6
6-6
Exercise 6 overview
Modify an existing toolbar Create and add commands to a new toolbar Add a command to a context menu Program a shortcut key Save interface modifications to a custom *.mxt file
6-7
6-7
Lesson 6 review
1. In order to modify the ArcMap interface you must write code. TRUE / FALSE
2. All available ArcMap functionality is already on the interface. TRUE / FALSE
3. The Customize dialog is not available in: a) ArcCatalog b) ArcMap c) ArcToolbox
4. A. What is the default template file for ArcMap? B. Where is it stored? A._________________________________________________________________________ ____________ B. ______________________________
5. Which of the following cannot be done through the Customize dialog? a) Adding toolbars b) Creating shortcut keys c) Removing tools d) Adding macros e) None of the above
6. Where can customizations be stored? __________________________________ _________________________________ ______________________________
7. How do you add functionality to context menus? ___________________________________________________________________________ ___________________________________________________________________________ ________________________________________________________________________ 8. What are shortcut keys? ___________________________________________________________________________ __________________________
6-8

Lesson overview The database design procedure Assessing needs Conceptual and logical design Determining the data storage format Why the geodatabase? Physical design Database schema Choosing a database projection The UTM projection series Automation plan Pilot project Exercise 7A - B overview Lesson overview Metadata: Documenting your data Types of metadata Viewing metadata 7-6 7-7 7-8 7-9 7-10 7-11 7-12 7-13 7-14 7-15 7-16 7-17 7-18
contents
7-2 7-3 7-4 7-5
Editing metadata documentation Setting metadata properties Metadata import and export Exercise 7C overview
7-19 7-20 7-21 7-22
7-1
Lesson overview
The database design procedure
Needs assessment Conceptual and logical design Physical design Automation plan Pilot project Implementation
Metadata
7-2
Overview Nothing is more critical to the success of a GIS project than good planning. In this lesson, you will be introduced to the issues and processes involved in designing a GIS database. You will then put some of these concepts into practice in the following lessons as you build a geodatabase and use it to conduct some simple analysis.
7-2
The database design procedure

Needs Needsassessment assessment Conceptual Conceptualand andlogical logical design design
Prototyping Prototyping
Physical Physicaldesign design Automation Automationplan plan Pilot Pilotproject project Final Finalimplementation implementation
7-3
The database design procedure There is no single correct procedure for database design; the procedure outlined here is a guideline. The database design process is not linear. There are feedback loops, especially between the pilot study, the conceptual and logical designs, and the physical design. Needs assessment Determine the functions that will be supported by the GIS in this time-consuming step. To get the information necessary to complete this task, you could interview potential users, tour operations, conduct inventories of data, hardware, software, and personnel, and conduct educational seminars. Conceptual and logical design Determine database contents and how to logically organize the data in the database. The conceptual and logical design for the project in this course is based on the concept of a shared database using ESRI data models, particularly the geodatabase. Physical design Physically structure the data so that it conforms to the ESRI data structures. A detailed database schema is also implemented in this phase, along with plans for documentation and naming conventions. Automation plan Establish automation procedures. Prepare data for automation and implement the plan. If there are problems during this step, you may need to reevaluate the design of the database. Pilot project Test the functionality, performance, and flexibility of the database design. At least one pilot study should be performed before full implementation of the database. Prototyping Remember to test as you go. Consistent feedback from users can avoid problems later.
7-3
Assessing needs
Define your objective Decide what you need to achieve it Ask the right people the right questions Data Data
GIS GIS tasks tasks
GIS database
Users Users
7-4
Assessing needs Perhaps no step in the database design process is as critical and potentially time-consuming as the needs assessment. There is a good reason for committing the proper attention and resources to this step. The ability of the GIS to operate acceptably is directly related to how well the necessary functions the GIS will perform are understood. To gather the right information, you must ask the right people the right questions. This means conducting detailed interviews with end users, data managers, supervisory personnel, and anyone else who might be impacted by the new system. From these interviews you should try to determine: What tasks are performed using spatial data. What tasks are performed that do not currently use spatial data, but have a spatial component. What tasks are not currently performed, but are desired. Who will be using the system and what their roles will be. What types of products the system will need to produce (maps, reports, etc.). What applications will need to be developed. What data will be needed to fulfill the stated tasks. Will the data be shared among multiple users. What special security measures are necessary.
7-4
Conceptual and logical design

Identify geographic entities and attributes Save entities into feature classes Organize geographic entities into thematic layers
Real-world Real-world entities entities Feature Featureclass class Attributes Streets Streets
Lines Lines Name Name Class Class Connectivity Connectivity rules rules
Soil Soiltypes types

Polys Polys Type Type Permeability Permeability Soil Soilclass class domain domain
City Cityparcels parcels

Polys Polys Land Landuse use Zoning Zoning Open Openspace space subtype subtype
City Citytrees trees

Points Points Species Species Age Age None None
Behavior
7-5
Conceptual and logical design Once you have determined which data to store in your database, your next task is to select feature classes and organize these feature classes into layers. The conceptual design is a top-level concept of how the database will work. The logical design is a detailed layout that fills in the conceptual design in accordance with a specific data model. This procedure includes determining the database contents (spatial, attribute, and behavior), selecting appropriate geographic datasets, and organizing the content into a series of themes.
7-5
Determining the data storage format

Choose a format that meets your needs You can convert between formats if necessary Think long-term
CAD CADfiles files Shapefiles Shapefiles Coverages Coverages
Raster Raster
Geodatabase Geodatabase
GIS database
7-6
Determining the data storage format Data storage formats ArcGIS offers you many choices for storing spatial and attribute data. Each format has its strengths and limitations, but if you understand your needs, you should be able to select the ones that will work best for the GIS being developed. Some issues to consider when choosing data formats are: Topology: Coverages store polygon and line topology. The geodatabase has multiple topology options. Shapefiles do not store topology. Vector versus raster data: Raster format is especially suited to data without clear boundaries (continuous data) such as temperature, pollution, 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.
7-6
Why the geodatabase?

Geodatabase
Scalability Scalability
Personal GDB (.mdb)
Validation Validation Spatial:

Geometric networks, Topology
Enterprise GDB (ArcSDE + RDBMS)
Attribute:
Subtypes, Domains Relationship classes Custom
7-7
Why the geodatabase? The geodatabase format offers many unique advantages for geographic data storage. Scalability As user needs for security and data management grow, the geodatabase can meet them. Custom features Because of its COM architecture, custom objects can be programmed that represent realworld features more accurately. Domains and subtypes These properties, easily created and maintained in the geodatabase, make data creation, editing, and maintenance much more efficient and would require special programming to be achieved in other formats. Geometric Networks Using the geodatabase, you can create geometric networks for modeling connectivity and performing trace and path finding analysis. 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. In addition, when you work with the geodatabase you have the choice between assigning or not assigning topology to your data. You can also pick which topology rules you want to use. The coverage model does not offer this flexibility.
Introduction to ArcGIS II (for ArcView 8, ArcEditor 8, and ArcInfo 8) Designing a GIS database 7-7
Physical design
Detailed layout of conceptual and logical steps Identify sources of data Clarify database schema
Tabular structure Relationships Coding schemes Domains and subtypes
Determine documentation procedures

Naming conventions Updating metadata
7-8
Physical design There are some physical design issues to take into consideration when designing your database. Data sources Decide which source of data to use for the GIS. This step may involve searching outside the organization. This is an important step because both the cost and quality of the database can be profoundly affected by the choice of data sources. Designing individual datasets Make the final layout of each geographic dataset and independent table. Decide precisely how each data element will be stored and what coding schemes will be used. Determine what relationships will be stored and what the keys will be. Also determine what domains and subtypes will be established. This step is a detailed translation of the conceptual design into a physical layout. Documentation Establish a standardized naming convention for spatial, attribute, and related file data. Determine what information will be stored as the documentation for the database and what the procedures will be to implement it.
7-8
Database schema
Database structure or design Thinking through ahead of time saves effort later
Field Fieldnames names Field Fieldtypes types
Values Values
R Re ella attiio on ns sh hiip ps s
s s in a in a m m o o D D
7-9
Database schema The schema of a GIS database is its overall structure. This part of the physical design translates the conceptual or logical design into a detailed layout. In addition to the data components, the schema should also take into account the physical storage devices, security issues, and user needs. Once designed, a database schema should be difficult to alter, but possible if truly necessary. The schema is similar to the blueprints for a house. It would be impractical to decide you want a French Tudor style house halfway through the construction of your Victorian cottage, yet you could do it. The key is to know what you want before you start and to plan for it.
7-9
Choosing a database projection

Issues to consider
Which spatial properties are most critical for your applications? Where is your study area? How large is your study area? Who will you share data with, and how often?
7-10
Choosing a database projection Because projecting a three-dimensional surface onto a flat one causes distortion of spatial properties, choosing the appropriate projection can have an important impact on your database. This slide lists some of the issues you need to consider when making this decision. You should also remember that even if you store datasets in different projections, the ArcMap application can still project them on the fly so they all display in the same coordinate space. For this reason, some database designers elect to store their data in decimal degrees of latitude and longitude, then apply a projection when the need arises.
7-10
The UTM projection series

Zone 1 11 Zone 60
Globe is divided into 60 zones, 6 degrees wide A separate Transverse Mercator projection is applied to each zone Redlands falls in Zone 11
7-11
The UTM projection series The Universal Transverse Mercator (UTM) projection series covers the world between latitudes of 80 south and 84 north. The earth is divided into 60 zones, each spanning 6 degrees of longitude. The zones are numbered 1 through 60, starting at 180 west longitude. The same Transverse Mercator projection is then applied to each zone. The UTM projection is based on a cylinder whose axis is oriented parallel to the plane of the equator, hence the transverse part of its name. Each zone has two lines of secancy. These two lines represent the points of true scale for the projection within the zone. The further a point is from one of these secants, the higher the positional error. The UTM projection is designed for a scale error not to exceed 0.1 percent within each zone. Error and distortion increase for regions that span more than one zone, so UTM may not be the best projection in all cases. The course exercises is built on data using the Universal Transverse Mercator (UTM) projection, Zone 11, Datum: NAD83, Spheroid: GRS_1980. You can learn more about the UTM projection series and other projections in the online documentation.
7-11
Automation plan
$
Data Datapurchase purchase Data Datacapture capture Part Partof ofthe the automation automationplan plan
Subtypes Subtypes Domain Domain Relationship Relationship classes classes Topology Topology Geometric Geometric networks networks Annotation Annotation
Data Dataconversion conversion and andediting editing

Data Data aggregation aggregation
7-12
Automation plan Automating data Once a database design has been finalized, you can begin to incorporate data into the database. Although there are a myriad of commercial sources and techniques for capturing data, the process usually follows these three steps: 1. Convert the data into the desired format. This could require multiple steps. 2. Correct any spatial errors and add the appropriate attribute data. 3. Aggregate individual pieces of data into the complete representation of your study area. This may also require eliminating some superfluous data. Remember to plan the methods of data automation before beginning this phase of the project and to document each step.
7-12
Pilot project
A small, focused test Determine if your design works It is better to go backwards than to go forward and fall
7-13
Pilot project Conducting at least one pilot study lets you evaluate the design of your database at a relatively low cost prior to full-scale implementation. The design should be tested for functionality, performance, and flexibility. To meet this objective, a pilot study should reflect the types of tasks the GIS will be required to perform. It should also use several different datasets to ensure that the design is working across the board. More than one pilot study may be required.
7-13
Exercise 7A - B overview
Given a needs assessment, create a simple, logical, and physical design Explore existing data from the database
7-14
7-14
Lesson overview
Database design Metadata
7-15
Overview When designing and implementing a GIS project, metadata is often overlooked. Keeping good quality and up to date metadata can be very time consuming. However, not keeping metadata for any piece of data can essentially make that piece of data worthless over time. For example, if you generate a feature class and choose not to store the projection information with that feature class, anyone who wants to use your data has to contact you. If you decide to move on to another job and someone else takes over the management of your data, then this data become useless. Creating and updating metadata for every piece of data you generate is crucial. In this lesson, you will explore the different metadata options that are available in ArcGIS.
7-15
Metadata: Documenting your data

Available for anything in ArcCatalog
Including added file types (.txt, .ppt, etc.)
Stored in Extensible Markup Language (XML)

Similar to HTML but with custom tags Example:
<abstract>Boundary of Aquidneck island</abstract>
Stored with the data

Moved/copied with the data if the data is managed by ArcCatalog
7-16
Metadata: Documenting your data Metadata (data about data) is a reference that serves as a blueprint both for building the database, and as a guide for subsequent users. Storing this documentation and keeping it current has long been one of the more frustrating and least-performed tasks in GIS database development, but ArcGIS 8 makes the creation and maintenance of metadata much easier than it has been in the past. The ArcCatalog application contains a special metadata tool that allows you to enter documentation for each component of the database. The information you can store conforms to the requirements of the Federal Geographic Data Committee (FGDC). ArcGIS will automatically capture and store some of the data (the Properties shown on this slide). The user is required to store any other information they believe is relevant. The metadata is stored in Extensible Markup Language (XML), a simple Internet-compliant format. This means that your metadata created in ArcCatalog can be viewed from there or with a Web browser. There are different predefined formats, or stylesheets, for viewing the metadata, but you can also create your own.
7-16
Types of metadata
Documentation
Created by the user
Documentation Documentation
Properties
Created by ArcCatalog Preferences for when to update
Properties Properties
7-17
Types of metadata Metadata created in ArcCatalog contains two components. Documentation This is the information added to the metadata by the user. It usually describes the quality or content of the data. Examples include field descriptions, code definitions, and contact information. Properties This information is automatically stored in the metadata for each feature class by ArcCatalog. Examples include projection definition and number of features.
7-17
Viewing metadata
Stylesheets define how XML data is presented
Written using Extended Stylesheet Language (XSL)
Stylesheets Stylesheets
XML XML FGDC FGDCESRI ESRI ISO ISO

7-18
Viewing metadata You can view metadata in ArcCatalog by clicking on 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, some of these include: FGDC ESRI, FGDC (which is the default), FGDC FAQ, the Geography Network and XML. Stylesheets define how XML data is presented and are written using Extended Stylesheet Language (XSL). XML: The Extensible Markup Language (XML) stylesheet presents the raw XML data and all the tags and values contained in the metadata. FGDC or FGDC FAQ: The Federal Geographic Data Committee (FGDC) stylesheet selects only the information defined by the FGDC standard. The FAQ formats the metadata by frequently asked questions. The Geography Network: Formats metadata as it is seen in the Geography Network. FGDC ESRI: The FGDC ESRI stylesheet selects a subset of the entire body of metadata and presents it as if it was in a tabbed dialog. You can also create your own customized stylesheet for displaying metadata in ArcCatalog.
7-18
Editing metadata documentation

Edit individual fields
Edit Editmetadata metadata
Add enclosures
Stores a copy of the file in the metadata
Metadata Metadata properties properties
7-19
Editing metadata Metadata can be edited using a special editor that you can access by clicking the Edit Metadata button on the Metadata toolbar. The metadata editor allows you to edit individual fields of the metadata. In addition, files describing the contents of a data source can be enclosed in the metadata. A copy of the file is contained within the metadata. Enclosing files in metadata works the same way that you enclose files in an E-mail message.
7-19
Setting metadata properties

Select default stylesheet
Many to choose from
Control when metadata is created or updated

Default is automatic
Select metadata editor

Use the default or create your own
7-20
Setting properties Options are available in the properties of the metadata to control automatic creation and updating of metadata. By default, when you go to view the metadata for an item in the Catalog tree for the first time, ArcCatalog will automatically create metadata for that item. You may also choose to have ArcCatalog automatically update metadata for a selected item in the Catalog tree.
7-20
Metadata import and export

Uses standard formats
Federal Geographic Data Committee (FGDC) Content Standard for Digital Geospatial Metadata (CSDGM)
Import
FGDC CSDGM
SGML, TXT, XML
XML
Import Import
Export Export
Export
FGDC CSDGM
FAQ, HTML, SGML, TXT, XML
HTML, XML
7-21
Importing and exporting metadata The standard format that ArcCatalog uses for exporting and importing metadata is FGDC CSDGM (Federal Geographic Data Committee Content Standard for Digital Geospatial Metadata). In addition, metadata can be imported or exported in different formats into ArcCatalog. The following formats are supported for importing metadata into ArcCatalog: FGDC CSDGM (SGML, TXT, XML) The following formats are supported for exporting metadata from ArcCatalog: FGDC CSDGM (FAQ, HTML, SGML, TXT, XML) and HTML
7-21
Exercise 7C overview
Display, create, and update metadata in ArcCatalog
7-22
7-22
Lesson 7 review
1. By skipping the needs assessment process, you can save time and money with your database. TRUE / FALSE
2. If problems with the database design arise during the pilot project, it is usually most cost-effective to carry on with the final implementation of GIS, resolving the issues as you go. TRUE / FALSE
3. Whenever data is copied, any existing metadata will be copied as well. TRUE / FALSE
4. Metadata is written in XFL. TRUE / FALSE
5. Stylesheets written in XSL define how metadata is presented. TRUE / FALSE
6. What are some advantages of using the geodatabase? _________________________________________________________________________________________ _________________________________________________________________________________________ _________________________________________________________________________________________ ______________________________
7. Which of the following should be considered when deciding on a storage format for your data: a) Data type b) Application c) Data security d) Long-term plans e) Conversion capabilities f) All of the above
8. What decisions are made at the conceptual and logical design phases? _________________________________________________________________________________________ _________________________________________________________________________________________ _________________________________________________________________________________________ ____________________________________
9. In addition to data entry, what are other issues you want to consider when preparing your automation plan? ____________________________________________________________________________________________ _________________________________________________________________________________________ _________________________________________________________________________________________ ____________________
Introduction to ArcGIS II (for ArcView 8, ArcEditor 8, and ArcInfo 8) Designing a GIS database 7-23
7-24
7-24
Automating data
Lesson overview Many spatial data automation options Creating new data Georeferencing your data Spatial reference Coordinate domain Creating new data Creating a new feature class in ArcCatalog Defining feature class properties Setting the spatial reference Creating feature datasets (FDS) Digitizing in ArcMap Exercise 8A overview Lesson overview Converting digital data
8-17
8-3 8-4 8-5 8-6 8-7 8-8 8-9 8-10 8-11 8-12 8-13 8-14 8-15 8-16
8-18 8-19 8-20 8-21 8-22 8-23
contents
8-2
Building a database from existing data sources Importing data into the geodatabase ArcCatalog Simple Data Loader Transferring data from GPS Importing data from the Internet Defining or changing projection Exercise 8B overview
Automating data
Automating data
8-1
Lesson overview
Data automation options Georeferencing Digitizing Data Data automation automation Setting Setting validation validation rules rules Data Data editing editing Spatial Spatial Adjustment Adjustment Pilot Pilot study study
Planning Planning
Data conversion Data loading Data import/export
8-2
Automating data
8-2
Many spatial data automation options

Paper Papermap map Cov Cov
Digitize Scan
Ras Ras
CAD CAD FC FC
Shape Shape
Import/Export/Load
Addresses Addresses Route Routeevents events x, x,y ycoordinates coordinates

Export
Shape Shape
Cov Cov
Vectorize
Ras Ras
Shape Shape
FC FC
Shape Shape
Cov Cov
FC FC
Geodatabase
Other Other vector vectorGIS GIS

Convert
Cov = ArcInfo coverage FC = Geodatabase feature class Ras = raster Shape = shapefile
Export
Shape Shape Cov Ras Cov Ras
FC FC
Shape Shape
Cov Cov
8-3
There are several data automation options available for you in ArcMap. Paper maps If your current data exists in paper map formats, you have two options: either (1) you can digitize the features off the map using a digitizing tablet, which can result either in a shapefile or a coverage, or (2) you can scan the entire map creating a raster image, which you can later use the ArcGIS ArcScan extension to clean it from unwanted cells ( e.g., dimensions, labels, dust, etc.) and vectorize the raster into either a shapefile, a coverage, or a geodatabase feature class. Import or export or load digital data There are several tools in both ArcToolbox, ArcCatalog, or ArcMap that can be used either to import or export or load different types of data (such as shapefiles, coverages, raster, images, CAD files, geodatabase feature classes) to or from the geodatabase. Each of the ArcGIS three applications have different types of tools. Addresses, route events, and x, y coordinates tables/files You can also create geodatabase feature classes or shapefiles from address tables, route event tables, and x, y coordinates tables or files. Other vector data Consult the ArcGIS Desktop Help to find out what other vector GIS data that are currently supported by ArcGIS.
Automating data
8-3
Creating new data

Scanning data
Produces raster image Georeference after scanning
Table digitizing
Produces vector feature class Georeference during or after tracing
Heads-up digitizing
Digitize over image on screen Georeference before or after digitizing
8-4
Creating new data Hardcopy spatial data can be digitally captured by scanning (taking a digital picture of the map), by digitizing (tracing the map with a digital tracing device), or a combination of the two, called heads-up digitizing. Scanning Scanning requires special hardware that creates a raster image of a hardcopy map. The resulting product may be converted directly to a grid or vectorizedconverted to a vector coverage. ArcInfo provides special vectorization software for converting grids and images to coverages. An automatic vectorization tool is provided with the core ArcInfo package; more specialized tools are supplied with the GRID and ArcScan software extensions. Georeferencing of the image, grid, or resulting vector dataset must be done before geographic analysis can be performed. Table digitizing Often, data is captured with special digital tracing hardware. Table digitizing produces a vector coverage, shapefile, or geodatabase feature class, which may or may not be georeferenced while tracing. Tics can be used to reference locations with known, realworld coordinates to locations on the digitizing tablet, allowing coordinates to be georeferenced during automation. Alternatively, features can be moved in coordinate space after tracing. Both methods will produce the same result. Heads-up digitizing Heads-up digitizing is a combination of scanning and manual digitizing. With heads-up digitizing, a map is scanned and the resulting image is traced on-screen with a mouse. The image may be georeferenced, producing a georeferenced dataset when traced, or the resulting dataset may be moved to real-world coordinate space after tracing.
Introduction to ArcGIS II (for ArcView 8, ArcEditor 8, and ArcInfo 8) Automating data 8-4
Georeferencing your data

Locating your data in real-world coordinates Aligned for analysis between layers
Customers Customers Buildings Buildings Streets Streets
Reality Reality
8-5
Georeferencing your data One important issue you must confront when adding data to your database is how to insure that all of the features in the individual datasets are properly aligned to locations on the earths surface. In the following pages, you will learn how a master dataset of established ground control points can serve as the spatial reference template for the rest of the database.
Automating data
8-5
Spatial reference
Defines coordinate system, coordinate domain Components
Coordinate system
Projection, datum, ellipsoid, prime meridian, units
Coordinate extents
Associated with a feature class or a feature dataset Feature classes are projected to match the spatial reference of the feature dataset they are loaded into
8-6
Spatial reference When creating a new feature dataset or feature class, you must specify its spatial reference. The spatial reference for a feature class includes its coordinate system (for example, geographic, or a projected coordinate system such as UTM or State Plane) and its spatial or coordinate domain. The coordinate system is composed of a projection, a datum, an ellipsoid, and units. Other elements such as the prime meridian, a coordinate shift, and a zone may also be defined. The spatial reference also includes the coordinate extent or spatial domain of the feature class or the feature dataset. Extents can be set for the x- and y-coordinates as well as z, usually an elevation value, and m, a measurement along a linear feature. The same spatial reference is shared by all the feature classes in a feature dataset. Any standalone feature class can have its own spatial reference associated with it. When importing spatial data (e.g., shapefile or coverage) to a feature dataset that has a different coordinate system, that data will automatically be projected to match the spatial reference of the feature dataset.
Automating data
8-6
Coordinate domain
Extent of available coordinates
Min and max X,Y coordinates Precision = storage units per map unit
Example, 1000 mm per meter
Make sure it covers study area ArcCatalog default

Import: data plus room for growth
Set your own

Import from existing data Type in extent for study area
2.14 billion storage units
8-7
Coordinate domain The spatial domain is best described as the allowable coordinate range for x,y coordinates. The precision describes the number of system units per one unit of measure. A spatial reference with a precision of 1 will store integer values, while a precision of 1,000 will store three decimal places. Once the spatial reference for a feature dataset or standalone feature class has been set, only the coordinate system can be modifiedthe spatial domain is fixed. The spatial domain for a feature class or feature dataset cannot be changed. If the required x-, y-, m-, or z-value ranges for your database change, the data has to be reloaded into feature classes with a spatial reference that accommodates the new value range. When you load data into the geodatabase, you must store your coordinates at a specific precision. For best results, ensure that the chosen precision will support the accuracy of your data. The ArcCatalog loading wizard will look at your data and determine defaults for your precision and database growth. Naturally, it is impossible for ArcCatalog to understand your intentions for the data you are loading, so the default settings may not always be the best choice for your application. It is important that you understand what the default spatial domain settings mean and how to change them if necessary. The geodatabase stores coordinates as a 4-byte integer that has a maximum value of 2,147,483,648. You decide what the units represent. For instance, if you need to store meter accuracy, then you have 2.1 billion meters to work with. If you could decide to store centimeters, you would have 2.1 billion centimeters to work with. These units are called storage units. Because you should set your storage units based on your accuracy, you may decide to make your storage units an order of magnitude greater than your current needs to anticipate more accurate data in the future. Map units are the measurement units of your data, and have nothing to do with accuracy. They are the units that represent measurements. For example, the meter is the standard unit for UTM data, while the foot is the standard unit for a state plane coordinate system.
Introduction to ArcGIS II (for ArcView 8, ArcEditor 8, and ArcInfo 8) Automating data 8-7
Creating new data

Create new feature class Spatial reference
Import the spatial reference Manually enter spatial reference
Add features to the empty feature class

Digitize or Simple Data Loader
Import Import spatial spatial reference reference
New NewFC FC
Existing Existingdata data
New Newdata data
8-8
Georeferencing new data When creating a new dataset, you can ensure new features will properly align with your existing data by importing the spatial reference of an existing feature class into the new dataset. By consistently referencing new datasets to a standard spatial reference, you can facilitate feature alignment between different datasets, as well as perform spatial analysis with results measured in real-world units.
Automating data
8-8
Creating a new feature class in ArcCatalog

Create within a feature dataset or independently Define geometry type, spatial reference, and fields Manually add features in ArcMap
8-9
Creating a new feature class A new feature class can be created by right-clicking on the geodatabase in the Catalog tree, or by right-clicking on the feature dataset it will belong to. Next, you will define all its properties, the geometry type, the spatial reference, and the fields to store its attributes.
Automating data
8-9
Defining feature class properties

Define the feature class name Set
Geometry type Spatial reference (if not in feature dataset)
Add fields or import schema from from an existing table

Geometry GeometryType Type Properties Propertiesfor for the theSHAPE SHAPEfield field
Spatial SpatialReference Reference
8-10
Creating feature classes When creating a feature class, you must define the geometry fields properties, such as its spatial reference and the geometry type: point, line, or polygon. Then, add fields for the attribute data by either defining them in the dialog, or importing the schema from an existing table.
Automating data
8-10
Setting the spatial reference

Set
Coordinate system X, Y domain Z domain M domain
Import Importfrom fromexisting existingfeature feature dataset datasetor orcoverage coverage
8-11
Setting the spatial reference When setting the spatial reference for a brand new feature dataset or class, the Spatial Reference Properties dialog will appear blank. You have options to select a coordinate system from the many standard coordinate systems stored by ArcGIS, to import the spatial reference information from an existing source (perhaps another feature class), or to create a new coordinate system. Setting the spatial reference includes setting the coordinate system information and the domains for the x,y,z, and m coordinates. Z values usually store elevation values, while the m coordinate can be used to store a measure along a feature. Z domain and M domain tabs These tabs will only appear in the Spatial Reference Properties dialog (like the example above) if the Contains Z values and Contains M values field properties were turned to yes.
Automating data
8-11
Creating feature datasets (FDS)

Container for spatially related feature classes (FCs) Has spatial reference (FCs inherit)
1
Select Selectthe thegeodatabase geodatabase
3 Name Namethe theFDS FDS
Select SelectNew New> >Feature FeatureDataset Dataset
Set Setspatial spatialreference reference

8-12
Creating feature datasets A new feature dataset in a geodatabase can be created in ArcCatalog by right-clicking on the geodatabase and choosing New > Feature Dataset. On the Feature Dataset dialog, fill in the name for the new feature dataset, and click the Edit button to set the spatial reference for the new feature dataset. A feature dataset is a container for spatially or topologically related feature classes. The feature classes that will combine to form a geometric network or feature classes that share exact boundaries belong in a feature dataset. To maintain these topological relationships, all feature classes in a feature dataset must share the same spatial reference. The spatial reference can be set as a property of the feature dataset, guaranteeing that all feature classes you add to this feature dataset will automatically be projected to match the spatial reference.
Automating data
8-12
Digitizing in ArcMap
Begin an Edit session Use the Create New Feature edit task
Specify
Tolerances Point or stream mode
Point Point Stream Stream
8-13
Digitizing in ArcMap When adding new features to a feature class, follow these steps: 1. Begin an editing session and click the Create New Feature edit task on the Editor toolbar. 2. Specify an appropriate tolerance for snapping your pointer to other features. 3. Specify the mode for adding vertices. Point mode requires you to click the mouse for each vertex. Stream tolerance requires you to click the mouse to enter only the first vertex, then adds vertices at every interval of the stream tolerance. 4. Specify the stream tolerancethe minimum distance between vertices when adding features using stream mode.
Automating data
8-13
Exercise 8A overview
Create an empty feature class Heads up digitizing
8-14
Automating data
8-14
Lesson overview
Data automation options Georeferencing Digitizing Data Data automation automation Setting Setting validation validation rules rules Data Data editing editing Data Data management management Pilot Pilot study study
Planning Planning
Data conversion Data loading Data import/export
8-15
Automating data
8-15
Converting digital data

ArcGIS supports the conversion of multiple formats
ArcView contains commonly used data format conversions ArcInfo contains all conversion tools Wizards and tools make conversion simple
Shapefile Shapefile GPS GPS Geocoding Geocoding SDTS SDTS IGDS IGDS etc.. etc.. Coverage Coverage Feature Featureclass class TIGER TIGER ETAK ETAK
CAD CAD DXF DXF
VPF VPF Table Table
Geodatabase
8-16
Converting existing digital data Increasing amounts of digital spatial data are becoming available from different agencies and organizations. If existing data meet your needs, it is often quicker and less expensive to convert it to an ESRI format than to create a new database from scratch. Both ArcView and ArcInfo have tools to convert existing data in a number of formats into coverages, shapefiles, or geodatabases. ArcToolbox in ArcInfo, with its advanced capabilities for geoprocessing, has a more extensive list of conversion tools for creating coverages from many different formats including Census TIGER files.
Automating data
8-16
Building a database from existing data sources

ArcGIS converts multiple formats into ArcGIS formats
Coverage, Shapefile, Geodatabase
Coverage Coverage Geodatabase TIGER/Line TIGER/Line
8-17
Data conversion You may want to add data that already exists digitally, but not in an ESRI format, to your database. In the example above, a TIGER/Line file is converted into a coverage that can then be imported into a geodatabase as a new feature class.
Automating data
8-17
Importing data into the geodatabase

ArcToolbox ArcToolboxtools tools
ArcCatalog ArcCatalogtools tools
8-18
Data importing options There are tools for importing existing data into a geodatabase in both ArcToolbox and ArcCatalog. These tools will import shapefiles, coverages, CAD data, or tables as new feature classes or tables in the geodatabase. These tools and wizards require that each shapefile, coverage feature class, or CAD file be loaded into a new feature class, and each INFO and dBase table be loaded into a new table. The feature class or table cannot exist before you begin the import process. Wizards in both applications provide a guided path through the loading process.
Automating data
8-18
ArcCatalog Simple Data Loader

Loads data into an existing GDB feature class or table Can use multiple data sources in one operation Will automatically project data during the load
ArcCatalog ArcCatalog
8-19
ArcCatalog Simple Data Loader A separate data loading tool is required to load data from a shapefile, coverage feature class, INFO table, or dBase table into an existing geodatabase feature class or table. This data loading operation is performed with the Simple Data Loader Wizard in ArcCatalog. The Wizard will allow you to specify a number of source tables and feature classes, provided their schema match. It also allows you to specify which fields in the input data are loaded into which fields of the target feature class or table.
Automating data
8-19
Transferring data from GPS

ArcPad From GPS software
Export to shapefile
GPS GPS
Table of x, y coordinates Developer scripts and ArcGIS extensions
8-20
Transferring data from GPS There are a variety of ways to get your GPS data into ArcGIS. ArcPad Using ArcPad in combination with GPS you can collect locations in the field and store them directly to shapefiles. You can then transfer the shapefiles from the handheld device to your computer and use them with ArcGIS. From GPS software Some GPS devices come with desktop software that can transfer the data you collect as shapefiles. Table of x, y coordinates Coordinate pairs collected can be added to a table (manually or through an automated process) then loaded into ArcGIS as an event theme. Text files storing coordinates can also be used to generate feature geometry. Developer scripts and ArcGIS extensions There are several developer scripts and extensions available that can help you get your GPS data into ArcGIS. To find these scripts go to http://arcscripts.esri.com/ and search for GPS.
Automating data
8-20
Importing data from the Internet

Add data from Feature Service to ArcMap Export to shapefile or GDB feature class
8-21
Importing data from Internet sources The Internet is a vast resource for geographic data. Now you can use this data directly on your maps through Geography Network and other Internet servers. Geography Network is a global community of data providers committed to making geographic content available to the public. Published from sites around the world, Geography Network gives you immediate access to the latest maps, data, and related services over the Internet. Use Geography Network to search for and explore maps and other geographic content. When you find what you want, add it directly to your maps in ArcMap. Types of Internet services ArcIMS provides two types of map services: an image map service and a feature map service. An image map service works by taking a snapshot of a map on a server and delivering it to you as an image. A feature map service streams the actual map features to you, providing more sophisticated functionality because the geographic features are directly accessible by ArcMap. When you add a feature map service to ArcMap, you will see a new layer corresponding to each of the layers in the feature map service. You work with these layers in the same way you work with layers based on other data sources.
Automating data
8-21
Defining or changing projection

Use ArcToolbox Projection Wizards Define Projection Wizard
Updates projection settings (.prj file) but does not project data
Project Wizard
Projects data to a different map projection Data must have a defined projection to start with
ArcInfo ArcInfoonly only
8-22
Tools for defining and changing a projection ArcToolBox contains wizards for both updating the projection information associated with your spatial data and changing the projected coordinate system of your data. Defining a projection for your data does not alter the data in any wayit only tags on the projection information to the spatial data. Changing the projection will alter your data as it moves into a new projection. Defining a projection ArcMap expects coordinate system information to be stored with the data source. For a layer in a geodatabase, this information is part of the layers metadata. For coverages and shapefiles, it is stored on disk in a separate file named after the data source but with a .prj file extension (for example, streets.prj). These files are optional files; thus, you may still need to define the coordinate system for one of these data sources. You can create a .prj file using the Define Projection Wizard in ArcToolBox. Changing the projection ArcGIS supports many different projections and is able to project your data from one projected coordinate system to another. This requires that the coordinate information is known for your data.
Automating data
8-22
Exercise 8B overview
Import a CAD file into a GDB feature class Import a coverage into a GDB feature class Import tables into the GDB Adding fields to tables Create a feature dataset Load a shapefile into a GDB feature class Import data from the Geography Network
8-23
Automating data
8-23
Lesson 8 review
1. Why is it necessary for your different geographic datasets to exist in the same coordinate space? _________________________________________________________________________________________ _________________________________________________________________________
2. What two digitizing modes are there? _________________________________________________________________________________
3. Feature classes are created in the ___________ application, and edited in the ___________ application.
4. Name three ways of creating new data. ___________________________ __________________________ __________________________
5. What snapping options are available? _________________________________________________________________________________________ _________________________________________________________________________
6. Name four ways to get GPS data in ArcMap. ___________________________________, ___________________________________, __________________________________, ______________________________________.
7. Why is georeferencing important? _________________________________________________________________________________________ _________________________________________________________________________
8. What two main things should you look for when setting the coordinate domain of your feature class? _________________________________________________________________________________________ _________________________________________________________________________________________ __________________________________
9. When would you use the ArcCatalog Simple Data Loader? _________________________________________________________________________________________ _________________
Automating data
8-24

Lesson overview 9-2 Introducing subtypes and domains 9-3 Anatomy of a subtype 9-4 Setting subtypes 9-5 Editing with subtypes 9-6 Domains 9-7 Anatomy of a domain 9-8 Setting domains 9-9 Editing coded value domains 9-10 Range domains in ArcMap 9-11 Exercise 9A overview 9-12 Lesson overview 9-13 Topology 9-14 Topology manages spatial integrity 9-15 Working with geodatabase topology 9-16 Creating a topology 9-17
9-23 9-24 9-25 9-26
contents
Cluster Tolerance Ranks Topology rules Three states of a topology Validating a topology Topology errors and their management The Error Inspector The Fix Topology Error tool Exercise 9B overview
9-18 9-19 9-20 9-21 9-22
Editing the database schema
9-1
Lesson overview
Setting attribute validation rules
Defining subtypes and domains
Planning Planning Data Data automation automation Setting Setting validation validation rules rules Data Data editing editing Spatial Spatial Adjustment Adjustment Pilot Pilot study study
Setting spatial validation rules

Topology
9-2
9-2
Introducing subtypes and domains

Prevent illegal attribute assignment to features, tables
Subtype: A subset of records within a field Domain: A definition of valid values for a field or subtype
Feature Featureclass class Subtypes Subtypes based basedon on CLASS CLASS Domain Domain
Streets Streets
PowerPoles PowerPoles
Local Local
Highway Highway
Wood Wood
Steel Steel
ST, ST,RD RD AV, AV,BLVD BLVD
HWY, HWY, FWY FWY
Height Height 20-30 20-30ft ft
Height Height 30-50 30-50ft ft
9-3
Domains and subtypes Two of the greatest concerns to most organizations are data integrity and efficiency during management, display, and editing operations. Domains and subtypes offer a way to organize your data so that certain operations, such as editing, become more efficient while the integrity of the attributes is maintained. Subtypes are a way to group features of one feature class into subsets based on an attribute value. In the example above, the Streets feature class is divided into two subtypes which are based on the value of the CLASS attribute field on the feature class table. A domain is just a declaration of acceptable attribute values. Whenever a domain is associated with an attribute field, only the values within that domain are valid for the field. In other words, the field will not accept a value that is not in the domain.
9-3
Anatomy of a subtype
Organizes single fields attribute values Can choose default subtype Requires integer values, user adds descriptions
Street Streetwithout withoutsubtypes subtypes Organize OrganizeCLASS CLASSfield fieldinto intogroups groups CLASS value Subtype description
1 2 Local Streets Major Highways
Street Streetwith withsubtypes subtypes
Domain Domain values values

9-4
Using subtypes Subtypes give you a method to divide your features into logical groupings based on an attribute value. In the example above, new subtypes, Local Streets and Major Highways, were created based on values from the CLASS field in the Street feature class. Any feature with a CLASS value of 1 will belong to the Local Streets subtype, and those features having a CLASS value of 2 will belong to the Major Highways subtype. Creating subtypes requires the functionality of ArcEditor or ArcInfo. Once created, subtypes can be used at the ArcView level to symbolize and edit features according to their subtype. You can also enforce data integrity for the entire subtype by associating a domain. In the above example, the selected street is part of the Major Highways subtype, and therefore can only accept values from the associated Highway Types domain.
9-4
Setting subtypes
Property of feature class or table
Select field with subtype code (integer) Enter subtype code and description Enter default values and domains for each subtype Set default subtype
9-5
Creating subtypes in ArcCatalog Subtypes must be created in ArcEditor or ArcInfo. Only integer fields may contain subtypes; therefore, only integer types, short or long, will appear as possible subtype field choices. Choose the subtype field, then enter the appropriate code and description. Optionally, set the default value. Default field values Setting a default subtype value is useful for editing. For instance, a new feature will inherit this subtype and any associated defaults for other fields. Set the defaults for any other field or fields based on your subtype value. For instance, the Local subtype of the Streets feature class may have a Type default of ST (Street) and a Road Condition default of Good. You can apply subtypes to any geodatabase table, whether or not it has records. You can apply the subtype and validate the attribute values after records have been added to the table. The Use Defaults button You may want to copy default values from one subtype code to another subtype code. The Use Defaults button lets you copy the default values and domains from the default subtype to any other subtype code. To use this option, first enter appropriate default values and domains for your default subtype. Next, click on any subtype code other than the default code. Finally, click the Use Defaults button to copy all your default subtypes default values and domains to the other subtype code.
9-5
Editing with subtypes

Add features by their subtype
Subtypes Subtypes
The new features automatically inherit the default values of their subtypes
9-6
Editing with subtypes Subtypes can make editing more efficient by automatically attributing new and updated features. For example, if you add a new feature that belongs to the Local subtype, it will automatically have the default values of Local Streets. This is insurance against data entry error. Defining subtypes simplifies the attributing process because your choices are listed by description and you do not have to remember all the codes. When adding new features, first choose the appropriate subtype from the Editors Target list. As you add features, they automatically inherit the subtype code and the defaults you created for any other fields in the table. Editing existing records You can also apply subtypes to existing records. Select records through a spatial or attribute query, then edit the subtype by choosing from a pulldown menu that lists all your available codes. This can be done directly in the table or in the Attribute Editor. The chosen subtype will set or update the default values for other attributes. If you are creating data, this will not cause problems because your defaults are usually set appropriately for your table. Realize, however, that choosing a subtype for a preexisting record may complicate your situation because the default values will overwrite your previous values.
9-6
Domains
Define a set of legal values for a field's attributes
Range
A pipe must be between 25 and 500 centimeters wide
Coded value
A residential parcel can only have a residential or vacant land use
A property of the geodatabase

Multiple objects may have the same field, use same domain
Can be applied to a subtype or all records in a feature class Also define Split/Merge rules for features
9-7
Incorporating attribute validation with domains You have learned that subtypes are useful for organizing your attribute data into groups. Domains are user-defined lists of valid attribute values for a column in the entire table or just the features grouped into a subtype. You can apply domains to your columns to prevent attribute errors and provide a way for you to validate records that were added before the domain was applied. There are two types of domains: Range and Coded Value. Range domains specify acceptable starting and ending numeric values. These can either be integers (9 to 66) or numbers with decimal places (9.15 to 19.66). Coded value domains are explicit listings of acceptable codes. These domains can be any value compatible with the field type. For instance, a coded value domain may be specified as a short integer field type. A domain named SEVERITY may include 1 (moderate), 2 (medium), and 3 (severe). A property of the geodatabase Because a domain is a geodatabase property, it is available to any table in the geodatabase. The only caveat is that the field or subtype to which you apply the domain must share its field type. For instance, text type domains can only be applied to text type fields.
9-7
Anatomy of a domain
Two types: Range, Coded Value Create in ArcCatalog
FC properties > Subtypes tab > Domains GDB properties > Domains tab
A property of the entire databasecan be associated with any relevant subtype or field
Local LocalStreet Street
TYPES TYPESdomain domain

Valid Validdomain domainvalues values Redlands Redlandsstreets streets
ST, ST,RD, RD, AV, BLVD AV, BLVD
Riverside Riversidestreets streets
9-8
Using domains Domains offer a way to define a range of values that can be used for multiple attribute fields. Using domains helps to ensure data integrity by limiting the choice of values for a particular field to only those within the domain. Validation for coded value domains is accomplished by forcing the user to choose field values from a dropdown list. Range domains are automatically validated during editing.
9-8
Setting domains
Property of the geodatabase Click on an existing or blank domain Enter name and description
Enter domain properties If necessary, enter coded values

9-9
Creating range domains in ArcCatalog Because domains are a property of the entire geodatabase, you can set them by right-clicking on a geodatabase and clicking Properties. Once the Properties dialog box is open, creating a domain is simple. First, click on a domain to edit an existing domain, or click a blank line to create a new domain. Then, under Domain Properties, you can set the field type to which this domain will be applied and an acceptable range of values for this domain. Creating coded value domains in ArcCatalog To create coded value domains, you use the same process used to set up a range domain, except that you have to specify the acceptable codes. The bottom of the dialog box is reserved for entering the codes and descriptions for the coded value domain.
9-9
Editing coded value domains

Domains will allow only valid values to be entered Valid values can be chosen from a pulldown list List displays the descriptionsnot the code values
9-10
Editing attribute domains When editing an attribute with an associated domain, the domain values appear in a pulldown choice list (except in the case of range domains, which are validated with the Validate tool). This prevents you from entering a value outside of the domain for that particular field.
9-10
Range domains in ArcMap

Use the Validate Feature command to see if any values are outside the range Invalid features remain selected
FACILITY_CODE has a range domain of 100-500
9-11
Editing records that have range domains The Attributes dialog box cannot give you a list of choices to pick from with a range domain because there are an infinite number of possibilities. You can validate features that have range domains by selecting those features and clicking Validate Features from the Editor menu. If you have multiple features that have broken the rules established by the domains, you will get a message box reporting the number of invalid features, and those features will continue to be selected. If only one feature is invalid, you will get a message box reporting the rule that has been broken for that feature.
9-11
Define subtypes Define coded value domains Examine subtypes and domains in ArcMap
9-12
9-12
Lesson overview
Setting attribute validation rules Setting spatial validation rules
Topology and how it manages spatial integrity Working with geodatabase topology Creating a topology Cluster tolerance Ranking and topology rules Validating topology, discovering errors and how to manage errors
9-13
9-13
Topology
Models spatial relationships between features
Connectivity, adjacency, coincidence Between one or more feature classes
Land parcels Soil
Allows for better models of the real world

Adjacency Adjacency Coastline Bus route Country boundary Roads Coincidence Coincidence Connectivity Connectivity Pipes Streams
9-14
Topology The primary purpose of topology is to define spatial relationships between features in one or more feature classes. Incorporating topology into your datasets allows you to better model the real world. The primary spatial relationships you want to model are adjacency, coincidence, and connectivity. Adjacency Adjacency allows you to identify which land owners or soil types share a common boundary with each other. Coincidence Coincidence lets you identify the bus routes on top of roads. Connectivity Connectivity allows you to identify a route to the airport, or connect streams to rivers, or follow a path from the water treatment plant to a house.
9-14
Topology manages spatial integrity

With tools for editing coincident geometry between feature classes With tools for finding and fixing errors Based on rules that can be validated
Examples
Parcels cannot overlap Valves cover pipes Move Movea apipe pipeand andits itsvalves valves Move Movea aparcel parcelboundary boundary
9-15
Topology manages spatial integrity Topology allows you to manage the spatial integrity of your data with tools for editing coincident geometry between feature classes. The coincidence of features is determined on-thefly within the edit session, as opposed to being stored as a series of tables in the database. 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 topology editing tools, moving a shared boundary can automatically update all your feature classes at once or you can select which individual shared features will be updated. The spatial integrity is managed by a set of rules defined by you, which will help you find and fix topologic errors. With streets, you may decide to implement a rule that the streets must not intersect each other.
9-15
Working with geodatabase topology

Can stop at any point of the process
Edit Edit features features Create Create topology topology Dirty Dirty areas areas Validate Validate topology topology Make Make exception exception
Cluster Cluster tolerance tolerance Ranks Ranks
Rules Rules
Errors Errors Fix Fix errors errors
Exceptions Exceptions
9-16
Working with geodatabase topology Working with a geodatabase topology is very flexible because once the topology has been created you can stop at any point in the process. New features can be added which may create errors in your topology. These errors can exist in the topology and the data is still fully available for view, query, or analysis operations. Dirty Areas Following the initial creation of a topology, the extent of all features is considered a dirty area until the topology is validated. A dirty area is created any time: 1. A features geometry is changed: a feature is modified, a new feature is created 2. A features subtype is changed 3. Versions reconciled 4. Topology properties are modified Dirty areas are generated because they may contain existing or undiscovered topology errors. Dirty areas allow the topology to optimize the validation process by limiting the extent of data whose spatial relationships need to be evaluated. This allows selected parts, rather than the whole extent of the topology to be validated after editing.
9-16
Creating a topology
In ArcCatalog In a feature dataset Only simple feature classes
No annotation, dimensions, geometric networks
Feature classes can only participate in one topology Stores groups of properties
Cluster Clustertolerance tolerance Ranks Ranks Rules Rules
Special topology features stored in the geodatabase

Errors Errors Exceptions Exceptions Dirty Dirtyareas areas
9-17
Creating a topology Creating a topology is performed in ArcCatalog in both ArcEditor and ArcInfo. Right-click on the feature dataset, and click New > Topology. Requirements for creating a Topology In order to create a topology, the following rules apply: Feature dataset Topologies can only be created inside a feature dataset because all feature classes must have the same spatial reference. A single feature dataset, however, may have multiple topologies. Simple feature classes Only simple feature classes can participate in a topology. A feature class can only participate in one topology at a time. The following feature classes can not participate in a topology: Annotation (neither static nor feature-linked) Dimension Geometric network feature classes Geodatabase topology When you create a topology it stores groups of properties and topology features in the geodatabase. The groups of properties include cluster tolerance, ranks, and rules. The topology features are errors, exceptions, and dirty areas.
9-17
Cluster Tolerance
A distance in which all geometry is considered identical, or coincident
Cluster Tolerance
After validating the topology Validating Validatingtopology topologyhappens happensafter aftertopology topologycreation creation
Make your cluster tolerance 10x smaller than your highest accuracy data
(1 (1cm cm//100 100cm cmin ina ameter) meter)//10 10(order (orderof ofmagnitude) magnitude)= =0.001 0.001
9-18
Cluster tolerance A distance range in which all vertices and boundaries are considered identical, or coincident. The default is the inverse of the precision of the feature dataset. Determining Cluster Tolerance The basic rule of thumb is to set the cluster tolerance to a value that is an order of magnitude less than the accuracy of your data. Units are Feet If the map units of your data are measured in feet, and the highest accuracy of your data is one inch, then your precision is 12. To make the cluster tolerance an order of magnitude less than that, use the formula:
The inverse of the precision / 10 (order of magnitude) = (1 / 12) / 10 = 0.00833 ft.
You are thus minimizing the amount of movement in your data that is induced by the cluster tolerance. Units are Decimal Degrees If the map units of your data are measured in angular units like Decimal Degrees, you would divide your highest accuracy data in meters by the number of meters in one angular unit at the equator. To make the cluster tolerance an order of magnitude less than that, use the formula:
(Highest accuracy in meters / (SpheroidsSemiMajorAxis in meters * RadiansPerAngularUnit)) / 10). For example, if you wanted to preserve 1 centimeter
accuracy using the WGS_1984 spheroid using decimal degrees the cluster tolerance would be:
(0.01 / (6378137 * 0.017453292519943299)) / 10, 8.9831528411952126884117666300479e-9
which equals:
Note: In the example above, 1 cm is the accuracy value, and 1 meter is the map unit, which is where the 100 cm value came from.
Introduction to ArcGIS II (for ArcView 8, ArcEditor 8, and ArcInfo 8) Editing the database schema 9-18
Ranks
Lower ranked (higher numbers) vertices move to higher ranked (lower numbers) vertices
Snap low quality FCs to high quality FCs 1 (highest) 50 (lowest)
Vertices of equal rank

Endpoints Endpointsmove moveto to average averagelocation location L Lline linemoves movesto toH Hline line
H
Equal Equalranks ranks Cluster Clustertolerance tolerance
L L H
Unequal Unequalranks ranks
Crackpoints Crackpointsmove move to toendpoints endpoints

H = Highest rank
L = Lowest rank
9-19
Ranks 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 classes in the topology. This allows you to integrate less-accurate 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. Snap low quality feature classes to high quality feature classes. 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., to 2), so the zoning boundaries would snap during the validate to match the parcel lines.
9-19
Topology rules
For feature classes or subtypes Checked during Validate Topology
Errors stored in geodatabase
Examples
Soil Soilpolygons polygonsmust mustnot notoverlap overlap Find error Overlap Overlaperror error
n ai
Fix error
Streets Streetsmust mustnot notintersect intersect n ai Find Fix n nM ai i a M error error M

t 1s
t 1s
Intersection Intersectionerror error

t 1s
t 1s
9-20
Topology Rules A topology rule defines a condition in the topology, which is a problem or possible problem in the topology features. Topology rules are used to specify and constrain the topological relationships that must exist within the topology. Topology rules can be defined for all feature geometry types. Rule files can be edited in ArcCatalog but not with a text editor. ArcGIS Version 8.3 currently supports 26 different topology rules: 9 polygon rules, 12 line rules, 4 point rules, 1 default rule related to cluster tolerance. Future releases of ArcGIS will continue to add new rules to this list. Saving Rules Topology rules can be saved to a binary file with a (*.rul) extension. A Rule Set file can be saved in order to preserve the rules that have been set up so they can be applied to another topology or shared with other users. NOTE: Topology rules cannot be created in a UML database design created with Visio. However, a Rule Set file can be created and distributed for databases whose schema has been generated from UML inside ArcCatalog. Differences in feature class names can be remapped when the rules are loaded. Topology Rules poster You can view or print a copy of the Topology Rules poster by going to the ArcGIS Desktop Help. Click Contents tab > Editing in ArcMap > Editing topology > Topology rules > click View a poster illustrating topology rules in ArcGIS. Additionally, your course data CD has a .pdf file of these rules.
9-20
Three states of a topology

Not Validated
Dirty areas exist
Validated - Errors Exist

All dirty areas have been validated and errors were found
Validated - No Errors
All dirty areas have been validated and no errors were found
9-21
Three states of a topology There are three states of a geodatabase topology: Not Validated This would be the state of a topology if you choose not to validate after you initially created the topology. This state also occurs if edits were made to the data and if these changes were saved without validating. Validated Errors exist Data has been validated after initial topology creation or edits were made and errors are existing in the topology. Validated No Errors Topology has been validated and the topology is error free.
9-21
Validating a topology
Validate snaps geometries based on cluster tolerance Identifies errors When to Validate Topology?
After initial creation After every edit operation Before saving Once a week
Specific Specificareas areas
Entire Entiretopology topology
Current Currentextent extent

9-22
Validating a topology Validating a topology evaluates the topology rules, and will create errors if it finds features which violate the rules. When you validate a topology, the geometries of features are integrated based upon the cluster tolerance, and vertices may be added to features within the cluster tolerance so that they can become coincident with other features in the same layer or in another layer. This does not split lines to create new features. It simply inserts vertices. During the validation, vertices that are within the cluster tolerance may be snapped together. A large cluster tolerance may cause undesirable results, because all vertices within the cluster tolerance will be modified to be coincident. On the other hand, a small cluster tolerance may not integrate vertices, and therefore could cause errors. Deciding when to validate a topology is left to the discretion of the user or database administrator. Validation can be done as often as after every edit operation or as infrequent as once a week. There are three different ways to validate a topology, but validating prior to saving edits is not required. ArcMap Validate based upon a user specified area. Validate the visible extent. Validate entire topology. ArcCatalog Validate the entire topology.
9-22
Topology errors and their management

Violated rule determines error geometry
Dangle point error feature Intersection (duplicate line features) line error feature Overlap or Gap area error feature
Error management
Leave it, fix it, or make it an exception, but cannot delete it
9-23
Topology errors and their management When a topology is validated, features are tested to determine if they adhere to the spatial relationships or rules that are defined. A violated rule determines error geometry and contains information on what rule was violated, and which features created the error (parentage). If an error in the topology is detected, an error feature is created. Error Features The rule which is violated determines the geometry of the error feature. Error features contain the rule that was violated and which features created the error (parentage). Below are some examples of errors and the error geometry that is created: Error Shape Point Line Area Rule Dangle (Parcel lines do not snap at end points) Intersection (Street segments have overlaps) Overlap (Parcel polygons that overlap)
9-23
The Error Inspector

Allows search for errors and exceptions
By category and extent
1
2 3
Right-click Right-clickon onone one or select multiple or select multiple
9-24
Among other things, the Topology toolbar has two tools for finding and fixing topology errors. The Error Inspector and the Fix Topology Error Tool. The Error Inspector allows you to search for errors and exceptions by category and extent. You can limit your search to just a certain type of error. You can do so by clicking the down arrow for the Show input field and select a certain rule. The listing in the Error Inspector will show the details of only those errors that pertain to the selected rule. You can right-click on any error (row) to access a context menu with added functionalities. You can pan/zoom to that error, select the feature which is in error, fix it with any of the commands available for fixing that error, or you may chose to mark it as an exception.
9-24
The Fix Topology Error tool

Allows error selection and apply a standard fix
Right-click Right-clickon onerror errorfeature feature
More on editing features in topology in Lesson 10

9-25
Fix Topology Error Tool The Fix Topology Error Tool allows you to select errors in the map interactively. Rightclicking with this tool opens a context menu that allows you to zoom to the selected error, pan to it, select the features that are in error, and show the rule description for the violated rule. You also have the option to apply a standard fix if applicable, to mark errors as exceptions and to reassign exceptions as errors.
9-25
Exercise 9B overview
Create and validate topology for parcels Create and validate topology for streets Find and fix errors Make exceptions
9-26
9-26
Lesson 9 review Attribute validation

1. What is a subtype?_________________________________________________________________ ________________________________________________________________________________
2. What is a domain?_________________________________________________________________ ________________________________________________________________________________
3. Domains are a property of the entire database and can be applied to multiple fields in different feature classes. TRUE / FALSE
4. What is the only field type that can serve as a subtype field? ________________
5. There are two types of domains. What are they? ___________________________ __________________________
6. New features automatically inherit the default values of their subtypes. TRUE / FALSE
7. Subtypes and domains are created in ArcToolbox. TRUE / FALSE
8. Subtypes and domains are types of behavior associated with the geodatabase. TRUE / FALSE
9-27
Lesson 9 review - Spatial validation

9. Topology models spatial relationships only between individual features in the same feature class. TRUE / FALSE
10. Once you have defined the topology for your feature dataset, all errors have to be fixed before you can view, query, or perform any analysis on the data. TRUE / FALSE
11. Topology is created in which of these application? ArcMap / ArcCatalog.
12. Standalone feature classes in the GDB can have topology rules. TRUE / FALSE
13. A topology needs to be validated before dirty areas can be found. TRUE / FALSE
14. List the two tools that deal with topology errors: _____________________________, __________________________________
9-28

Lesson overview Editing security Navigating the Editor Sketches Editing attributes Feature creation tools Split and Divide Buffer Copy Parallel Union and Intersect Merge Editi g topologies in ArcMap Coincident geometry Moving coincident geometry Topology Edit Tasks Auto Complete Polygon Create polygons from lines Intersecting lines 10-2 10-3 10-4 10-5 10-6 10-7 10-8 10-9 10-10 10-11 10-12 10-13 10-14 10-15 10-16 10-17 10-18 10-19
contents
Map topology Topology functional comparison The Map Topology tools Exercise 10 overview
10-20 10-21 10-22 10-23
10-1
Lesson overview
Editing basics
Security Spatial data Attribute data
Feature creation tools Editing features in a topology

Topology tools Topology tasks Creating polygons from lines
10-2
Overview In addition to mapmaking and map analysis, ArcMap is the application for creating and editing geographic data as well as tabular data. With ArcMap, you can edit all of your feature classes with one common user interface. ArcMap contains sophisticated CAD-based editing tools that help you construct features quickly and easily while maintaining the spatial integrity of your GIS database.
10-2
Editing security
Editing security prevents data corruption
Others cannot edit the features you are working with
Personal geodatabase
One editorMultiple readers First editor locks the entire database
Enterprise RDBMS format geodatabase

Multiple editorsMultiple readers Versioning allows multiple editors
GIS Database
10-3
Editing security Editing security measures are necessary to ensure that multiple editors do not attempt to edit the same feature at the same time causing database inconsistency. The two formats of the geodatabase have different available security measures. The personal geodatabase performs an entire database lock when an editing session is started. This prohibits anyone from editing any of the feature classes in the geodatabase except the user who started the editing session. This type of security works well when there is no need for multiple users to edit the database simultaneously, but it can be inflexible in other circumstances. With an ArcSDE geodatabase, in an enterprise RDBMS format, multiple editors are allowed through a process called versioning. The versioning process is covered in detail in the Introduction to ArcSDE class. See the ESRI training Web site (www.esri.com/training) for more details on this course.
10-3
Navigating the Editor toolbar

Editing functions are controlled through the toolbar
Edit Edittool tool Sketch Sketchtool tool
Target TargetLayer Layer
Attribute Attribute dialog dialog
Sketch Sketch Properties Properties
Task Tasklist list
Edit Editsession session commands commands

10-4
Navigating the Editor toolbar In ArcMap, editing operations are controlled through the editing toolbar. The toolbar contains several important controls: Editor pulldown 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 pulldown list. The listed tasks will change according to the feature class you are editing. Target layer: This control allows you to select the layer you want to edit. Attribute dialog: This window allows you to edit the attribute values of selected features. Sketch properties: This window will allow you to display and edit the X and Y coordinates of your current sketch.
10-4
Sketches
A sketch lets you perform an editing task
Add new features Modify features Reshape features
Sketches work with the current task

Create New Feature Reshape Feature Extend/Trim Features More
Current Currenttask task
Set snapping tolerances for working with sketches
10-5
Edit sketches An edit sketch lets you perform various editing tasks, such as adding new features, modifying features, and reshaping features. Tasks are listed in the Current Task dropdown list on the Editor toolbar. You can use the tasks in the Current Task dropdown list in conjunction with a sketch you create to edit your geographic data in ArcMap. Here are some examples: The Create New Feature task uses a sketch you create to make the new feature. The Select Features Using a Line task uses a sketch you create to select features; the features the line intersects are selected. The Cut Polygon Features task uses a line sketch you draw to cut a polygon.
10-5
Editing attributes
Attributes dialog
Field Calculator
10-6
Editing attribute data The Attributes dialog lets you view attributes of features you have selected in your map. The left side of the dialog contains a list of the features you have selected. Features are listed by their unique ID numbers and grouped by layer name. The right side of the attributes dialog contains two columns: the attribute properties of the layer you are viewing, such as Type or Owner, and the values of those attribute properties. Field Calculator By accessing the Field Calculator from an open table, you can edit the values of attributes directly on the attribute table. You open the calculator by right-clicking the field you want to edit values for. The calculator menu allows you to perform simple calculations and complex logical expressions including other fields in the table.
10-6
Feature creation tools

Create features in the target layer
Divide Buffer Copy Parallel Union Intersect Clip
Create features in the same layer

Split Merge
10-7
Feature creation tools From the Editor menu, there are a variety of tools for creating new features. Tools that create features in the target layer may use features selected in other layers to create new features. For example, create a new water main parallel to a road feature. Tools such as Split and Merge will create new features from features in the same layer.
10-7
Split and Divide

Split line into two
By distance or percentage along line From start or end of line
Splitting Splittinga awater watermain mainin inhalf half
Divide creates points at intervals along a line

Number of points evenly spaced Specified distance
Poles Poles Electric Electric line line
Target Target layer layer
10-8
Split Use the Split command when you know the distance at which you want to split the line, measured from either the first or last vertex. You can also use this command when you want to split a line at a certain percentage of the original length. For example, you can use the Split command to split a power line at a known distance along the line when you want to add an electrical pole that requires its own service. The Split dialog box displays the length of the original feature in current map units to help you split it accurately. When you split the line using the Split command, the attributes of the original line are copied to each of the new lines. Divide The Divide command creates points at a given interval along a line. For instance, you could use Divide to place utility poles along a primary. You can create a specific number of points that are evenly spaced, or you can create points at a distance interval you choose.
10-8
Buffer
Buffers selected features by a specified distance
Two Twodiscrete discrete polygons polygonsin in target targetlayer layer
10-9
Buffer You can create a buffer around a feature by using the Buffer command. For instance, you might use Buffer to show the area around a well that is contaminated or to represent a floodplain around a river. You can buffer more than one feature at once, but a separate buffer will be created around each feature.
10-9
Copy Parallel
Copies a line feature parallel to the original feature
Positive is on the right side of the feature
Creates feature in target layer
20
10-10
Copy Parallel The Copy Parallel tool allows you to create a new feature parallel, on either side, to an existing one. You will be able to specify the distance between the original line and the new parallel line. A positive distance between the parallel lines will create the new parallel line to the right side of the feature; negative values will create the new parallel line to the left. It would help to change the symbol from a simple line to one with an arrow in order to see this relative location (i.e., to see the right side of the feature). The new parallel line is created as a new feature in the target layer. You can use the Copy Parallel command, for example, to create a street centerline or a gas line that runs parallel to a road.
Editing spatial and attribute data 10-10
Union and Intersect

Creates features in a target layer Does not delete original features Union
Creating Creatinga asales salesterritory territory
Intersect
Overlapping Overlappingarea areaof ofsales salesterritories territories
10-11
Union and Intersect The Union command combines features from different layers into one feature while maintaining the original features and attributes (table fields). For example, you can create a sales territory from several ZIP codes. You can also create a multipart feature using the Union command by combining nonadjacent features from different layers. For example, to create a sedimentary rock polygon in a new rock classification layer given selected clay and quartz polygons in an existing rock composite layer, you would use the Union command to combine the clay and quartz features to create a new multipart sedimentary rock feature in the rock classification layer. Although the features may be from different layers, the layers must be of the same typeeither line or polygon. The new feature is created in the current layer without attribute values. The Intersect command creates a new feature from the area where features overlap. For instance, you can create a new sales territory out of overlapping trade areas. You can find the intersection between features of different layers, but the layers must be of the same type (either line or polygon). The original features are maintained and the new feature is created without attribute values in the current layer. You must manually enter attribute values for the new feature.
Merge
Replace existing feature with new feature
In the same layer Deletes original features Line or polygon
Combining Combiningtwo twoparcels parcels
10-12
Merge The Merge command combines features of the same layer into one feature. The features must be from either a line or a polygon layer. You can also merge nonadjacent features to create a multipart feature. For example, you could merge the individual islands that make up Hawaii to create a multipart polygon feature. When you merge features a dialog appears asking the user to choose which feature the other features will be merged with. The new features attribute values are copied from the feature that the user selects.
Editing topologies in ArcMap

Topology toolbar contains editing tools
Example workflow for editing geodatabase topology

Add topology layer and participating feature classes in ArcMap Edit features Use same edit and sketch tools as for simple features Use specialized tools on Topology toolbar Editing creates dirty areas Validate Topology Correct errors Make exceptions
10-13
Editing topologies in ArcMap In the last lesson, you created topologies in the geodatabase to model spatial relationships for features in the Streets and Parcel feature classes. You selected which feature classes participated in the topology, defined rules for the topology and validated to identify potential errors in the data. ArcGIS provides topology tools to analyze, visualize, report and if necessary, repair the spatial integrity of the data after it is initially created as well as after editing. As the geodatabase is used and maintained, new features are added and existing features are modified. Data editors update features in the geodatabase and use the editing and topology tools to construct and maintain relationships between features. Depending on the work flow of your organization, the topology may be validated after each edit session or on a schedule. The Topology toolbar provides a series of tools for editing and managing coincident geometry in ArcMap. In this lesson, you will see there are two different 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, layers, or both that participate in a topology. Youll remember that a geodatabase topology consists of a persisted set of user-defined rules and properties that are applied to your data.
Coincident geometry
Lines 5 5features features 7 coordinate 7 coordinatepairs pairs Points 1 3
X: 100.50 Y: 200.50
Polygons
2 2features features 8 coordinate 8 coordinatepairs pairs 1
4 2
122.50 200.50
5
144.50 200.50 X: 100.50 Y: 200.50
2
100.50 220.00
Determined on-the-fly Tools for editing and managing spatial relationship
10-14
Coincident geometry Topology in the geodatabase data model is used to model spatial relationships and for editing spatial data. The spatial relationships between features participating in a geodatabase topology or map topology are not persistently stored in the database, but discovered on-the-fly while editing. Using the Topology Edit Tool in ArcMap, coincident geometries can be determined with shapefiles and geodatabase feature classes. This tool also permits multiple feature classes to be edited with a single edit operation. When features in the topology have parts that intersect or overlap, the lines (edges) and points (nodes) that define these parts are shared. For example, a stream may have a coincident line (edge) that is shared between a state, county, city, parcel, zoning, and land use polygon. Selecting this coincident line with the Topology Edit Tool and then using the Sketch Tool with the edit task set to Reshape Edge, will allow you to simultaneously edit many layers. Shared lines (edges) are determined for all the layers that participate in a geodatabase topology whether they are in the map or not. Conversely, if a map topology is being used, shared lines (edges) are only determined for the layers that have been selected to participate in a map topology.
Moving coincident geometry

Topology Edit Tool
Selects and modifies edges and nodes Press E to only select edges, and N to only select nodes
Show Shared Features

To pull coincident geometries apart
Uncheck Unchecklayers layersso sothey they are arenot notmodified modifiedwith with the thecoincident coincidentgeometry geometry
10-15
Moving coincident geometry The Topology Edit Tool is used to select and edit coincident edges and nodes. Holding down the E key while selecting with the Topology Edit Tool will select only edges. Holding down the N will select only nodes. The Show Shared Features tool allows users to select which features will be altered by modifications to a shared edge/node.
Topology Edit Tasks

Modify Edge
Edit vertices of an edge in the sketch
Reshape Edge
Update shared edge using a sketch
Reshape ReshapeEdge Edge

10-16
Edge tasks Two edit tasks, Reshape Edge and Modify Edge, have been added to the Task list, under the category Topology Tasks. These tasks allow you to work with shared edges. The Reshape Edge task is similar to Reshape Feature, but applies only to shared edges. Using this edit task lets you reshape a shared edge with a sketch. The Modify edge task allows you to edit the vertices of an edge in the edit sketch.
Auto Complete Polygon

Ensures coincident edge between polygons All polygons in a polygon layer must be created with this task
All polygons are adjacent to another polygon
10-17
Auto Complete Polygon The Auto Complete Polygon task will allow you to add a polygon to the edge of existing ones without having to sketch in a duplicate boundary between them. Using this task you will sketch in all the polygon boundaries except the one common to the other adjacent polygon(s).
Create polygons from lines

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
10-18
Create polygon from lines 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.
Intersecting lines
Planarize
Two selected lines
splits selected lines where they intersect

1 2 3 3 5 1 4 4 2 5
In Inone oneFC FC
Three total lines
Five total lines
Construct features selected lines

Two selected lines
1 2 3
splits lines in Target layer with

1 3 5 4 7 2 6
In Inone oneFC FC
Three total lines

Seven total lines

10-19
Planarize The Planarize command splits selected line features where they intersect. The Planarize command is enabled only when a selection is made to features in the same line layer. Construct features The Construct Features command can also be used to split lines in the Target layer when considering existing features. Within the same layer, all selected lines or any lines that intersect the selection will be split.
Map topology
Coincident geometry editing without a persisted topology Feature classes or shapefiles
Must be in same geodatabase or folder Feature classes can be in different feature datasets
Allows for topology with ArcView
10-20
A map topology can be applied to simple features in a shapefile or to simple feature classes in a geodatabase. The feature classes that participate in the map topology must be in the same folder or geodatabase. A map topology cannot be applied to feature classes that participate in a geometric network. A map topology creates topological relationships between the parts of features that are coincident. You can choose the distance, or cluster tolerance, that defines how close together edges and vertices must be in order to be considered coincident. The cluster tolerance is typically a very small actual ground distance. Setting large cluster tolerances can result in features being collapsed or distorted when vertices with a given feature snap together. You can also specify the feature classes that you want to participate in the map topology. You do not specify any topology rules for a map topology. All edges or vertices of features in the map topology that fall within the cluster tolerance are considered to be topologically shared. You edit shared edges and vertices in a map topology in the same way, and with the same tools, as you would edit a geodatabase topology. Because there are no topology rules, there is no need to validate a map topology, and there is no creation of error features.
Topology functional comparison

Geodatabase Topology
Topology Edit Tool Show Shared Features Planarize Lines Construct Features Validate Error Management
Map Topology ArcEditor
Map Topology ArcView
10-21
You can build topological relationships between features with a geodatabase topology or a map topology. With a map topology, you have access to different editing tools depending on what license of ArcGIS you have. Geodatabase topology The geodatabase topology is actually stored in the geodatabase. You must have an ArcEditor or ArcInfo license to create or edit a geodatabase topology. Because the topology is stored in the geodatabase you can store rules, errors, and exceptions with the topology. The geodatabase topology allows you to use all the validation and editing tools available on the topology toolbar. Map Topology using an ArcEditor or ArcInfo license The Map Topology allows you to perform topological edits on shapefiles or feature classes without creating a topology in the geodatabase. When you are have an ArcEditor license you can use the Topology Edit, Show Shared Features, Planarize Lines and the Construct Features tools to edit the map topology. Map Topology using an ArcView license Creating a map topology works exactly the same as it does with an ArcEditor license. The main difference between the two licenses is the ArcView license only allows you to edit with the Topology Edit and Show Shared Features tools.
The Map Topology tools

Simultaneous editing of coincidence boundaries
1 Map Topology Map Topology 2
Show ShowShared SharedFeatures Features 3 Topology TopologyEdit EditTool Tool
4 8 6 Select Select Topology Topology Task Task 7 Four Fourcoincident coincident features features
10-22
Map Topology Tools To create a map topology, you need to start an editing session; this will enable the Map Topology command. Once you click on this command, the Map Topology dialog will appear. From here you can choose which layers you want to participate in the topology. You will also choose a cluster tolerance. The cluster tolerance represents the precision of your data. It is a tolerance value in map units where all vertices within that tolerance will be snapped together to create shared geometry. As soon as you generate the map topology, you can use the Topology Edit Tool and the Topology Modify Edge and Reshape Edge edit tasks (Note: do not get these confused with the Modify Feature and Reshape Feature tasks) to modify coincident features. You can also use the Show Shared Features command to display all shared features for any given edge or node. The Shared Features dialog will also allow you to choose which features you want to participate in any given editing operation.
Exercise 10 overview
Perform simple spatial edits Create features with the feature creation tools Edit features using subtypes and domains Calculate new values for a field Edit coincident features
10-23
Lesson 10 review
1. Personal geodatabases can have more than one person editing at the same time. TRUE / FALSE
2. What is the difference between creating polygons from lines in ArcCatalog and in ArcMap? _______________________________________________________________________________ _______________________________________________________________________________
3. What is the difference between the Planarize command and the Construct Features command? ________________________________________________________________________________ ________________________________________________________________________________
4. What is the difference between a sketch and a feature? ________________________________________________________________________________ ________________________________________________________________________________
5. What editing tasks can be used for maintaining boundary coincidence for polygons features? _________________________ _________________________ ____________________________
6. What is the difference between the Split and the Divide commands? _________________________________________________________________________________ _________________________________________________________________________________
7. What is the difference between the Union and Merge commands on the Editor menu? _______________________________________________________________________________ _______________________________________________________________________________ _______________________________________________________________________________ _______________________________________________________________________________
8. Copy parallel copies a line feature parallel to the original based on the lines direction. TRUE / FALSE
9. How does the Map Topology tools in ArcMap differ from the topology rules created in ArcCatalog and used in ArcMap? _______________________________________________________________________________ _______________________________________________________________________________ _______________________________________________________________________________
Lesson 10 review - continued

10. The attributes from the original features are copied to a new feature when created using Union and Intersect under the Editor menu. TRUE / FALSE
11. When editing data using the Attribute editor, it is not possible to add or copy/cut and paste values for multiple selected features. TRUE / FALSE
10-26
Spatial adjustment
Lesson overview Why use Spatial adjustment? Spatial adjustment Transformation Transformation methods Creating displacement links RMS error Rubbersheeting Edge Snap Attribute transfer Aggregating spatial data Exercise 11 overview
11-2 11-3 11-4 11-5 11-6 11-7 11-8 11-9 11-10 11-11 11-12 11-13
contents
Spatial adjustment
Data management
11-1
Lesson overview
Spatial adjustment Data aggregation Data Dataautomation automation Setting Setting validation validationrules rules Data Dataediting editing Spatial Spatialadjustment adjustment Pilot Pilotstudy study
Planning Planning
11-2
Data management
11-2
Why use Spatial adjustment?

Align vector data to more accurate data
Digitized data in tablet or scanner units Less accurate data
Usually followed by aggregating data
Make Makeadjustments adjustments
Aggregate Aggregate
11-3
Spatially adjusting data Spatial adjustment allows you to adjust the location of features to match more accurate data in your database through the processes of transform, rubbersheet and edge match. You will need to spatially adjust data that has been digitized or scanned to move it from the units of the digitizer or scannerfor example inchesto match the rest of your data in real world units. You can also use it to adjust lower accuracy data to higher accuracy data. Examples would include: Rubbersheeting the edge of a lakeshore to match the lake outline on a new orthophoto. Edgematching streets or streams along the borders of two municipalities. Once data has been adjusted to match the higher accuracy data, the next step is often to aggregate this data into the more accurate data. In this lesson, you will review the different spatial adjustment tools and the different options in ArcGIS for aggregating data.
Data management
11-3
Spatial adjustment
Spatial Adjustment toolbar allows
Transform Rubbersheet Edge Snap Transfer attributes
Attribute Attribute transfer transfer tool tool
Tools operate within an Edit session

Copy Features tool Honor snapping environment
Features are moved to new location based on displacement links
11-4
Spatial adjustment The Spatial Adjustment toolbar provides tools and commands for spatially adjusting and editing vector features, helping you improve the quality of your data. Often, you need to make adjustments to integrate new data to existing data or match less accurate data to more precise data. The Spatial Adjustment tools allow you to edge snap, rubbersheet, and transform spatial features, and also transfer attributes from one feature to another. This new toolbar works in conjunction with the ArcMap Editor Toolbar within an ArcMap Edit session. Spatial adjustments are performed interactively in ArcMap and may affect a selected set or all features in a layer. While the spatial adjustment methods differ, all are accomplished by using displacement links to define the source points in the data being edited and the destination points in the control data. Displacement links may be added interactively or in a batch process. The types of adjustment supported are: Transformation (Affine, Projective, Similarity) - The adjustment affects all of the features in the input layer equally. Root Mean Square errors are calculated to indicate the accuracy of the derived transformation. Rubbersheeting (Linear, Natural Neighbor) - The adjustment is applied piecewise throughout the layer or throughout the selected features of the layer. No errors are calculated. Edgematching (Smooth, Linear) - Uses rubbersheeting to match features at the edge of layers. The adjustment only affects selected features. No errors are calculated. Through the spatial adjustment toolbar you are also able to transfer the attributes of features to other features.
Data management
11-4
Transformation
Change location of features in 2-D coordinate space
Converts data in digitizer or scanner units to real-world units Shift data within coordinate system, example feet to meters
Source Source x, x,y y= =8.4, 8.4,9.5 9.5 digitizer digitizerunits units
Displacement Displacement links links Destination Destination x, y = 470525.03, x, y = 470525.03,3749885.77 3749885.77 UTM UTMmeters meters
11-5
Transforming features Transformation from one coordinate system to another is used frequently in GIS. The effect of a transformation varies from simple changes of position and direction, without changing shape or size, to a uniform change in scale (with no change in shape), to changes in shape and size of varying degrees. Transform can be used to move features that were digitized in inches or centimeters to the correct real world coordinates. It could also be used to move features within the same coordinate system; for example, you could transform features from UTM kilometers to UTM meters. Transformation (Affine, Projective, Similarity) - The adjustment affects all of the features in the input layer equally. Root Mean Square errors are calculated to indicate the accuracy of the derived transformation.
Data management
11-5
Transformation methods
Transform will translate, rotate, and scale data Use Affine, Similarity, or Projective method
Affine transformation can
Translate Translate Rotate Rotate
Scale Scale
Skew Skew
11-6
Transformation methods Depending on the method used to transform your data from one coordinate system to another, the transformation may translate or shift features in coordinate space, scale features in size, rotate, or skew them. ArcGIS supports the three transformation methods summarized below. The ArcGIS Help provide more information on the mathematical functions used for the transformations. Similarity This method is also sometimes referred to as an orthogonal or two-dimensional linear conformal transformation. It is commonly used to adjust data between two similar coordinate systems; for example, to change the map units of data from one linear unit to another. This method will translate, rotate, and scale features. A minimum of two displacement links are required for this four parameter transformation. Affine This method expands on the similarity transformation by allowing two scale factors instead of one, and will allow features to be skewed while being rotated. There is a minimum of three links required to perform this six parameter transformation. Transforming digitized data to real world coordinates is a good example where this transformation is applicable, as it allows for the small distortions such as stretch, shrink, and skew that occur to paper and other media that is digitized. Projective This is a specialized transformation used to transform coordinates digitized directly off high altitude aerial photography or aerial photographs of relatively flat terrain. It is an eight parameter transformation and requires a minimum of four links to perform.
Data management
11-6
Creating displacement links

Graphic elements define the source and destination Create manually or load from links or control point file
Create links file from existing displacement links
11-7
Creating displacement links Links are used to define how an adjustment affects a dataset. A link is a displacement vector that represents a source location to a destination location. Links are graphic elements in a map and are always displayed as arrows with the arrowhead pointing towards the destination. You can change the symbol, size, and color of displacement links from the Adjustment Properties dialog from the Options command on the Spatial Adjustment menu. The Spatial Adjustment toolbar has tools to manually add a displacement link, to modify an existing link, and a tool to automatically add multiple links between two selected features. The current snap environment is honored when manually adding displacement links. Create links from text files You can also create links from coordinates saved in a link file. A link file is a text file that contains a list of X, Y source and X, Y destination coordinates. A link file can be comma, space, or tab delimited and may contain ID values that precede each record. When you open a links file from the Links submenu, the source and destination displacement links will be automatically created based on the coordinate locations in the link file. You can also create links based on a control points file. A control points file contains the X and Y destination coordinates and may contain ID values for each record. When a control points file is opened, the Control Points Window dialog will open and display the coordinate locations. These locations will become destination points for new displacement links. Double-clicking or right-clicking and choosing Add link will create a link starting at the destination coordinate, and then you will manually add the source location. Create links file from existing displacement links It is possible to create a links file from existing displacement links in ArcMap, regardless of whether the links were created manually or loaded from another file. Choose the Save Links File option from the Links submenu and you will be able to save the displacement link coordinates to a text file.
Introduction to ArcGIS II (for ArcView 8, ArcEditor 8, and ArcInfo 8) Data management 11-7
RMS error
Transformed locations may not match control points RMS error indicates discrepancy View RMS in links table, drop links with high RMS error
Destination control point Transformed source control point Error
RMS error =
2 2 2 2 e 1 + e2 + e3 + . . . + e n
11-8
RMS Errors A root mean square error (RMS) describes the deviation that will occur when the transformation is applied to the input and the output coordinate systems. The error is determined using the least squares regression method. The transformation parameters are a best-fit between the source and destination control points. If you use the transformation parameters to transform the actual source control points, the transformed output locations wont be an exact match to the true output control point locations. This is called the residual error; it is a measure of the fit between the true locations and the transformed locations of the output control points. This error is generated for each displacement link.
Data management
11-8
Rubbersheeting
Adjust source layer to match more accurate layer Features are stretched, straight lines preserved Identity links hold features in place Adjust all features or only within a limited area
11-9
Rubbersheeting Geometric distortions commonly occur in data. They may be introduced by imperfect registration in map compilation, lack of geodetic control in source data, or a variety of other causes. Rubbersheeting corrects flaws through the geometric adjustment of coordinates. Rubbersheeting stretches the features along the displacement links and holds features in place at the identity links. An identity link is a link whose source and destination coordinate are the same. Identity links act like nails to hold specific locations in place. After an adjustment, displacement links become identity links. Identity links can also be added manually with the Identity link tool on the Spatial Adjustment toolbar. At least one displacement link is required to perform the rubbersheeting adjustment. Rubbersheeting can be performed on a selected set of features to fit them to another set of features. For example, a lakeshore in one layer could be rubbersheeted to match a more accurate boundary in another layer. You can also perform rubbersheeting on all features in a feature class or feature dataset to another control dataset. That dataset could be a raster image as in the graphic above, a CAD drawing, locations specified interactively, coordinates in a text file, or by interactively entering coordinates into a table. Rubbersheeting (Linear, Natural Neighbor) - The adjustment is applied piecewise throughout the layer or throughout the selected features of the layer. No errors are calculated. Limited adjustment area The New Limit Adjustment Area tool allows you to draw a polygon shape around the features you want to adjust. This allows you to limit your adjustment to just the area covered by the added polygon. Features that are outside the adjustment area will not be adjusted.
Data management
11-9
Edge Snap
Aligns features in adjoining layers Edge Snap tool adds links within snapping tolerance Options
Smooth or line methods Adjust to midpoint of links Use attributes to define the edgematch
11-10
Edge Snap Edge snap, also sometimes referred to as edge matching, uses rubber sheeting to match features along the edges of layers. If you are combining data from different sources, features may not align perfectly along the borders. The edge snap adjustment can be used to move the features in a source layer to match those in a target layer or to adjust to the midpoints of the links in which case features from both layers will be adjusted. When performing an edge snap, you can add displacement links manually, from a file, or automatically using the Edge Snap tool on the Spatial Adjustment toolbar. The Edge Snap tool allows you to drag a box over the source and target features to be edge matched. Links will be automatically added between source and target features that are within the current snapping tolerance set for the edit session. The Edge Snap adjustment method requires more property settings than other methods. You can set these property settings in the Edge Match panel of the Adjustment Properties dialog box accessed from the Options command on the Spatial Adjustment pull down menu. When using the Smooth edge snap method, vertices at the link source point are moved to the destination point. The remaining vertices are also moved, giving an overall smoothing effect. When using the Line edge snap method, only the vertices at the link source point are moved to the destination point. The remaining vertices on the feature remain unchanged. You have the option to specify one link per destination point and to prevent duplicate links. These settings can help you avoid creating unnecessary links. The Spatial Adjustment tool supports the ability to use attributes to enhance the edgematching process. Based on the Attribute Transfer Mapping dialog box, you have the option to match fields between the source and target layers and use common attributes to define the edgematch. This function can help ensure the accuracy of the edgematch. Edgematching (Smooth, Linear) Uses rubbersheeting to match features on the edit of layers. The adjustment only affects selected features. No errors are calculated.
Introduction to ArcGIS II (for ArcView 8, ArcEditor 8, and ArcInfo 8) Data management 11-10
Attribute transfer
Interactively transfer attributes between features Match common fields between layers
Set source and target layers Specify fields to transfer Option to transfer geometry
Click on 2 destination 1 LO AB Click on P N SA source
11-11
Transferring Attributes Attribute transfer is the transfer of attribute values from a target feature to a source feature based on user-defined field matching. Source and target features may reside in the the same feature class or different feature classes. Source and target feature geometry can differ. Geometry transfer is the altering of a target features geometry based on the geometry of a source feature. This is achieved via the transference of shape values from source to target features as an attribute transfer. Geometry and attribute transfer are typically performed after ensuring that the target and source datasets are aligned using one of the spatial adjustment methods. Although both the target and source features are expected to be in close proximity, often overlapping, this is not a requirement for using the transfer tool.
Data management 11-11
Aggregating spatial data

Copy and Paste Simple Data Loader Object Loader Merge command in Geoprocessing Wizard
Merge adjacent layers
11-12
Aggregating spatial data After data has been spatially adjusted, you will probably aggregate it with other data in your database. For example, after transforming street features for a new subdivision, you will add them into your street feature class. ArcGIS offers a number of tools and options for aggregating spatial data. Copy and Paste While in an editing session in ArcMap, you may copy selected features and paste them into the target layer using the Copy and Paste tools on the Standard toolbar. Simple Data Loader You can load features into an existing simple feature class (one that does not store custom or network features or is in a versioned geodatabase) using the Simple Data Loader in ArcCatalog. The wizard will allow you to specify a number of source tables and feature classes, provided their schema match. Object Loader If you are loading features into either a simple feature class or a feature class that contains custom or network features or is in a versioned geodatabase, you can use the Object Loader command. This command can be added to your ArcMap session from the Customize dialog. Merge Use the Merge command in the GeoProcessing Wizard in ArcMap. Merge is normally used to combine the features from adjacent layers together where the features do not overlap, and where the layers share the same attribute definitions. You can merge layers that overlap, however, the features are not unioned together to create new features with common boundaries or common line segments. Instead, both sets of features are just appended into the output layer, and the features will simply overlap.
Exercise 11 overview
Convert a DXF file to a GDB feature class Add displacement links Transform data to real world coordinates Edge snap two layers Transfer attributes Merge two feature classes into one
11-13
Lesson 11 review
1. Why is spatial adjustment important? _________________________________________________________________________________ _________________________________________________________________________________
2. What four things you can do to your data with the Spatial Adjustment toolbar? ____________________________ _____________________________ ____________________________ _____________________________
3. What are the four transformation methods available in ArcGIS? ____________________________ _____________________________ ____________________________ _____________________________
4. What is rubbersheeting? __________________________________________________________________________________ __________________________________________________________________________________
5. What tools are available for you in ArcGIS to aggregate spatial data in different feature classes into one feature class? ___________________________________________________________________________________ ___________________________________________________________________________________ ___________________________________________________________________________________ ___________________________________________________________________________________

Lesson overview Dissolving features Aggregating spatial data Clipping features The GeoProcessing Wizard Spatial analysis functions Buffering The Buffer Wizard Overlay analysis and geoprocessing overview Overlay analysis functions Union Intersect Spatial join The analytical process Deciding on project data Analysis options Review analysis tools
12-10 12-11 12-12 12-13 12-14 12-15 12-16 12-17 12-18
contents
12-2 12-3 12-4 12-5 12-6 12-7 12-8 12-9
Exercise 12A overview Exercise 12B - C overview
12-19 12-20
12-1
Lesson overview
Preparing data for analysis
Dissolve Merge Clip
ArcGIS spatial analysis

Buffer Overlay
The analytical process
12-2
12-2
Dissolving features
Simplify data based on common attribute values
9 66 15 15 9 15 66 Fewer Feweroutput outputfeatures features with attribute with attributevalues values
2 nd
Input Inputfeatures features with withattribute attributevalues values

2 nd
1st 1st
1st
Main
1st
Main
12-3
Dissolving features Dissolve combines adjacent features within a feature class based on an attribute value. You can dissolve either polygon or line feature classes, and the output will contain the same feature type as your input. Note that the Dissolve column will be the only user-defined attribute added to your output table. You can later join attributes from the original table, but be carefulit may not be appropriate to assign attributes from an individual feature to the group of features. Dissolving means you are throwing away data. For example, if you dissolve a feature class based on street names, the output feature class would have no user-added attributes other than those street names. Usually, you would not dissolve features permanently in the database. Instead, you would perform a dissolve temporarily for a particular project and, after you are done, archive the feature class or throw it away.
12-3
Aggregating spatial data

Merge separate layers into one
Options for assigning attributes to the output layer
12-4
Aggregating spatial data Use Merge when you want to combine two or more adjacent layers into one large layer that contains all their features. For example, you may want to merge highway data that you received as a series of separate tiles of data into one continuous layer. The merge operation will create a new shapefile or geodatabase feature class. Merge is normally used to combine the features from adjacent layers together where the features do not overlap, and where the layers share the same attribute definitions. You can merge layers that overlap; however, the features are not unioned together to create new features with common boundaries or common line segments. Instead, both sets of features are just appended into the output layer, and the features will simply overlap. Postprocessing If you save the output as a shapefile, the new features do not have their area, perimeter, or length calculated automatically. If the inputs had these values in their attribute tables, these attributes may be carried over into the output layer, but they will not be updated to reflect the new size of the features, so they should not be used as the basis for analysis. You can add these attributes to the output shapefile after using the Geoprocessing Wizard. See the online documentation on How to make field calculation for instructions on updating the size of features. If you save the output as a feature class inside the geodatabase, the size of the new features will be automatically calculated.
12-4
Clipping features
Use one feature class to define the boundary of another
Original Originaldata data
Clipping ClippingFC FC
Final FinalFC FC
12-5
Clipping data Use Clip when you want to cut out a piece of one layer using one or more of the polygons in another layer as a cookie cutter. This is particularly useful for creating a new layer that contains a geographic subset of the features in another larger layer. For example, suppose you are studying the transportation needs of a particular county. You would like to work with a layer that contains only the roads or segments of roads that fall inside this county boundary, but all you have is a layer containing roads for the whole state. You can clip the roads in the state roads layer using the county polygon as the cookie cutter to create a new layer containing just the roads in the county. The layer that is having its features clipped can contain points, lines, or polygons. The cookie cutter or clip layer must contain polygon features. If you only want a subset of the features in this layer to be clipped, you can select them using any of the feature selection tools in ArcMap, before you start the Geoprocessing Wizard. You should then check the Use selected features only box on the second panel of the Wizard, just below where you specify this input layer.
12-5
The GeoProcessing Wizard

Helps conceptualize process Use for dissolving, merging, and clipping
12-6
The GeoProcessing Wizard The Geoprocessing Wizard in ArcMap helps you choose the correct operation and input themes for overlay analysis. The graphic inside the Wizard menu changes to reflect the spatial operation you choose. Each operation also has comprehensive Help files associated with it.
12-6

Proximity analysis
Locating features based on their distance from other features Finding the nearest feature
Which Whichparcels parcelsare are within within50 50feet feetof ofthe theroad? road?
Overlay analysis
Combining features and attributes
Well Drilled Welltype type Drilled Building owner Building owner Smith Smith Soil Sandy Soiltype type Sandy
12-7
Spatial analysis functions For some types of spatial analysis, you can use the Select by Location query to find features in relation to other features. For example, finding shopping malls close to your office would involve a simple Select by Location query. Other spatial analysis operations require more advanced tools, such as those found in the Geoprocessing Wizard. For instance, if you wanted to find the exact land area in layer A contained within the extent of layer B, you would need to perform a union or intersection operation. The spatial analysis functions are divided into two main sections: proximity analysis and overlay analysis.
12-7
Buffering
A distance analysis tool for points, lines, and areas Create new polygon representing specified distance Answer questions based on proximity
Buffer Buffer50 50meters meters
Buffer Buffer100 100meters, meters, do not do notdissolve dissolve interior interiorborders borders
Buffer Bufferby by attribute attributevalues values
12-8
Buffering A buffer is a polygon zone around some geographic feature or set of features. You can use buffer zones to find features contained inside or that fall outside of your specified distance. For example, you could create a buffer representing a one-mile radius from an earthquake fault line and find out how many major shopping malls are within this area. With buffers, you could quickly determine which malls are in the greatest danger of being damaged in an earthquake. Create new shapes You create buffer zones by specifying a distance. You can use the same distance for every feature in the layer or use a numeric attribute to specify different distances for each feature. The output of the buffer operation is either a new polygon shapefile or geodatabase feature class. Answer questions based on proximity You can use buffers to select features from other layers in your view. In addition to finding shopping malls near fault lines, you can apply buffers to zoning or real estate problems. For instance, in some parts of Texas, there are ordinances prohibiting liquor from being sold within one mile of an elementary school. You could buffer the schools to create a new set of polygons representing the one-mile distance and then do a selection to make sure no liquor stores fall within the no liquor zone.
12-8
The Buffer Wizard
1 Choose Choosethe thefeatures features
2 Choose Choosethe thedistances distances
3 Choose Choosethe theoutput output

Display Displaythe theoutput output layer layeror orgraphic graphic

12-9
The Buffer Wizard The Buffer Wizard allows you to create a buffer as graphics in the display, as new polygon features in an existing editable layer, or as a new shapefile or geodatabase feature class. The Wizards dialogs guide you through choosing the features to be buffered, choosing the buffer distances, and choosing the output. Choose the features The first Buffer Wizard dialog prompts you for the type of feature you want to buffer. This can be a graphic in your view, all features in a layer, or only selected features in a layer. Choose the distances The second dialog prompts you for the buffer distance. You can choose a specified distance to buffer all features, use a numeric fields attribute value to buffer each feature by a different distance, or create multiple concentric buffer zones of a specified distance. You choose the buffers distance units; they can be different from the units set in the Data Frame Properties. Choose the output The final dialog asks if you want to dissolve the borders between adjacent buffer polygons and how you want the output formatted. If you are not concerned with buffers around individual features, you should dissolve the borders between adjacent areas. Note: If you dissolve adjacent borders, all buffer polygons will be grouped into one record in the feature class table.
12-9
Overlay analysis and geoprocessing overview

Point-in-polygon Point-in-polygon
Input layer
Line-in-polygon Line-in-polygon
Polygon-on-polygon Polygon-on-polygon
Overlay layer
Output Outputlayer layerinherits inherits overlay overlaylayers layersattributes attributes
Different from select by location
12-10
Point-in-polygon overlay To find which point falls inside which polygon, use the point-in-polygon analysis. For example, suppose you want to know how many grocery stores are inside each census tract. The new grocery store layer will have census tract attributes. You can query the store to find out which census tract it falls within. Line-in-polygon overlay To find the common areas between a line layer and a polygon layer, use line-in-polygon analysis. If you have a river layer and a parcels layer, for example, you could find out which river falls inside each parcel and exactly how much river is contained in each parcel. The output is much more accurate than a Select by Location query because input features are physically split by the overlay layer. Polygon-on-polygon overlay For studying common areas between the two layers, use polygon-on-polygon overlay analysis. For example, if your first layer represents parcels and your second layer represents flood zones, you can find the flood risk for each parcel and the exact area of flood zone contained within each parcel.
Spatial analysis functions 12-10
Overlay analysis functions

Union and Intersect in the Geoprocessing Wizard Intersect Intersect
Lines or polygons Combine attributes Limited extent
Union Union
Polygons Combine attributes Full extent
12-11
Overlay analysis functions The Geoprocessing Wizard accomplishes overlay analysis through unioning and intersecting layers. Intersect Intersect combines features from two layers that share the same geographic extent into a third layer. You can intersect line or polygon layers with another polygon layer. The output layer will contain the same feature type you input as well as both input sets of attribute fields. Union Union combines features from two polygon layers to create a new polygon layer. The new layer will contain both sets of input attribute fields.
Union
Create a new layer from combined geometry of two input layers Both input and overlay layers must be polygons
Input Input two two vegetation vegetation polygons polygons Output Output
+
Overlay Overlay four four soil soil polygons polygons Many Manyvegetation vegetationpolygons polygonswith with inherited soil shapes inherited soil shapesand andattributes attributes
12-12
Union The union operation allows you to integrate two layers and create a new layer that contains all the features from both. For example, suppose you were interested in finding out the relationship between vegetation and underlying soil characteristics. You could union the vegetation and soil layers to create a new layer that now has the polygon boundaries and attributes for both vegetation and soils. The vegetation shape geometry is split by the soil polygons and will inherit the soil attributes. Once you have this information, you can query the vegetation areas to see which ones have a certain soil characteristic. You could make a chart showing the relationship between vegetation type and soil class. Technically speaking Union computes the geometric combination of two layers and adds the new layer to your ArcMap display. Both the input and overlay layers must be polygons. All input features that cross the polygon borders of the overlay layer will be split and written to a new shape in the new layer. The output shapefiles features will also be polygons that inherit the attributes from both input layers. Recalculating area, perimeter, and length for shapefiles When you perform a union operation, the geometric attributes of a new shapefile are not automatically updated. See the online help for how to update the area and length field values for shapefiles. Geometric attributes for geodatabase feature classes will be automatically updated.
Intersect
Create new layer from common spatial extent between two input layers Input lines or polygons; overlay polygons
Input Input 3 3roads roads Output Output
5 5roads roadswith with inherited inherited soil soilattributes attributes
Overlay Overlay
4 4soil soil polygons polygons
12-13
Intersect Intersect allows you to integrate two layers and preserve only the features falling within the spatial extent common to both layers. Suppose you want to determine the soil characteristics under the existing roads in your study area. You could use the Geoprocessing Wizard to intersect the soils with the roads to create a new layer where each road is clipped to the soil polygon boundary and inherits the soils attributes. You would be able to find out which roads were built on soils susceptible to erosion. You could then figure out how to prevent road damage after heavy rainfall. Technically speaking Intersect computes the geometric intersection of two layers. The input layers can be lines or polygons, but the intersect (overlay) layer must be polygons. All input features that cross internal polygon borders will be split and written to a new shape in the new layer. Any features in the input layer that are not spatially coincident with the polygon features will be ignored. The output feature class will be of the same geometric type as the input layer features and will inherit the attributes of both input layers. Note: If you want to do a point-in-polygon overlay, you have to do a spatial join.
Spatial join
Join based on spatial location
Use for point-in-polygon analysis Find the nearest feature
Appends attributes and calculates distance
Well Welllocations locationson onsoil soiltypes types
Distance Distanceto toclosest closestlake lakefrom fromwolf wolfden den

12-14
Spatial join In earlier lessons, you joined tables based on common attribute values. You can also join tables based on their spatial locations. A join in this manner allows you to find out which features fall within a polygon, which features intersect, and what are the closest features between two layers. Like joining two tables by matching attribute values in a field, a spatial join appends the attributes of one layer to another. You can then use the additional information to query your data in new ways. A spatial join creates a new layer containing both sets of attributes.
The analytical process

What question are you trying to answer? What criteria are involved? REGIS database
Where Whereis isthe thebest bestlocation locationfor foran anamusement amusementpark? park?
Agriculture Agricultureor orvacant vacant landuse landuse Within Withincensus censusblockgroups blockgroups with high with hightarget targetage ageand and income population income population
1 1kilometer kilometerfrom from the theRedlands Redlandshistoric historic driving drivingtour tour Within Within500 500meters meters of a highway of a highway
12-15
Defining the project scenario The first step to successfully completing an analysis is to clearly define the question to be answered. See if you can put the scope of the analysis into one or two sentences. If you can do this, then the data needs and the process to follow will become much more obvious. After you have defined the question, you can determine what criteria will be used to answer it. In the example above, if you are looking for a location to build an amusement park, you will look for areas that meet certain criteria.
Deciding on project data

What feature classes will you use? What attributes and values will you query on? What preprocessing will be necessary before analysis?
Table joins Data conversions
Feature Featureclasses classes Parcels Parcels BlockGroups BlockGroups Attributes Attributes LU_CODE LU_CODE TARGET_AGE TARGET_AGE INC_MEDN INC_MEDN Values Values AGR AGRor orVAC VAC > >350 350 > >35,000 35,000 Preprocessing Preprocessing None Nonenecessary necessary Join Joinwith with BG_DMG BG_DMGtable table
12-16
Deciding on project data Once the scope of the analysis (the question and criteria) are determined, you can decide what data will be necessary to successfully complete the analysis. The criteria will usually describe the data and attributes needed. You should also determine if any preprocessing of the data is going to be necessary before the analysis is performed. Often, you will need to convert data from one format to another that is more suitable for a specific type of analysis. For example, if you need to perform a polygon overlay on data in a geodatabase, you might convert the data to coverage format first, perform the overlay, then convert the resulting coverage back into the geodatabase. In this step, you will also need to determine if the attributes you need are available on an independent table. You may have to create a relationship class or perform a data join to access the attributes you need.
Analysis options
What spatial operations will answer the questions most efficiently?
Often many paths to the same result
Chart the flow of operations and data

Parcels
Select AGR or VAC land use
Parcels_sel
Select parcels contained within the blockgroups
Final
BlockGroups TARGET _AGE > 350

and INC_MEDN > $35,000
Select
BG_sel
Report Map
12-17
Analysis options The final step in analysis preparation is deciding which spatial analysis operations will achieve the results you are seeking. Often, you will find that you have several options which will deliver the information you need, but some might be less convenient than others. Try to choose the method that answers the question in the most efficient manner. Finally, it is highly recommended that you chart out the proposed analytical process. This will encourage you to think the problem through from start to finish, and you can save a lot of trouble in the long run.
Review analysis tools

ArcMap tools
Select By Attribute Select By Location Buffer Spatial Join
GeoProcessing Wizard
Overlay (union, intersect) Merge Clip Dissolve
12-18
Review analysis tools Do not forget that you have many different tools for analysis at your disposal. Think about the problem you are about to solve and which tools will be most appropriate to use.

Exercise 12A
Find a suitable location for an amusement park using Selection by Attributes and by Location
12-19
Exercise 12B - C overview

Exercise 12B
Choose an analysis project
Project A: Police department pilot study Project B: Environmental quality pilot study
Exercise 12C
Produce a map of your study
12-20
Lesson 12 Review
1. If you Merge two layers together, the area and length fields for the output data will be automatically updated if: a) you save the output as a shapefile b) you save the output as a feature class in the geodatabase c) all of the above d) none of the above
2. The Geoprocessing Wizard will create output data in the format of a shapefile or geodatabase feature class. TRUE / FALSE
3. Why is it important to create an analysis plan? _________________________________________________________________________________________ _________________________________________________________________________ _________________________________________________________________________________
4. What is the difference between an overlay and a Select by Location query? _________________________________________________________________________________________ _________________________________________________________________________ _________________________________________________________________________________
5. You can predict the number of output features with a Union overlay. TRUE / FALSE
6. What is buffering? Provide an example. _________________________________________________________________________________________ _________________________________________________________________________ _________________________________________________________________________________
7.
What is a spatial join? _________________________________________________________________________________________ _________________________________________________________________________ _________________________________________________________________________________
8. What is an overlay operation? _________________________________________________________________________________________ _________________________________________________________________________ _________________________________________________________________________________
9. Union works with points, lines, and polygons. TRUE / FALSE
12-22

ArcGIS2 3.0 Lecture1

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

ArcGIS2 3.0 Lecture1

Hochgeladen von

Copyright:

Verfügbare Formate

Title Page

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

Working with ArcCatalog

Copyright 20002003 ESRI

Introduction to ArcGIS II (for ArcView 8, ArcEditor 8, and ArcInfo 8)

Working with layers and map symbology

Working with labels and annotation

Copyright 20002003 ESRI

4-11 4-12 4-13

Displaying locations from tabular data

Modifying the ArcGIS interface

Designing a GIS database

Copyright 20002003 ESRI

Introduction to ArcGIS II (for ArcView 8, ArcEditor 8, and ArcInfo 8)

7-8 7-9 7-10 7-11 7-12 7-13 7-14

7-15 7-16 7-17 7-18 7-19 7-20 7-21 7-22

Copyright 20002003 ESRI

8-20 8-21 8-22 8-23

Setting geodatabase validation rules

Editing spatial and attribute data

Copyright 20002003 ESRI

Introduction to ArcGIS II (for ArcView 8, ArcEditor 8, and ArcInfo 8)

Copyright 20002003 ESRI

Spatial analysis functions

Copyright 20002003 ESRI

Introduction to ArcGIS for ArcView and ArcInfo II ModuleTitle

Introduction to ArcGIS II (for ArcView 8, ArcEditor 8, and ArcInfo 8)

Copyright 20002003 ESRI. All rights reserved.

Introduction to ArcGIS II (for ArcView 8, ArcEditor 8, and ArcInfo 8)

Introduction to ArcGIS II (for ArcView 8, ArcEditor 8, and ArcInfo 8)

Copyright 20002003 ESRI. All rights reserved.

Introduction to ArcGIS II (for ArcView 8, ArcEditor 8, and ArcInfo 8)

Introduction to ArcGIS II (for ArcView 8, ArcEditor 8, and ArcInfo 8)

Copyright 20002003 ESRI. All rights reserved.

Introduction to ArcGIS II (for ArcView 8, ArcEditor 8, and ArcInfo 8)

Introduction to ArcGIS II (for ArcView 8, ArcEditor 8, and ArcInfo 8)

Introduction to ArcGIS II (for ArcView 8, ArcEditor 8, and ArcInfo 8)

Online course evaluation

Copyright 20002003 ESRI. All rights reserved.

Introduction to ArcGIS II (for ArcView 8, ArcEditor 8, and ArcInfo 8)

Introduction to ArcGIS II (for ArcView 8, ArcEditor 8, and ArcInfo 8)

Copyright 20002003 ESRI. All rights reserved.

Introduction to ArcGIS II (for ArcView 8, ArcEditor 8, and ArcInfo 8)

Introduction to ArcGIS II (for ArcView 8, ArcEditor 8, and ArcInfo 8)

Implement advanced editing techniques Perform spatial analysis functions

Introduction to ArcGIS II (for ArcView 8, ArcEditor 8, and ArcInfo 8)

Web browser Web server RDBMS server

Data Personal geodatabase Enterprise geodatabase

ArcToolbox Coverage Shapefile Grid TIN Image CAD

Copyright 20002003 ESRI. All rights reserved.

Introduction to ArcGIS II (for ArcView 8, ArcEditor 8, and ArcInfo 8)

Introduction to ArcGIS II (for ArcView 8, ArcEditor 8, and ArcInfo 8)

GIS in the enterprise

Data management and distribution

ArcSDE & ArcIMS ArcInfo

ArcEditor & ArcPad ArcView 8 & ArcView 3 ArcReader Web browser

Introduction to ArcGIS II (for ArcView 8, ArcEditor 8, and ArcInfo 8)

Proficiency Introduction to ArcGIS II Learning ArcGIS II: Presenting information

Copyright 20002003 ESRI. All rights reserved.

Introduction to ArcGIS II (for ArcView 8, ArcEditor 8, and ArcInfo 8)

Introduction to ArcGIS II (for ArcView 8, ArcEditor 8, and ArcInfo 8)

Software support resources

ESRI Technical Support