Searching for different z-values at intersections

Available with Data Reviewer license.

When features from two different feature classes intersect in the x,y plane, it is possible for them to have two different z-values. For example, a contour and a bridge can have two different elevations since the contour may measure the elevation on the ground and the bridge can be significantly above the ground, which can be valid. However, a road feature intersecting the bridge should have the same z-value at the intersection; they cannot have different z-values and still have a valid intersection point.

Note:

A vertical coordinate system must be defined for the feature classes you want to use with this check.

The Different Z at Intersection check searches for intersecting polyline features with z-value differences that are larger than a specified tolerance at the intersection points. The check can be run on an entire feature class, a subtype, or a set of features selected using a SQL query. Two-dimensional multipoint geometries at the locations of feature crossings or intersections are returned for all errant features.

Once you have defined the criteria for the check, you can configure the notes and a severity rating. The notes allow you to provide a more specific description for the feature that has been written to the Reviewer table and are copied to the Notes field in the Reviewer table. The severity rating allows you to indicate how important the results from a check are in terms of your quality assurance/quality-control processes. The lower the number, the greater the priority the check's results have.

1. Start ArcMap.
2. On the main menu, click Customize > Toolbars > Data Reviewer.
3. Click the Select Data Check drop-down arrow on the Data Reviewer toolbar, click the plus sign (+) next to Z Value Checks, then click Different Z at Intersection Check.

   The Different Z at Intersection Check Properties dialog box appears.

   

4. Click the Feature Class/Subtype drop-down arrow in the Feature Class 1 area and choose a feature class and subtype on which to run the check.
5. To run the check on the entire feature class and save this setting, check the Always Run on Full Database check box.
6. To run the check on specific features in a feature class, click SQL to construct an SQL query.
7. Repeat steps 4–6 in the Feature Class 2 area.

   Note:

   If you want to run the check using selected features in feature class 1 and all the features in feature class 2, check the Always Run on Full Database check box.

8. Click the Type of Intersection drop-down arrow and choose the type of intersection to be used with the check.
   • Crosses—The interior of a feature from feature class 1 comes into contact with the interior or boundary (if a polygon) of a feature from feature class 2 at a point.
   • Touches—A part of the feature from feature class 1 comes into contact with the boundary of a feature from feature class 2. The interiors of the features do not intersect.
9. Type the minimum number of units for the elevation difference tolerance in the Minimum text box.
10. Type the maximum number of units for the elevation difference tolerance in the Maximum text box.
11. Click the Units drop-down arrow and choose the units for the tolerance.

    You can choose from both page units and map units. Page units include points, centimeters, inches, and millimeters. Map units include feet, yards, miles, nautical miles, meters, kilometers, decimal degrees, and decimeters.

12. If necessary, type descriptive text for the check results in the Notes text box in the Reviewer Remarks area.
13. If necessary, click the Severity drop-down arrow and choose a value that indicates the priority of the check's results in the Reviewer Remarks area.

    The severity indicates the importance of the check result. The values range from 1 to 5, with 1 being the highest priority and 5 being the lowest.

14. Click OK.
15. Click the Run Data Check button on the Data Reviewer toolbar.

    The Features to Validate dialog box appears.

    

16. Choose an option in the Features to Validate area.
    • Selection Set—The check is run on the features that are currently selected in the map.
    • Current Extent—The check is run on the current map extent, which is controlled by the map scale.
    • Definition Query—The check is run on the features that are displayed based on definition queries that have been created for the feature class.
    • Full Database—The check is run on all the features in the feature class.
17. To run the check only on features that have been edited in a versioned workspace, check the Changed Features Only check box.

    Note:

    The Changed Features Only option is available only for a versioned database.

18. Click OK.

    The check is run on the extent specified on the Features to Validate dialog box.

    When the check finishes, a check results dialog box appears.

19. Do one of the following:
    • If you want to browse the results in the Browse Features window, choose the Browse Results option.
    • If you have started a Reviewer session and want to record the results in the Reviewer table, choose the Write to Reviewer Table option.
20. Click OK.