Find Event Gaps

Available with ArcGIS Pro Standard and Data Reviewer licenses.

Summary

The Find Event Gaps  check finds linear-referenced events with gaps between events of the same category in the same route or across multiple routes. For example, it will find two speed limit events registered on the same route that do not cover the entire length of the route, creating a gap.

Note:

The Find Event Gaps check must be authored in the route's network feature class.

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		Constraint
Reviewer batch job	Attribute (validation) rule	No
Yes	Yes (ArcGIS Pro 3.1 and ArcGIS Enterprise11.1 or later)

Overview

The Find Event Gaps check finds linear-referenced events that have gaps on the same route or across multiple routes.

Industry scenarios

This check can be used in the following scenarios:

• In roadway management, a speed limit event representing 55 miles per hour (mph) needs to cover the entire measure of its corresponding route feature.
• To avoid pipeline corrosion in pipeline management, recording the measure of protective coating applied to underground assets without gaps ensures the accuracy of reporting and safety of underground features.

Example

The following image illustrates linear error events in red that represent gaps between other events in the same route and across multiple routes:

Syntax

Parameter	Required	Explanation	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
Route Properties/Route Identifier	Yes	The name of the field that contains values used to associate events to routes. The field must be a numeric data type.	Validation
Route Properties/Route From Date	Yes	The name of the field that contains values that define the starting date for a route. The field must be a date data type.	Validation
Route Properties/Route To Date	Yes	The name of the field that contains values that define the ending date for a route. The field must be a date data type.	Validation
Event Properties/Event Source	Yes	The line event registered with the route network to be validated for gaps.	Validation
Event Properties/Route Identifier	Yes	The name of the field that contains values used to associate events to routes. The field must be a numeric data type.	Validation
Event Properties/From Measure	Yes	The name of the field that contains the starting measure value for a point or linear event feature. The field must be a numeric data type.	Validation
Event Properties/To Measure	Yes	The name of the field that contains the ending measure value for a linear event feature. The field must be a numeric data type.	Validation
Event Properties/Event From Date	Yes	The name of the field that contains values that define the starting date for a point or linear event feature. The field must be a date data type.	Validation
Event Properties/Event To Date	Yes	The name of the field that contains values that define the ending date for a point or linear event feature. The field must be a date data type.	Validation
Measure Tolerance	No	An optional value used when finding event gaps based on a specific tolerance value. The linear referencing system m-tolerance is used by default.	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 you define of the error when a noncompliant feature is found. This information is used to provide guidance to facilitate corrective workflows.	Validation
Severity	No	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:

• The check must be authored in the route's network feature class.
• This check supports validation of events stored in line feature classes.
• Optionally, you can define a Measure Tolerance value to use when finding events that have invalid measures. This value cannot be less than the m-tolerance value of the input route feature.

  Learn more about properties of a spatial reference

• This check supports validation of events that are stored in an enterprise geodatabase and registered with the linear referencing system (LRS) of either ArcGIS Roads and Highways or ArcGIS Pipeline Referencing.
• Route features must be m-enabled and registered with the LRS of either Roads and Highways or Pipeline Referencing.
• A route identifier field (numeric data type) is required for all route and event features.
• An attribute index on the route identifier field speeds up the dynamic segmentation process.
• Events associated with nonmonotonic route features are not evaluated by this check. Nonmonotonic routes are routes that contain measure values that are either continuous or do not strictly increase or decrease in value.

  The Monotonicity check is used to find nonmonotonic routes that require correction.

• Only input features with a validation status of 2 (No calculation required, validation required, no error), 3 (No calculation required, validation required, has error(s)), 6 (Calculation required, validation required, no error) or 7 (Calculation required, validation required, has error(s)) are considered during rule evaluation.
• The Attribute filter parameter is limited to comparison (=, <>, >, <, >=, <=) and logical (AND/OR, IN/NOT IN, LIKE/NOT LIKE, IS NULL) operators.
• Event checks are not supported in composite rule configurations.