Available with ArcGIS Pro Standard and Data Reviewer licenses.
Summary
The Evaluate Part Count check returns polygon and polyline features with part counts that are within a specified range.
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:
Workflow | Supported | Licensing |
---|---|---|
Validation attribute rule | Yes (ArcGIS Pro 2.5 and ArcGIS Enterprise10.8 or later) | Available with ArcGIS Pro Standard and Data Reviewer license |
Constraint attribute rule | Yes (ArcGIS Pro 2.4 or later) | Available with ArcGIS Pro Standard and Data Reviewer license |
Run Data Checks | Yes (ArcGIS Pro 3.5 or later) | Available with Data Reviewer license |
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.
Attribute Rule syntax
The following table describes the validation and constraint attribute rule parameters:
Parameter | Required | Description | Workflow |
---|---|---|---|
Subtype |
No | The subtype(s) to which the rule is applied. |
Constraint |
Validation | |||
Attribute |
No | A query that identifies the features to which the rule is 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.
More 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.
|
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 | A description of the error you define when a noncompliant feature is found. This information is used to provide guidance for corrective workflows. |
Constraint |
Validation | |||
Severity |
No | The 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 | 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 |
Run Data Checks syntax
The following table describes the Run Data Checks parameters:
Parameter | Required | Description |
---|---|---|
Input Feature | Yes | The input feature layer that is evaluated by the rule. Note:You can disable a map selection or layer definition query using the toggle button that honors the selection or filter before evaluation. Layer definition queries that include a spatial clause are not supported. |
Attribute Filter | No | A query that identifies the features to which the rule is applied. |
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.
More input is required if you choose an operator with upper and lower bounding values. |
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. |
Extent | Yes |
|
Notes
Keep the following in mind when using the check:
- Polygon and polyline features are supported with this check.
- The Attribute filter parameter is limited to comparison (=, <>, >, <, >=, and <=) and logical (AND/OR, IN/NOT IN, LIKE/NOT LIKE, and IS NULL) operators.
- The Attribute filter parameter does not support the following field types: Big Integer, Date Only, Time Only, and Timestamp Offset. If selected, the row header is marked in red and does not allow the rule to be saved.