44
Fall 2013 LDA 150/ABT 150 4-Units Introduction to Geographic Information Systems (GIS) Instructor: Stavros G. Vougioukas, Ph.D. Lecture: Tuesday and Thursday, 3 Kleiber, 3:10-4:30 PM Lab Sections: 1137 PLESC Lab--Friday (01 & 04), Monday (02), Wednesday (03 & 06), Thursday (05) Lec #12 11/6/2013 6:05 PM 1

Lecture+12+topology+2013 (3)

Embed Size (px)

DESCRIPTION

 

Citation preview

Page 1: Lecture+12+topology+2013 (3)

Fall 2013

LDA 150/ABT 150

4-Units

Introduction to

Geographic Information Systems (GIS)

Instructor:

Stavros G. Vougioukas, Ph.D.

Lecture: Tuesday and Thursday, 3 Kleiber, 3:10-4:30 PM

Lab Sections: 1137 PLESC Lab--Friday (01 & 04), Monday (02), Wednesday (03 & 06), Thursday (05)

Lec #12

11/6/2013 6:05 PM 1

Page 2: Lecture+12+topology+2013 (3)

Lecture contents

• Topology in GIS.

• Topology errors.

• Fixing topology.

11/6/2013 6:05 PM 2

Page 3: Lecture+12+topology+2013 (3)

Limitations of geometry • Consider the geometric description of three

polylines.

– Both descriptions are geometrically equivalent.

11/6/2013 8:52 PM 3

(5.1,2.3)

(4.8,1.3)

1

2

3

(6.2,3.3)

(6.6,1.4)

(5.7,0.2)

Polyline Coordinates

1 (4.8, 1.3), (5.1, 2.3), 6.2, 3.3), (6.6, 1.4)

2 (4.8, 1.3), (6.6, 1.4)

3 (4.8, 1.3), (5.7, 0.2), (6.6, 1.4)

Polyline Coordinates

1 (6.6, 1.4), (6.2, 3.3), (5.1, 2.3), (4.8, 1.3)

2 (4.8, 1.3), (6.6, 1.4)

3 (4.8, 1.3), (5.7, 0.2), (6.6, 1.4)

Page 4: Lecture+12+topology+2013 (3)

Limitations of geometry

• If lines are a road network and polygons are land parcels:

– What about one way streets?

– Which road is between parcels?

– Which parcel is on the ‘left’?

• Something more than geometry is needed…

11/6/2013 8:57 PM 4

(5.1,2.3)

(4.8,1.3)

b

a

1

2

3

(6.2,3.3)

(6.6,1.4)

(5.7,0.2)

Page 5: Lecture+12+topology+2013 (3)

Topology

• The representation of the arrangements of geometric objects and the relationships among them.

• Some fundamental relationships

– Connectivity: what is connected to what.

– Area definition: containment.

– Contiguity: borders and left/right adjacent areas.

11/6/2013 9:24 PM 5

Page 6: Lecture+12+topology+2013 (3)

Topology

• Topological relationships are invariant under:

– Affine transformations

– Bending

– Stretching.

11/7/2013 11:37 AM 6 http://www.indiana.edu/~gisci/courses/g338/lectures/introduction_vector.html

Page 7: Lecture+12+topology+2013 (3)

Directed graph (digraph)

• In GIS vector data topology is implemented using graph theory.

• Graph: A set of

– nodes, and

– ordered pairs of nodes, called arcs

• Each arc connects two nodes and has direction from the 1st node to the 2nd node.

11/7/2013 8:54 AM 7

Page 8: Lecture+12+topology+2013 (3)

Connectivity: Adjacency

• If an arc joins 2 nodes, the nodes are called adjacent.

• Represented by the adjacency matrix. – Encodes direction.

– No arc identity.

11/6/2013 10:20 PM 8

Page 9: Lecture+12+topology+2013 (3)

Connectivity: Incidence

• If an arc joins 2 nodes, the nodes are called incident to the arc.

• Incidence matrix

– Encodes direction, and

– Arc identity.

11/6/2013 10:35 PM 9

Page 10: Lecture+12+topology+2013 (3)

ESRI Coverage: Topological properties

• Connectivity.

– Arcs connect to each other at nodes.

• Area definition.

– Connected arcs that surround an area define a polygon.

• Contiguity.

– Arcs have direction and left and right sides).

11/7/2013 9:18 AM 10 Lo and Yeung p. 86

Page 11: Lecture+12+topology+2013 (3)

Coverage Connectivity: Arc-node topology

11/7/2013 9:33 AM 11

• Beginning and ending node of each arc.

• Remember: A node is either the end of a line or the intersection of lines.

Page 12: Lecture+12+topology+2013 (3)

Coverage Area definition: Polygon-arc topology

• Area: series of connected arcs; polygon-arc list.

• Containment:

– 0 precedes internal polygon.

11/7/2013 8:57 AM 12

Page 13: Lecture+12+topology+2013 (3)

Coverage Contiguity: Left-right topology

• Relationships between arcs and their left and right polygons.

• A background polygon (100) must be defined.

11/6/2013 10:59 PM 13

Page 14: Lecture+12+topology+2013 (3)

