Available with Location Referencing license.
When route calibration occurs, events are impacted depending on the configured event behavior for each event layer.
Note:
Events are not updated until the Apply Event Behaviors tool is run after route edits. If you are using conflict prevention on branch versioned data, you are prompted to run Apply Event Behaviors before posting to the default version.
Calibration can occur on a route when one or more calibration points are added, edited, deleted, or when downstream recalibration is specified for LRS route editing tools.
Calibration point changes can be performed by doing the following:
- Use the calibration tools on the Location Referencing tab.
- Create or edit calibration points using create features.
- Use Apply downstream recalibration in the Location Referencing route editing tools.
The route calibration and corresponding event behaviors are described below.
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.
Refer to the following image to understand the upstream and downstream section for the route calibration scenario where the route is not calibrated downstream:
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 is updated to the new location of measures on the route. | The event polyline shape is updated to the new location of measures on the route if crossing a section of the route with a calibration point with measures is updated. |
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 contains events that span routes in the line network. The behaviors are still applied in the same manner.
- Because the LRS is time aware, edit activities, such as calibrating or retiring a route, time slices routes and events.
- If the route is calibrated the same day that it's created and the event behavior for calibrate is set to retire, the events are deleted and not retired.
Route calibration results
In this example, route Route1 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 graphics and tables below demonstrate the route information before and after the calibration.
Before route calibration
The following image 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 |
After route calibration
The following image shows the route after the calibration:
In this example, the Recalibrate downstream option is chosen, so the recalibrated route section starts from the nearest upstream calibration point of the edited calibration point to the end of the route. If the Recalibrate downstream option is not chosen, 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 |
Events before route calibration
There are three events on Route1 and all of them have a start date (From Date) of 1/1/2000. The following image 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 |
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
Although the geographic location of the event is maintained, the measures can change.
The route calibration described above has the following effects:
- Event1 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 (From Date). The start measure (From Measure) value changes 0 and the end measure (To Measure) value change to 9 to accommodate the new measures of Route1.
- Event2 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 Route1.
- Event3 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 Route1.
The following image shows the route and events after the calibration:
Note:
The retired event is not drawn in the graphic above.
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 |
Move event behavior
Although the measures of the event are maintained, the geographic location can change.
The route calibration described above has the following effects:
- Event1 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.
- Event2 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.
- Event3 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 image 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 |
Retire event behavior
Events in the recalibrated route section are retired. All three events are retired.
The route calibration described above has the following effects:
- Event1 was partially within the recalibrated route section; it is retired on the date of calibration.
- Event2 was completely within the recalibrated route section; it is retired on the date of calibration.
- Event3 was completely within the recalibrated route section; it is retired on the date of calibration.
The following image 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 |
Detailed behavior results on routes in a line network with events that span routes
In this example, there are four routes on LineA and the routes are active from 1/1/2000. The calibration is set to occur on 1/1/2005 where a new calibration point is added to Route 3 at existing measure 28 with a new measure value of 31. The Recalibrate downstream option is not chosen. The images and tables below demonstrate the route information before and after the calibration.
Before route calibration
The following image 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 |
After route calibration
The following image 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.
Route3 did not change its end measure because the Recalibrate downstream option was not chosen.
Events before calibration
There are two spanning events on routes on LineA. The following image 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
Although the geographic location of the event is maintained, the measures can change.
The route calibration described above has the following effects:
- Event1 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 (From Date). The start measure (From Measure) value changes to 0 on Route1 and the end measure (To Measure) value changes to 33 on Route3 to accommodate the new measures of Route3.
- Event2 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 Route3 and the end measure value changes to 48 on Route4 to accommodate the new measures of Route3.
The following image shows the routes and events after calibration:
Note:
The retired event is not drawn in the image above.
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
Although the measures of the event are maintained, the geographic location can change.
The route calibration described above has the following effects:
- Event1 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 Route1 and end measure value of 30 on Route3.
- Event2 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 Route3 and end measure value of 48 on Route4.
The following image 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 |
| Event1 | 1/1/2005 | <Null> | Route3 | 30 | Route4 | 48 |
Retire event behavior
The two events in the recalibrated route section are retired.
The route calibration described above has the following effects:
- Event1 was partially within the recalibrated route section; it is retired on the date of calibration.
- Event2 was partially within the recalibrated route section; it is retired on the date of calibration.
The following image 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 |