Evaluating the intersection count (Production Mapping)

The intersection count is the number of times polylines from one feature class intersect other polylines or polygons in either the same or another feature class. For example, two road features are permitted to intersect once, but not more than once.

The Evaluate Intersection Count check searches for features from two feature classes whose intersections fall within a specified range. The check can be run on an entire feature class, a subtype, or a set of features selected using a SQL query. Features with a number of intersections that match the specified threshold are returned as results.

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.

Steps:

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 Spatial Parameter Evaluation Checks, then click Evaluate Intersection Count Check.

   The Evaluate Intersection Count Check Properties dialog box appears.
4. Click the Feature Class/Subtype drop-down arrow in the Feature Class 1 area and choose the 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 in the Feature Class 2 area.

8. Click the Operation drop-down arrow and choose the operation to use.
   • Less than—The number of intersections is less than the value specified. For example, if the value is 10, features from feature class 1 and feature class 2 that intersect 9 through 0 times are returned as results.
   • Less than or equal—The number of intersections is equal to or less than the value specified. For example, if the value is 10, features from feature class 1 and feature class 2 that intersect 10 through 0 times are returned as results.
   • Greater than—The number of intersections is greater than the value specified. For example, if the value is 10, features from feature class 1 and feature class 2 that intersect 11 or more times are returned as results.
   • Greater than or equal—The number of intersections is equal to or greater than the value specified. For example, if the value is 12, features from feature class 1 and feature class 2 that intersect 12 or more times are returned as results.
   • Not equal to—The number of intersections is not equal to the value specified. For example, if the value is 10, features from feature class 1 and feature class 2 that intersect 8, 12, or any other number of times that is not equal to 10 are returned as results.
   • Equal to—The number of intersections is equal to the value specified. For example, if the value is 10, features from feature class 1 and feature class 2 that intersect 10 times are returned as results.
   • In Between - Including Bounds—The number of intersections is between or equal to the values specified in the Lower Bound (minimum) and Upper Bound (maximum) text boxes. For example, if the lower bound is 1 and the upper bound is 10, features from feature class 1 and feature class 2 that intersect 1 through 10 times are returned as results.
   • In Between - Not Including Bounds—The number of intersections is between the values specified in the Lower Bound (minimum) and Upper Bound (maximum) text boxes. For example, if the lower bound is 1 and the upper bound is 10, features from feature class 1 and feature class 2 that intersect 2 through 9 times are returned as results.
   • Not (In Between - Including Bounds)—The number of intersections is not equal to or between the values specified in the Lower Bound (minimum) and Upper Bound (maximum) text boxes. For example, if the lower bound is 1 and the upper bound is 10, features from feature class 1 and feature class 2 that intersect 0 or 11 or greater times are returned as results.
   • Not (In Between - Not Including Bounds)—The number of intersections is equal to or not between the values specified in the Lower Bound (minimum) and Upper Bound (maximum) text boxes. For example, if the lower bound is 1 and the upper bound is 10, features from feature class 1 and feature class 2 that intersect 1 or less or 10 or greater times are returned as results.

   The operation text box appears. If you choose an operation with bounding values, the Lower Bound and Upper Bound text boxes appear.

9. Type the number of units to use with the operation.

   If you choose an operation with bounding values, you must indicate two values: one each for the minimum and maximum ranges of the tolerance.

10. If necessary, type descriptive text for the check results in the Notes text box in the Reviewer Remarks area.
11. 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.

12. Click OK.
13. Click the Run Data Check button on the Data Reviewer toolbar.

    The Features to Validate dialog box appears.
14. 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.
15. 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.

16. 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.

17. 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.
18. Click OK.