Route reassignment

Available with Location Referencing license.

Reassignment is the technique by which all or a portion of a route or line is moved, or reassigned, to the immediate upstream or downstream of another route or line. Another example is to redesignate a portion of a road that now falls on the other side of a boundary after administrative boundaries change.

In addition to route reassignment, the Reassign tool can update attribute fields and calibration points located along the reassigned route.

Scenarios that can be accomplished using the reassign activity are described below.

Note:

In the scenarios described below, you can choose entire routes or partial routes.

Route merges to an existing route

RouteX and RouteY are adjoining routes. You can use the Reassign tool to merge RouteX with RouteY or vice versa. The existing RouteX and RouteY are retired and a new RouteY is created on the date of reassignment. You can merge the reassigned portion to any immediate upstream or downstream route.

Before reassignment table:

Route ID	From Date	To Date
RouteX	1/1/2005	<Null>
RouteY	1/1/2005	<Null>

The following are inputs used for the Reassign tool.

Method	Merge to adjacent route
Source
Route ID	RouteX
From Measure	0
To Measure	20
Target
Route ID	RouteY
From Measure	0
To Measure	30

After reassignment table:

Route ID	From Date	To Date
RouteX	1/1/2005	1/1/2010
RouteY	1/1/2005	1/1/2010
RouteY	1/1/2010	<Null>

Split to an existing route

RouteXYZ has measures from 0 to 30. In the following example, the route is split in two: a new Route1 and a new version of RouteXYZ. The existing RouteXYZ is retired as a result of this operation.

Before reassignment table:

Route ID	From Date	To Date
RouteXYZ	1/1/2005	<Null>

The following are inputs used for the Reassign tool.

Method	Form a new route
Source
Route ID	RouteXYZ
From Measure	0
To Measure	19
Target
Route ID	Route1 (new)
From Measure	10
To Measure	29

After reassignment table:

Route ID	From Date	To Date
RouteXYZ	1/1/2005	1/1/2010
RouteXYZ	1/1/2010	<Null>
Route1	1/1/2010	<Null>

Route is renamed

You can rename an existing route and change its start (From) and end (To) measure values using the Reassign tool. In the following example, RouteXYZ is renamed Route123 and contains new measures. The existing RouteXYZ is retired as a result of this operation.

Note:

If all route records across all time slices need to be renamed without generating additional time slices, use the Rename tool.

Before reassignment table:

Route ID	From Date	To Date
RouteXYZ	1/1/2005	<Null>

The following are inputs used for the Reassign tool.

Method	Form a new route
Source
Route ID	RouteXYZ
From Measure	0
To Measure	30
Target
Route	Route123
From Measure	15
To Measure	45

After reassignment table:

Route ID	From Date	To Date
RouteXYZ	1/1/2005	1/1/2010
Route123	1/1/2010	<Null>

Calibration point transfers to a target route

You can transfer calibration points to a target route on networks that have a user-created Route ID.

Note:

The option to transfer calibration points to a target route during reassignment is checked by default and is the preferred method to maintain established measures.

Before reassignment table:

Route ID	From Date	To Date
RouteX	1/1/2005	<Null>
RouteY	1/1/2005	<Null>

The following are inputs used for the Reassign tool.

Method	Merge to adjacent route
Source
Route ID	RouteX
From Measure	0
To Measure	20
Target
Route	RouteY
From Measure	0
To Measure	30

After reassignment table:

Route ID	From Date	To Date
RouteX	1/1/2005	1/1/2010
RouteY	1/1/2005	1/1/2010
RouteY	1/1/2010	<Null>

Downstream recalibration

The following examples describe downstream recalibration. You can choose whether to recalibrate the source route downstream when you reassign routes.

Reassignment with the source route not calibrated downstream

RouteX is split into two routes: RouteX and Route1. Route1 starts at the beginning of the old RouteX and ends at the middle of the old RouteX. The end measure value for the new Route1 is 3 instead of the suggested measure of 5. The downstream measures for RouteX remain intact because the Recalibrate route downstream check box is unchecked for the source route.

Before reassignment table:

Route ID	From Date	To Date
RouteX	1/1/2005	<Null>
RouteY	1/1/2005	<Null>

The following are the inputs used for the Reassign tool.

Method	Form a new route
Source
From Route	RouteX
From Measure	0
To Route (option only for networks with lines)	RouteX
To Measure	5
Target
Route	Route1 (new)
From Measure	0
To Measure	3

After reassignment table:

