Available with ArcGIS Pro Standard and Data Reviewer licenses.
Summary
The Composite check finds features or rows based on the results from multiple Reviewer checks. Features or rows that satisfy all check conditions are returned as an error.
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 | Attribute (validation) rule | No |
Yes Note:Only batch jobs with Geometry on Geometry and Table to Table Attribute checks are supported. | Yes (ArcGIS Pro 2.9 and ArcGIS Enterprise 10.9.1 or later) | |
Overview
You may need to identify errors based on multiple error conditions, such as features that have spatial relationships with two or more feature classes. However, if you create separate checks for each condition, you may not get the expected results. The Composite check configures multiple checks into one rule so that you can combine error conditions on the same input feature. This allows you to identify features or rows that meet all configured conditions in a single error.
Industry scenarios
In topographic mapping, you can find bridges that are not coincident with either a road feature or a railroad feature. If you create a Feature on Feature check that finds all bridges that do not intersect roads, some of the check results may intersect railroad features. You can then add a second Feature on Feature check that finds all bridges that do not intersect railroads. The Composite check combines error conditions from each Feature on Feature check and identifies those bridges that are not coincident with either a road feature or a railroad feature.
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 |
Error Message | Yes | A description of the error results returned by the rule. This information appears in the error message returned by this rule. | 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 you define of the error when a noncompliant feature is found. This information is used to provide guidance to facilitate corrective workflows. | Validation |
Severity | Yes | 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 |
Notes
Keep the following in mind when using the check:
- Error features produced by this check always match the input feature’s geometry type.
- The Subtype and Attribute filter parameters defined for the input data source are applied to each check that participates in the Composite check.
- Include the data sources of the checks that participate in the Composite check when creating map or project packages, and sharing web layers with the Validation capability enabled.
- The Attribute filter parameter is limited to comparison (=, <>, >, <, >=, <=) and logical (AND/OR, IN/NOT IN, LIKE/NOT LIKE, IS NULL) operators.
- Event checks are not supported in composite rule configurations.