Available with Location Referencing license.
When routes are retired, 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 .
Note:
When Recalibrate route downstream is chosen for an LRS route edit, the configured calibrate event behavior is applied to downstream sections. You can review configured event behaviors by viewing LRS event properties.
Running the Apply Event Behaviors tool on event features after a corresponding route edit is described below.
Route retirement scenario
The following retirement scenario involves one route and three events. The retirement starts in Event1, completely spans Event2, and ends in Event3.
Stay Put behavior
While the geographic location of the event outside the retire region is preserved, the measures can change. The event can also split if it crosses the retire region. Portions of the reassign region are retired.
Move behavior
The measures and route of the event are maintained; the geographic location can change.
Retire behavior
The geographic location and measure of the event are preserved; the event is retired. Events intersecting the retire region are retired.
Upstream and downstream sections
Route editing impacts upstream and downstream sections differently.
The following image shows the upstream and downstream sections for the route retirement scenario:
The following table details how the retirement editing activity impacts upstream and downstream events according to the configured event behavior:
| Behavior | Events upstream | Events intersecting | Events downstream |
|---|---|---|---|
Stay Put | No action. | Retire event; line events crossing the edit region are split and the original event is retired. | If route calibration is changed, the recalibrate event behavior is applied; otherwise, no action is taken. |
Move | Shape regenerated, if needed, to new location of route measures. | Shape regenerated to new location of route measures. | If route calibration is changed, the recalibrate event behavior is applied; otherwise, no action is taken. |
Retire | No action. | Retire event; line events crossing the edit region are not split. | If route calibration is changed, the recalibrate event behavior is applied; otherwise, no action is taken. |
Note:
- Point events follow the same behavior as line events but don't need to be split.
- If the Recalibrate route downstream option is chosen, calibrate route event behaviors are applied to the events downstream of the edited portion of the route.
- The network can contain events that span multiple routes in a line network. In this case, the behaviors are applied in the same manner.
- Since the LRS is time aware, edit activities—such as retiring a route—time slice routes and events.
Detailed behavior results
The following sections detail how event behavior rules are enforced when a route is retired.
Stay Put event behavior
The route is active from 1/1/2000, and if the retirement is set to occur on 1/1/2005 and Recalibrate route downstream is not chosen, this has the following effects:
- Event1 is represented by two time slices. There is a time slice from 1/1/2000 to 1/1/2005, with the original measures from 0 to 20, and a time slice from 1/1/2005 to <Null>, with measures from 0 to 15, that stay the same location geographically.
- Event2 retires to maintain geographic location.
- Event3 is represented by two time slices. There is a time slice from 1/1/2000 to 1/1/2005, with the original measures from 30 to 45, and a time slice from 1/1/2005 to <Null>, with measures from 35 to 45, that stay the same geographically.
Before Stay Put event behavior
The following image shows the route before retirement:
The following table provides details about the events before retirement:
| Event | Route Name | From Date | To Date | From Measure | To Measure |
|---|---|---|---|---|---|
Event1 | Route1 | 1/1/2000 | <Null> | 0 | 20 |
Event2 | Route1 | 1/1/2000 | <Null> | 20 | 30 |
Event3 | Route1 | 1/1/2000 | <Null> | 30 | 45 |
After Stay Put event behavior
The following image shows the route after retirement:
The following table provides details about the events after retirement 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 | 20 | No Error |
Event1 | Route1 | 1/1/2005 | <Null> | 0 | 15 | No Error |
Event3 | Route1 | 1/1/2000 | 1/1/2005 | 30 | 45 | No Error |
Event3 | Route1 | 1/1/2005 | <Null> | 35 | 45 | No Error |
Move event behavior
The route is active from 1/1/2000, and if the retirement is set to occur on 1/1/2005 and Recalibrate route downstream is not chosen, this has the following effects:
- Event1 is represented by two time slices. There is a time slice from 1/1/2000 to 1/1/2005 and a time slice from 1/1/2005 to <Null>, both with the original measures from 0 to 20. This new time slice will only partially locate since the event time slice has measures from 0 to 20, but the underlying route time slice only has measures from 0 to 15 and 35 to 55, with a physical gap created due to retirement.
- Event2 is represented by two time slices. There is a time slice from 1/1/2000 to 1/1/2005 and a time slice from 1/1/2005 to <Null>, both with the measures from 20 to 30. This new time slice will not locate since the event time slice has measures from 20 to 30, but the underlying route does not have a route with those measures.
- Event3 is represented by two time slices. There is a time slice from 1/1/2000 to 1/1/2005 and a time slice from 1/1/2005 to <Null>, both with the original measures 30 to 45. This new time slice only partially locates since the event time slice has measures from 30 to 45, but the underlying route time slice only has measures from 0 to 15 and 35 to 55, with a physical gap created due to retirement.
Before Move event behavior
The following image shows the route before retirement:
The following table provides details about the events before retirement:
| Event | Route Name | From Date | To Date | From Measure | To Measure |
|---|---|---|---|---|---|
Event1 | Route1 | 1/1/2000 | <Null> | 0 | 20 |
Event2 | Route1 | 1/1/2000 | <Null> | 20 | 30 |
Event3 | Route1 | 1/1/2000 | <Null> | 30 | 45 |
After Move event behavior
The following image shows the route after retirement:
The following table provides details about the events after retirement 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 | 20 | No Error |
Event1 | Route1 | 1/1/2005 | <Null> | 0 | 20 | Partial match for the to measure |
Event3 | Route1 | 1/1/2000 | 1/1/2005 | 30 | 45 | No Error |
Event3 | Route1 | 1/1/2005 | <Null> | 30 | 45 | Partial match for the from measure |
Retire event behavior
The route is active from 1/1/2000, and if the retirement is set to occur on 1/1/2005 and Recalibrate route downstream is not chosen, this has the following effects:
- Event1 retires since it intersects the retired region.
- Event2 retires since it is completely inside the retired region.
- Event3 retires since it intersects the retired region.
Before Retire event behavior
The following image shows the route before retirement:
The following table provides details about the events before retirement:
| Event | Route Name | From Date | To Date | From Measure | To Measure |
|---|---|---|---|---|---|
Event1 | Route1 | 1/1/2000 | <Null> | 0 | 20 |
Event2 | Route1 | 1/1/2000 | <Null> | 20 | 30 |
Event3 | Route1 | 1/1/2000 | <Null> | 30 | 45 |
After Retire event behavior
The following image shows the route after retirement:
The following table provides details about the events after retirement 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 | 20 | No Error |
Event2 | Route1 | 1/1/2000 | 1/1/2005 | 20 | 30 | No Error |
Event3 | Route1 | 1/1/2000 | 1/1/2005 | 30 | 45 | No Error |
Detailed behavior on routes in a line network with events that span routes
Stay Put event behavior
This retirement scenario involves four routes on a line in a line network and two events. Route3 will be retired. The retired route (depicted with a dotted line) impacts both Event1 and Event2.
The routes are active from 1/1/2000 and if the retirement is set to occur on 1/1/2005 and Recalibrate route downstream is unchecked, this will have the following effects:
- Event1 will be represented by two time slices. There will be a time slice from 1/1/2000 to 1/1/2005, with the original measures of 0 to 30 on Route1 and Route3, and a time slice from 1/1/2005 to <null>, with measures of 0 on Route1 to 22 on Route2 as it stays in the same location geographically. The portion of the event on Route3 will be retired since there is no route to build that part of the event shape on any longer.
- Event2 will be represented by two time slices. There will be a time slice from 1/1/2000 to 1/1/2005, with the original measures of 30 on Route3 to 48 on Route4, and a time slice from 1/1/2005 to <null>, with measures of 38 on Route4 to 48 on Route4 as it stays in the same location geographically. The portion of the event on Route3 will be retired since there is no route to build that part of the event shape on any longer.
Before Stay Put event behavior
The following image shows the routes before retirement:
The following table provides details about the events before retirement.
| Event ID | From Date | To Date | From RouteID | To Route ID | From Measure | To Measure |
|---|---|---|---|---|---|---|
Event1 |
1/1/2000 | <null> | Route1 | Route3 | 0 | 30 |
Event2 |
1/1/2000 | <null> | Route3 | Route4 | 30 | 48 |
After Stay Put event behavior
The following image shows the routes after retirement:
The following table provides details about the events after retirement when Stay Put is the configured event behavior.
| Event ID | From Date | To Date | From RouteID | To Route ID | From Measure | To Measure | Location Error |
|---|---|---|---|---|---|---|---|
Event1 | 1/1/2000 | 1/1/2005 | Route1 | Route3 | 0 | 30 | No Error |
Event1 | 1/1/2005 | <null> | Route1 | Route2 | 0 | 22 | No Error |
Event2 | 1/1/2000 | 1/1/2005 | Route3 | Route4 | 30 | 48 | No Error |
Event2 | 1/1/2005 | <null> | Route4 | Route4 | 38 | 48 | No Error |
Move event behavior
The routes are active from 1/1/2000 and if the retirement is set to occur on 1/1/2005 and Recalibrate route downstream is unchecked, this will have the following effects:
- Event1 will be represented by two time slices. There will be a time slice from 1/1/2000 to 1/1/2005 and a time slice from 1/1/2005 to <null>, both with the original measures 0 on Route1 to 30 on Route3. This new time slice will only partially locate since the event time slice has measures of 0 to 30 on Route1 to Route3, but Route3 has been retired, so there is no route in that location to build a shape.
- Event2 will be represented by two time slices. There will be a time slice from 1/1/2000 to 1/1/2005 and a time slice from 1/1/2005 to <null>, both with the measures of 30 on Route3 to 48 on Route4. This new time slice will not locate since the event time slice has measures of 30 to 48 on Route3 to Route4, but Route3 has been retired, so there is no route in that location to build a shape.
Before Move event behavior
The following image shows the routes before retirement:
The following table provides details about the events before retirement.
| Event ID | From Date | To Date | From RouteID | To Route ID | From Measure | To Measure |
|---|---|---|---|---|---|---|
Event1 | 1/1/2000 | <null> | Route1 | Route3 | 0 | 30 |
Event2 | 1/1/2000 | <null> | Route3 | Route4 | 30 | 48 |
After Move event behavior
The following image shows the routes after retirement:
The following table provides details about the events after retirement when Move is the configured event behavior.
| Event ID | From Date | To Date | From RouteID | To Route ID | From Measure | To Measure | Location Error |
|---|---|---|---|---|---|---|---|
Event1 | 1/1/2000 | 1/1/2005 | Route1 | Route3 | 0 | 30 | No Error |
Event1 | 1/1/2005 | <null> | Route1 | Route3 | 0 | 30 | Partial Match for the To Measure |
Event2 | 1/1/2000 | 1/1/2005 | Route3 | Route4 | 30 | 48 | No Error |
Event2 | 1/1/2005 | <null> | Route3 | Route4 | 30 | 48 | Partial Match for the From Measure |
Retire event behavior
The routes are active from 1/1/2000 and if the retirement is set to occur on 1/1/2005 and Recalibrate route downstream is unchecked, this will have the following effects:
- Event1 will retire since it is located within the retired region.
- Event2 will retire since it is located within the retired region.
Before Retire event behavior
The following image shows the routes before retirement:
The following table provides details about the events before retirement.
| Event ID | From Date | To Date | From RouteID | To Route ID | From Measure | To Measure |
|---|---|---|---|---|---|---|
Event1 | 1/1/2000 | <null> | Route1 | Route3 | 0 | 30 |
Event2 | 1/1/2000 | <null> | Route3 | Route4 | 30 | 48 |
After Retire event behavior
The following image shows the routes after retirement:
The following table provides details about the events after retirement when Retire is the configured event behavior.
| Event ID | From Date | To Date | From RouteID | To Route ID | From Measure | To Measure | Location Error |
|---|---|---|---|---|---|---|---|
Event1 | 1/1/2000 | 1/1/2005 | Route1 | Route3 | 0 | 30 | No Error |
Event2 | 1/1/2000 | 1/1/2005 | Route3 | Route4 | 30 | 48 | No Error |