Skip To Content

Geodatabase topology rules and fixes for point features

Available with Standard or Advanced license.

Geodatabase topology rules allow you to define relationships between features in the same feature class or subtype or between two feature classes or subtypes. The status of a topology, including errors and exceptions, is saved to the source geodatabase. In the Contents pane, geodatabase topology rules appear as group layers containing sublayers that symbolize modified areas, and errors organized by geometry type.

This topic explains the topology rules available for point features and their predefined fixes. For steps to validate a geodatabase topology and fix errors, see Validate and fix geodatabase topology.

Note:

For a poster-size PDF file listing all topology rules, see ArcGIS Geodatabase Topology Rules.

Must be Coincident With

Points in one feature class or subtype must be coincident with points in another feature class or subtype. Use this rule when points from one feature class or subtype should be aligned with points from another feature class or subtype, for example, when service meters must be coincident with service points in an electric utility network.

Must be Coincident With

Errors

Point errors are created where points from the first feature class or subtype are not covered by points from the second feature class or subtype.

Must be Coincident With errors

Predefined fixes

Snap List By Snapping moves a point feature in the first feature class or subtype to the nearest point in the second feature class or subtype that is located within a given distance. If no point feature is found within the tolerance specified, the point is not snapped.

Must Be Disjoint

Points cannot overlap within the same feature class or subtype. Use this rule when points within one feature class or subtype should never occupy the same space, for example, when fittings in a water distribution network should not overlap.

Must Be Disjoint

Errors

Point errors are created where points overlap.

Must Be Disjoint errors

Predefined fixes

A predefined fix is not available for this error. Consider using tools in the Modify Features pane.

Must Be Covered By Boundary Of

Points in one feature class or subtype must touch boundaries of polygons from another feature class or subtype. Use this rule when you want points to be on or inside the boundaries of polygons, for example, when utility service points are required to be within the boundary of a parcel.

Must Be Covered By Boundary Of

Errors

Point errors are created where points do not touch the boundaries of polygons.

Must Be Covered By Boundary Of errors

Predefined fixes

A predefined fix is not available for this error. Consider using tools in the Modify Features pane.

Must Be Properly Inside Polygons

Points in one feature class or subtype must be inside polygons of another feature class or subtype. Use this rule when you want points to be completely within the boundaries of polygons, for example, when state capitals must be inside each state.

Must Be Properly Inside Polygons

Errors

Point errors are created where the points are outside or touch the boundary of the polygons.

Must Be Properly Inside Polygons errors

Predefined fixes

Delete Feature Delete removes point features that are not properly within polygon features.

Note:

To keep a feature, you can enable your snapping preferences and use Move Move in the Modify Features pane.

Must Be Covered By Endpoint Of

Points in one feature class or subtype must be covered by the ends of lines in another feature class or subtype. Use this rule when you want to model points that are coincident with the ends of lines, for example, when street intersections must be covered by the endpoints of street centerlines.

Must Be Covered By Endpoint Of

Errors

Point errors are created on the points that are not covered by the ends of lines.

Must Be Covered By Endpoint Of errors

Predefined fixes

Delete Feature Delete removes point features that are not coincident with the endpoint of line features.

Note:

To keep a feature, you can enable your snapping preferences and use Move Move in the Modify Features pane.

Point Must Be Covered By Line

Points in one feature class or subtype must be covered by lines in another feature class or subtype. Use this rule when you want to model points that are coincident with lines, for example, when monitoring stations must fall along streams.

Point Must Be Covered By Line

Errors

Point errors are created on the points that are not covered by lines.

Point Must Be Covered By Line errors

Predefined fixes

A predefined fix is not available for this error. Consider using tools in the Modify Features pane.