Finding invalid events

Disponible avec une licence Data Reviewer.

The Invalid Event Check finds linear referenced events that do not have an associated route (orphaned events) or contain invalid measure values. The check also identifies gaps or overlaps between events, within the same route or across multiple routes. Event features that contain invalid measure values impact the results of your analysis. The following two examples illustrate those impacts:

• In roadway management, a speed limit event representing 55 mph needs to have the same measure value as the related route feature.

  In roadway management, event features that contain invalid measure values adversely affect length calculations (for example, United States Department of Transportation mileage reports).

• In pipeline management, recording of the protective coating applied to underground assets ensures accurate reporting on features that cannot be directly observed during inspections.

  To avoid pipeline corrosion, recording the measure of protective coating applied to underground assets ensures accuracy of reporting and safety of underground features.

Check notes

• Validation of point and line events is supported.
• The Invalid Event Check supports validation of events stored in the following:
  • Line feature classes
  • Point feature classes
• A From Route ID field (numeric data type) is required for all events.
• The event's related Route Source feature class must be M-enabled.
• Optionally, you can define a Tolerance value that will be used when finding events which have invalid measures or represent a gap or overlap on other events. This value cannot be less than the M Tolerance value of the Route Source.
• Events associated with non-monotonic route features are not evaluated when using the Find invalid measures search criteria. Use the Monotonicity check to find non-monotonic routes, measures with values that are either continuous or not strictly increasing or decreasing in value, that require correction. For more information, see Evaluating monotonicity of measure and elevation values.
• Events that do not have an associated route (orphaned events) are not evaluated by either the Find overlaps or Find gaps search criteria. Orphan events are those features which do not have a corresponding route feature (as identified by the event's RouteID attribute value).
• Events that contain invalid measure values are not evaluated by either the Find overlaps or Find Gaps search criteria. Invalid event values are those measure values which are greater than, less than, or within a gap in a related linear feature's measure values.

  The Find invalid Measures search criteria finds events with invalid measure values and is automatically enabled with either the Find Overlaps or Find Gaps search criteria.

• The following scenarios are not currently supported when using the Find Overlaps or Find Gaps search criteria.
  • Events associated with multipart route features that contain gaps in measure values between parts.
  • Events associated with multiple route features during the same time period.
• When using the Find Gaps search goal, the Full Database option (Batch Validate tool) should be enabled to ensure that all gap error scenarios are detected.

Configuration steps

To use the Invalid Event Check option, complete the following steps:

1. Démarrez 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, expand the Event Checks group, and choose Invalid Event Check.

   The Invalid Event Check Properties dialog box appears.

   

4. In the Event Source section, click the Feature Class drop-down arrow and choose the feature class on which to run the check.

   Remarque :

   Only line and point feature classes are displayed.

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, click SQL to construct an SQL query.
7. In the Event Properties section, configure the required parameters.
   1. Route ID—A required numeric string data type
   2. From Measure—A required numeric string data type
   3. To Measure—A required numeric string data type
8. In the Route Source section, choose Feature Class to compare against the measures of event source data.
9. Validate that the appropriate field has been preselected in the Route ID drop-down menu.
10. To run the check on specific features in the feature class, click SQL to construct an SQL query.
11. Check each Search Goal option that applies.
    • Find orphans
    • Find invalid measures
    • Find overlaps
    • Find gaps
12. Optionally, define the Tolerance value that will be used to determine if an event has invalid measures or represents a gap or overlap on other events.

    Remarque :

    The Tolerance default value will be the same as the M-tolerance value from the Route Source feature class.

    The event's minimum and maximum measures that exceed the defined tolerance value will be returned as an error in the Reviewer Results table.

13. If necessary, type descriptive text about the check's results in the Notes text box in the Reviewer Remarks section.
14. 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 section.

    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.

15. Cliquez sur OK.
16. Click the Run Data Check button on the Data Reviewer toolbar.

    The Features to Validate dialog box appears.

    

17. Choose an option in the Features to Validate section.

    • Selection Sets—Runs the check on the features that are currently selected in the map.

    • Current Extent—Runs the check on the features of the current map extent, which is controlled by the map scale.

    • Definition Query—Runs the check on the features that are displayed based on the definition queries that have been created for the feature class.

    • Full Database—Runs the check on all the features in the feature class.

18. To run the check only on features that have been edited in a versioned workspace, check the Changed Features Only check box.

    Remarque :

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

19. Click OK.

    The check is run on the extent specified in the Features to Validate dialog box. When the check finishes, a Check Results dialog box appears.

20. 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.
21. Cliquez sur OK.