Topology creation

• Can we build topology from geometry?

11/7/2013 10:07 AM 14

(5.1,2.3)

(4.8,1.3)

b

a

1

2

3

(6.2,3.3)

(6.6,1.4)

(5.7,0.2)

2. Arc Coordinate List

Arc # Coordinates

1 (4.8,1.3), (5.1,2.3), (6.2,3.3)

2 (4.8,1.3), (6.2,3.3)

3 (6.2,3.3), (5.7,0.2), (4.8,1.3)

(6.6, 1.4)

(6.6, 1.4)

(6.6, 1.4)

1.

1. Arc-Node List

Arc # From-nodeTo- node

1 a b

2 a b

3 b a

2.

a b

Page 15: Lecture+12+topology+2013 (3)

Topology creation

11/7/2013 9:59 AM 15

b

a

1

2

A

3

B

1. Arc-Node List

Arc # From-nodeTo- node

1 a b

2 a b

3 b a

2.

3. Polygon-Arc List

Poly # Arcs

A 1, 2

B 2, 3

Page 16: Lecture+12+topology+2013 (3)

Topology & errors

• Building topology from geometry involves identifying all nodes, arcs, and polygons.

• What if there are errors in the geometry?

– No problem in topology…

–Only in geometry.

11/7/2013 10:41 AM 16

Polyline Coordinates

1 (4.8, 1.3), (5.1, 2.3), (6.19, 3.3), (6.6, 1.4)

2 (4.8, 1.3), (6.6, 1.4)

3 (4.8, 1.3), (5.7, 0.2), (6.6, 1.4)

(5.1,2.3)

(4.8,1.3)

b

a

1

2

3

(6.2,3.3)

(6.6,1.4)

(5.7,0.2)

(6.19,3.3)

Page 17: Lecture+12+topology+2013 (3)

Topology & errors

• What about this error?

– What happens to node b?

–What happens to polygons?

11/7/2013 11:44 AM 17

(5.1,2.3)

(4.8,1.3)

1

2

3

(6.2,3.3)

(6.6,1.4)

(5.7,0.2)

Polyline Coordinates

1 (4.8, 1.3), (5.1, 2.3), 6.2, 3.3), (6.599, 1.4)

2 (4.8, 1.3), (6.6, 1.4)

3 (4.8, 1.3), (5.7, 0.2), (6.6, 1.4)

(6.599,1.4)

Page 18: Lecture+12+topology+2013 (3)

Topology & errors

• Nonsensical vertex order (ambiguity).

11/7/2013 11:46 AM 18

(5.1,2.3)

(4.8,1.3)

1

2

3

(6.2,3.3)

(6.6,1.4)

(5.7,0.2)

Polyline Coordinates

1 (4.8, 1.3), (6.2, 3.3), (5.1, 2.3), (6.6, 1.4)

2 (4.8, 1.3), (6.6, 1.4)

3 (4.8, 1.3), (5.7, 0.2), (6.6, 1.4)

Page 19: Lecture+12+topology+2013 (3)

Geometry errors

• Geometrical errors

– May cause topological errors, i.e., violations of topological relathionships

– May only affect spatial data accuracy.

• Accuracy standards govern ‘acceptable’ geometrical errors (see Book, section 7.2).

• Topological errors caused by very small geometry errors can cause severe effects!

11/7/2013 10:31 AM 19

Page 20: Lecture+12+topology+2013 (3)

‘Small’ error example • An ambulance carrying a stroke victim needs

to take the fastest route from A to B.

• Two arcs in a road network do not ‘exactly connect’.

• The car navigator takes a long route…

11/7/2013 11:08 AM 20

B

A

20 miles

14 miles

3 miles

Page 21: Lecture+12+topology+2013 (3)

Line feature topological errors

• Undershoot – Gap between lines.

• Overshoot – Overextended lines.

• Both errors cause dangling nodes. – Such nodes could be OK

though (when?) 11/7/2013 11:16 AM 21

Page 22: Lecture+12+topology+2013 (3)

Line feature topological errors

• Pseudonodes

– Nodes not located at end of arc or at line intersection.

• Direction of line.

– Important in the case of one way streets or rivers/streams.

11/7/2013 12:32 PM 22

Page 23: Lecture+12+topology+2013 (3)

Polygon feature topological errors

• Unclosed polygons.

• Gap between two polygons.

11/7/2013 12:07 PM 23

Page 24: Lecture+12+topology+2013 (3)

Polygon feature topological errors

• Overlap: Sliver polygons

• Gaps

11/7/2013 12:07 PM 24

htt

p:/

/sca

pet

oad

.ch

oro

s.ch

/hel

p/v

11/

a-ca

rto

gram

-cre

atio

n.p

hp

Page 25: Lecture+12+topology+2013 (3)

Point feature topological errors

• Each polygon requires a label point to link it to its attribute data.

• If a polygon has zero or several label points, an error occurs.

11/7/2013 12:34 PM 25

×

×

Page 26: Lecture+12+topology+2013 (3)

Error sources

• Due to digitization errors within a data layer

– E.g., ‘Heads-down’ manual map digitization using a digitizing table.

