Skip To Content

Evaluate Part Count

Available with Data Reviewer license.

Summary

The Evaluate Part Count check returns 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.

Syntax

Parameter Required DescriptionWorkflows

Subtype

No

The subtype that the rule will be applied to if the dataset has subtypes.

Attribute rules

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.

Attribute rules

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.

Attribute rules

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.

Attribute rules (constraint)

Title/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.

Attribute rules

Notes/Description

No

Descriptive text of the error condition when noncompliant features are found.

This information is used to provide guidance to facilitate corrective workflows.

Attribute rules

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.

Attribute rules

Notes

  • When configuring filter parameters, care should be taken when using database-specific SQL functions that differ from those supported in your production environment. For more information, see SQL reference for query expressions used in ArcGIS.
  • Polyline and polygon feature layers are supported with this check.

Related topics