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 may optionally include null attribute values.
Subtypes are a subset of features in a feature layer. For example, features in the Bridge line layer can be organized into separate subtypes for bridges, overpasses, and viaducts instead of combining them into one subtype. However, if the product specification does not allow this type of granularity between feature types, these subtypes would be considered invalid.
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 | No |
Yes | Yes | No | |
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 |
Search for Null Values | Yes | Indicates whether the check searches for null subtype values. | Validation |
Title | No | 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 | No | Descriptive text of the error condition when noncompliant features are found. This information is used to provide guidance to facilitate corrective workflows. | Validation |
Severity | No | Severity of the error 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. | Validation |
to apply filtering to specific features in the feature layer or specific rows in the stand-alone table.Notes
- 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 will be required once subtype-related errors are corrected.
- When this check is authored as a map-based rule, care should be taken when configuring filter parameters using database-specific SQL functions that differ from those supported in your production environment.