Available with Data Reviewer license.
Summary
The Subtype check finds features with improper or null subtype values.
Overview
The purpose of the Subtype check is to find 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 standalone 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.
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:
| Validation | Constraint | ||
|---|---|---|---|
Reviewer batch job | Reviewer map rule | Attribute (validation) rule | N0 |
Yes | Yes | Yes (ArcGIS Pro 2.7 or later) | |
Note:
Map-based Reviewer rules are deprecated as of ArcGIS Pro 2.8 and are no longer recommended for use. This functionality will be removed in the next major release of ArcGIS Pro. It is recommended that you migrate automated review workflows to Data Reviewer capabilities available in attribute rules.
Syntax
| Parameter | Required | Description | Workflows |
|---|---|---|---|
Input Layers/Stand-alone Tables | Yes | The input feature layers or stand-alone tables evaluated by the rule. Valid inputs for this rule type are feature
layers and stand-alone tables. Click the Forward button | Validation (map rules) |
Subtype | No | The subtype to which the rule is applied. | Validation (attribute rules) |
Attribute | No | A query that identifies the features to which the rule is applied. | Validation (attribute rules) |
Search for Null Values | No | Attribute values that are <Null> (no value) are returned as an error. | Validation |
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. | Validation |
Notes/Description | No | A description you define of the error when a noncompliant feature is found. This information is used to provide guidance to facilitate 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 |
to apply filtering to specific features in the feature layer or specific rows in the stand-alone table.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. Evaluation of domain-restricted attributes is required once subtype-related errors are corrected.
- When this check is authored as an attribute (validation) rule, the Attribute filter parameter is limited to comparison (=, <>, >, <, >=, <=) and logical (AND/OR, IN/NOT IN, LIKE/NOT LIKE, IS NULL) operators.
- When this check is authored as a map-based rule, verify that the filter parameters using database-specific SQL functions are the same as from those supported in your production environment.