Available with Data Reviewer license.
Summary
The Subtype check finds features with improper or null subtype values.
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.7 and ArcGIS Enterprise 10.9 or later) | Available with ArcGIS Pro Standard and Data Reviewer license | |
Constraint attribute rule | No | Available with ArcGIS Pro Standard and Data Reviewer license | |
Run Data Checks | Yes (ArcGIS Pro 3.4 or later) | Available with Data Reviewer license | |
Legacy:
Map-based Reviewer rules are deprecated and are not available for use. It is recommended that you migrate automated review workflows to Data Reviewer capabilities available in attribute rules. Opening or saving a map document (.aprx file) at ArcGIS Pro 3.0 or later removes all the existing map rules from the document.
Overview
The Subtype check finds features that contain attribute values that are not defined for the subtype. This includes attribute values that are inconsistent with the subtype's defined values and, optionally, null attribute values.
Subtypes are a subset of features in a feature class or objects in a stand-alone table that share the same attributes. For example, features in the Bridge line feature class can be organized into separate subtypes for bridges, overpasses, and viaducts instead of combining them into one subtype.
Attribute Rule Syntax
| Parameter | Required | Description | Workflow |
|---|---|---|---|
|
Subtype |
No | The subtype to which the rule is applied. | Validation |
|
Attribute |
No | A query that identifies the features to which the rule is applied. | Validation |
|
Search for Null Values |
No | Attribute values that are <Null> are returned as an error. | Validation |
|
Name |
Yes | A unique name for the rule. This information is used to support data quality requirement traceability, automated reporting, and corrective workflows. | 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. | Validation |
|
Severity |
No | The severity of the error assigned when a noncompliant feature is 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. | Validation |
Run Data Checks Syntax
| Parameter | Required | Description |
|---|---|---|
Input Feature | Yes | The input feature layer that is evaluated by the rule. |
Attribute | No | A query that identifies the features to which the rule is applied. |
Search for Null Values | No | Attribute values that are <Null> are returned as an error. |
Name | No | A unique name for the rule. This information is used to support data quality requirement traceability, automated reporting, and corrective workflows. |
Visible Extent | No | Evaluate the visible extent of the map. |
Full Extent | No | Evaluate the full extent of the data. |
Notes
Keep the following in mind when using the check:
- Domain-restricted attributes for features or table records assigned to an invalid subtype can't be evaluated when using the Domain check. You must correct subtype-related errors before evaluating domain-restricted attributes.
- 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.