Beruflich Dokumente
Kultur Dokumente
UT-Dallas Briggs
UT-Dallas Briggs
ArcGIS System
Clients
ArcEditor
ArcView
ArcMap
ArcCatalog
ArcToolbox
ArcMap
ArcCatalog
ArcToolbox
ArcMap
ArcCatalog
ArcToolbox
ArcEngine/
ArcObjects
Application
Development &
Customization
Consistent interface
Increasing capability
ArcExplorer
ArcServer Services
ArcIMS Services
ArcSDE Services
Internet
ArcPad
Databases
Files
Handheld/Wireless
Browser
(Personal Geodatabase,
Shapefiles, Coverages,
Grids, tins, etc) GISC
Multi-user Geodatabases
(in Oracle, SQL Server,
UT-Dallas
IBM Briggs
DBII, etc)
Extensions: for special apps.: Spatial Analyst, 3D Analyst, Geostatistics, Business Analyst, etc.
ArcObjects: build specialized capabilities within ArcMap or ArcCatalog using VB for Applications
Set of embeddable GIS components (ArcObjects software objects) for use in building custom
applications
Runs under Windows, Unix and Linux, with support for Java, C++, COM and .NET
Replaces MapObjects which were based upon a previous generation of GIS objects
Notes:
ArcGIS 8 released 2000 to integrate two previous standalone products: ArcView and ArcInfo
ArcGIS 9 released 2004 providing the full capability that should have been in ArcGIS 8!!!
--full support for all data types (coverages, shapefiles, geodatabases)
--full support for all previous geoprocessing analyses
--Modelbuilder for scripting and repetitive processing
--ArcEngine for building custom applications
ArcView 3.3 (the predecessor to ArcGIS 8.x) the only GUI option for UNIX.
GISC 6382 Applied GIS
UT-Dallas Briggs
ArcGIS Server
Permits the creation of server-based GIS services using any ArcGIS
capability
Provides GIS capabilities to a user without a desktop GIS system:
ArcIMS
Software to develop Internet server-based mapping and basic analysis
Provides maps to the user without a desktop GIS system :
ArcGIS Services
Server based applications built and operated by ESRI or its partners and
made available on the Internet for subscription
Normally charged on a per transaction basis, but can be flat fee
presumably built using ArcGIS Server
GISC 6382 Applied GIS
UT-Dallas Briggs
ArcLogistics Route
Specialized business application for delivery routing
ArcFM
water and telecom: industry specific facilities management
ArcGIS Extensions
BusinessMap:
$99 standalone business mapping (originally Richardson-based MapLynx)
GISC 6382 Applied GIS
UT-Dallas Briggs
Discontinued Products
ArcCAD
CAD product from ESRI
PC ArcInfo
Atlas/GIS
once a leader in PC-based mapping
Bought by ESRI in 1996 & discontinued in 2001
GISC 6382 Applied GIS
UT-Dallas Briggs
ArcGISVersion 8/9
With Version 8 & 9, now have two flavors:
Desktop:
Largest Microsoft COM/ActiveX application to date
Full GUI interface
Customization via Visual Basic for Applications (altho must
have ArcInfo to run custom apps)
New data base concepts: Geodatabase
Runs on XP/2000/NT only
no UNIX version available
Workstation:
classic, command-line ArcInfo with AMLs (Arc Macro
Language) for customization
same as version 7 and earlier, with minor enhancements
the only option for UNIX, but also available on MS XP
With release of GISC
ArcGIS
9, little
reason to use
6382 Applied GIS
UT-Dallas Briggs
UT-Dallas Briggs
UT-Dallas Briggs
UT-Dallas Briggs
UT-Dallas Briggs
Geographic Data
Concepts
File Formats
Topology
UT-Dallas Briggs
UT-Dallas Briggs
The same entity can be represented at different scales by different object types: the
multi-representation problem
Behavior can be associated with objects thus they can change over time
Field View
The real world has properties which vary continuously over space; every place
has a value
May be represented as raster data, or with vector data as a TIN (triangulated irregular
network
If the value is a categorical or integer variable, then places with the same value
(e.g. soil type) can be grouped--and doesnt this give us an area object?!
UT-Dallas Briggs
UT-Dallas Briggs
Database
Environment
Geo-relational
Database
Geodatabase
The new approach
Replacement for coverages, with support for
Simple features: points, lines polygons
Complex features: real world entities modeled
as objects with properties, behavior, rules, &
relationships
ArcView downgrades complex features to
simple features
Personal Geodatabase
Single-user editing
Stored as one .mdb file
Max 2GB total & 250,000 features per layer
Multiuser Geodatabase
Multi-user simultaneous editing via
versioning and long transactions
Uses ArcSDE 8 as middleware to store in
standard db: ORACLE, MS SQL Server, etc
GIS
User
UT-Dallas Briggs
SDE
db
Geodatabase
Features
Workspace
Coverages
Rules
Tins
Images
Relationships
Images
Shapes
Grids
Grids
Tables
Tables
One Repository
Source: ESRI, Inc.
UT-Dallas Briggs
Concept of Topology
Topology distinguishes GIS data models from nontopological data models supported by many CAD, mapping
and graphics systems
Topology refers to knowledge about relative spatial
positioning of features.
knowledge about how features are connected and which features are
adjacent to each other.
UT-Dallas Briggs
UT-Dallas Briggs
Topology Concept I
Arc-node topology is how Arc/INFO keeps track of
which arcs are connected to other arcs through shared
nodes (nodes are endpoints of arcs). It defines length,
direction, and connectivity for arcs.
UT-Dallas Briggs
Topology Concept II
Polygon-arc topology expresses the relationship
between the arc features and the polygon features for
which the arcs create boundaries. It defines area and
adjacency. Arcs or a set of arcs that form a closed
figure define the area of a polygon. Two polygons are
adjacent if they share an arc. Polygons are stored as a
list of arcs to avoid redundancy.
UT-Dallas Briggs
2
3
6
7
UT-Dallas Briggs
Shapefiles
share some similarities with coverages but are not fully topological
May need to covert to coverages for some analyses.
Discuss topology for coverages later today and for geodatabases later in the course.
GISC 6382 Applied GIS
UT-Dallas Briggs
UT-Dallas Briggs
Feature ID
(key field)
Feature
type
Secondary or
Foreign key
Raster
Tracts
shapefile
Trans
shapefile
GISC 6382 Applied GIS
UT-Dallas Briggs
Shapefiles
openly published structure for spatial data (Coverages &
Geodatabases are proprietary)
Partially an attempt (successfully!) by ESRI to make their format the
industry standard
road.shx
road.dbf
UT-Dallas Briggs
UT-Dallas Briggs
Geodatabase (gdb)
Feature datasets
Spatial Reference
Object classes and subtypes
Feature Classes and subtypes
Relationship classes
Network Topology
Planar topology
Domains
Validation Rules
Raster Datasets
rasters
TIN datasets
nodes, edges, faces
Locators
addresses
x,y locations
Zip codes place names
route locations
Anatomy of a Geodatabase
Geodatabases may contain: feature datasets,
raster datasets, TIN datasets, locators
Feature datasets contain vector data
All data in a single feature dataset share a
common spatial reference system
Similar Objects (e.g. Jane Blow, land owner) are
instances of object classes (e.g. land owners)
and have no spatial form.
Features and feature classes are spatial objects
(e.g. land parcels) which are similar and have
same spatial form (e.g. polygon)
Object (or feature) classes are the tables, and
objects (or features) are the rows of the table
Attributes are in the columns of the table
Subtypes are an alternative to multiple object (or
feature) classes (e.g. concrete, asphalt,
gravel road subtypes): think of subtype as
the most significant classification variable
(attribute) in the class table
Domains define permitted data values.
Topology is saved as a relationship between the
feature classes in the feature dataset.
Spatial Reference
All feature classes within a feature dataset must have the same spatial reference.
Coordinate System
Datum
Geographic (lat/long) or projected?
Projection parameters: central meridian, standard parallels, coordinate system origin
(false easting and northing)
Measurement (map) units: dd (for lat/long), feet, meters, etc. (for proj.)
Spatial domain
The allowable coordinate range for the geographic coordinates
X/Y Domain: MinX, MaxX, MinY, MaxY (horizontal extent)
Z Domain: Min, Max (vertical extent)
M Domain: Min, Max (other parameter, e.g. distance from river mouth ) (can differ within
feature data set)
Once created, the spatial domain for feature dataset/class cannot be changed.
Data outside extent will require a new feature dataset or standalone feature class.
Precision
Number of system storage units (SU) per one map measurement unit (MU)
If precision is 1 and mu= 1 meter ( 1 SU per MU), cannot record values less than 1 meter
If precision is 100 and mu= 1 meter (100 SUs per MU), can record values
to 1/100 = .01 = 1 cm
UT-Dallas Briggs
Workspace
Coverages must be stored in workspaces
A workspace is the work area used during an
ARC/INFO session.
Within the computer file system, the workspace is
a directory (folder) containing one or more
geographic data sets (e.g., coverage, tin, grid), a
local INFO database, and other supporting data.
at a minimum it is a folder containing an INFO
subfolder (subdirectory)
More than one user can read data from the same
workspace, however, it is strongly recommend
that only one user access a workspace for creating
or updating data.
GISC 6382 Applied GIS
UT-Dallas Briggs
The Coverage
Digital version of a single map sheet layer and generally contains one type of
map feature such as streets, parcels, soils,
Can contain both the coordinate/spatial data and the descriptive data for features
in a given geographic area.
Additional attribute data about features (entities) can be stored in data base
tables using proprietary INFO relational data base system
Allowed user to customize, organize and store substantial amounts of attribute data
and relate to spatial data
UT-Dallas Briggs
UT-Dallas Briggs
The INFO folder contains the feature attribute tables and related tables for all
coverage in that workspace.
Unfortunately, file names do not correspond to the names of files we work with!
GISC 6382 Applied GIS
UT-Dallas Briggs
Soil
POLYGON
ARC/INFO Spatial
Database Structure
(coverage)
INFO
ARC
Soil
AAT
TIC
BND
ETC.
PAT
Exceptions:
Can drag and drop, cut, copy, paste, and delete the entire
workspace
Can drag and drop, cut, copy, paste, and delete the interchange file
(e00) created by exporting the coverage
Naming Coverages
Names for coverages are maximum 13 characters in length and
cannot include blanks or special characters (-,#, etc) other than
under_score
GISC 6382 Applied GIS
UT-Dallas Briggs
UT-Dallas Briggs
UT-Dallas Briggs
You can add items (columns) to the PAT after the <cover>-id item.
GISC 6382 Applied GIS
UT-Dallas Briggs
UT-Dallas Briggs
You can add items (attributes) to the PAT after the <cover>-id item.
The first polygon is always the universal polygon which represents the
coverage boundary.
UT-Dallas Briggs
UT-Dallas Briggs
UT-Dallas Briggs
TYPE
ABBREV.
WIDTH
Main Street
Character
1 to 320
10/15/1990
Date
23675
Integer
1-16
347.22
Numeric
1-16
1344719822
Binary number
2 or 4
99378164.788
Binary floating
point
4 or 8
UT-Dallas Briggs
In ArcToolbox:
The greatest number of conversion options are available here.
GISC 6382 Applied GIS
UT-Dallas Briggs
Coordinate Systems
UT-Dallas Briggs
Coordinate Systems
All spatial data is in a coordinate system
You must know what it is!
Projection
The transformation by which 3D lat/long is converted to 2D X/Y Cartesian values
parameters normally required to describe the exact nature of the projection
Projected Coordinates must be in some measurement unit: usually feet or meters
Thus, for any a spatial data set, knowing simply the name of the
projection is not sufficient. Must also know:
Datum
Parameter(s)
We often
say map units
projection, when we really mean coordinate system!
Measurement
GISC 6382 Applied GIS
UT-Dallas Briggs
Project
Actually projects the data. Think of this as reproject.
The data does change.
The current projection (input) must already be known by the
ArcGIS system,
That is, you have to do a Define first, if somebody has not already done it
UT-Dallas Briggs
In ArcMap
Providing that it is already defined (projection system known to ArcGIS), data brought
into a data frame (whose coordinate system is also known) will be reprojected in
memory to the coordinate system of the frame for display.
It can be exported in this (potentially) new projection, if desired.
In effect, this projects the data.
Note double proviso: known coordinate system for data inputted and for frame.
UT-Dallas Briggs
Appendix
UT-Dallas Briggs
Vertice
Node
UT-Dallas Briggs
from-node/to-node
to-
from-
1
GISC 6382 Applied GIS
2
1
UT-Dallas Briggs
3
Arcs
4
2
Main Street
UT-Dallas Briggs
Computing
Evolution
And it will all keep changing!
Pervasive
Computing
Internet
Desktop
Workstation
Mini
Source: ESRI, Inc.
Mainframe
GISC 6382 Applied GIS
UT-Dallas Briggs