Available with ArcGIS Pro Standard and Data Reviewer licenses.
Summary
The Nonlinear Segment check finds features that contain nonlinear segments. This includes polyline or polygon features that contain curves and arcs.
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:
| Workflow | Supported | Licensing |
|---|---|---|
Validation attribute rule | Yes (ArcGIS Pro 2.6 and ArcGIS Enterprise10.8.1 or later) | Available with ArcGIS Pro Standard and Data Reviewer license |
Constraint attribute rule | No | N/A |
Run Data Checks | Yes (ArcGIS Pro 3.5 or later) | Available with Data Reviewer license |
Overview
The Nonlinear Segment check identifies polyline or polygon features that contain nonlinear segments. Nonlinear segments include those that contain circular or elliptic arcs and Bézier curves. Nonlinear segments can impact analysis and sharing workflows.
Industry scenarios
This check can be used in the following scenarios:
- In national and defense mapping workflows, features that contain nonlinear segments can impact feature generalization and sharing to non-Esri data formats.
- In roadway management, centerline features that contain nonlinear segments can result in the creation of nonmonotonic routes.
- In network datasets, curves or arcs without vertex coincidence to straight line vertices create an impact on network connectivity.
Attribute Rule syntax
The following table describes the validation attribute rule parameters:
| Parameter | Required | Description | Workflow |
|---|---|---|---|
|
Subtype |
No | The subtype(s) to which the rule is applied. | Validation |
|
Attribute |
No | A query that identifies the features to which the rule is applied. | Validation |
|
Name |
Yes | A unique name for the rule. This information is used to support data quality requirement traceability, automated reporting, and corrective workflows. | Validation |
|
Description |
No | A description of the error you define when a noncompliant feature is found. This information is used to provide guidance for 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 |
Run Data Checks syntax
The following table describes the Run Data Checks parameters:
| Parameter | Required | Description |
|---|---|---|
Input Feature | Yes | The input feature layer that is evaluated by the rule. Note:You can disable a map selection or layer definition query using the toggle button that honors the selection or filter before evaluation. Layer definition queries that include a spatial clause are not supported. |
Attribute Filter | No | A query that identifies the features to which the rule is applied. |
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. |
Extent | Yes |
|
Notes
Keep the following in mind when using the check:
- Polyline and polygon feature layers are supported.
- The Attribute filter parameter is limited to comparison (=, <>, >, <, >=, and <=) and logical (AND/OR, IN/NOT IN, LIKE/NOT LIKE, and 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 is marked in red and does not allow the rule to be saved.