Evaluate Part Count

Mit der Data Reviewer-Lizenz verfügbar.

Summary

The Evaluate Part Count check returns polygon, polyline, and multipoint features with part counts that are within a specified range.

Overview

The Evaluate Part Count check searches for features that contain part counts that are within a specified range. For example, if you search for all road features with more than two parts, all road features with three or more parts would be returned.

When configured as a constraint rule, an error notification is returned when a feature that contains the number of parts specified in the rule is created or modified.

When configured as a validation rule, an error is created for each feature that contains a part count within the specific 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	Workflows
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
Number of Parts	Yes	The query that is applied to the count of a feature's parts. Any feature with a part count that matches what is defined in the rule is returned as an error. Is equal to—The number of parts is equal to the specified value. For example, if the value is 10, features with 10 parts are returned as results. Is not equal—The number of parts is not equal to the specified value. Is less than—The number of parts is less than the specified value. Is less than or equal to—The number of parts is equal to or less than the specified value. Is greater than—The number of parts is greater than the specified value. Is greater than or equal to—The number of parts is equal to or greater than the specified value. Is between (including bounds)—The number of parts is between or equal to the lower bound (minimum) and upper bound (maximum) values. Is between (excluding bounds)—The number of parts is between the lower bound (minimum) and upper bound (maximum) values. Is not between (including bounds)—The number of parts is not between or equal to the lower bound (minimum) and upper bound (maximum) values. Is not between (excluding bounds)—The number of parts is not between 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
Greater than	Yes	The number of units to use for the operation. If you chose an operator with upper and lower bounding values, two additional values must be specified, one for the minimum range and one for the maximum range of the tolerance.	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
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-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

Notes

• Polygon, polyline, and multipoint features are supported with this check.
• 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.