Available with Data Reviewer license.
Summary
The Query Attributes check finds features based on a query against its attribute 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.5 and ArcGIS Enterprise 10.8 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 Query Attributes check identifies 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
This check can be used in the following 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.
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 Goal |
Yes | The query expression to be applied to a feature layer or stand-alone table. All features or rows with attributes that match those defined in the query are returned as an error result. | 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 Goal | Yes | The query expression to be applied to a feature layer or stand-alone table. All features or rows with attributes that match those defined in the query are returned as an error result. |
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:
- The Attribute filter parameter is limited to comparison (=, <>, >, <, >=, and <=) and logical (AND/OR, IN/NOT IN, LIKE/NOT LIKE, and IS NULL) operators.
- The Search Goal parameter is limited to comparison (=, <>, >, <, >=, and <=) and logical (AND/OR, IN/NOT IN, LIKE/NOT LIKE, and IS NULL) operators.
- The Attribute and Search Goal filter parameters do not support the following field types: Big Integer, Date Only, Time Only, and Timestamp Offset. If selected, the row header will turn red and will not allow the rule to save.