Available with Data Reviewer license.
Summary
The Feature on Feature check finds features from the same or two different feature layers that share a spatial relationship and returns them as results.
Overview
The purpose of the Feature on Feature check is to find features that spatially relate to each other, such as a road on a land feature or a lake surrounded by grassland. Features from the same feature class can also overlap one another and share common attribute values.
When configured as a constraint rule, an error notification is returned when a feature that meets the conditions defined in the parameters of the rule is created or modified.
When configured as a validation rule, an error is created for each feature that meets the conditions defined in the parameters of the rule.
Industry scenarios
Keep the following in mind when using the check:
- In parcel management, the Feature on Feature check ensures that lot units within tax parcels do not overlap each other.
- In address management, road centerline features that contain overlaps or gaps in address ranges can impact the accuracy of locators used in geocoding.
- In water utility management, features connected with different values on key attributes are a common problem. For example, errors may occur when a valve is connected to a pipe but the diameters of the pipes are different, such as a 12-inch diameter valve that connects to two 8-inch diameter water mains.
- In electrical utility management, for proper network analysis, features that are connected must be located on the endpoints of another feature. For example, analysis errors may occur when a switch feature does not split the primary conductor line that it is connected to.
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 | Yes |
Yes | Yes | Yes | |
Syntax
| Parameter | Required | Description | Workflow |
|---|---|---|---|
| Input Feature Layers | Yes | The input feature layers evaluated by the rule. Valid inputs are point, polyline, and polygon features. | Validation (map rules) |
Subtype | No | If the dataset has subtypes, specify the subtype to which the rule will be applied. | Constraint |
Validation | |||
Attribute | No | A query that identifies the features to which the rule is applied. | Validation |
| Features to Compare | Yes | Input features are returned as errors based on their relationship to the features from this data source. Valid inputs are point, polyline, and polygon features. | Constraint |
Validation | |||
Features to Compare Filter | No | A query that identifies the features to include in the rule. | Validation |
| Spatial Relationship | Yes | The spatial relationship to be evaluated.
| Constraint |
Validation | |||
| Search Distance | No | A buffer distance used in determining the spatial relationship. This parameter is only valid if the Spatial Relationship parameter is set to Intersects. | Constraint |
Validation | |||
Attribute Relationship | No | After the spatial relationship is evaluated, this option enables the comparison of attribute values to be included in the validation. For example, this option can be used to identify features that intersect and share a common attribute value. | 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 features that do not intersect or are not within a defined distance of another feature.
| Constraint |
Validation | |||
Triggers | Yes | The editing events that trigger the rule to take effect.
| Constraint |
| Title/Name | Yes | A unique title or name for the rule. This information is used to support data quality requirement traceability, automated reporting, and corrective workflows. | Constraint |
Validation | |||
| Notes/Description | No | Descriptive text of the error condition when noncompliant features are found. This information is used to provide guidance to facilitate corrective workflows. | Constraint |
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. | Constraint |
Validation |
Notes
Keep the following in mind when using the check:
- The data sources of the input and Features to Compare parameter must share a common datum.
- The data sources of the input and Features to Compare parameter must share a common datum.
- When this check is authored as an attribute (constraint) rule, support for geographic coordinate system-based datasets is limited to those using Web Mercator (WKID 3857) or WGS 84 (WKID 4326).
- The following conditions apply when this check is authored as an attribute (validation) rule:
- 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 from the data source in the Features to Compare parameter are not considered during rule evaluation.
- The Attribute and Features to Compare Filter parameters are limited to comparison (=, <>, >, <, >=, <=) and logical (AND/OR, IN/NOT IN, LIKE/NOT LIKE, IS NULL) operators.
- Include the data source for the Features to Compare parameter when sharing web layers with the Validation capability enabled.
- The following conditions apply when this check is authored as a map-based rule:
- Verify that filter parameters using database-specific SQL functions are the same as those supported in your production environment.
- When authoring a validation rule for multiple input feature layers, only fields that are common (matching name and data type) across all layers can be used in the Attribute Relationship parameter.