Route ID	From Date	To Date
RouteX	1/1/2005	1/1/2010
RouteY	1/1/2005	1/1/2010
RouteX	1/1/2010	<Null>
RouteY	1/1/2010	<Null>
Route1	1/1/2010	<Null>

Reassignment with the source route calibrated downstream

RouteX is split into two routes: RouteX and Route1. Route1 starts at the beginning of the old RouteX and ends at the middle of the old RouteX. The end measure value for the new Route1 is 3 instead of the suggested measure of 5. If the Recalibrate route downstream check box is checked for the source route, the downstream route's (RouteX) measures change to a starting measure value of 0 and ending measure value of 5.

Before reassignment table:

Route ID	From Date	To Date
RouteX	1/1/2005	<Null>
RouteY	1/1/2005	<Null>

The following are the inputs used for the Reassign tool:

Method	Form a new route
Source
From Route	RouteX
From Measure	0
To Route (option only for networks with lines)	RouteX
To Measure	5
Target
Route	Route1 (new)
From Measure	0
To Measure	3

After reassignment table:

Route ID	From Date	To Date
RouteX	1/1/2005	1/1/2010
RouteY	1/1/2005	1/1/2010
RouteX	1/1/2010	<Null>
RouteY	1/1/2010	<Null>
Route1	1/1/2010	<Null>

Reassignment with the target route calibrated downstream

A part of RouteX is merged with the adjoining route, RouteY. The reassignment takes place from the middle of RouteX on the downstream side. Because the Recalibrate route downstream check box is checked for the target route, the measure of RouteY downstream of the reassigned portion is recalibrated. The new version of RouteY now has an end measure value of 9.

Before reassignment table:

Route ID	From Date	To Date
RouteX	1/1/2005	<Null>
RouteY	1/1/2005	<Null>

The following are the inputs used for the Reassign tool:

Method	Merge to adjacent route
Source
From Route	RouteX
From Measure	5
To Measure	10
Target
Route	RouteY
From Measure	0
To Measure	9

After reassignment table:

RouteX	1/1/2005	1/1/2010
RouteY	1/1/2005	1/1/2010
RouteX	1/1/2010	<Null>
RouteY	1/1/2010	<Null>

Complex route reassignment scenarios

Complex route reassignment scenarios for complex routes and shapes, including loop, lollipop, branch, and barbell shapes are described below.

Reassignment resulting in a loop

In the following example, RouteX and RouteY are merged to create a loop route after reassignment. RouteX has measures 0 to 2 and RouteY has measures 2 to 4:

The following are the inputs used for the Reassign tool:

Method	Merge to adjacent route
Source
From Route	RouteX
From Measure	0
To Measure	2
Recalibrate source route	No
Target
To Route	RouteY
From Measure	0
To Measure	2
Recalibrate target route	No

After reassignment, a calibration point is added at measure 1, and RouteY is recalibrated with measures 0 to 4.

Split to an existing loop

In the following example, RouteX, on a loop with measures 0 to 12, is split and the edit section is reassigned to a new route (RouteY):

The following are the inputs used for the Reassign tool:

Method	Form a new route
Source
From Route	RouteX
From Measure	0
To Measure	4
Recalibrate source route	Yes
Target
To Route	RouteY
From Measure	0
To Measure	4

After reassignment, RouteY is created with measures 0 to 4. The calibration point formerly at 8 is updated to 4, and RouteX is recalibrated with measures 0 to 8.

Reassignment resulting in a lollipop

RouteX has measures 0 to 4 and RouteY has measures 0 to 1. In the following example, a loop route (RouteX) is merged with a simple route (RouteY) to create a lollipop route after reassignment:

The following are the inputs used for the Reassign tool:

Method	Merge to adjacent route
Source
From Route	RouteX
From Measure	0
To Measure	4
Recalibrate source route	No
Target
To Route	RouteY
From Measure	1
To Measure	5
Recalibrate target route	Yes

After reassignment, the resulting lollipop route (RouteY) has updated measures 0 to 5.

Splits to an existing lollipop

RouteX has measures 0 to 5 and RouteY has measures 0 to 1. In the following example, the stick portion of a lollipop route (RouteX) is split and reassigned to an existing route (RouteY):

The following are the inputs used for the Reassign tool:

Method	Merge to adjacent route
Source
From Route	RouteX
From Measure	0
To Measure	1
Recalibrate source route	Yes
Target
To Route	RouteY
From Measure	0
To Measure	1
Recalibrate target route	Yes

