Form a new route method

Available with Location Referencing license.

During route reassignment, 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 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:

The reassignment method, route edit, and event behaviors are described below.

Form a new route method

• A new route is created by merging source routes if multiple routes are selected in the source.
• A new route is created by splitting source route if a partial route is selected in the source.
• Route is renamed by selecting an entire route and providing a new route name or ID.

Upstream and downstream sections

Route editing impacts upstream and downstream sections differently.

The following image 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 LRS is time aware, routes and events are time sliced with edit activities, such as reassigning a route.

The following sections detail the two capabilities in 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 Route1 splits out and forms a new route in 2005. The graphics and tables below demonstrate the route information before and after the reassignment.

Before route reassignment

The following image 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

After route reassignment

The following image 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 image 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:

• Event1 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 From Date. The To Measure is changed to accommodate the new ending measure 5 of Route1.
• Event2 is retired on the date of reassignment because it fell entirely within the edit section.

The following image shows the routes and events after reassignment:

Note:

It is important to note that retired events are not drawn in the graphic above.

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	Loc 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:

• Event1 was partially in the edit section. It is retired on the date of reassignment, and a new event with the reassignment date as the From Date is created on the nonimpacted portion. Because the measures do not change for the Move behavior, there is a location error for the To Measure because that measure 7 no longer exists on Route1.
• Event2 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 Route1.

The following image 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 Event2 exists after the Apply Event Behaviors tool is run but has no shape.

Retire event behavior

Events intersecting the reassignment region are retired.

• Event1 was present in the edit section; it is retired on the date of reassignment.
• Event2 was present in the edit section; it is retired on the date of reassignment.

The following image shows the routes and events after reassignment:

Note:

It is important to note that retired events are not drawn in the graphic above.

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	Loc 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:

• Event1 was partially in the edit section. It is retired on the date of reassignment, and a new event with the reassignment date as the From Date is created on the nonimpacted portion of Route1.
• Part of Event1 that was in the impacted portion is snapped to the new route with the new measures underlying on RouteNew. It gets its From Date from the date of reassignment.
• Event2 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 From Date from the date of reassignment.

The following image 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 Route1 is renamed to RouteNew while maintaining its measures in 2005. The graphics and tables below demonstrate the route information before and after the reassignment.

Before route reassignment

The following image 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

After route reassignment

The following image 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 image 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 Route1 is reassigned to RouteNew, both the events retire.

• Event1 was entirely in the edit section; it is retired on the date of reassignment.
• Event2 was entirely in the edit section; it is retired on the date of reassignment.

The following image shows the routes and events after reassignment:

Note:

It is important to note that retired events are not drawn in the graphic above.

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:

• Event1 was entirely in the edit section. It is retired on the date of reassignment, and a new event with the reassignment date as the From Date is created. A location error is generated for the new event as the original route Route1 does not exist from 1/1/2005 as a new route RouteNew has taken its place, although the measures remain the same.
• Event2 was entirely in the edit section. It is retired on the date of reassignment, and a new event with the reassignment date as the From Date is created. A location error is generated for the new event as the original route Route1 does not exist from 1/1/2005 as a new route RouteNew has taken its place, although the measures remain the same.

The following image 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 Event1 and Event2 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 Route1 is reassigned to RouteNew, both the events retire.

• Event1 was entirely in the edit section; it is retired on the date of reassignment.
• Event2 was entirely in the edit section; it is retired on the date of reassignment.

The following image 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:

• Event1 was entirely in the edit section; it is retired on the date of reassignment, and a new event with the reassignment date as the From Date is created on the new route with the new measures underlying on RouteNew. The geographic location of the event is maintained.
• Event2 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 image 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 Route1 and Route2 into a new route, RouteM.
• The second reassignment splits Route3 at measure 28 and creates a new route called RouteS out of the original measure 28 to 35 on Route3 with target values of 0 to 20.
• The third reassignment renames Route4 to RouteR and maintains Route4's original measures.

The graphics and tables below demonstrate the route information before and after the reassignment.

Before route reassignment

The following image 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

After route reassignment

The following image 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 image 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 behavior

After the three separate reassignments described above, Event1 falls in the edit section. It is retired on the date of reassignment, and a new event with the reassignment date as the From Date is created. The new event is located only on part of the Route3 that was not impacted by the three edits.

The following image shows the routes and event after reassignment:

Note:

It is important to note that the retired event is not drawn in the graphic above.

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	Loc 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 behavior

After the three separate reassignments described above, Event1 was partially in the edit section. It is retired on the date of reassignment, and a new event with the reassignment date as the From 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 (Route1 and Route4) do not exist as of 1/1/2005.

The following image 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 Event1 exists after the Apply Event Behaviors tool is run but has no shape.

Retire behavior

After the three separate reassignments described above, Event1 was present in the edit section. It is retired on the date of reassignment.

The following image 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	Loc Error
Event1	Route1	Route4	1/1/2000	1/1/2005	0	48	No Error

Snap event behavior

After the three separate reassignments described above, Event1 was present in the edit section. It is retired on the date of reassignment, and a new event with the reassignment date as the From Date is created on the new routes with the new underlying measures to maintain its geographic location.

The following image 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