Transfer to another line 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.

Transfer to another line method

This method is for line networks only.

  • Routes are transferred to a new line if a new line name is provided.
  • Routes are transferred to an adjacent line if an existing line name is provided.

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:

Upstream and downstream sections with an edited section in between

The following table details how the reassignment editing activity impacts upstream and downstream events according to the configured event behavior:

BehaviorEvents upstream reassignmentEvents intersecting reassignmentEvents 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 multiple 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.

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 LineA are transferred to a new line, LineNew.

  • Route2 has changed its name.
  • Route3 has changed measures in the reassignment.

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 routes before reassignment with all three routes in LineA to transfer to a new line

The following table provides details about the routes before reassignment:

Route NameLine NameLine OrderFrom DateTo DateFrom MeasureTo 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

After route reassignment

The following image shows the routes after reassignment:

The routes after reassignment with all three routes to transfer to a new line

The following table provides details about the routes after reassignment:

Route NameLine NameLine OrderFrom DateTo DateFrom MeasureTo 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 image shows the routes and events before reassignment:

The routes and events before reassignment with all three routes to transfer to a new line

The following table provides details about the events before reassignment:

EventFrom Route NameTo Route NameFrom DateTo DateFrom MeasureTo 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 are enforced after running the Apply Event Behaviors tool, when the routes on LineA are transferred to a new line, LineNew.

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 is retired on the date of reassignment because it fell entirely within the edit section.
  • Event2 is not affected by the reassignment as it is in part of routes in LineB.

The following image shows the routes and events after reassignment:

The routes and events after reassignment with Event1 retired and Event2 not affected
Note:

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

The following table provides details about the events after reassignment when Stay Put is the configured event behavior:

EventFrom Route NameTo Route NameFrom DateTo DateFrom MeasureTo MeasureLocation 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

Although the measures of the event are maintained, the geographic location can change.

The route reassignment 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. Because the measures do not change for the Move behavior, this new event still spans from measure 5 on Route1 to measure 40 on Route3, but its location has changed due to change in the underlying measures in Route3.
  • Event2 is not affected by the reassignment as it is in LineB.

The following image shows the routes and events after reassignment:

The routes and events after reassignment with Event1 retired, a new Event1 with location change, and Event2 not affected

The following table provides details about the events after reassignment when Move is the configured event behavior:

EventFrom Route NameTo Route NameFrom DateTo DateFrom MeasureTo MeasureLocation 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 Event1 exists after the Apply Event Behavior 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:

  • Event1 was present in the edit section; it is retired on the date of reassignment.
  • Event2 is not affected by the reassignment as it is in Line B.

The following image shows the routes and events after reassignment:

The routes and events after reassignment with Event1 retired and Event2 not affected
Note:

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

The following table provides details about the events after reassignment when Retire is the configured event behavior:

EventFrom Route NameTo Route NameFrom DateTo DateFrom MeasureTo MeasureLocation 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

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 gets a new time slice when the route it belongs to has reassigned to another line, whether or not the Route Name or measure change in the reassignment. The event can also split if it crosses the reassign region.

The route reassignment described above has the following effects:

  • 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.
  • Event2 is not affected by the reassignment as it is in Line B.

The following image shows the routes and events after reassignment:

The routes and events after reassignment with the original Event1 retired, new records of Event1 created, and part of Event2 not affected

The following table provides details about the events after reassignment when Snap is the configured event behavior:

EventFrom Route NameTo Route NameFrom DateTo DateFrom MeasureTo MeasureLocation 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 Route2 and the entire Route3 within LineA are transferred to an existing line, LineB.

  • The reassigned portion of Route2 has got a new route name.
  • Route3 has changed measures in the reassignment.

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 routes before reassignment with a portion of Route2 and the entire Route3 transferred to an existing line

The following table provides details about the routes before reassignment:

Route NameLine NameLine OrderFrom DateTo DateFrom MeasureTo 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

After route reassignment

The following image shows the routes after reassignment:

The routes after reassignment with a portion of Route2 and the entire Route3 transferred to an existing line

The following table provides details about the routes after reassignment:

Route NameLine NameLine OrderFrom DateTo DateFrom MeasureTo 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 image shows the routes and events before reassignment:

The routes and events before reassignment with a portion of Route2 and the entire Route3 transferred to an existing line

The following table provides details about the events before reassignment:

EventFrom Route NameTo Route NameFrom DateTo DateFrom MeasureTo 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 are enforced after running the Apply Event Behaviors tool, when the routes on LineA are transferred to LineB.

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 removed.

The route reassignment described above has the following effects:

  • 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 Route1 and part of Route2 that were not impacted by the edit.
  • Even though the line orders have changed on the three routes on LineB, Event2 is not affected by the reassignment, because it can still locate the From and To routes and measures.

The following image shows the routes and events after reassignment:

The routes and events after reassignment with Event1 partially retired and Event2 not affected
Note:

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

The following table provides details about the events after reassignment when Stay Put is the configured event behavior:

EventFrom Route NameTo Route NameFrom DateTo DateFrom MeasureTo MeasureLocation 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

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. The move behavior does not allow changing the From and To route IDs or measures of the event. It returns a location error because Route1 and Route3 are now on different lines, but the event cannot span across lines.
  • Even though the line orders have changed on the three routes on LineB, Event2 is not affected by the reassignment, because it can still locate the From and To routes and measures.

The following image shows the routes and events after reassignment:

The routes and events after reassignment with Event1 having a location error and Event2 not affected

The following table provide details about the events after reassignment when Move is the configured event behavior:

EventFrom Route NameTo Route NameFrom DateTo DateFrom MeasureTo MeasureLocation 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 Event1 exists after the Apply Event Behavior 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:

  • Event1 was 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 LineB, Event2 is not affected by the reassignment, because it can still locate the From and To routes and measures.

The following image shows the routes and events after reassignment:

The routes and events after reassignment with Event1 retired and Event2 not affected
Note:

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

The following table provides details about the events after reassignment when Retire is the configured event behavior:

EventFrom Route NameTo Route NameFrom DateTo DateFrom MeasureTo MeasureLoc 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

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 gets a new time slice when the route it belongs to has reassigned to another line, no matter the Route Name or measures change or not in the reassignment. 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 non-impacted portion from Route1 to the measure 10 of Route2.
  • Part of Event1, that was in the impacted portion, is snapped to the new routes with the new measures: from measure 10 of Route2_reassign to measure 60 of Route3. It gets its From Date from the date of reassignment.
  • Even though the line orders have changed on the three routes on LineB, Event2 is not affected by the reassignment, because it can still locate the From and To routes and measures.

The following image shows the routes and events after reassignment:

The routes and events after with the original Event1 retired, new records of Event1 created, and Event2 not affected.

The following table provides details about the events after reassignment when Snap is the configured event behavior:

EventFrom Route NameTo Route NameFrom DateTo DateFrom MeasureTo MeasureLocation 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