Available with Data Reviewer license.
Summary
The Table to Table Attribute check finds features or rows that contain attribute values that meet a relationship you define to values in another feature class or stand-alone table. This can include comparing string values that match or do not match, numeric values that are greater than or less than those in a related field, and dates that are not equal.
Overview
The purpose of the Table to Table Attribute check is to identify attribute values that meet a relationship you define to values in another data source. This can include a comparison of values stored in a feature class to those stored in a stand-alone table, values stored in a feature class to those stored in another feature class, or values stored in a stand-alone table to those stored in another stand-alone table. Features or rows from the input data source are returned as errors when attribute values match the user-defined relationship.
Industry scenarios
The following are scenarios in which you can use this check:
- In address management, the names of road centerline features should match those stored in a master street list.
- In tax parcel management, the legal start date of a parcel feature should match the legal date a plan or record of survey was recorded.
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 | No | Yes | |
Syntax
| Parameter | Required | Description | Workflow |
|---|---|---|---|
Subtype | No | The subtype that the rule is applied to if the dataset has subtypes. | Validation |
Attribute | No | A query that identifies the features to which the rule is applied. | Validation |
Features/Rows to Compare | Yes | Input features or rows are returned as errors based on their relationship to the features or rows from this data source. Valid inputs are point, polyline, polygon, and stand-alone table data sources. | Validation |
Attribute Relationship | Yes | The attribute value comparison between features or rows from the input data source and the data source of the Features/Rows to Compare parameter. | Validation |
Invert Relationship | No | After the relationship is evaluated, this option determines if the result should be used as is or inverted. For example, this option can be used to identify attribute values that do not match values from the data source of the Features/Rows to Compare parameter.
| 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 | 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 |
Notes
Keep the following in mind when using the check:
- Comparisons defined in the Attribute Relationship parameter that include only the is not equal to operator must use the Invert Relationship parameter and is equal to operator instead. For example, use the following configuration to identify attribute values in the input data source that do not exist in the data source of the Features/Rows to Compare parameter:
Parameter Input Attribute Relationship
<Input.FieldToCompare> is equal to <Features/RowsToCompare.FieldToCompare>
Invert Relationship
Checked
- This check supports comparison of values stored in text, numeric, and date field types. It also supports the comparison of values in text fields with those stored in GUID (globally unique identifier), Esri GlobalID, and ObjectID field types.
- Only input features with a validation status of 2 (No calculation required, validation required, no error), 3 (No calculation required, validation required, has error(s)), 6 (Calculation required, validation required, no error) or 7 (Calculation required, validation required, has error(s)) are considered during rule evaluation. The validation status of features or rows from the data source in the Features/Rows to Compare parameter are not considered during rule evaluation.
- Include the data source for the Features to Compare parameter when sharing web layers with the Validation capability enabled.