Available with Data Reviewer license.
Summary
The Cutbacks check finds polyline or polygon features that contain high-angle turns that cause features to turn back toward themselves.
Overview
The purpose of the Cutbacks check is to identify features that contain high-angle turns between vertices. These angles affect polyline and polygon features and can be created during editing and data conversion. Features that contain cutbacks impact length and perimeter calculations and analysis results.
When configured as a constraint rule, an error notification is returned upon creation or modification of a feature that contains one or more segments in which the angle between segments is below a specified minimum value.
When configured as a validation rule, an error is created during validation when a feature contains segments in which the angle between segments is below a specified minimum value.
Industry scenarios
The following examples highlight the impact that errors of this type represent:
- In topographic mapping, elevation contours that contain cutbacks impact cartographic products, feature labeling, and generalization workflows.
- In pipeline management, cutbacks on route features impact measurement values and the referencing of events along the route.
Supported workflows
ArcGIS Data Reviewer checks support multiple methods for implementing automated review of your data. The following table identifies the supported implementation methods for this check:
| Validation | Constraint | ||
|---|---|---|---|
Reviewer batch job | Reviewer map rule | Attribute (validation) rule | Yes (ArcGIS Pro 2.4 or later) |
Yes | Yes | Yes (ArcGIS Pro 2.5 or later) | |
Note:
This check will not be supported in map rules in subsequent versions of ArcGIS Pro, you are strongly encouraged to use this check in attribute rule-based workflows.
Syntax
| Parameter | Required | Explanation | Workflow |
|---|---|---|---|
| Input Layers | Yes | The input feature layers evaluated by the rule. Valid inputs for this rule type are polyline and polygon feature layers. Click the Forward button | Validation (map rules) |
Subtype | No | The subtype that the rule is applied to if the dataset has subtypes. | Constraint |
Validation (attribute rules) | |||
Attribute | No | A query that identifies the features to which the rule is applied. | Validation (attribute rules) |
| Minimum Angle Size | Yes | The minimum angle (in degrees) used to determine a cutback. Features with an angle between segments below this value are returned as an error. | Constraint |
Validation | |||
Triggers | Yes | The editing events that trigger the rule to take effect.
| Constraint |
| Title/Name | Yes | A unique title or name for the rule. This information is used to support data quality requirement traceability, automated reporting, and corrective workflows. | Constraint |
Validation | |||
| Notes/Description | No | Descriptive text of the error condition when noncompliant features are found. This information is used to provide guidance to facilitate corrective workflows. | Constraint |
Validation | |||
| Severity | No | Severity of the error created when noncompliant features are 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 | Tag property of the rule. This information is used in rule authoring and management workflows to support traceability and reporting of data quality requirements. | Constraint |
Validation |
to apply filtering to specific features in the feature layer.Notes
- Polyline and polygon feature layers are supported with this check.
- The Attribute parameter is limited to comparison (=, <>, >, <, >=, <=) and logical (AND/OR, IN/NOT IN, LIKE/NOT LIKE, IS NULL) operators.
- When this check is authored as a map-based rule, verify that filter parameters using database-specific SQL functions are the same as from those supported in your production environment.