Evaluate Polyline Length

Available with ArcGIS Pro Standard and Data Reviewer licenses.

Summary

The Evaluate Polyline Length check finds polyline segments, parts, or features that have a length within a specified tolerance.

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:

ValidationConstraint

Reviewer batch job

Attribute (validation) rule

Yes

(ArcGIS Pro 2.4 or later)

Yes

Yes

(ArcGIS Pro 2.5 and ArcGIS Enterprise 10.8 or later)

Overview

The Evaluate Polyline Length check identifies features that meet length conditions that are invalid. This can include an evaluation of the polyline's entire geometry or its individual parts or segments.

When configured as a constraint rule, an error notification is returned when a feature with a length measurement specified in the rule is created or modified.

When configured as a validation rule, an error is created during validation for each feature that contains a length measure within the specified range.

Syntax

Parameter Required DescriptionWorkflow

Subtype

No

The subtype to which the rule is applied.

Constraint

Validation

Attribute

No

A query that identifies the features to which the rule is applied.

Validation

Type

Yes

The method used when evaluating a feature's length.

  • Polyline—Evaluates the length of the entire polyline feature.
  • Parts—Evaluates the length of individual parts of a polyline.
  • Segments—Evaluates the length of the segments of a polyline.

Constraint

Validation

Length

Yes

The query that is applied to the length of a feature geometry, parts, or segments. Any feature with length values that match those defined in the rule is returned as an error.

  • Is equal to—The length is equal to the number of units specified.
  • Is not equal—The length is not equal to the number of units specified.
  • Is less than—The length is less than the number of units specified.
  • Is less than or equal to—The length is equal to or less than the number of units specified.
  • Is greater than—The length is greater than the number of units specified.
  • Is greater than or equal to—The length is equal to or greater than the number of units specified.
  • Is between (including bounds)—The length is between or equal to the number of units specified in the lower bound (minimum) and upper bound (maximum) values.
  • Is between (excluding bounds)—The length is between the number of units specified in the lower bound (minimum) and upper bound (maximum) values.
  • Is not between (including bounds)—The length is not between or equal to the number of units specified in the lower bound (minimum) and upper bound (maximum) values.
  • Is not between (excluding bounds)—The length is not between the number of units specified in the lower bound (minimum) and upper bound (maximum) values.

Additional input is required if you choose an operator with upper and lower bounding values.

Constraint

Validation

Triggers

Yes

The editing events that trigger the rule to take effect.

  • Insert—Triggers the rule when a new feature is added.
  • Update—Triggers the rule when a feature is updated.
  • Delete—Triggers the rule when a feature is deleted.

Constraint

Name

Yes

A unique name for the rule.

This information is used to support data quality requirement traceability, automated reporting, and corrective workflows.

Constraint

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

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.

Constraint

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.

Constraint

Validation

Notes

Keep the following in mind when using the check:

  • The errors found by this check differ depending on whether the entire feature or its individual parts or segments are evaluated.
  • When this check is authored as an attribute (constraint) rule, support for geographic coordinate system-based datasets is limited to those using Web Mercator (WKID 3857) or WGS84 (WKID 4326).
  • The Attribute filter parameter is limited to comparison (=, <>, >, <, >=, <=) and logical (AND/OR, IN/NOT IN, LIKE/NOT LIKE, IS NULL) operators.

Related topics