Event on Event—ArcGIS Pro

Summary

The Event on Event check finds linear referenced events that overlay other events based on a defined relationship. Optionally, you can also find events not in the specified relationship.

Overview

The Event on Event check identifies invalid overlay combinations with regard to two or more event features. It can help determine whether a location requires event coverage given other events' values.

Industry scenarios

The following are scenarios in which you can use this check:

In roadway management, event features must be compliant with highway performance monitoring system (HPMS) guidelines.
In roadway management, a speed limit event representing a 55 mph zone cannot overlay a local road section or an event representing the ramp section of a route.
In pipeline management, the protective coating must be appropriate for the material type, pressure, and diameter of the pipeline.

Supported workflows

ArcGIS Data Reviewer checks support multiple methods for implementing automated review of your data. The following table identifies the supported implementation methods for this check:


Validation			Constraint
Reviewer batch job	Reviewer map rule	Attribute (validation) rule	No
No	Yes	Yes	No

Syntax


Parameter	Required	Description	Workflow
Input Route Layers	Yes	The input feature layers to which the events are referenced. Valid inputs for this rule type are m-enabled polyline feature layers. Click the Forward button to define route field settings and to apply filtering to specific features in the feature layer.	Validation (map rules)
Route Identifier	Yes	The name of the field that contains values used to associate events to routes.	Validation (attribute rules)
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 (attribute rules)
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 (attribute rules)
Overlay Events	Yes	The events that are overlaid and evaluated by the rule. Valid inputs for this rule type are polyline feature layers. Map rules: Click the Forward button to define event field settings and to apply filtering to specific features in the feature layer.	Validation
Search Goal	Yes	The query expression to be applied to overlay events. Each event whose values match those defined in the SQL query is returned as a Reviewer result.	Validation
Invert Relationship	No	After the search goal is evaluated, this parameter determines whether the result should be used as-is or inverted. For example, this parameter can be used to identify events that don't match the Search Goal query expression. Unchecked—The result of the validation will not be inverted. This is the default. Checked—The result of the validation will be inverted.	Validation
Title/Name	No	A unique title or name for the rule. This information is used to support data quality requirement traceability, automated reporting, and corrective workflows.	Validation
Notes/Description	No	Descriptive text of the error condition when noncompliant features are found. This information is used to provide guidance to facilitate corrective workflows.	Validation
Severity	No	Severity of the error created when noncompliant features are 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	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

Input layer settings (map rules only)


Parameter	Required	Description	Workflow
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 (map rules)
From Measure	Yes	The name of the field that contains the starting measure value for a linear event feature. The field must be a numeric data type.	Validation (map rules)
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 (map rules)
Fields to Compare	Yes	The fields from the input event layer used in defining the rule's search goal.	Validation (map rules)

Notes

Keep the following in mind when using the check:

Validation of line events that are registered with the location referencing system (LRS) of either ArcGIS Roads and Highways or ArcGIS Pipeline Referencing are supported.
Route features must be m-enabled and registered with the location referencing system (LRS) of either Roads and Highways or Pipeline Referencing.
A route identifier field (numeric data type) is required for all route and event layers.
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.
Events that do not have an associated route (orphaned events) are not evaluated by this check. Orphan events are event features that do not have a corresponding route feature (as identified by the event’s route identifier attribute value).
The Invalid Events check is used to find orphaned events that require correction.
Events that contain invalid measure values are not evaluated by this check. Invalid event values are event measure values that are greater than, less than, or within a gap in a related route’s measure values.
The Invalid Events check is used to find events that contain invalid measure values.
The following conditions apply when this check is authored as an attribute (validation) rule:
- 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 validation status of features from the data source in the Overlay Events parameter are not considered during rule evaluation.
- Include the data sources for the Overlay Events parameter when sharing web layers with the Validation capability enabled.
When this check is authored as a map-based rule, verify that filter parameters using database-specific SQL functions are the same as from those supported in your production environment.