After reassignment, both routes are recalibrated. The updated simple route (RouteY) has measures 0 to 2, and the loop route (RouteX) has measures 0 to 4.

Routes that merge to create a barbell

In the following example, a loop route (RouteX) with measures 0 to 4 is merged with a lollipop route (RouteY) that has measures from 0 to 5:

The following are the inputs used for the Reassign tool:

Method	Merge to adjacent route
Source
From Route	RouteX
From Measure	0
To Measure	4
Recalibrate source route	No
Target
Target Route	RouteY
From Measure	5
To Measure	9
Recalibrate target route	Yes

After reassignment, a new barbell route (RouteY) is created from the merged routes. RouteY has recalibrated measures from 0 to 9.

Simple route merges to create a branch

In this example, a simple route (RouteY) is merged to another simple route (RouteX) to create a branch route after reassignment. RouteX has measures 0 to 6, while RouteY has measures from 5 to 10.

The following are the inputs used for the Reassign tool:

Method	Merge to adjacent route
Source
From Route	RouteY
From Measure	5
To Measure	10
Recalibrate source route	No
Target
To Route	RouteX
From Measure	6
To Measure	11
Recalibrate target route	Yes

After reassignment, RouteY is merged with RouteX to create a branch route with recalibrated measures 0 to 11.

Splits on an infinity route

In the following example, an existing infinity route (RouteX) with measures 0 to 24 is split to create an alpha route and a new simple route (RNew):

The following are the inputs used for the Reassign tool:

Method	Form a new route
Source
From Route	RouteX
From Measure	18
To Measure	24
Recalibrate source route	Yes
Target
To Route	RNew
From Measure	0
To Measure	6

After reassignment, RouteX is an alpha route with measures 0 to 18, and RNew has measures 0 to 6.

Route reassignment in a line network

Routes in a line network can be reassigned to new or existing routes as shown in the following examples.

Multiple routes merge to a new route

RouteX, RouteY, and RouteZ are consecutive routes that belong to the same line Line1. You can use the Reassign tool to merge all of them together into a new route, RouteXYZ, that belongs to the same line. The date of reassignment is 1/1/2010.

The following shows routes before reassignment:

Route Name	Line Name	From Date	To Date	Line Order
RouteX	Line1	1/1/2005	<Null>	100
RouteY	Line1	1/1/2005	<Null>	200
RouteZ	Line1	1/1/2005	<Null>	300

The following are inputs used for the Reassign tool.

Method	Form a new route
Source
From Route	RouteX
From Measure	10
To Route	RouteZ
To Measure	60
Target
Route	RouteXYZ
From Measure	0
To Measure	30

RouteXYZ has the line order of 100. RouteX, RouteY, and RouteZ are retired as a result of this operation. You can choose new start and end measure values for RouteXYZ.

The following shows routes after reassignment.

Route Name	Line Name	From Date	To Date	Line Order
RouteX	Line1	1/1/2005	1/1/2010	100
RouteY	Line1	1/1/2005	1/1/2010	200
RouteZ	Line1	1/1/2005	1/1/2010	300
RouteXYZ	Line1	1/1/2010	<Null>	100

Note:

• Both the From Route and the To Route values from Source can be partially reassigned.
• Line orders of the remaining routes in the source line may be recalculated as a result.

Route merges to an existing route

RouteX and RouteY are consecutive routes that belong to Line1. You can use the Reassign tool to merge them with RouteZ, which belongs to the adjoining Line2. The date of reassignment is 1/1/2010.

The following shows routes before reassignment:

Route Name	Line Name	From Date	To Date	Line Order
RouteX	Line1	1/1/2005	<Null>	100
RouteY	Line1	1/1/2005	<Null>	200
RouteZ	Line2	1/1/2005	<Null>	100

The following inputs are used for the Reassign tool:

Method	Merge to adjacent route
Source
From Route	RouteX
From Measure	10
To Route	RouteY
To Measure	40
Target
Route	RouteZ
From Measure	0
To Measure	20

The target is recalibrated downstream.

RouteX, RouteY, and RouteZ are retired because of this operation. In this case, the reassign portion is from the start of RouteX to the end of RouteY.

The following shows routes after reassignment.

Route Name	Line Name	From Date	To Date	Line Order
RouteX	Line1	1/1/2005	1/1/2010	100
RouteY	Line1	1/1/2005	1/1/2010	200
RouteZ	Line2	1/1/2005	1/1/2010	100
RouteZ	Line2	1/1/2010	<Null>	100

