Evaluate Polyline Length

Mit der Data Reviewer-Lizenz verfügbar.

Summary

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

Overview

The purpose of the Evaluate Polyline Length check is to identify 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.

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
Yes	No	Yes

Syntax

Parameter	Required	Description	Workflow
Subtype	No	The subtype that the rule will be applied to if the dataset has subtypes.	Constraint
			Validation
Attribute	No	A query that identifies the features to which the rule will be 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 title or name for the rule. This information is used to support data quality requirement traceability, automated reporting, and 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
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
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

Notes

• The errors found by this check will 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 WGS 84 (wkid 4326).
• When this check is authored as an attribute (validation) rule, the Attribute and Features to Compare Filter parameters are limited to comparison (=, <>, >, <, >=, <=) and logical (AND/OR, IN/NOT IN, LIKE/NOT LIKE, IS NULL) operators.