Finding topology errors with the Error Inspector and editing a feature to correct an error
Segment 7 of 14
|Top Previous Next|
The Error Inspector can selectively show the errors where a specific rule is violated. You can also use the Error Inspector to find all errors, regardless of their type or whether they are in the visible extent, or you can use it to find exceptions to topology rules. An exception is an error feature that has been marked as representing a valid exception to a topology rule.
In this geodatabase, Blocks features have a subtype field that codes them as either Residential or Non-Residential. The Residential block features could be used by the Planning and Zoning office to track whether a given block has parcels that are used for housing.
The topology rule "Must Be Covered By" ensures that residential parcels must be covered by, or fall within, Block features that are marked as residential.
The first Parcel feature that was edited was originally nonresidential. When it was edited, it was switched to the Residential subtype, which triggered this topology error.
There are several possible ways to deal with features that cause topology errors. In this case, some of the options include:
Delete the residential parcel feature.
Create a new block feature that covers just the residential parcel.
Mark the error as an exception.
Ignore the error.
Change the subtype of the Block feature to Residential.
Change the subtype of the Parcel feature to Non-Residential.
Let’s assume that the original edit was correct and that this parcel really was supposed to be reassigned to the Residential subtype. It follows that the block should be changed to reflect its new status as a block containing a residential parcel. Making that edit means that when you validate the part of the topology visible on the map, the error is removed.