Evaluate Vertex Count

Mit der Data Reviewer-Lizenz verfügbar.

Summary

The Evaluate Vertex Count check finds polyline or polygon features that have a vertex count within a specified tolerance.

Overview

The purpose of the Evaluate Vertex Count check is to identify features that meet vertex count conditions that are considered to be invalid. For example, to improve system performance and reduce data storage requirements, it may be important to identify features that contain an excessive number of vertices.

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

When configured as a validation rule, an error is created for each feature that contains a vertex count 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
Number of Vertices	Yes	The query that is applied to the vertex count of a feature. Any feature with a vertex count that matches what is defined in the rule is returned as an error. Is equal to—The vertex count is equal to the specified value. Is not equal—The vertex count is not equal to the specified value. Is less than—The vertex count is less than the specified value. Is less than or equal to—The vertex count is equal to or less than the specified value. Is greater than—The vertex count is greater than the specified value. Is greater than or equal to—The vertex count is equal to or greater than the specified value. Is between (including bounds)—The vertex count is between or equal to the lower bound (minimum) and upper bound (maximum) values. Is between (excluding bounds)—The vertex count is between the lower bound (minimum) and upper bound (maximum) values. Is not between (including bounds)—The vertex count is not between or equal to the lower bound (minimum) and upper bound (maximum) values. Is not between (excluding bounds)—The vertex count 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
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 Reviewer result 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

Notes

• Polyline and polygon feature layers 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.