Available with ArcGIS Pro Standard and Data Reviewer licenses.
Summary
The Adjacent Vertex Elevation Change check searches for polyline and polygon features with vertices that have elevation differences (z-values) greater than a specified tolerance. The tolerance value helps identify significant gaps between feature elevations.
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 attribute rule | Constraint attribute rule | |
|---|---|---|
Yes (ArcGIS Pro 2.9 and ArcGIS Enterprise 10.9.1 or later) | No | |
Overview
When performing quality control checks on your database, you can search for features with significant differences in elevation represented by the z-value. For example, within a contour feature class, the z-value for a given contour should be constant for all vertices. Occasionally, there are outlying vertices with different z-values.
The Adjacent Vertex Elevation Change check returns vertices for polylines or polygon features with an elevation (Z) change greater than the specified tolerance. The tolerance value helps identify significant gaps between feature elevations. You can run the check on an entire feature class, subtype, or set of features selected using a SQL query. The features that fall outside of the specified tolerance, or have a difference that is greater than the value specified, are returned as errors. These features can then be written to the Reviewer table for further inspection and correction.
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 |
Elevation Difference Tolerance | Yes | The minimum value allowed for elevations between vertices. The value must be greater than the geodatabase Z tolerance. Map units include feet, U.S. feet and meters, kilometers, decimal degrees, and decimeters. | 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 | 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:
- This check supports z-enabled polyline and polygon features.
- A vertical coordinate system must be defined for the feature classes you want to use with this check.
- The Validation Status attribute value of input features is ignored during evaluation. For example, input features with a validation status of 0 (No calculation required, no validation required, no error), 1 (No calculation required, no validation required, has error(s)),4 (Calculation required, no validation required, no error), or 5 (Calculation required, no validation required, has error(s)) are still included during rule evaluation.
- The Attribute filter parameter is limited to comparison (=, <>, >, <, >=, and <=) and logical (AND/OR, IN/NOT IN, LIKE/NOT LIKE, and IS NULL) operators.
- The Attribute filter parameter does not support the following field types: Big Integer, Date Only, Time Only, and Timestamp Offset. If selected, the row header is marked in red and does not allow the rule to be saved.