Evaluating segment, part/path, and polyline lengths

Available with Data Reviewer license.

Polyline features can be analyzed as whole features or in terms of their components, such as segments and parts or paths. Paths are specific to polylines and rings are specific to polygons. The Evaluate Polyline Length check evaluates the length of any of the polyline components to make sure it is within allowed parameters. Any features that meet the conditions specified in the check are returned as results. For example, you can find street centerlines with parts that are too small relative to the size of the feature. In this case, street centerlines with any part less than one meter can be returned as results.

The check can be run on an entire feature class, a subtype, or a set of features selected using a SQL query.

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 Polyline Checks, then click Evaluate Polyline Length Check.

   The Evaluate Polyline Length Check Properties dialog box appears.

   

4. If necessary, type a unique name for the check in the Check Title text box.

   Note:

   The check title can be used to describe the conditions you are looking for with the check. This is useful when you have multiple instances of the same check to validate the same feature classes or tables but with different validation parameters.

5. Click the Feature Class/Subtype drop-down arrow to choose the feature class and subtype on which to run the check.
6. To run the check on the entire feature class and save this setting, check the Always Run on Full Database check box.
7. To run the check on specific features in a feature class, click SQL to construct an SQL query.
8. Click an option for the polyline feature in the Type area.
   • Polyline—An entire linear feature
   • Part/Path—A part of a multipart line feature or a single path on a line feature
   • Segment—A section of a line feature that is connected by two adjacent vertices on a line feature
9. Click the drop-down arrow in the Length area and choose the unit of measurement to use with the feature length.
10. Click the Operation drop-down arrow and choose an operation to use.
    • Less than—The line length is less than the number of units specified. For example, if the value is 10, lines with length values of 9 through 0 are returned as results.
    • Less than or equal—The line length is equal to or less than the number of units specified. For example, if the value is 10, lines with length values of 10 through 0 are returned as results.
    • Greater than—The line length is greater than the number of units specified. For example, if the value is 10, lines with a length value of 11 or more are returned as results.
    • Greater than or equal—The line length is equal to or greater than the number of units specified. For example, if the value is 12, lines with a length value of 12 or more are returned as results.
    • Not equal to—The line length is not equal to the number of units specified. For example, if the value is 10, lines with a length value of 8, 12, or any other value that is not equal to 10 are returned as results.
    • Equal to—The line length is equal to the number of units specified. For example, if the value is 10, lines with a length value of 10 are returned as results.
    • In Between - Including Bounds—The line length is between or equal to the number of units 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, lines with length values of 1 through 10 are returned as results.
    • In Between - Not Including Bounds—The line length is between the number of units 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, lines with length values of 2 through 9 are returned as results.
    • Not (In Between - Including Bounds)—The line length is not equal to or between the number of units 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, lines with length values of 0 or less or 11 or greater are returned as results.
    • Not (In Between - Not Including Bounds)—The line length is equal to or not between the number of units 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, lines with length values of 1 or less or 10 or greater are returned as results.

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

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

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.