Available with ArcGIS Pro Standard and Data Reviewer licenses.
Sliver polygons are usually small polygons resulting from overlay operations such as Intersect or Union. Sliver polygons typically have an area that is much smaller than the perimeter. The Polygon Sliver check finds polygon features with a thinness ratio below a specified threshold. Optionally, you can require that the area of each polygon is below a maximum area threshold.
ArcGIS Data Reviewer checks support multiple methods for implementing automated review of data. The following table identifies the supported implementation methods for this check:
Reviewer batch job
Attribute (validation) rule
(ArcGIS Pro 2.9 and ArcGIS Enterprise 10.9.1 or later)
Polygon slivers can occur during data extraction when small, thin polygons are created due to an overlap with existing features. Tiny sliver polygons or gaps between polygons often result from creating polygons without using snapping or from editing shared boundaries without a topology. A sliver polygon is defined by its thinness ratio and maximum area. If a polygon is below a specified thinness ratio and area, it is considered a sliver. You can run this check on an entire feature class, a subtype, or a set of features selected using an SQL query.
The subtype to which the rule is applied.
A query that identifies the features to which the rule is applied.
The thinness ratio (T) between a feature’s area (A) and its perimeter (P) is calculated using the following equation:
A thinness ratio of 1 is a perfect circle and a thinness ratio of 0 is a line.
This measure takes a maximum value of 1 for a circle. Objects of regular shape have a higher thinness ratio than irregular ones.
The maximum area that is considered a sliver. If the polygon's area is equal to or less than this value, it is considered a sliver.
The default unit of measure is the input data source's horizontal spatial reference.
A unique name for the rule.
This information is used to support data quality requirement traceability, automated reporting, and corrective workflows.
A description of the error you define when a noncompliant feature is found.
This information is used to provide guidance to facilitate corrective workflows.
The severity of the error assigned when a noncompliant feature is found.
This value indicates the importance of the error relative to other errors. Values range from 1 to 5, with 1 being the highest priority and 5 being the lowest.
The tag property of the rule.
This information is used in rule authoring and management workflows to support traceability and reporting of data quality requirements.
The Attribute parameter is limited to comparison (=, <>, >, <, >=, <=) and logical (AND/OR, IN/NOT IN, LIKE/NOT LIKE, IS NULL) operators.
- The Attribute filter parameter does not support the following field types: Big Integer, Date Only, Time Only, and Timestamp Offset. If selected, the row header will turn red and will not allow the rule to save.