Available with Location Referencing license.
When a route realignment occurs, events are impacted in the edit activity area, as well as upstream and downstream of the realignment, depending on the configured event behavior for each event layer. ArcGIS Roads and Highways has options to retire a realigned route, or to reassign the realigned portion of the route to an abandoned route with a new route name and route ID.
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:
For any LRS route edit in which Recalibrate route downstream is chosen, 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 realignment scenario
This realignment scenario involves one route and three events that cover the length of Route1. The realignment (depicted with a gray line) starts in Event1, completely spans Event2, and ends in Event3.
The following image shows the route before realignment:
Stay Put behavior
The geographic location of the event outside the realign region is maintained; the measures can change. The event can also split if it crosses the realign region. Portions of events in the realign region are retired. Event1, Event2, and Event3 have the same measurements, but their location on the route has changed.
Move behavior
The measures of the event are maintained; the geographic location can change.
Retire behavior
Events intersecting the realignment region are retired.
Cover behavior
The event measures on the route are changed; the geographic location is changed to include the realigned section.
Snap behavior
The event measures on the route are preserved by snapping the event to a concurrent route; the geographic location is changed to include the realigned section.
Detailed behavior results
Event behaviors for route realignment are described in the following sections. This realignment (depicted with a gray line) starts in Event1, completely spans Event2, and ends in Event3. The realignment occurs on 1/1/2005, and the Recalibrate route downstream option is chosen unless stated otherwise.
Stay Put behavior
The geographic location of the event outside the realign region is maintained; the measures can change. The event may also split if it crosses the realign region. Portions of events in the realign region are retired. The following changes occur in the LRS:
- 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 8 and a time slice from 1/1/2005 to <Null>, with measures from 0 to 6 that stay the same geographically but have the new measures from Route1.
- 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 12 to 20, and a time slice from 1/1/2005 to <Null>, with measures from 18 to 24 that stay the same geographically but have the new measures from Route1.
Before Stay Put behavior
The following image shows the route before realignment:
Note:
For any route edit in which Recalibrate route downstream is chosen, any portion of the route downstream of the edited section is recalibrated. Calibrate event behavior is applied in these recalibrated sections.
The following table provides details about the events before realignment:
| Event ID | Route Name | From Date | To Date | From Measure | To Measure |
|---|---|---|---|---|---|
Event1 | Route1 | 1/1/2000 | <Null> | 0 | 8 |
Event2 | Route1 | 1/1/2000 | <Null> | 8 | 12 |
Event3 | Route1 | 1/1/2000 | <Null> | 12 | 20 |
After Stay Put behavior
The following image shows the route after realignment.
The following table provides details about the events after realignment when Stay Put is the configured event behavior:
| Event ID | Route Name | From Date | To Date | From Measure | To Measure | Location Error |
|---|---|---|---|---|---|---|
Event1 | Route1 | 1/1/2000 | 1/1/2005 | 0 | 8 | No Error |
Event1 | Route1 | 1/1/2005 | <Null> | 0 | 6 | No Error |
Event2 | Route1 | 1/1/2000 | 1/1/2005 | 8 | 12 | No Error |
Event3 | Route1 | 1/1/2000 | 1/1/2005 | 12 | 20 | No Error |
Event3 | Route1 | 1/1/2005 | <Null> | 18 | 24 | No Error |
Move behavior
The measures of the event are maintained; the geographic location can change. The following changes occur in the LRS:
- 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 8, and a time slice from 1/1/2005 to <Null> with measures from 0 to 8 that move geographically to maintain the original event measures. The event has the same measures but different geometry in the new time slice.
- Event2 is represented by two time slices. There is a time slice from 1/1/2000 to 1/1/2005, with the original measures from 8 to 12, and a time slice from 1/1/2005 to <Null>, with measures from 8 to 12 that move geographically to maintain the original event measures. The event has the same measures but different geometry in the new time slice.
- 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 12 to 20, and a time slice from 1/1/2005 to <Null>, with measures from 12 to 20 that move geographically to maintain the original event measures. The event has the same measures but different geometry in the new time slice.
Before Move event behavior
The following image shows the route before realignment:
The following table provides details about the events before realignment:
| Event ID | Route Name | From Date | To Date | From Measure | To Measure |
|---|---|---|---|---|---|
Event1 | Route1 | 1/1/2000 | <Null> | 0 | 8 |
Event2 | Route1 | 1/1/2000 | <Null> | 8 | 12 |
Event3 | Route1 | 1/1/2000 | <Null> | 12 | 20 |
After Move event behavior
The following image shows the route after realignment:
The following table provides details about the events after realignment when Move is the configured event behavior:
| Event ID | Route Name | From Date | To Date | From Measure | To Measure | Location Error |
|---|---|---|---|---|---|---|
Event1 | Route1 | 1/1/2000 | 1/1/2005 | 0 | 8 | No Error |
Event1 | Route1 | 1/1/2005 | <Null> | 0 | 8 | No Error |
Event2 | Route1 | 1/1/2000 | 1/1/2005 | 8 | 12 | No Error |
Event2 | Route1 | 1/1/2005 | <Null> | 8 | 12 | No Error |
Event3 | Route1 | 1/1/2000 | 1/1/2005 | 12 | 20 | No Error |
Event3 | Route1 | 1/1/2005 | <Null> | 12 | 20 | No Error |
Retire behavior
Events intersecting the realignment region are retired. In this scenario, Event2 was retired on 1/1/2005 because it was entirely in the realignment portion. Additionally, Event1 and Event3 were retired on 1/1/2005 because they were partially within the realignment portion.
Before Retire event behavior
The following image shows the route before realignment:
The following table provides details about the events before realignment:
| Event ID | Route Name | From Date | To Date | From Measure | To Measure |
|---|---|---|---|---|---|
Event1 | Route1 | 1/1/2000 | <Null> | 0 | 8 |
Event2 | Route1 | 1/1/2000 | <Null> | 8 | 12 |
Event3 | Route1 | 1/1/2000 | <Null> | 12 | 20 |
After Retire event behavior
The following image shows the route after realignment:
The following table provides details about the events after realignment when Retire is the configured event behavior:
| Event ID | Route Name | From Date | To Date | From Measure | To Measure | Location Error |
|---|---|---|---|---|---|---|
Event1 | Route1 | 1/1/2000 | 1/1/2005 | 0 | 8 | No Error |
Event2 | Route1 | 1/1/2000 | 1/1/2005 | 8 | 12 | No Error |
Event3 | Route1 | 1/1/2000 | 1/1/2005 | 12 | 20 | No Error |
Cover event behavior
The event measures on the route are changed; the geographic location is changed to include the realigned section. The following changes occur in the LRS:
- 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 8. There are two Event1 upstream event records from 1/1/2005 to <Null>. The first upstream Event1 event record runs from the start of Route1 at 0 to the start of the realign section at 6. The second upstream Event1 event record is created at the start of the realign section from 6 to 9.
- Event2 is represented by two time slices. There is a time slice from 1/1/2000 to 1/1/2005 with the original measures from 8 to 12, and a time slice from 1/1/2005 to <Null> with updated measures from 9 to 15.
- 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 12 to 20, and a time slice from 1/1/2005 to <Null> with updated measures from 15 to 24.
Before Cover event behavior
The following image shows the route before realignment:
The following table provides details about the events before realignment:
| Event ID | Route Name | From Date | To Date | From Measure | To Measure |
|---|---|---|---|---|---|
Event1 | Route1 | 1/1/2000 | <Null> | 0 | 8 |
Event2 | Route1 | 1/1/2000 | <Null> | 8 | 12 |
Event3 | Route1 | 1/1/2000 | <Null> | 12 | 20 |
After Cover event behavior
Note:
When Recalibrate route downstream is chosen for an LRS route edit, all of the route downstream of the edited section is recalibrated. Calibrate event behavior is applied in these recalibrated sections.
The following image shows the route after realignment:
The following table provides details about the events after realignment when Cover is the configured event behavior:
| Event ID | From Date | To Date | From Measure | To Measure | Location Error |
|---|---|---|---|---|---|
| Event1 | 1/1/2000 | 1/1/2005 |
0 | 8 | No Error |
| Event1 | 1/1/2005 | <Null> | 0 | 6 | No Error |
| Event1 | 1/1/2005 | <Null> | 6 | 9 | No Error |
| Event2 | 1/1/2000 | 1/1/2005 |
8 | 12 | No Error |
| Event2 | 1/1/2005 | <Null> | 9 | 15 | No Error |
| Event3 | 1/1/2000 | 1/1/2005 |
12 | 20 | No Error |
| Event3 | 1/1/2005 | <Null> |
15 | 24 | No Error |
Snap event behavior
The event measures on the route are preserved by snapping the event to a concurrent route; the geographic location is changed to include the realigned section. The following changes occur in the LRS:
- 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 8 and a time slice from 1/1/2005 to <Null> with updated measures from 0 to 6.
- Event2 is represented by one time slice. There is a time slice from 1/1/2000 to 1/1/2005 with the original measures from 8 to 12.
- 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 12 to 20, and a time slice from 1/1/2005 to <Null> with updated measures 18 to 24.
Before Snap event behavior
The following image shows the route before realignment:
The following table provides details about the events before realignment:
| Event ID | Route Name | From Date | To Date | From Measure | To Measure |
|---|---|---|---|---|---|
Event1 | Route1 | 1/1/2000 | <Null> | 0 | 8 |
Event2 | Route1 | 1/1/2000 | <Null> | 8 | 12 |
Event3 | Route1 | 1/1/2000 | <Null> | 12 | 20 |
After Snap event behavior
Note:
For any LRS route edit in which Recalibrate route downstream is chosen, any portion of the route downstream of the edited section is recalibrated. Calibrate event behavior is applied in these recalibrated sections.
The following image shows the route after realignment:
The following table provides details about the events after realignment when Snap is the configured event behavior:
| Event ID | Route Name | From Date | To Date | From Measure | To Measure | Location Error |
|---|---|---|---|---|---|---|
| Event1 | Route1 | 1/1/2000 | 1/1/2005 |
0 | 8 | No Error |
| Event1 | Route1 | 1/1/2005 | <Null> |
0 | 6 | No Error |
| Event2 | Route1 | 1/1/2000 | 1/1/2005 |
8 | 12 | No Error |
| Event3 | Route1 | 1/1/2000 | 1/1/2005 |
12 | 20 | No Error |
| Event3 | Route1 | 1/1/2005 | <Null> |
18 | 24 | No Error |
Upstream and downstream sections
The following table provides additional information about how events are impacted by a realignment depending on the configured event behavior:
| Behavior | Events upstream realignment | Events intersecting realignment | Events downstream realignment |
|---|---|---|---|
Stay Put | Up to closest upstream calibration point; one or more measures adjusted to retain x,y if needed. | Retire event; line events crossing the edit section 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 is regenerated, if needed, to new location of route measures. | Shape is regenerated to new location of route measures. | If route calibration is changed, the recalibrate event behavior is applied; otherwise, no action is taken. |
Retire | Up to closest upstream calibration point; retire event if needed. | Retire event; line events crossing the edit section are not split. | If route calibration is changed, the recalibrate event behavior is applied; otherwise, no action is taken. |
Cover | No action. | Retire event; line events crossing the edit section are split. | If route calibration is changed, the recalibrate event behavior is applied; otherwise, no action is taken. |
Snap | No action. | Retire event; the retired event is snapped to a concurrent route, if one exists. | 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 following image shows the upstream and downstream section for an edit:
- The network can contain events that span multiple routes in a line network. In this case, the behaviors are applied in the same manner.
- When the LRS is time aware, edit activities—such as realigning a route—time slice routes and events.
Realign with abandonment scenario (reassign to abandoned route)
The route section in the realign section is reassigned to a new route on a new line, and any event in the realign section follows the reassign event behavior. Stay Put, Move, Cover, and Retire reassign event behavior settings result in the same behavior as shown in the previous diagrams. If you want your events to transfer to the abandoned route, configure the Snap behavior for reassign route.
The reassign event behavior is applied before the realign event behavior, so it is important to verify the event feature layer's reassign event behavior configuration before checking the Reassign to abandoned route check box.
Stay Put behavior (with Reassign set to Snap behavior)
The geographic location of the event outside the realign region is maintained; the measures can change. The event can also split if it crosses the realign region. Portions of the event in the realign region are snapped to the reassigned route.
Move behavior (with Reassign set to Snap behavior)
The measures of the event are maintained; the geographic location can change. Portions of the event in the realign region are snapped to the reassigned route.
Retire behavior (with Reassign set to Snap behavior)
Events intersecting the realignment region are retired. Portions of the event in the realign region are snapped to the reassigned route.
Cover behavior (with Reassign set to Snap behavior)
The event measures on the route are changed; the geographic location is changed to include the realign section. Portions of the event in the realign region are snapped to the reassigned route.
Snap behavior (with Reassign set to Stay Put behavior)
The event measures on the route are changed; the geographic location is changed to include the realign section. Portions of the event in the realign region are snapped to the reassigned route.
Detailed behavior results with realigned abandonment
The following sections detail how event behavior rules are enforced when a route is realigned with abandonment.
Before realignment with abandonment
The following scenario involves one route and three events. The realignment (depicted with a gray line) starts in Event1, completely spans Event2, and ends in Event3. The resulting behaviors, time slices, and measures with abandonment are detailed in the following sections.
The following image shows the route before realignment:
The following table provides details about the events before realignment:
| Event | Route Name | From Date | To Date | From Measure | To Measure |
|---|---|---|---|---|---|
Event1 | Route1 | 1/1/2000 | <Null> | 0 | 8 |
Event2 | Route1 | 1/1/2000 | <Null> | 8 | 12 |
Event3 | Route1 | 1/1/2000 | <Null> | 12 | 20 |
Stay Put behavior (with Reassign set to Snap behavior)
If the realignment is set to occur on 1/1/2005 and both Recalibrate route downstream and Reassign to abandoned route(s) are 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 8, and a time slice from 1/1/2005 to <Null> with two event records. The first Event1 event record after realignment has measures from 0 to 6 that stay in the same location geographically but have the new measures from Route1. The second Event1 record is located on Route1_Ab, which is on a new line, Line1_Ab, and has measures from 6 to 8 that snap to the abandoned route.
- Event2 is represented by two time slices. There is a time slice from 1/1/2000 to 1/1/2005, with the original measures from 8 to 12, and a time slice from 1/1/2005 to <Null> located on Route1_Ab, which is on a new line, Line1_Ab, and has measures from 8 to 12 that snap to the abandoned route.
- 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 12 to 20, and a time slice from 1/1/2005 to <Null> with two event records. The first Event3 event record after realignment has measures from 18 to 24 that stay in the same location geographically, but have the new measures from Route1. The second Event3 event record is located on Route1_Ab, which is on a new line, Line1_Ab, and has measures from 12 to 14 that snap to the abandoned route.
The following image shows the route after realignment:
The following table provides details about the events after realignment when Stay Put is the configured event behavior and Reassign is set to Snap:
| Event | Route Name | From Date | To Date | From Measure | To Measure | Location Error |
|---|---|---|---|---|---|---|
Event1 | Route1 | 1/1/2000 | 1/1/2005 | 0 | 8 | No Error |
Event1 | Route1 | 1/1/2005 | <Null> | 0 | 6 | No Error |
Event1 | Route1_Ab | 1/1/2005 | <Null> | 6 | 8 | No Error |
Event2 | Route1 | 1/1/2000 | 1/1/2005 | 8 | 12 | No Error |
Event2 | Route1_Ab | 1/1/2005 | <Null> | 8 | 12 | No Error |
Event3 | Route1 | 1/1/2000 | 1/1/2005 | 12 | 20 | No Error |
Event3 | Route1 | 1/1/2005 | <Null> | 18 | 24 | No Error |
Event3 | Route1_Ab | 1/1/2005 | <Null> | 12 | 14 | No Error |
Move behavior (with Reassign set to Snap behavior)
If the realignment is set to occur on 1/1/2005 and both Recalibrate route downstream and Reassign to abandoned route(s) are 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 8, and a time slice from 1/1/2005 to <Null> with two event records. The first Event1 event record after realignment has measures from 0 to 6 that move geographically to maintain the original event measures. This event record has the same measures but different geometry in the new time slice. The second event record, which is located on Route1_Ab, has measures from 6 to 8 that snap to the abandoned route.
- Event2 is represented by two time slices. There is a time slice from 1/1/2000 to 1/1/2005, with the original measures from 8 to 12, and a time slice from 1/1/2005 to <Null> located on Route1_Ab with measures from 8 to 12 that snap to the abandoned route.
- 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 12 to 20, and a time slice from 1/1/2005 to <Null> with two event records. The first Event3 event record after realignment has measures from 14 to 20 that move geographically to maintain the original event measures. This event record has the same measures but different geometry in the new time slice. The second Event3 event record, which is located on Route1_Ab, has measures from 12 to 14 that snap to the abandoned route.
The following image shows the route after realignment:
The following table provides details about the events after realignment when Move is the configured event behavior and Reassign is set to Snap:
| Event | Route Name | From Date | To Date | From Measure | To Measure | Location Error |
|---|---|---|---|---|---|---|
Event1 | Route1 | 1/1/2000 | 1/1/2005 | 0 | 8 | No Error |
Event1 | Route1 | 1/1/2005 | <Null> | 0 | 8 | Partial match for To Measure |
Event1 | Route1_Ab | 1/1/2005 | <Null> | 6 | 8 | No Error |
Event2 | Route1 | 1/1/2000 | 1/1/2005 | 8 | 12 | No Error |
Event2 | Route1_Ab | 1/1/2005 | <Null> | 8 | 12 | No Error |
Event3 | Route1 | 1/1/2000 | 1/1/2005 | 12 | 20 | No Error |
Event3 | Route1 | 1/1/2005 | <Null> | 14 | 20 | No Error |
Event3 | Route1_Ab | 1/1/2005 | <Null> | 12 | 14 | No Error |
Retire behavior (with Reassign set to Snap behavior)
If the realignment is set to occur on 1/1/2005 and both Recalibrate route downstream and Reassign to abandoned route(s) are 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 measures from 0 to 8, and a time slice from 1/1/2005 to <Null> with two event records. The first Event1 event record after realignment in the 1/1/2005 to <Null> time slice has measures from 0 to 6. This event record is created because the reassign edit behavior is processed before the realign edit behavior, causing the upstream linear event that crossed the realign region to split rather than retire. The second Event1 event record, which is located on Route1_Ab, has measures from 6 to 8 that snap to the abandoned route.
- Event2 is represented by two time slices. There is a time slice from 1/1/2000 to 1/1/2005, with measures from 8 to 12. There is also a time slice from 1/1/2005 to <Null>, located on Route1_Ab, with measures from 8 to 12 that has snapped to the abandoned route.
- Event3 is represented by two time slices. There is a time slice from 1/1/2000 to 1/1/2005, with measures from 12 to 20. There is also a time slice from 1/1/2005 to <Null>, located on Route1_Ab, with measures from 12 to 14 that has snapped to the abandoned route.
The following image shows the route after realignment:
The following table provides details about the events after realignment when Retire is the configured event behavior and Reassign is set to Snap:
| Event | Route Name | From Date | To Date | From Measure | To Measure | Location Error |
|---|---|---|---|---|---|---|
Event1 | Route1 | 1/1/2000 | 1/1/2005 | 0 | 8 | No Error |
Event1 | Route1 | 1/1/2005 | <Null> | 0 | 6 | No Error |
Event1 | Route1_Ab | 1/1/2005 | <Null> | 6 | 8 | No Error |
Event2 | Route1 | 1/1/2000 | 1/1/2005 | 8 | 12 | No Error |
Event2 | Route1_Ab | 1/1/2005 | <Null> | 8 | 12 | No Error |
Event3 | Route1 | 1/1/2000 | 1/1/2005 | 12 | 20 | No Error |
Event3 | Route1_Ab | 1/1/2005 | <Null> | 12 | 14 | No Error |
Cover behavior (with Reassign set to Snap behavior)
If the realignment is set to occur on 1/1/2005 and both Recalibrate route downstream and Reassign to abandoned route(s) are 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 measures from 0 to 8, and a time slice from 1/1/2005 to <Null> with two event records. The first Event1 event record after realignment has measures from 0 to 9. The second Event1 record, which is located on Route1_Ab, has measures from 6 to 8 that snap to the abandoned route (Route1_Ab).
- Event2 is represented by two time slices. There is a time slice from 1/1/2000 to 1/1/2005, with measures from 8 to 12, and a time slice from 1/1/2005 to <Null> with two event records. The first Event2 event record after realignment has measures from 9 to 15. The second Event2 event record has measures from 8 to 12 that snap to the abandoned route (Route1_Ab).
- Event3 is represented by two time slices. There is a time slice from 1/1/2000 to 1/1/2005, with measures from 12 to 20, and a time slice from 1/1/2005 to <Null> with two event records. The first Event3 event record after realignment has measures from 15 to 24. The second Event3 event record has measures from 12 to 14 that snap to the abandoned route (Route1_Ab).
The following image shows the route after realignment:
The following table provides details about the events after realignment when Cover is the configured event behavior and Reassign is set to Snap:
| Event ID | From Date | To Date | Route Name | From Measure | To Measure | Location Error |
|---|---|---|---|---|---|---|
| Event1 | 1/1/2000 | 1/1/2005 |
Route1 | 0 | 8 | No Error |
| Event1 | 1/1/2005 | <Null> |
Route1_Ab | 6 | 8 | No Error |
| Event1 | 1/1/2005 | <Null> |
Route1 | 0 | 9 | No Error |
| Event2 | 1/1/2000 | 1/1/2005 |
Route1 | 8 | 12 | No Error |
| Event2 | 1/1/2005 | <Null> |
Route1 | 8 | 12 | No Error |
| Event2 | 1/1/2005 | <Null> |
Route1 | 9 | 15 | No Error |
| Event3 | 1/1/2000 | 1/1/2005 |
Route1 | 12 | 20 | No Error |
| Event3 | 1/1/2005 | <Null> |
Route1_Ab | 12 | 14 | No Error |
| Event3 | 1/1/2005 | <Null> |
Route1 | 15 | 24 | No Error |
Snap behavior (with Reassign set to Stay Put behavior)
If the realignment is set to occur on 1/1/2005 and both Recalibrate route downstream and Reassign to abandoned route(s) are chosen, this has the following effects:
- For the abandoned portion of Route1, Route1_Ab is created using a from date of 1/1/2000 and to date of 1/1/2005.
- Event1 is represented by two time slices. There is a time slice from 1/1/2000 to 1/1/2005, with measures from 0 to 8, and a time slice from 1/1/2005 to <Null> with measures from 0 to 6.
- Event2 is represented by one time slice. There is a time slice from 1/1/2000 to 1/1/2005, with measures from 8 to 12.
- 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> with two event records. The first Event3 record after realignment has measures from 12 to 14 that snap to the abandoned route (Route1_Ab). The second Event3 event record has measures from 18 to 24.
The following image shows the routes after realignment:
The following table provides details about the events after realignment when Snap is the configured event behavior and Reassign is set to Stay Put:
| Event ID | From Date | To Date | Route Name | From Measure | To Measure | Location Error |
|---|---|---|---|---|---|---|
| Event1 | 1/1/2000 | 1/1/2005 | Route1 | 0 | 8 | No Error |
| Event1 | 1/1/2005 | <Null> | Route1 | 0 | 6 | No Error |
| Event2 | 1/1/2000 | 1/1/2005 | Route1 | 8 | 12 | No Error |
| Event3 | 1/1/2000 | 1/1/2005 | Route1 | 12 | 14 | No Error |
| Event3 | 1/1/2005 | <Null> | Route1 | 18 | 24 | No Error |
Detailed behavior on routes in a line network with events that span routes
The following sections detail how event behavior rules are enforced for events that span routes when a route on a line in a line network is realigned.
Stay Put behavior (with Reassign set to Snap for abandonment)
If the realignment with abandonment is set to occur on 1/1/2005 from measure 17 on Route2 to measure 43 on Route4 and Recalibrate route downstream is unchecked, this has the following effects:
- For the abandoned portions of Route2, Route3, and Route4, the following routes are created: Route2_Ab, Route3_Ab, Route4_Ab.
- 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 on Route1 to 30 on Route3, and a time slice from 1/1/2005 to <Null> with two event records. Because the realignment with abandonment takes place in the middle of the event, Event1 splits after realignment. The first Event1 event record after realignment has measures from 0 on Route1 to 17 on Route2, while the second Event1 record has measures from 17 on Route2_Ab to 30 on Route3_Ab. Both records stay in the same location geographically.
- Event2 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 on Route3 to 48 on Route4. The second time slice from 1/1/2005 to <Null> has two event records. Because the realignment with abandonment takes place in the middle of the event, Event2 splits after realignment. The first Event2 event record after realignment has measures from 30 on Route3_Ab to measure 43 on Route4_Ab, while the second Event2 event record has measures from 43 to 48 on Route4. Both records stay in the same location geographically.
Before Stay Put behavior (with Reassign set to Snap for abandonment)
The following image shows the routes before realignment:
The following table provides details about the events before realignment:
| 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 behavior (with Reassign set to Snap for abandonment)
For the abandoned portions of Route2, Route3, and Route4, the following routes are created: Route2_Ab, Route3_Ab, Route4_Ab.
The following image shows the routes after realignment:
The following table provides details about the events after realignment when Stay Put behavior is the configured event behavior with Reassign set to Snap:
| 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 | 17 | No Error |
Event1 | 1/1/2005 | <Null> | Route2_Ab | Route3_Ab | 17 | 30 | No Error |
Event2 | 1/1/2000 | 1/1/2005 | Route3 | Route4 | 30 | 48 | No Error |
Event2 | 1/1/2005 | <Null> | Route3_Ab | Route4_Ab | 30 | 43 | No Error |
Event2 | 1/1/2005 | <Null> | Route4 | Route4 | 43 | 48 | No Error |
Move behavior (with Reassign set to Move for abandonment)
If the realignment with abandonment is set to occur on 1/1/2005 from measure 17 on Route2 to measure 43 on Route4 and Recalibrate route downstream is unchecked, 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 on Route1 to 30 on Route3, and a time slice from 1/1/2005 to <Null> with measures from 0 on Route1 to 17 on Route2. After realignment with abandonment, the event record gets the Location Error value, Partial Match for the To Measure, because part of Route2 and all of Route3 retire after realignment.
- Event2 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 on Route3 to 48 on Route4, and a time slice from 1/1/2005 to <Null>, which has measures from 43 to 48 on Route4. The event record gets the Location Error value, Partial Match for the From Measure, because Route3 retires after realignment.
Before Move behavior (with Reassign set to Move for abandonment)
The following image shows the routes before realignment:
The following table provides details about the events before realignment:
| 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 behavior (with Reassign set to Move for abandonment)
For the abandoned portions of Route2, Route3, and Route4, the following routes are created: Route2_Ab, Route3_Ab, Route4_Ab.
The following image shows the routes after realignment:
The following table provides details about the events after realignment when Move behavior is the configured event behavior with Reassign set to Move:
| 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 | 17 | Partial Match for the To Measure |
Event2 | 1/1/2000 | /1/2005 | Route3 | Route4 | 30 | 48 | No Error |
Event2 | 1/1/2005 | <Null> | Route4 | Route4 | 43 | 48 | Partial Match for the From Measure |
Cover behavior (with Reassign set to Snap for abandonment)
If the routes are active from 1/1/2000, the realignment with abandonment is set to occur on 1/1/2005, and Recalibrate route downstream is unchecked, this has the following effects:
- Event1 is represented by two time slices since event measures are altered on one of the routes on which Event1 is located. There is a time slice from 1/1/2000 to 1/1/2005, with the measures from 0 on Route1 to 30 on Route3, and a time slice from 1/1/2005 to <Null> with two event records. The first Event1 record after realignment has measures from 0 on Route1 to 30 on RouteNew, and the second Event1 record has measures from 17 on the abandoned portion of Route2 (Route2_Ab) to 30 on the abandoned portion of Route3 (Route3_Ab).
- Event2 is represented by two time slices since event measures are altered on one of the routes on which Event2 is located. There is a time slice from 1/1/2000 to 1/1/2005, with the measures from 30 on Route1 to 48 on Route3, and a time slice from 1/1/2005 to <Null> with two event records. The first Event2 record after realignment has measures from 30 on the new route (RouteNew) to 48 on Route4, and the second Event2 record has measures from 30 on the abandoned portion of Route3 (Route3_Ab) to 42 on the abandoned portion of Route4 (Route4_Ab).
Before Cover event behavior (with Reassign set to Cover for abandonment)
The following image shows the routes before realignment:
The following table provides details about the events before realignment:
| Event ID | From Date | To Date | From RouteId | From Measure | To RouteID | To Measure |
|---|---|---|---|---|---|---|
Event1 | 1/1/2000 | <Null> | Route1 | 0 | Route3 | 30 |
Event2 | 1/1/2000 | <Null> | Route3 | 30 | Route4 | 48 |
After Cover event behavior (with Reassign set to Cover for abandonment)
A new route (RouteNew) is created in the realign section. For the abandoned portions of Route2, all of Route3, and Route4, the following routes are created: Route2_Ab, Route3_Ab, Route4_Ab.
The following image shows the routes after realignment:
The following table provides details about the events after realignment when Cover is the configured event behavior with Reassign set to Cover:
| Event ID | From Date | To Date | From RouteId | From Measure | To RouteId | To Measure | Location Error |
|---|---|---|---|---|---|---|---|
Event1 | 1/1/2000 | 1/1/2005 |
Route1 | 0 | Route3 | 30 | No Error |
Event1 | 1/1/2005 | <Null> |
Route1 | 0 | RouteNew | 30 | No Error |
Event1 | 1/1/2005 | <Null> |
Route2_Ab | 17 | Route3_Ab | 30 | No Error |
Event2 | 1/1/2000 | 1/1/2005 |
Route3 | 30 | Route4 | 48 | No Error |
Event2 | 1/1/2005 | <Null> |
RouteNew | 30 | Route4 | 48 | No Error |
Event2 | 1/1/2005 | <Null> |
Route3_Ab | 30 | Route4_Ab | 42 | No Error |
Retire behavior (with Reassign set to Retire for abandonment)
- If the realignment with abandonment is set to occur on 1/1/2005 from measure 17 on Route2 to measure 43 on Route4 and Recalibrate route downstream is unchecked, this has the following effects:
- Event1 retires since it is located within the realigned or abandoned region.
- Event2 retires since it is located within the realigned or abandoned region.
Before Retire behavior (with Reassign set to Retire)
The following image shows the routes before realignment:
The following table provides details about the events before realignment:
| 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 behavior (with Reassign set to Retire)
For the abandoned portions of Route2, Route3, and Route4, the following routes are created: Route2_Ab, Route3_Ab, Route4_Ab.
The following image shows the routes after realignment:
The following table provides details about events on LineA, which are retired after realignment with Reassign set to Retire:
| Event ID | From Date | To Date | From RouteId | To Route ID | From Measure | To Measure |
|---|---|---|---|---|---|---|
Event1 | 1/1/2000 | 1/1/2005 | Route1 | Route3 | 0 | 30 |
Event2 | 1/1/2000 | 1/1/2005 | Route3 | Route4 | 30 | 48 |
Snap behavior (with Reassign set to Stay Put for abandonment)
- If the realignment with abandonment is set to occur on 1/1/2005 from measure 17 on Route2 to measure 43 on Route4 and Recalibrate route downstream is unchecked, 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 measures from 0 on Route1 to 30 on Route3, and a time slice from 1/1/2005 to <Null>, with measures from 0 on Route1 to 17 on Route2.
- Event2 is represented by two time slices. There is a time slice from 1/1/2000 to 1/1/2005, with the measures from 30 on Route3 to 48 on Route4, and a time slice from 1/1/2005 to <Null>, with measures from 43 to 48 on Route4.
Before Snap behavior (with Reassign set to Stay Put)
The following image shows the routes before realignment:
The following table provides details about the events before realignment:
| 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 Snap behavior (with Reassign set to Stay Put)
A new route (RouteNew) are created in the realign section. For the abandoned portions of Route2, all of Route3, and Route4, the following routes are created: Route2_Ab, Route3_Ab, Route4_Ab.
The following image shows the routes after realignment:
The following table provides details about the events after realignment when Snap is the configured event behavior with Reassign set to Stay Put:
| Event ID | From Date | To Date | From RouteId | From Measure | To RouteId | To Measure | Location Error |
|---|---|---|---|---|---|---|---|
| Event1 | 1/1/2000 | 1/1/2005 | Route1 | 0 | Route3 | 30 | No Error |
| Event1 | 1/1/2005 | <Null> | Route1 | 0 | Route2 | 17 | No Error |
| Event2 | 1/1/2000 | 1/1/2005 | Route3 | 30 | Route4 | 48 | No Error |
| Event2 | 1/1/2005 | <Null> | Route4 | 43 | Route4 | 48 | No Error |
Detailed behavior on concurrent routes with Cover behavior
The following sections detail how the Cover event behavior rule is enforced when a route that has a concurrent section with a dominant route is realigned.
Concurrent routes before realignment with Cover behavior
In the following scenario, Route2 is realigned in a section that overlaps with a dominant concurrent route, Route1, while the Cover behavior is configured.
If the realignment is set to occur on 1/1/2005 and Recalibrate route downstream is 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 30, and a time slice from 1/1/2005 to <Null> with two event records. The upstream event record has measures from 0 to 15, and the downstream event record has measures from 25 to 40.
Before realignment of concurrent routes with Cover behavior and a nonspanning event
The following image shows the routes before realignment:
| Event ID | Route Name | From Date | To Date | From Measure | To Measure | Location Error |
|---|---|---|---|---|---|---|
| Event1 | Route1 | 1/1/2000 | <Null> |
0 | 30 | No Error |
After realignment of concurrent routes with Cover behavior and a nonspanning event
The following image shows the routes after realignment:
Event1 on Route1 is not present in the concurrent section of Route2 and Route1 as Route1 is the dominant route in that section.
The following table provides details about the event after realignment when Cover is the configured event behavior:
| Event ID | Route Name | From Date | To Date | From Measure | To Measure | Location Error |
|---|---|---|---|---|---|---|
| Event1 | Route1 | 1/1/2000 | 1/1/2005 |
0 | 30 | No Error |
| Event1 | Route1 | 1/1/2005 | <Null> |
0 | 15 | No Error |
| Event1 | Route1 | 1/1/2005 | <Null> |
25 | 40 | No Error |
Concurrent routes before realignment with Cover behavior and a spanning event
In the following scenario, Route2 and Route3 on LineA are realigned in a section that overlaps with a dominant concurrent route, Route1 on LineB, while the Cover behavior is configured.
If the realignment is set to occur on 1/1/2005 and Recalibrate route downstream is 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 on Route2 to 28 on Route3, and a time slice from 1/1/2005 to <Null> with an upstream and a downstream event record. The upstream record has measures from 0 to 16 on Route2, and the downstream record has measures from 20 to 36 on Route2.
Before realignment of concurrent routes with Cover behavior and a spanning event
The following image shows the routes before realignment:
The following table provides details about the event before realignment:
| Event ID | From Date | To Date | FromRoute Name | From Measure | ToRoute Name | To Measure | Location Error |
|---|---|---|---|---|---|---|---|
| Event1 | 1/1/2000 | <Null> |
Route2 | 0 | Route3 | 28 | No Error |
After realignment of concurrent routes with Cover behavior and a spanning event
The following image shows the routes after realignment:
Event1 on Route1 is not present in the concurrent section of Route2 and Route1, as Route1 is the dominant route in that section.
The following table provides details about the event after realignment when Cover is the configured event behavior:
| Event ID | From Date | To Date | FromRoute Name | From Measure | ToRoute Name | To Measure | Location Error |
|---|---|---|---|---|---|---|---|
| Event1 | 1/1/2000 | 1/1/2005 |
Route2 | 0 | Route3 | 28 | No Error |
| Event1 | 1/1/2005 | <Null> |
Route2 | 0 | Route2 | 16 | No Error |
| Event1 | 1/1/2005 | <Null> |
Route2 | 20 | Route2 | 36 | No Error |