Transfer to another line method
Available with the Linear Referencing license.
When you reassign a route, events are impacted in the edit section and upstream and downstream of the reassignment, 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.
The following sections describe the Transfer to another line method and the corresponding event behaviors.
Transfer to another line method
The Transfer to another line method is for line networks only and supports the following:
Transfers routes to a new line if you provide a new line name.
Transfers routes to an adjacent line if you provide an existing line name.
Upstream and downstream sections
Route editing impacts upstream and downstream sections differently.
The following diagram shows the upstream and downstream section for the route reassignment scenario:
The following table details how the reassignment editing activity impacts upstream and downstream events according to the configured event behavior:
| Behavior | Events upstream reassignment | Events intersecting reassignment | Events downstream reassignment |
|---|---|---|---|
| Stay Put | No action | Retire event. Line events crossing the edit section are split and the original event is retired. | If route calibration is changed, the calibrate event behavior is applied; otherwise, no action is taken. |
| Move | Shape regenerated, if needed, to new location of route measures | Shape regenerated to the new location of route measures. | If route calibration is changed, the calibrate event behavior is applied; otherwise, no action is taken. |
| Retire | No action | Retire event. Line events crossing the reassign region do not split. | If route calibration is changed, the calibrate event behavior is applied; otherwise, no action is taken. |
| Snap | No action | Geographic location (x,y) is maintained. The event is migrated to the reassigned route. Line events crossing the edit section are split. | If route calibration is changed, the calibrate event behavior is applied; otherwise, no action is taken. |
Note:
The network can contain events that span routes in a line network. The behaviors are still applied in the same manner.
Because the linear referencing system (LRS) is time aware, routes and events are time sliced with edit activities, such as reassigning a route.
Transfer routes to a new line
In this example, there are two lines, each with three routes that are active from 1/1/2000. On 1/1/2005, all three routes within Line A are transferred to a new line, Line New.
Route 2 has changed its name.
Route 3 has changed measures in the reassignment.
The following graphics and tables demonstrate the route information before and after the reassignment.
Routes before reassignment
The following diagram shows the routes before reassignment:
The following table provides details about the routes before reassignment:
| 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> | 5 | 15 |
| Route3 | LineA | 300 | 1/1/2000 | <Null> | 20 | 40 |
| RouteA | LineB | 100 | 1/1/2000 | <Null> | 5 | 15 |
| RouteB | LineB | 200 | 1/1/2000 | <Null> | 0 | 10 |
| RouteC | LineB | 300 | 1/1/2000 | <Null> | 25 | 45 |
Routes after reassignment
The following diagram shows the routes after reassignment:
The following table provides details about the routes after reassignment:
| Route Name | Line Name | Line Order | From Date | To Date | From Measure | To Measure |
|---|---|---|---|---|---|---|
| Route1 | LineA | 100 | 1/1/2000 | 1/1/2005 | 0 | 10 |
| Route1 | LineNew | 100 | 1/1/2005 | <Null> | 0 | 10 |
| Route2 | LineA | 200 | 1/1/2000 | 1/1/2005 | 5 | 15 |
| Route2_new | LineNew | 200 | 1/1/2005 | <Null> | 5 | 15 |
| Route3 | LineA | 300 | 1/1/2000 | 1/1/2005 | 20 | 40 |
| Route3 | LineNew | 300 | 1/1/2005 | <Null> | 20 | 60 |
| RouteA | LineB | 100 | 1/1/2000 | <Null> | 5 | 15 |
| RouteB | LineB | 200 | 1/1/2000 | <Null> | 0 | 10 |
| RouteC | LineB | 300 | 1/1/2000 | <Null> | 25 | 45 |
Events before reassignment
The following diagram shows the routes and events before reassignment:
The following table provides details about the events before reassignment:
| Event | From Route Name | To Route Name | From Date | To Date | From Measure | To Measure |
|---|---|---|---|---|---|---|
| Event1 | Route1 | Route3 | 1/1/2000 | <Null> | 5 | 40 |
| Event2 | RouteA | RouteB | 1/1/2000 | <Null> | 5 | 5 |
The following sections detail how event behavior rules apply after you run the Apply Event Behaviors tool when the routes on Line A are transferred to a new line, Line New.
Stay Put event behavior
The Stay Put behavior maintains the geographic location of the event outside the reassign region, but the measures can change. The event can also split if it crosses the reassign region. The Stay Put behavior retires portions in the reassign region.
The route reassignment described previously has the following effects:
Event 1 is retired on the date of reassignment because it is entirely within the edit section.
Event 2 is not affected by the reassignment as it is in part of routes in Line B.
The following diagram shows the routes and events after reassignment:
Note:
The retired event is not drawn in the previous diagram.
The following table provides details about the events after reassignment when Stay Put is the configured event behavior:
| Event | From Route Name | To Route Name | From Date | To Date | From Measure | To Measure | Location Error |
|---|---|---|---|---|---|---|---|
| Event1 | Route1 | Route3 | 1/1/2000 | 1/1/2005 | 5 | 40 | No Error |
| Event2 | RouteA | RouteB | 1/1/2000 | <Null> | 5 | 5 | No Error |
Move event behavior
The Move behavior maintains the measures of the event, but the geographic location can change.
The route reassignment described previously has the following effects:
Event 1 is entirely in the edit section; it is retired on the date of reassignment, and a new event with the reassignment date as the start date is created. Because the measures do not change for the Move behavior, this new event still spans from measure 5 on Route 1 to measure 40 on Route 3, but its location has changed due to a change in the underlying measures in Route 3.
Event 2 is not affected by the reassignment as it is in Line B.
The following diagram shows the routes and events after reassignment:
The following table provides details about the events after reassignment when Move is the configured event behavior:
| Event | From Route Name | To Route Name | From Date | To Date | From Measure | To Measure | Location Error |
|---|---|---|---|---|---|---|---|
| Event1 | Route1 | Route3 | 1/1/2000 | 1/1/2005 | 5 | 40 | No Error |
| Event2 | RouteA | RouteB | 1/1/2000 | <Null> | 5 | 5 | No Error |
| Event1 | Route1 | Route3 | 1/1/2005 | <Null> | 5 | 40 | No Error |
Note:
The new Event 1 exists after the Apply Event Behaviors tool is run but has no shape.
Retire event behavior
The Retire behavior retires events that intersect the reassign region.
The route reassignment described previously has the following effects:
Event 1 is present in the edit section; it is retired on the date of reassignment.
Event 2 is not affected by the reassignment as it is in Line B.
The following diagram shows the routes and events after reassignment:
Note:
The retired event is not drawn in the previous diagram.
The following table provides details about the events after reassignment when Retire is the configured event behavior:
| Event | From Route Name | To Route Name | From Date | To Date | From Measure | To Measure | Location Error |
|---|---|---|---|---|---|---|---|
| Event1 | Route1 | Route3 | 1/1/2000 | 1/1/2005 | 5 | 40 | No Error |
| Event2 | RouteA | RouteB | 1/1/2000 | <Null> | 5 | 5 | No Error |
Snap event behavior
Snapping to the route that the event is reassigned to maintains the geographic location of the event, but the measures can change. The event gets a new time slice when the route it belongs to is reassigned to another line, whether or not the route name or measure changes in the reassignment. The event can also split if it crosses the reassign region.
The route reassignment described previously has the following effects:
Event 1 is present in the edit section; it is retired on the date of reassignment, and a new event with the reassignment date as the start date is created on the new routes with the new underlying measures to maintain its geographic location.
Event 2 is not affected by the reassignment as it is in Line B.
The following diagram shows the routes and events after reassignment:
The following table provides details about the events after reassignment when Snap is the configured event behavior:
| Event | From Route Name | To Route Name | From Date | To Date | From Measure | To Measure | Location Error |
|---|---|---|---|---|---|---|---|
| Event1 | Route1 | Route3 | 1/1/2000 | 1/1/2005 | 5 | 40 | No Error |
| Event1 | Route1 | Route3 | 1/1/2005 | <Null> | 5 | 60 | No Error |
| Event2 | RouteA | RouteB | 1/1/2000 | <Null> | 5 | 5 | No Error |
Transfer routes to an existing, adjacent line
In this example, there are two lines, each with three routes that are active from 1/1/2000. On 1/1/2005, a portion of Route 2 and the entire Route 3 within Line A are transferred to an existing line, Line B.
The reassign portion of Route 2 has a new route name.
Route 3 has changed measures in the reassignment.
The following graphics and tables demonstrate the route information before and after the reassignment.
Routes before reassignment
The following diagram shows the routes before reassignment:
The following table provides details about the routes before reassignment:
| 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> | 5 | 15 |
| Route3 | LineA | 300 | 1/1/2000 | <Null> | 20 | 40 |
| RouteA | LineB | 100 | 1/1/2000 | <Null> | 5 | 15 |
| RouteB | LineB | 200 | 1/1/2000 | <Null> | 0 | 10 |
| RouteC | LineB | 300 | 1/1/2000 | <Null> | 25 | 45 |
Routes after reassignment
The following diagram shows the routes after reassignment:
The following table provides details about the routes after reassignment:
| 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 | 1/1/2005 | 5 | 15 |
| Route2 | LineA | 200 | 1/1/2005 | <Null> | 5 | 10 |
| Route2_reassign | LineB | 100 | 1/1/2005 | <Null> | 10 | 15 |
| Route3 | LineA | 300 | 1/1/2000 | 1/1/2005 | 20 | 40 |
| Route3 | LineB | 200 | 1/1/2005 | <Null> | 20 | 60 |
| RouteA | LineB | 100 | 1/1/2000 | 1/1/2005 | 5 | 15 |
| RouteA | LineB | 300 | 1/1/2005 | <Null> | 5 | 15 |
| RouteB | LineB | 200 | 1/1/2000 | 1/1/2005 | 0 | 10 |
| RouteB | LineB | 400 | 1/1/2005 | <Null> | 0 | 10 |
| RouteC | LineB | 300 | 1/1/2000 | 1/1/2005 | 25 | 45 |
| RouteC | LineB | 500 | 1/1/2005 | <Null> | 25 | 45 |
Events before reassignment
The following diagram shows the routes and events before reassignment:
The following table provides details about the events before reassignment:
| Event | From Route Name | To Route Name | From Date | To Date | From Measure | To Measure |
|---|---|---|---|---|---|---|
| Event1 | Route1 | Route3 | 1/1/2000 | <Null> | 5 | 40 |
| Event2 | RouteA | RouteB | 1/1/2000 | <Null> | 5 | 5 |
The following sections detail how event behavior rules apply after you run the Apply Event Behaviors tool when the routes on Line A are transferred to Line B.
Stay Put event behavior
The Stay Put behavior maintains the geographic location of the event outside the reassign region, but the measures can change. The event can also split if it crosses the reassign region. The Stay Put behavior retires portions in the reassign region.
The route reassignment described previously has the following effects:
Event 1 falls in the edit section; it is retired on the date of reassignment, and a new event with the reassignment date as the start date is created. The new event is located only on Route 1 and the part of Route 2 that the edit did not impact.
Even though the line orders have changed on the three routes on Line B, Event 2 is not affected by the reassignment, because it can still locate the start and end routes and measures.
The following diagram shows the routes and events after reassignment:
Note:
The retired event is not drawn in the previous diagram.
The following table provides details about the events after reassignment when Stay Put is the configured event behavior:
| Event | From Route Name | To Route Name | From Date | To Date | From Measure | To Measure | Location Error |
|---|---|---|---|---|---|---|---|
| Event1 | Route1 | Route3 | 1/1/2000 | 1/1/2005 | 5 | 40 | No Error |
| Event1 | Route1 | Route2 | 1/1/2005 | <Null> | 5 | 10 | No Error |
| Event2 | RouteA | RouteB | 1/1/2000 | <Null> | 5 | 5 | No Error |
Move event behavior
The Move behavior maintains the measures of the event, but the geographic location can change.
The route reassignment described previously has the following effects:
Event 1 is partially in the edit section; it is retired on the date of reassignment, and a new event with the reassignment date as the start date is created. The Move behavior does not allow changing the start and end route IDs or measures of the event. It returns a location error because Route 1 and Route 3 are now on different lines, but the event cannot span across lines.
Even though the line orders have changed on the three routes on Line B, Event 2 is not affected by the reassignment, because it can still locate the start and end routes and measures.
The following diagram shows the routes and events after reassignment:
The following table provides details about the events after reassignment when Move is the configured event behavior:
| Event | From Route Name | To Route Name | From Date | To Date | From Measure | To Measure | Location Error |
|---|---|---|---|---|---|---|---|
| Event1 | Route1 | Route3 | 1/1/2000 | 1/1/2005 | 5 | 40 | No Error |
| Event2 | RouteA | RouteB | 1/1/2000 | <Null> | 5 | 5 | No Error |
| Event1 | Route1 | Route3 | 1/1/2005 | <Null> | 5 | 40 | Different From And To Route Line IDs |
Note:
The new Event 1 exists after the Apply Event Behaviors tool is run but has no shape.
Retire event behavior
The Retire behavior retires events that intersect the reassign region.
The route reassignment described previously has the following effects:
Event 1 is present in the edit section; it is retired on the date of reassignment.
Even though the line orders have changed on the three routes on Line B, Event 2 is not affected by the reassignment, because it can still locate the start and end routes and measures.
The following diagram shows the routes and events after reassignment:
Note:
The retired event is not drawn in the previous diagram.
The following table provides details about the events after reassignment when Retire is the configured event behavior:
| Event | From Route Name | To Route Name | From Date | To Date | From Measure | To Measure | Location Error |
|---|---|---|---|---|---|---|---|
| Event1 | Route1 | Route3 | 1/1/2000 | 1/1/2005 | 5 | 40 | No Error |
| Event2 | RouteA | RouteB | 1/1/2000 | <Null> | 5 | 5 | No Error |
Snap event behavior
Snapping to the route that the event is reassigned to maintains the geographic location of the event, but the measures can change. The event gets a new time slice when the route it belongs to is reassigned to another line, whether or not the route name or measure changes in the reassignment. The event can also split if it crosses the reassign region.
The route reassignment described previously has the following effects:
Event 1 is partially in the edit section; it is retired on the date of reassignment, and a new event with the reassignment date as the start date is created on the nonimpacted portion from Route 1 to measure 10 of Route 2.
The part of Event 1 that was in the impacted portion is snapped to the new routes with the new measures: from measure 10 of Route 2_reassign to measure 60 of Route 3. It gets its From Date from the date of reassignment.
Even though the line orders have changed on the three routes on Line B, Event 2 is not affected by the reassignment, because it can still locate the start and end routes and measures.
The following diagram shows the routes and events after reassignment:
The following table provides details about the events after reassignment when Snap is the configured event behavior:
| Event | From Route Name | To Route Name | From Date | To Date | From Measure | To Measure | Location Error |
|---|---|---|---|---|---|---|---|
| Event1 | Route1 | Route3 | 1/1/2000 | 1/1/2005 | 5 | 40 | No Error |
| Event1 | Route1 | Route2 | 1/1/2005 | <Null> | 5 | 10 | No Error |
| Event1 | Route2_reassign | Route3 | 1/1/2005 | <Null> | 10 | 60 | No Error |
| Event2 | RouteA | RouteB | 1/1/2000 | <Null> | 5 | 5 | No Error |