3.3 Geodatabase Topology and Validation Rules

Geodatabase Topology and Validation

Quick Answer: Geodatabase Topology is a set of rules that enforce spatial integrity by defining how features share geometry. Housed within a feature dataset, topology identifies spatial errors like overlaps or gaps, allowing editors to correct them or mark them as valid exceptions.

While attribute domains and subtypes ensure the integrity of the tabular data, Geodatabase Topology ensures the integrity of the spatial data. Topology manages how point, line, and polygon features share coincident geometry. It is an essential component for maintaining high-quality GIS data, particularly for authoritative datasets like land records (parcels), utility networks, and administrative boundaries.

The Architecture of Topology

Geodatabase topology is not applied arbitrarily. It has specific architectural requirements within the geodatabase:

1. Feature Datasets are Mandatory: A topology can only be created inside a Feature Dataset. You cannot create a topology for standalone feature classes at the root level of the geodatabase.
2. Coordinate System Consistency: Because topologies reside in feature datasets, all participating feature classes are guaranteed to share the exact same spatial reference (coordinate system). This is necessary for precise spatial calculations.
3. Multi-Class Participation: A single topology can manage the spatial relationships within a single feature class, or between multiple feature classes, provided they are all in the same feature dataset.

Core Concepts

When configuring a topology, several key parameters dictate how it behaves.

Cluster Tolerance

The Cluster Tolerance is the critical distance under which vertices and edges are considered identical (coincident). When topology is validated, if two vertices fall within the cluster tolerance of each other, ArcGIS Pro snaps them together to become a single coordinate location.

• It is usually set to a very small distance (e.g., 0.001 meters).
• Setting the cluster tolerance too high will cause distinct features to collapse into each other, warping the geometry.

Coordinate Accuracy Ranks

When vertices snap together during validation, which vertex moves to meet the other? This is determined by Accuracy Ranks. You assign a rank (from 1 to 50) to each feature class in the topology. A lower number indicates higher accuracy (Rank 1 is the highest).

If a vertex from a Rank 1 feature class (e.g., highly accurate surveyed points) is within the cluster tolerance of a vertex from a Rank 5 feature class (e.g., digitized sketch lines), the Rank 5 vertex will move to snap to the Rank 1 vertex. The Rank 1 vertex remains anchored.

Topology Rules

Topology rules define the permissible spatial relationships. ArcGIS Pro offers a vast library of rules tailored to points, lines, and polygons.

Common Polygon Rules:

• Must Not Overlap: Parcels in a tax fabric cannot overlap each other.
• Must Not Have Gaps: A continuous zoning map should not have unzoned gaps between zoning districts.
• Must Be Covered By Feature Class Of: Building footprint polygons must be entirely covered by parcel polygons.

Common Line Rules:

• Must Not Have Dangles: Water mains should connect to other mains or fittings; a line segment ending in empty space (a dangle) is often a digitization error.
• Must Not Intersect Or Touch Interior: Contour lines should never cross each other.

Common Point Rules:

• Must Be Properly Inside: Address points must fall completely inside a parcel polygon, not on the boundary.

The Validation Workflow

Creating rules does not automatically fix data. Editors must run a validation process to find violations.

1. Dirty Areas

When a topology is first created, or when features participating in a topology are created, modified, or deleted, ArcGIS Pro flags the affected geographic region as a Dirty Area. A dirty area is a bounding box indicating that the spatial relationships in that location are unknown and need to be checked.

2. Validation

The editor initiates the Validate command. ArcGIS Pro analyzes the dirty areas, checks the features against the defined topology rules, snaps vertices within the cluster tolerance, and clears the dirty area.

3. Errors and Exceptions

If a rule violation is found during validation, it is flagged as an Error. Errors are visualized on the map with specific symbology (usually red areas, lines, or points).

Not all errors represent bad data. Sometimes, the real world violates the rule. For example, a topology rule might state "Street lines must not have dangles" (dead ends). A cul-de-sac is a legitimate dead end.

Using the Error Inspector pane, an editor can review each error individually. They have two choices:

1. Fix the Error: Use editing tools to correct the geometry (e.g., extend the line to snap to the next street).
2. Mark as Exception: Tell the geodatabase that this specific violation is acceptable (e.g., marking the cul-de-sac as an exception). The error disappears from the map and is ignored in future validations.

The Error Inspector is a crucial tool for quality assurance, providing a centralized list of all topological issues, allowing editors to systematically review and resolve them.