Available with Data Reviewer license.
Summary
The Unnecessary Polygon Boundaries check finds polygon features that share a common boundary and contain identical attribute values.
Overview
When polygon features share a common boundary and contain identical attribute values on editable fields, the shared boundary is often unnecessary. Features found with this check can be merged without a loss of information and can result in enhanced database performance.
Supported workflows
ArcGIS Data Reviewer checks support multiple methods for implementing automated review of data. The following table identifies the supported implementation methods for this check:
| Validation | Constraint | ||
|---|---|---|---|
Reviewer batch job | Reviewer map rule | Attribute (validation) rule | No |
Yes | No | Yes (ArcGIS Pro 2.7 or later) | |
Syntax
| Parameter | Required | Description | Workflow |
|---|---|---|---|
Subtype | No |
The subtype to which the rule is applied. | Validation |
Attribute | No | A query that identifies the features to which the rule is applied. | Validation |
Attributes to Ignore | No | The attribute values to ignore when evaluating for unnecessary polygon boundaries. The attribute values to ignore during evaluation. Only editable fields can be ignored. | Validation |
Name | No | A unique title or name for the rule. This information is used to support data quality requirement traceability, automated reporting, and corrective workflows. | Validation |
Description | No | A description you define of the error when a noncompliant feature is found. This information is used to provide guidance to facilitate corrective workflows. | Validation |
Severity | No | 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. | Validation |
Tags | No |
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. | Validation |
Notes
- The Validation Status attribute value of input features is ignored during evaluation. For example, input features with a validation status of 0 (No calculation required, no validation required, no error), 1 (No calculation required, no validation required, has error(s)), 4 (Calculation required, no validation required, no error), or 5 (Calculation required, no validation required, has error(s)) are still included during rule evaluation.
- The Attribute filter parameter is limited to comparison (=, <>, >, <, >=, <=) and logical (AND/OR, IN/NOT IN, LIKE/NOT LIKE, IS NULL) operators.