Event behavior for route calibration
Available with the Linear Referencing license.
When route calibration occurs, events are impacted depending on the configured event behavior for the event layer.
Note:
Events are not updated until you run the Apply Event Behaviors tool after route edits. If conflict prevention is enabled, you are prompted to run the Apply Event Behaviors tool before posting to the default version.
When you check the Recalibrate route downstream option during route editing, the tool applies the event behavior for route calibration to downstream sections. You can review configured event behaviors by viewing the LRS event properties.
Adding, editing, or deleting one or more calibration points can calibrate a route. Specifying downstream recalibration in linear referencing system (LRS) route editing tools can also calibrate a route.
You can change calibration points using the following methods:
Use one of the calibration point editing tools in the Route Editing group on the Linear Referencing tab.
Add a calibration point using the Create Features pane.
Check the Recalibrate route downstream check box in LRS route editing tools.
Run the Append Calibration Points tool.
The following sections describe route calibration and the corresponding event behaviors.
Route calibration scenario
A route can be calibrated at any location on the route.
Upstream and downstream sections
Route editing impacts upstream and downstream sections differently.
The following diagram shows the upstream and downstream sections for a route calibration scenario without downstream recalibration:
The following table details how the calibration editing activity impacts upstream and downstream events according to the configured event behavior:
| Behavior | Events upstream of calibration point edit | Events crossing calibration point edit | Events downstream of calibration point edit |
|---|---|---|---|
| Stay Put | Measures on an event update to maintain the geographic location if the event crosses the section between the edited calibration point and the nearest upstream calibration point. | Measures on an event update to maintain the geographic location of the event. | Measures on an event update to maintain the geographic location of the event. If the event crosses the section between the edited calibration point and the nearest upstream calibration point, measures update due to calibration point values changing. |
| Move | The event polyline shape updates to the new location of measures on the route if the event crosses the section between the edited calibration point and the nearest upstream calibration point. | The event polyline shape moves to the new measure locations on the route. | If the event crosses a route section whose calibration point measures change, the event polyline shape moves to the new measure locations. |
| Retire | The event retires if the event crosses the section between the edited calibration point and the nearest upstream calibration point. | The event retires; line events crossing the edited calibration point are not split. | The event retires if the event crosses a section of the route with a calibration point with measures updated. |
Note:
The network can contain events that span routes in the line network. The behaviors apply in the same manner.
Because the LRS is time aware, edit activities, such as calibrating or retiring a route, time slice routes and events.
If you calibrate a route on the same day that you create it and set the calibrate event behavior to Retire, the events are deleted instead of retired.
Route calibration results
In this example, Route 1 is active from 1/1/2000. The calibration is set to occur on 1/1/2005 where a calibration point at the existing measure 10 is changed to 15, resulting in recalibrated measures downstream.
The following graphics and tables demonstrate the route information before and after calibration.
Route before calibration
The following diagram shows the route before calibration:
The following table provides details about the route before the calibration:
| Route Name | From Date | To Date | From Measure | To Measure |
|---|---|---|---|---|
| Route1 | 1/1/2000 | <Null> | 0 | 20 |
| Route ID | From Date | To Date | From Measure | To Measure |
|---|---|---|---|---|
| Route1 | 1/1/2000 | <Null> | 0 | 20 |
Route after calibration
The following diagram shows the route after the calibration:
In this example, the Recalibrate route downstream check box is checked, so the recalibrated route section starts at the nearest calibration point upstream of the edited calibration point and continues to the end of the route. If the Recalibrate route downstream check box is not checked, the recalibrated route section is between the nearest upstream and downstream calibration points of the edited calibration point.
The following table provides details about the route after the calibration:
| Route Name | From Date | To Date | From Measure | To Measure |
|---|---|---|---|---|
| Route1 | 1/1/2000 | 1/1/2005 | 0 | 20 |
| Route1 | 1/1/2005 | <Null> | 0 | 25 |
| Route ID | From Date | To Date | From Measure | To Measure |
|---|---|---|---|---|
| Route1 | 1/1/2000 | 1/1/2005 | 0 | 20 |
| Route1 | 1/1/2005 | <Null> | 0 | 25 |
Events before route calibration
There are three events on Route 1 and all of them have a start date of 1/1/2000. The following diagram shows the route and events before the calibration:
The following table provides details about the events before the calibration:
| Event | Route Name | From Date | To Date | From Measure | To Measure |
|---|---|---|---|---|---|
| Event1 | Route1 | 1/1/2000 | <Null> | 0 | 7 |
| Event2 | Route1 | 1/1/2000 | <Null> | 7 | 15 |
| Event3 | Route1 | 1/1/2000 | <Null> | 15 | 20 |
| Event | Route ID | From Date | To Date | From Measure | To Measure |
|---|---|---|---|---|---|
| Event1 | Route1 | 1/1/2000 | <Null> | 0 | 7 |
| Event2 | Route1 | 1/1/2000 | <Null> | 7 | 15 |
| Event3 | Route1 | 1/1/2000 | <Null> | 15 | 20 |
The following sections detail how event behavior rules are enforced after running the Apply Event Behaviors tool under this route calibration scenario.
Stay Put event behavior
The Stay Put behavior maintains the geographic location of the event, but the measures can change.
The route calibration described above has the following effects:
Event 1 is retired on the date of calibration because it is partially within the recalibrated route section. A new event is created on the post-calibration route with the calibration date as the start date. The start measure changes to 0 and the end measure changes to 9 to accommodate the new measures of Route 1.
Event 2 is retired on the date of calibration because it is completely within the recalibrated route section. A new event is created on the post-calibration route with the calibration date as the starting date. The start measure value changes to 9 and the end measure value changes to 20 to accommodate the new measures of Route 1.
Event 3 is retired on the date of calibration because it is completely within the recalibrated route section. A new event is created on the post-calibration route with the calibration date as the starting date. The start measure value changes to 20 and the end measure value changes to 25 to accommodate the new measures of Route 1.
The following diagram shows the route and events after the calibration:
Note:
The retired event is not drawn in the previous diagram.
The following table provides details about the events after the calibration when Stay Put is the configured event behavior:
| Event | Route Name | From Date | To Date | From Measure | To Measure | Location Error |
|---|---|---|---|---|---|---|
| Event1 | Route1 | 1/1/2000 | 1/1/2005 | 0 | 7 | No Error |
| Event1 | Route1 | 1/1/2005 | <Null> | 0 | 9 | No Error |
| Event2 | Route1 | 1/1/2000 | 1/1/2005 | 7 | 15 | No Error |
| Event2 | Route1 | 1/1/2005 | <Null> | 9 | 20 | No Error |
| Event3 | Route1 | 1/1/2000 | 1/1/2005 | 15 | 20 | No Error |
| Event3 | Route1 | 1/1/2005 | <Null> | 20 | 25 | No Error |
| Event | Route ID | From Date | To Date | From Measure | To Measure | Location Error |
|---|---|---|---|---|---|---|
| Event1 | Route1 | 1/1/2000 | 1/1/2005 | 0 | 7 | No Error |
| Event1 | Route1 | 1/1/2005 | <Null> | 0 | 9 | No Error |
| Event2 | Route1 | 1/1/2000 | 1/1/2005 | 7 | 15 | No Error |
| Event2 | Route1 | 1/1/2005 | <Null> | 9 | 20 | No Error |
| Event3 | Route1 | 1/1/2000 | 1/1/2005 | 15 | 20 | No Error |
| Event3 | Route1 | 1/1/2005 | <Null> | 20 | 25 | No Error |
Move event behavior
The Move behavior maintains the measures of the event, but the geographic location can change.
The route calibration described above has the following effects:
Event 1 is retired on the date of calibration because it is partially within the recalibrated route section. A new event is created on the post-calibration route with the calibration date as the starting date. Because the measures do not change for the Move behavior, the event is slightly shortened on the end to maintain its original start measure value of 0 and end measure value of 7.
Event 2 is retired on the date of calibration because it is completely within the recalibrated route section. A new event is created on the post-calibration route with the calibration date as the starting date. Because the measures do not change for the Move behavior, the event shifts to the left to maintain its original start measure value of 7 and end measure value of 15.
Event 3 is retired on the date of calibration because it is completely within the recalibrated route section. A new event is created on the post-calibration route with the calibration date as the starting date. Because the measures do not change for the Move behavior, the event shifts to the left to maintain its original start measure value of 15 and end measure value of 20.
The following diagram shows the route and events after the calibration:
The following table provides details about the events after the calibration when Move is the configured event behavior:
| Event | Route Name | From Date | To Date | From Measure | To Measure | Location Error |
|---|---|---|---|---|---|---|
| Event1 | Route1 | 1/1/2000 | 1/1/2005 | 0 | 7 | No Error |
| Event1 | Route1 | 1/1/2005 | <Null> | 0 | 7 | No Error |
| Event2 | Route1 | 1/1/2000 | 1/1/2005 | 7 | 15 | No Error |
| Event2 | Route1 | 1/1/2005 | <Null> | 7 | 15 | No Error |
| Event3 | Route1 | 1/1/2000 | 1/1/2005 | 15 | 20 | No Error |
| Event3 | Route1 | 1/1/2005 | <Null> | 15 | 20 | No Error |
| Event | Route ID | From Date | To Date | From Measure | To Measure | Location Error |
|---|---|---|---|---|---|---|
| Event1 | Route1 | 1/1/2000 | 1/1/2005 | 0 | 7 | No Error |
| Event1 | Route1 | 1/1/2005 | <Null> | 0 | 7 | No Error |
| Event2 | Route1 | 1/1/2000 | 1/1/2005 | 7 | 15 | No Error |
| Event2 | Route1 | 1/1/2005 | <Null> | 7 | 15 | No Error |
| Event3 | Route1 | 1/1/2000 | 1/1/2005 | 15 | 20 | No Error |
| Event3 | Route1 | 1/1/2005 | <Null> | 15 | 20 | No Error |
Retire event behavior
The Retire behavior retires all three events in the recalibrated route section.
The route calibration described above has the following effects:
Event 1 is partially within the recalibrated route section, so it is retired on the date of calibration.
Event 2 is completely within the recalibrated route section, so it is retired on the date of calibration.
Event 3 is completely within the recalibrated route section, so it is retired on the date of calibration.
The following diagram shows the route and events after the calibration:
The following table provides details about the events after the calibration when Retire is the configured event behavior:
| Event | Route Name | From Date | To Date | From Measure | To Measure | Location Error |
|---|---|---|---|---|---|---|
| Event1 | Route1 | 1/1/2000 | 1/1/2005 | 0 | 7 | No Error |
| Event2 | Route1 | 1/1/2000 | 1/1/2005 | 7 | 15 | No Error |
| Event3 | Route1 | 1/1/2000 | 1/1/2005 | 15 | 20 | No Error |
| Event | Route ID | From Date | To Date | From Measure | To Measure | Location Error |
|---|---|---|---|---|---|---|
| Event1 | Route1 | 1/1/2000 | 1/1/2005 | 0 | 7 | No Error |
| Event2 | Route1 | 1/1/2000 | 1/1/2005 | 7 | 15 | No Error |
| Event3 | Route1 | 1/1/2000 | 1/1/2005 | 15 | 20 | No Error |
Detailed behavior results on routes in a line network with events that span routes
In this example, four routes on Line A are active from 1/1/2000. Calibration occurs on 1/1/2005 when a new calibration point with a measure value of 31 is added to Route 3 at the existing measure of 28. The Recalibrate route downstream check box is not checked. The following diagrams and tables demonstrate the route information before and after calibration.
Routes before calibration
The following diagram shows the routes before calibration:
The following table provides details about the routes before calibration:
| Route Name | Line Name | Line Order | From Date | To Date | From Measure | To Measure |
|---|---|---|---|---|---|---|
| Route1 | LineA | 100 | 1/1/2000 | <Null> | 0 | 10 |
| Route2 | LineA | 200 | 1/1/2000 | <Null> | 12 | 22 |
| Route3 | LineA | 300 | 1/1/2000 | <Null> | 25 | 35 |
| Route4 | LineA | 400 | 1/1/2000 | <Null> | 38 | 48 |
Routes after calibration
The following diagram shows the routes after calibration:
The following table provides details about the routes after calibration:
| Route Name | Line Name | Line Order | From Date | To Date | From Measure | To Measure |
|---|---|---|---|---|---|---|
| Route1 | LineA | 100 | 1/1/2000 | <Null> | 0 | 10 |
| Route2 | LineA | 200 | 1/1/2000 | <Null> | 12 | 22 |
| Route3 | LineA | 300 | 1/1/2000 | 1/1/2005 | 25 | 35 |
| Route4 | LineA | 300 | 1/1/2005 | <Null> | 25 | 35 |
| Route5 | LineA | 400 | 1/1/2000 | <Null> | 38 | 48 |
Note:
Calibration points affect only the route on which they are added or updated.
Route 3 does not change its end measure because the Recalibrate route downstream check box is not checked.
Events before calibration
There are two spanning events on routes on Line A. The following diagram shows the routes and events before calibration:
The following table provides details about the events before calibration:
| Event ID | From Date | To Date | From Route Name | To Route Name | From Measure | To Measure |
|---|---|---|---|---|---|---|
| Event1 | 1/1/2000 | <Null> | Route1 | Route3 | 0 | 30 |
| Event2 | 1/1/2000 | <Null> | Route3 | Route4 | 30 | 48 |
The following sections describe how event behavior rules are enforced when a route on a line in a line network is calibrated.
Stay Put event behavior
The Stay Put behavior maintains the geographic location of the event, but the measures can change.
The route calibration described above has the following effects:
Event 1 is retired on the date of calibration because it is partially within the recalibrated route section. A new event is created on the post-calibration route with the calibration date as the start date. The start measure changes to 0 on Route 1 and the end measure changes to 33 on Route 3 to accommodate the new measures of Route 3.
Event 2 is retired on the date of calibration because it is partially within the recalibrated route section. A new event is created on the post-calibration route with the calibration date as the start date. The start measure value changes to 33 on Route 3 and the end measure value changes to 48 on Route 4 to accommodate the new measures of Route 3.
The following diagram shows the routes and events after calibration:
Note:
The retired event is not drawn in the preceding image.
The following table provides details about the events after calibration when Stay Put is the configured event behavior:
| Event ID | From Date | To Date | From Route Name | To Route Name | From Measure | To Measure |
|---|---|---|---|---|---|---|
| Event1 | 1/1/2000 | 1/1/2005 | Route1 | Route3 | 0 | 30 |
| Event1 | 1/1/2005 | <Null> | Route1 | Route3 | 0 | 33 |
| Event2 | 1/1/2000 | 1/1/2005 | Route3 | Route4 | 30 | 48 |
| Event2 | 1/1/2005 | <Null> | Route3 | Route4 | 33 | 48 |
Move event behavior
The Move behavior maintains the measures of the event, but the geographic location can change.
The route calibration described above has the following effects:
Event 1 is retired on the date of calibration because it is partially within the recalibrated route section. A new event is created on the post-calibration route with the calibration date as the starting date. Because the measures do not change for the Move behavior, the event is slightly shortened on the end to maintain its original start measure value of 0 on Route 1 and end measure value of 30 on Route 3.
Event 2 is retired on the date of calibration because it is completely within the recalibrated route section. A new event is created on the post-calibration route with the calibration date as the starting date. Because the measures do not change for the Move behavior, the event shifts to the left to maintain its original start measure value of 30 on Route 3 and end measure value of 48 on Route 4.
The following diagram shows the route and events after calibration:
The following table provides details about the events after calibration when Move is the configured event behavior:
| Event ID | From Date | To Date | From Route Name | From Measure | To Route Name | To Measure |
|---|---|---|---|---|---|---|
| Event1 | 1/1/2000 | 1/1/2005 | Route1 | 0 | Route3 | 30 |
| Event1 | 1/1/2005 | <Null> | Route1 | 0 | Route3 | 30 |
| Event2 | 1/1/2000 | 1/1/2005 | Route3 | 30 | Route4 | 48 |
| Event2 | 1/1/2005 | <Null> | Route3 | 30 | Route4 | 48 |
Retire event behavior
The Retire behavior retires the two events in the recalibrated route section.
The route calibration described above has the following effects:
Event 1 is partially within the recalibrated route section, so it is retired on the date of calibration.
Event 2 is partially within the recalibrated route section, so it is retired on the date of calibration.
The following diagram shows the route and events after calibration:
The following table provides details about the events after calibration when Retire is the configured event behavior:
| Event | From Date | To Date | From Route Name | From Measure | To Route Name | To Measure | Location Error |
|---|---|---|---|---|---|---|---|
| Event1 | 1/1/2000 | 1/1/2005 | Route1 | 0 | Route3 | 30 | No Error |
| Event2 | 1/1/2000 | 1/1/2005 | Route3 | 30 | Route4 | 48 | No Error |