Form a new route 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 Form a new route method and the corresponding event behaviors.
Form a new route method
The Form a new route method supports the following:
Merges source routes into a new route when you select multiple routes in the source.
Splits a source route into a new route when you select a partial route in the source.
Renames a route when you select an entire route and provide a new route name or ID.
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 reassignment 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.
The following sections detail two capabilities in the Form a new route method: splitting and renaming. Additional capabilities, such as merging, work similarly to the Merge to adjacent route method.
Form a new route by splitting an existing route
In this example, the routes are active from 1/1/2000. Reassignment is set to occur on 1/1/2005, where the second half of Route 1 splits out and forms a new route in 2005. 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 | From Date | To Date | From Measure | To Measure |
|---|---|---|---|---|
| Route1 | 1/1/2000 | <Null> | 0 | 10 |
Routes after reassignment
The following diagram shows the routes after reassignment:
The following table provides details about the routes after reassignment:
| Route Name | From Date | To Date | From Measure | To Measure |
|---|---|---|---|---|
| Route1 | 1/1/2000 | 1/1/2005 | 0 | 10 |
| Route1 | 1/1/2005 | <Null> | 0 | 5 |
| RouteNew | 1/1/2005 | <Null> | 0 | 5 |
Events before reassignment
The following diagram shows the routes and events before reassignment:
The following table provides details about the events before reassignment:
| 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 | 10 |
The following sections detail how event behavior rules are enforced after running the Apply Event Behaviors tool, when a new route is created by splitting from the source route.
Stay Put event behavior
Although the geographic location of the event outside the reassign region is maintained, the measures can change. The event can also split if it crosses the reassign region. Portions in the reassign region are retired.
The route reassignment described above has the following effects:
Event 1 was partially in the edit section. It is retired on the date of reassignment, and a new event is created on the nonimpacted portion with the reassignment date as the start date. The end measure is changed to accommodate the new end measure 5 of Route 1.
Event 2 is retired on the date of reassignment because it fell entirely within the edit section.
The following diagram shows the routes and events after reassignment:
Note:
Retired events are 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 | 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 | 5 | No Error |
| Event2 | Route1 | 1/1/2000 | 1/1/2005 | 7 | 10 | No Error |
Move event behavior
Although the measures of the event are maintained, the geographic location can change.
The route reassignment described above has the following effects:
Event 1 was 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. Because the measures do not change for the Move behavior, a location error occurs for the end measure since measure 7 no longer exists on Route 1.
Event 2 is retired on the date of reassignment since it fell within the edit section. From the date of reassignment, a new event is created. Because the measures remain same, the newly produced event receives the location error because both its From and To measures cannot be found on Route 1.
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 | 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 | 10 | No Error |
| Event1 | Route1 | 1/1/2005 | <Null> | 0 | 7 | Partial Match For The To Measure |
| Event2 | Route1 | 1/1/2005 | <Null> | 7 | 10 | Measure Extent Out of Route Measure Range |
Note:
The new Event 2 exists after the Apply Event Behaviors tool is run but has no shape.
Retire event behavior
Events intersecting the reassignment region are retired.
The route reassignment described above has the following effects:
Event 1 was present in the edit section; it is retired on the date of reassignment.
Event 2 was present in the edit section; it is retired on the date of reassignment.
The following diagram shows the routes and events after reassignment:
Note:
Retired events are not drawn in the previous diagram.
The following table provides details about the events after reassignment 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 | 10 | No Error |
Snap event behavior
Although the geographic location of the event is maintained by snapping to the route that it was reassigned to, the measures can change. The event can also split if it crosses the reassign region.
The route reassignment described above has the following effects:
Event 1 was 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 of Route 1.
Part of Event 1 that was in the impacted portion is snapped to the new route with the new measures underlying on RouteNew. It gets its start date from the date of reassignment.
Event 2 is retired on the date of reassignment since it fell within the edit section. From the date of reassignment, a new event is created snapped to the new route with the new measures underlying on RouteNew. It gets its start date from the date of reassignment.
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 | 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 | 5 | No Error |
| Event1 | RouteNew | 1/1/2005 | <Null> | 0 | 2 | No Error |
| Event2 | Route1 | 1/1/2000 | 1/1/2005 | 7 | 10 | No Error |
| Event2 | RouteNew | 1/1/2005 | <Null> | 2 | 5 | No Error |
Form a new route by renaming an existing route
In this example, the routes are active from 1/1/2000. Reassignment is set to occur on 1/1/2005, where Route 1 is renamed to RouteNew while maintaining its measures in 2005. 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 | From Date | To Date | From Measure | To Measure |
|---|---|---|---|---|
| Route1 | 1/1/2000 | <Null> | 0 | 10 |
Route after reassignment
The following diagram shows the routes after reassignment:
The following table provides details about the routes after reassignment:
| Route Name | From Date | To Date | From Measure | To Measure |
|---|---|---|---|---|
| Route1 | 1/1/2000 | 1/1/2005 | 0 | 10 |
| RouteNew | 1/1/2005 | <Null> | 0 | 10 |
Events before reassignment
The following diagram shows the routes and events before reassignment:
The following table provides details about the events before reassignment:
| 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 | 10 |
The following sections detail how event behavior rules are enforced after running the Apply Event Behaviors tool, when a new route is created by renaming a source route.
Stay Put event behavior
Although the geographic location of the event outside the reassign region is maintained, the measures can change. The event can also split if it crosses the reassign region. Portions in the reassign region are retired.
Since the entire route Route 1 is reassigned to RouteNew, both events retire, as follows:
Event 1 was entirely in the edit section; it is retired on the date of reassignment.
Event 2 was entirely in the edit section; it is retired on the date of reassignment.
The following diagram shows the routes and events after reassignment:
Note:
Retired events are 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 | Route Name | From Date | To Date | From Measure | To Measure |
|---|---|---|---|---|---|
| Event1 | Route1 | 1/1/2000 | 1/1/2005 | 0 | 7 |
| Event2 | Route1 | 1/1/2000 | 1/1/2005 | 7 | 10 |
Move event behavior
Although the measures of the event are maintained, the geographic location can change.
The route renaming scenario described above has the following effects:
Event 1 was 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. A location error is generated for the new event because the original route, Route 1, does not exist as of 1/1/2005; a new route, RouteNew, has taken its place, although the measures remain the same.
Event 2 was 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. A location error is generated for the new event because the original route, Route 1, does not exist as of 1/1/2005; a new route, RouteNew, has taken its place, although the measures remain the same.
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 | 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 | 10 | No Error |
| Event1 | Route1 | 1/1/2005 | <Null> | 0 | 7 | Route Not Found |
| Event2 | Route1 | 1/1/2005 | <Null> | 7 | 10 | Route Not Found |
Note:
The new Event 1 and Event 2 exist after the Apply Event Behaviors tool is run but have no shape.
Retire event behavior
Events intersecting the reassignment region are retired. Since the entire route Route 1 is reassigned to RouteNew, both events retire, as follows:
Event 1 was entirely in the edit section; it is retired on the date of reassignment.
Event 2 was entirely in the edit section; it is retired on the date of reassignment.
The following diagram shows the routes and events after reassignment:
The following table provides details about the events after reassignment when Retire is the configured event behavior:
| Event | Route Name | From Date | To Date | From Measure | To Measure |
|---|---|---|---|---|---|
| Event1 | Route1 | 1/1/2000 | 1/1/2005 | 0 | 7 |
| Event2 | Route1 | 1/1/2000 | 1/1/2005 | 7 | 10 |
Snap event behavior
Although the geographic location of the event is maintained by snapping to the route that it was reassigned to, the measures can change. The event can also split if it crosses the reassign region.
The route renaming scenario described above has the following effects:
Event 1 was 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 on the new route with the new measures underlying on RouteNew. The geographic location of the event is maintained.
Event 2 is retired on the date of reassignment since it fell within the edit section. From the date of reassignment, a new event is created snapped to the new route with the new measures underlying on RouteNew.
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 | 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 | RouteNew | 1/1/2005 | <Null> | 0 | 7 | No Error |
| Event2 | Route1 | 1/1/2000 | 1/1/2005 | 7 | 10 | No Error |
| Event2 | RouteNew | 1/1/2005 | <Null> | 7 | 10 | No Error |
Detailed behavior results on routes in a line network with events that span routes
In this example, there are four routes on the same line, and the routes are active from 1/1/2000. On 1/1/2005, three separate reassignments are set to occur.
The first reassignment merges Route 1 and Route 2 into a new route, Route M.
The second reassignment splits Route 3 at measure 28 and creates a new route called Route S out of the original measure 28 to 35 on Route 3 with target values of 0 to 20.
The third reassignment renames Route 4 to Route R and maintains Route 4's original measures.
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> | 12 | 22 |
| Route3 | LineA | 300 | 1/1/2000 | <Null> | 25 | 35 |
| Route4 | LineA | 400 | 1/1/2000 | <Null> | 38 | 48 |
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 |
| Route2 | LineA | 200 | 1/1/2000 | 1/1/2005 | 12 | 22 |
| RouteM | LineA | 100 | 1/1/2005 | <Null> | 0 | 20 |
| Route3 | LineA | 300 | 1/1/2000 | 1/1/2005 | 25 | 35 |
| Route3 | LineA | 200 | 1/1/2005 | <Null> | 25 | 28 |
| RouteS | LineA | 300 | 1/1/2005 | <Null> | 0 | 20 |
| Route4 | LineA | 400 | 1/1/2000 | 1/1/2005 | 38 | 48 |
| RouteR | LineA | 400 | 1/1/2005 | <Null> | 38 | 48 |
Events before reassignment
The following diagram shows the routes and event before reassignment:
The following table provides details about the spanning event before reassignment:
| Event ID | From Date | To Date | From Route Name | To Route Name | From Measure | To Measure |
|---|---|---|---|---|---|---|
| Event1 | 1/1/2000 | <Null> | Route1 | Route4 | 0 | 48 |
The following sections detail how event behavior rules are enforced when routes on a line in a line network are reassigned.
Stay Put event behavior
After the three separate reassignments described above, 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 part of Route 3 that was not impacted by the three edits.
The following diagram shows the routes and event after reassignment:
Note:
The retired event is not drawn in the previous diagram.
The following table provides details about the event 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 | Route4 | 1/1/2000 | 1/1/2005 | 0 | 48 | No Error |
| Event1 | Route3 | Route3 | 1/1/2005 | <Null> | 25 | 28 | No Error |
Move event behavior
After the three separate reassignments described above, Event 1 was 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 From and To route IDs or measures of the event. It returns a location error because both the From and To routes (Route 1 and Route 4) do not exist as of 1/1/2005.
The following diagram shows the routes and event after reassignment:
The following table provides details about the event after reassignment when Move is the configured event behavior:
| Event ID | From Date | To Date | From Route Name | To Route Name | From Measure | To Measure | Location Error |
|---|---|---|---|---|---|---|---|
| Event1 | 1/1/2000 | 1/1/2005 | Route1 | Route4 | 0 | 48 | No Error |
| Event1 | 1/1/2005 | <Null> | Route1 | Route4 | 0 | 48 | Route Not Found |
Note:
The new Event 1 exists after the Apply Event Behaviors tool is run but has no shape.
Retire event behavior
After the three separate reassignments described above, Event 1 was present in the edit section. It is retired on the date of reassignment.
The following diagram shows the routes and event after reassignment:
The following table provides details about the event 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 | Route4 | 1/1/2000 | 1/1/2005 | 0 | 48 | No Error |
Snap event behavior
After the three separate reassignments described above, Event 1 was 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.
The following diagram shows the routes and event after reassignment:
The following table provides details about the event after reassignment when Snap is the configured event behavior:
| Event | From Date | To Date | From Route Name | To Route Name | From Measure | To Measure | Location Error |
|---|---|---|---|---|---|---|---|
| Event1 | 1/1/2000 | 1/1/2005 | Route1 | Route4 | 0 | 48 | No Error |
| Event1 | 1/1/2005 | <Null> | RouteM | RouteR | 0 | 48 | No Error |