Skip To Content

Event on Event

Mit der Data Reviewer-Lizenz verfügbar.

Summary

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

Overview

The purpose of the Event on Event check is to identify invalid values in a single event feature and to identify invalid values in relation to two or more event features. It is used to help answer questions such as: Should there be event coverage at this location given these other events' values?

Industry scenarios

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

Syntax

Parameter Required DescriptionWorkflows

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 Vorwärts to define route field settings and to apply filtering to specific features in the feature layer.

Reviewer rules

Overlaying Event Layers

Yes

The events that are overlaid and evaluated by the rule.

Valid inputs for this rule type are polyline feature layers. Click the Forward button Vorwärts to define event field settings and to apply filtering to specific features in the feature layer.

Reviewer rules

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.

Reviewer rules

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 do not overlay another event.

  • Unchecked—The result of the validation will not be inverted. This is the default.
  • Checked—The result of the validation will be inverted.

Reviewer rules

Title

No

A unique title or name for the rule.

This information is used to support data quality requirement traceability, automated reporting, and corrective workflows.

Reviewer rules

Notes

No

Descriptive text of the error condition when noncompliant features are found.

This information is used to provide guidance to facilitate corrective workflows.

Reviewer rules

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.

Reviewer rules

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.

Reviewer rules

Input layer settings

ParameterRequiredDescriptionWorkflows

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.

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

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

Reviewer rules

Fields to Compare

Yes

The fields from the input event layer used in defining the rule's search goal.

Reviewer rules

Notes

  • Validation of line events is supported.
  • A route identifier field (numeric data type) is required for all route and event layers.
  • The Input Route Layers parameter must be m-enabled.
  • 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.

  • When configuring filter parameters, care should be taken when using database-specific SQL functions that differ from those supported in your production environment. For more information, see SQL reference for query expressions used in ArcGIS.

Verwandte Themen