Note:

• Any one of the From Route and the To Route values from Source can be partially reassigned to any immediate upstream or downstream route.
• Line orders of the remaining routes in the source line may be recalculated as a result.
• Routes from one line can be merged to an adjoining route in another line. Either one of the Source From or To routes of one line should be touching either start or end of the target route in another line.
• Routes from a line can be merged to an existing adjoining route in the same line.

Route splits

RouteZ has measures from 40 to 60. As shown in this example, you can split the route into two: RouteY, which is a new route, and a new version of RouteZ.

The following shows routes before reassignment.

Route Name	Line Name	From Date	To Date	Line Order
RouteX	Line1	1/1/2005	<Null>	100
RouteZ	Line1	1/1/2005	<Null>	200

The following inputs are used for the Reassign tool.

Method	Form a new route
Source
From Route	RouteZ
From Measure	40
To Route	RouteZ
To Measure	50
Target
Route	RouteY
From Measure	30
To Measure	40

The source is not recalibrated downstream.

The existing RouteZ retires as a result of this operation. RouteY has the line order of RouteZ, and the new version of RouteZ has the next line order value.

The following shows routes after reassignment.

Route Name	Line Name	From Date	To Date	Line Order
RouteX	Line1	1/1/2005	<Null>	100
RouteZ	Line1	1/1/2005	1/1/2010	200
RouteY	Line1	1/1/2010	<Null>	200
RouteZ	Line1	1/1/2010	<Null>	300

Note:

• Choose the same From and To source route to split a single route.
• Line orders of the remaining routes in the source line may be recalculated as a result.

Route splits and merges

RouteY has measures from 30 to 40. As shown in this example, you can split the route and then merge one of the parts to the adjoining route RouteZ.

The following shows routes before reassignment.

Route Name	Line Name	From Date	To Date	Line Order
RouteX	Line1	1/1/2005	<Null>	100
RouteY	Line1	1/1/2005	<Null>	200
RouteZ	Line1	1/1/2005	<Null>	300

The following are inputs for the Reassign tool.

Method	Merge to adjacent route
Source
From Route	RouteY
From Measure	35
To Route	RouteY
To Measure	40
Target
Route	RouteZ
From Measure	45
To Measure	50

The existing RouteY and RouteZ retire because of this operation. The new version of RouteY has the same line order as the previous one. The other split part of RouteY is merged to RouteZ.

The following shows routes after reassignment.

RouteX	Line1	1/1/2005	<Null>	100
RouteY	Line1	1/1/2005	1/1/2010	200
RouteZ	Line1	1/1/2005	1/1/2010	300
RouteY	Line1	1/1/2010	<Null>	200
RouteZ	Line1	1/1/2010	<Null>	300

Route is renamed

You can rename an existing route and change its start and end measure values with the help of the Reassign tool. RouteX is renamed RouteX_New and has new measures. The line order remains the same. The existing RouteX retires because of this operation.

The following shows routes before reassignment.

Route Name	Line Name	From Date	To Date	Line Order
RouteX	Line1	1/1/2005	<Null>	100

Note:

If all of the route records across all of the time slices need to be renamed without generating more time slices, use the Rename tool.

The following are inputs used for the Reassign tool.

Method	Form a new route
Source
From Route	RouteX
From Measure	10
To Route	RouteX
To Measure	20
Target
Route	RouteX_New
From Measure	10.1
To Measure	20.1

The following shows routes after reassignment.

Route Name	Line Name	From Date	To Date	Line Order
RouteX	Line1	1/1/2005	1/1/2010	100
RouteX_New	Line1	1/1/2010	<Null>	100

Route transfers to an existing line

Routes can be transferred entirely or partially to an existing line. In this case, the reassign portion should be either on the upstream or downstream ends of the source line. As shown in the example RouteZ belongs to Line2. You can take RouteZ from Line2 and transfer it to an existing adjoining line Line1.

The following shows routes before reassignment.

Route Name	Line Name	From Date	To Date	Line Order
RouteX	Line1	1/1/2005	<Null>	100
RouteY	Line1	1/1/2005	<Null>	200
RouteZ	Line2	1/1/2005	<Null>	100

The following are inputs used for the Reassign tool.

Method	Transfer to another line
Source
From Route	RouteZ
From Measure	50
To Route	RouteZ
To Measure	60
Target
Line Name	Line1
Route	RouteZ
From Measure	50
To Measure	60

