Available with Data Reviewer license.
Summary
The Query Attributes check finds features based on a query against its attribute values.
Overview
The purpose of the Query Attributes check is to identify errors based on a Structured Query Language (SQL) query that can include one or more attribute values. Depending on the database type, this query can also include functions (string and numeric) to implement complex queries. Features or rows returned by the query are written as an error.
Industry scenarios
- In parcel management, features that contain invalid values in their parcel identification numbers, invalid conveyance type, and encumbrance type attributes impact attribute consistency between features and reporting.
- In gas utility management, pipe features that contain invalid values in the material and diameter fields impact asset reporting and modeling.
- In water utility management, network features that contain invalid values based on known construction methods (such as butterfly valves measuring less than 24 inches in diameter) impact asset reporting, modeling, and locator services.
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 | Yes (ArcGIS Pro 2.5 or later) | |
Note:
This check will not be supported in map rules in subsequent versions of ArcGIS Pro, you are strongly encouraged to use this check in attribute rule-based workflows.
Syntax
| Parameter | Required | Description | Workflows |
|---|---|---|---|
Input Layers/Standalone 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 that the rule is applied to if the dataset has subtypes. | Validation (attribute rules) |
Attribute | No | A query that identifies the features to which the rule is applied. | Validation (attribute rules) |
Search Goal | Yes | The query expression to be applied to a feature layer or stand-alone table. All features or rows whose attributes match those defined in the query are returned as an error result. | 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
The following conditions apply when this check is authored as an attribute (validatio ) rule:
- The Attribute parameter is limited to comparison (=, <>, >, <, >=, <=) and logical (AND/OR, IN/NOT IN, LIKE/NOT LIKE, IS NULL) operators.
- The Search Goal parameter is limited to comparison (=, <>, >, <, >=, <=) and logical (AND/OR, IN/NOT IN, LIKE/NOT LIKE, IS NULL) operators.
The following conditions apply when this check is authored as a map-based validation rule:
- When this check is authored as a map-based rule, verify that filter parameters using database-specific SQL functions are the same as from those supported in your production environment.
- When authoring a rule for multiple layers or stand-alone tables, only those fields that are common (matching name and data type) across all layers or tables can be used in the Search Goal parameter.