11/7/2013 12:17 PM 26

– ‘Heads-up’ manual digitization of CAD or scanned rasters on the screen.

Page 27: Lecture+12+topology+2013 (3)

Error sources

• Due to digitization or alignment errors between layers.

• Don’t need to be of the same feature type. E.g.:

– Adjoining layer edges don’t match.

11/7/2013 12:15 PM 27

– Distortion between overlapping layers.

– Overlap, undershoot, overshoot.

Page 28: Lecture+12+topology+2013 (3)

Building topology in ArcGIS

• Create topology 1. Define participating feature classes

2. Specify the topology rules between feature classes

3. Set cluster tolerance

4. Identify the accuracy ranks of the coordinates in each feature class.

5. Validate topology

6. Find and fix errors or mark exceptions

7. Iterate

11/7/2013 1:06 PM 28

Page 29: Lecture+12+topology+2013 (3)

ArcGIS topology rules

• Topology rules allow you to define spatial relationships between features in a single feature class or subtype or between two feature classes or subtypes.

• Topology rules allow you to define the spatial relationships that meet the needs of your data model.

• A pdf poster with all rules: http://help.arcgis.com/en/arcgisdesktop/10.0/help/001t/pdf/topology_rules_poster.pdf

11/7/2013 1:18 PM 29

Page 30: Lecture+12+topology+2013 (3)

Examples: ArcGIS topology rules

• Data theme: Parcels

• Feature classes: – Parcel polygons,

– Parcel boundaries (lines)

– Parcel corners (points)

• Some topology rules – Parcel polygons must not overlap.

– Parcel polygon boundaries must be covered by Parcel boundary lines.

– Parcel boundary endpoints must be covered by Parcel corner points.

11/7/2013 1:15 PM 30

Page 31: Lecture+12+topology+2013 (3)

Identifies errors in Arc-Node topology

11/6/2013 11:21 PM 31

Page 32: Lecture+12+topology+2013 (3)

Identifies polygon containment errors

11/6/2013 11:23 PM 32

Single

Page 33: Lecture+12+topology+2013 (3)

Identifies adjacency errors

11/6/2013 11:25 PM 33

Single

Page 34: Lecture+12+topology+2013 (3)

Identifies point in polygon containment errors

11/6/2013 11:25 PM 34

Multiple

Page 35: Lecture+12+topology+2013 (3)

Cluster tolerance

• ArcGIS analyzes the coordinate locations of feature vertices among features in the same feature class as well as between the feature classes that participate in the topology.

• Those that fall within a specified distance of one another are assumed to represent the same location and are assigned a common coordinate value (in other words, they are collocated).

11/7/2013 1:22 PM 35

Page 36: Lecture+12+topology+2013 (3)

Cluster tolerance

• A cluster tolerance is used to integrate vertices.

– All vertices that are within the cluster tolerance may move slightly in the validation process.

• The default cluster tolerance is based on the precision defined for the dataset.

• The default cluster tolerance is 0.001 meters in real-world units.

11/7/2013 1:22 PM 36

Page 37: Lecture+12+topology+2013 (3)

XY tolerance

11/7/2013 1:28 PM 37 http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#//006200000003000000.htm

Page 38: Lecture+12+topology+2013 (3)

Z-tolerance

• If necessary, a z-tolerance is also defined to distinguish whether or not the z-heights or elevations of vertices are within the tolerance of one another and should be clustered.

11/7/2013 1:28 PM 38

Page 39: Lecture+12+topology+2013 (3)

Coordinate accuracy ranks

• Which vertices should move?

• Coordinate ranks ensure that reliably placed vertices are the anchor locations toward which less reliable vertices are moved. E.g.,

– RTK-GPS vertices would have high rank (1)

– Standard GPS vertices would have lower rank (2, 3)…

• Equally ranked vertices are geometrically averaged.

11/7/2013 1:32 PM 39

Page 40: Lecture+12+topology+2013 (3)

Validate topology: algorithmic

11/7/2013 1:59 PM 40

• Algorithmic clustering and cracking.

• Insertion of common coordinate vertices into coincident features that share geometry.

Page 41: Lecture+12+topology+2013 (3)

Validate topology: manual

• Topology errors are violations of the rules that are initially stored as errors in an error log.

• Error features record where topological errors were discovered during validation.

– Example: Error features for the “must not have dangles” rule.

11/7/2013 1:43 PM 41

Page 42: Lecture+12+topology+2013 (3)

Fixing errors

• User intervention

– Change vertex locations, trace new lines and replace old ones, etc.

11/7/2013 2:02 PM 42

Fix!

Page 43: Lecture+12+topology+2013 (3)

Mark exceptions

• Certain errors may be acceptable, in which case the error features can be marked as exceptions. E.g.:

11/7/2013 1:45 PM 43

Page 44: Lecture+12+topology+2013 (3)

Iterate

• Topology validation is user driven.

• Dirty areas are areas that have been edited, updated, or affected by the addition or deletion of features; they are maintained automatically by ArcGIS.

• This allows selected parts, rather than the whole extent of the topology, to be validated.

11/7/2013 1:50 PM 44