The original RouteZ is retired on the date of reassignment. RouteZ is recreated on Line1 with the date of reassignment as its From Date and its line order is updated.

The following shows routes after reassignment.

Route Name	Line Name	From Date	To Date	Line Order
RouteX	Line1	1/1/2005	<Null>	100
RouteY	Line1	1/1/2005	<Null>	200
RouteZ	Line2	1/1/2005	1/1/2010	100
RouteZ	Line1	1/1/2010	<Null>	300

Note:

• Multiple adjoining routes from a line can be transferred to an adjoining line.
• Line orders of the remaining routes in the source line may be recalculated as a result.
• Line orders of the existing routes in the target line may be recalculated as a result.
• If the source routes are transferred to another line in entirety, the original route names and route IDs as well as their measurements can be preserved. Alternatively, you can choose a new route name and start and end measures for the transferred routes.
• If a portion of the source routes are transferred to another line, the original route names cannot be preserved, and a new route name must be selected for the transferred route.

Route transfers to a new line

Routes can be transferred entirely or partially to a new line. As shown in the example RouteZ belongs to Line1. You can transfer it to a new line Line2.

The following shows routes before reassignment.

Route Name	Line Name	From Date	To Date	Line Order
RouteX	Line1	1/1/2005	<Null>	100
RouteY	Line1	1/1/2005	<Null>	200
RouteZ	Line1	1/1/2005	<Null>	300

The following are inputs used for the Reassign tool:

Method	Transfer to another line
Source
From Route	RouteZ
From Measure	50
To Route	RouteZ
To Measure	60
Target
Line Name	Line2
Route	RouteZ
From Measure	50
To Measure	60

The original RouteZ is retired on the date of reassignment. RouteZ is recreated on Line2 with the date of reassignment as its starting date value and its line order is updated.

The following shows routes after reassignment.

Route Name	Line Name	From Date	To Date	Line Order
RouteX	Line1	1/1/2005	<Null>	100
RouteY	Line1	1/1/2005	<Null>	200
RouteZ	Line1	1/1/2005	1/1/2010	300
RouteZ	Line2	1/1/2010	<Null>	100

Note:

• Multiple adjoining routes from a line can be transferred to a new line.
• Line orders of the remaining routes in the source line may be recalculated as a result.
• If the source routes are transferred to a new line in entirety, the original route names and route IDs as well as their measurements can be preserved. Alternatively, you can choose a new route name, as well as start and end measures for the transferred routes.
• If a portion of the source routes are transferred to a new line, the original route names cannot be preserved, and a new route name must be provided for the transferred route.

Parameters in the network

The following tables describe the parameter values used in the Reassign tool:

For a network that supports lines

Variable	Description
Network	The network that supports lines in which the routes exist.
Effective Date	This is the date when the reassignment has taken place on the ground.
Source: From Route Name	The route where the reassignment starts.
Source: From Measure	The measure on the source route where the reassignment starts; shown by the green dot.
Source: To Route Name	The route where the reassignment ends. For example, if the reassignment takes place on a single route, the source route and target route are the same. The source routes should belong to the same line.
Source: To Measure	The measure on the source route where the reassignment ends, shown by the red dot.
Target: Route Name	The route to which the reassigned portion will be added. This can also be a new route.
Target: From Measure	The starting measure on the reassigned portion.
Target: To Measure	The ending measure on the reassigned portion.

For continuous networks

Variable	Description
Network	The network in which the continuous routes exist.
Effective Date	This is the date when the reassignment has taken place on the ground.
Source: Route Name/ID	The route where the reassignment starts.
Source: From Measure	The measure on the source route where the reassignment starts; shown by the green dot.
Source: To Measure	The measure on the source route where the reassignment ends, shown by the red dot.
Target: Route Name/ID	The route to which the reassigned portion will be added. This can also be a new route.
Target: From Measure	The starting measure on the reassigned portion.
Target: To Measure	The ending measure on the reassigned portion.

Implement the parameters

There are three methods where you can implement the above parameters using the Reassign tool:

• Merge to adjacent route—Either a portion of a route, the entire route, or multiple routes can be reassigned and merged with the adjacent route.
• Form a new route—A new route is created either by merging source routes if multiple routes are selected in the source or by splitting the source route if a portion of a route is selected in the source. A route can also be renamed by selecting an entire route and providing a new route name or ID.
• Transfer to another line—Routes are transferred to a new line if a new line name is provided, or routes are transferred to an adjacent line if an existing line name is provided.