Event behavior for route retirement

Available with Location Referencing license.

When routes are retired, events are impacted depending on the configured event behavior for each 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:

When Recalibrate route downstream is chosen for an LRS route edit, the configured calibrate event behavior is applied to downstream sections. You can review configured event behaviors by viewing LRS event properties.

The route retirement and corresponding event behaviors are described below.

Route retirement scenario

A route can be retired at the beginning, in the middle, or at the end of the route. If the retirement takes place in the middle of the route, the resulting route is a gapped route. For line network, you can fully or partially retire multiple adjoining routes that belong to the same line.

Upstream and downstream sections

Route editing impacts upstream and downstream sections differently.

The following image shows the upstream and downstream sections for the route retirement scenario:

Upstream and downstream sections of route retirement scenarios

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

Behavior Events upstream Events intersecting Events downstream

Stay Put

No action.

Retire event; line events crossing the edit region 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 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 edit region are not split.

If route calibration is changed, the calibrate event behavior is applied; otherwise, no action is taken.

Snap

No action

Retire event; line events crossing the edit section will be split. The new event is snapped to a concurrent route, if one exists.

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, edit activities such as retiring a route will time slice routes and events.

Route retirement results

In this example, the route Route1 is active from 1/1/2000. The retirement is set to occur at the beginning of the route on 1/1/2005. The Recalibrate route downstream option is chosen and the route is recalibrated after retirement. The graphics and tables below demonstrate the route information before and after the retirement.

Note:

In all the examples below, the calibrate event behavior for the events is set to Stay Put.

The calibrate event behavior is applied before the retire event behavior, so it is important to verify the event feature layer's calibrate event behavior configuration before checking the Recalibrate route downstream check box.

For other event behaviors for calibration, refer to the calibrate event behavior.

Before route retirement

The following image shows the route before the retirement:

Route1 before retirement

The following table provides details about the route before the retirement:

Route IDFrom DateTo DateFrom MeasureTo Measure

Route1

1/1/2000

<Null>

0

55

After route retirement

The following image shows the route after the retirement.

Route1 after retirement

The following table provides details about the route after the retirement:

Route IDFrom DateTo DateFrom MeasureTo Measure

Route1

1/1/2000

1/1/2005

0

55

Route1

1/1/2005

<Null>

0

30

Events before route retirement

There are three events on Route1 and all of them have a start date (From Date) of 1/1/2000. The following image shows the route and events before the retirement:

Route1 and associated events before retirement

The following table provides details about the events before the retirement:

EventRoute IDFrom DateTo DateFrom MeasureTo Measure

Event1

Route1

1/1/2000

<Null>

0

20

Event2

Route1

1/1/2000

<Null>

20

30

Event3

Route1

1/1/2000

<Null>

30

45

The following sections detail how event behavior rules are enforced after running the Apply Event Behaviors tool under this route retirement scenario.

Stay Put event behavior

Although the geographic location of the event is maintained, the measures can change. The event can also split if it crosses the retire region and portions within the retirement region are retired.

The following table shows the edit activities involved in the route edit and their corresponding event behaviors:

Edit activityEvent behavior

Retire

Stay Put

Calibrate

Stay Put

The route retirement described above has the following effects:

  • Event1 is retired on the date of the retirement because it is completely in the edit section.
  • Event2 is retired on the date of the retirement because part of it is in the edit section. A new event is created on the post-retirement route with the retirement date as the starting date (From Date). The length of the new Event2 is shorter and its start measure (From Measure) value changes to 0 and end measure (To Measure) value changes to 5 to accommodate the new measures of Route1.
  • Event3 is not in the retirement region, so retire event behavior does not apply to it. As Route1 is recalibrated, the calibration Stay Put behavior is applied to maintain Event3's geographic location. Event3's start measure value changes to 5 and end measure value changes to 20 to accommodate the new measures of Route1.

The following image shows the route and events after the retirement:

Route1 and associated events after retirement when Stay Put is the configured event behavior
Note:

The retired event is not drawn in the graphic above.

The following table provides details about the events after the retirement:

EventRoute IDFrom DateTo DateFrom MeasureTo MeasureLocation Error

Event1

Route1

1/1/2000

1/1/2005

0

20

No Error

Event2

Route1

1/1/2000

1/1/2005

20

30

No Error

Event2

Route1

1/1/2005

<Null>

0

5

No Error

Event3

Route1

1/1/2000

1/1/2005

30

45

No Error

Event3

Route1

1/1/2005

<Null>

5

20

No Error

Move event behavior

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

The following table shows the edit activities involved in the route edit and their corresponding event behaviors:

Edit activityEvent behavior

Retire

Move

Calibrate

Stay Put

The route retirement described above has the following effects:

  • Event1 is retired on the date of the retirement because part of it is in the edit section. A new event is created on the post-retirement route with the retirement date as the starting date. Because the measures do not change for the Move behavior, the event moves to the new location of Route1 to maintain its original start measure value of 0 and end measure value of 20.
  • Event2 is retired on the date of the retirement because it is completely in the edit section. A new event is created on the post-retirement route with the retirement date as the starting date. Because the measures do not change for the Move behavior, the event moves to the new location of Route1 to maintain its original start measure value of 20 and end measure value of 30.
  • Event3 is not in the retirement region, so retire event behavior does not apply to it. As Route1 is recalibrated, the calibration Stay Put behavior is applied to maintain Event3's geographic location. Event3's start measure value changes to 5 and end measure value changes to 20 to accommodate the new measures of Route1.

The following image shows the route and events after the retirement:

Route1 and associated events when Move is the configured event behavior

The following table provides details about the events after the retirement:

EventRoute IDFrom DateTo DateFrom MeasureTo MeasureLocation Error

Event1

Route1

1/1/2000

1/1/2005

0

20

No Error

Event1

Route1

1/1/2005

<Null>

0

20

No Error

Event2

Route1

1/1/2000

1/1/2005

20

30

No Error

Event2

Route1

1/1/2005

<Null>

20

30

No Error

Event3

Route1

1/1/2000

1/1/2005

30

45

No Error

Event3

Route1

1/1/2005

<Null>

5

20

No Error

Retire event behavior

Events intersecting the retire region are retired.

The following table shows the edit activities involved in the route edit and their corresponding event behaviors:

Edit activityEvent behavior

Retire

Retire

Calibrate

Stay Put

The route retirement described above has the following effects:

  • Event1 retires on the date of the retirement because it is completely inside the retired region.
  • Event2 retires on the date of the retirement because it intersects the retired region.
  • Event3 is not in the retirement region, so retire event behavior does not apply to it. As Route1 is recalibrated, the calibration Stay Put behavior is applied to maintain Event3's geographic location. Event3's start measure value changes to 5 and end measure value changes to 20 to accommodate the new measures of Route1.

The following image shows the route and events after the retirement:

Route1 and associated events after retirement when Retire is the configured event behavior

The following table provides details about the events after the retirement:

EventRoute IDFrom DateTo DateFrom MeasureTo MeasureLocation Error

Event1

Route1

1/1/2000

1/1/2005

0

20

No Error

Event2

Route1

1/1/2000

1/1/2005

20

30

No Error

Event3

Route1

1/1/2000

1/1/2005

30

45

No Error

Event3

Route1

1/1/2005

<Null>

5

20

No Error

Snap event behavior

Although the geographic location of the event is maintained by snapping to the new route location of retirement, the measures can change. The event can also split if it crosses the retirement where concurrent routes exist.

In this example, there is a Route2 that is concurrent with Route1. Route2 is in reversed direction and has the start measure value of 0 and end measure value of 55.

The following table shows the edit activities involved in the route edit and their corresponding event behaviors:

Edit activityEvent behavior

Retire

Snap

Calibrate

Stay Put

The route retirement described has the following effects:

  • Event1 is retired on the date of the retirement because it is completely in the edit section. As a concurrent route exists in the realignment section, Event1 snaps to Route2, the concurrent route, after retirement. It is also reversed to accommodate the direction of Route2. The new event record has the retirement date as the starting date. The new start measure value of Event1 became 35 and the end measure value remained 55 on Route2 to maintain Event1's geographic location.
  • Event2 is retired on the date of retirement since part of it is in the edit section. It then splits into two event records on the post-retirement routes with the retirement date as the starting date. This is because a concurrent route exists in the retirement section, and the portion of Event2 in the retirement section snaps to Route2, the concurrent route, after retirement. This portion of Event2 is also reversed to accommodate the direction of Route2. As a result, Event2 splits into two pieces to maintain its geographic location. The first event record has the start measure value of 0 and end measure value of 5 on Route1 when the calibrate Stay Put behavior is applied. The second event record snaps to Route2 and has the start measure value of 30 and end measure value of 35 on Route2.
  • Event3 is not in the retirement region, so retire event behavior does not apply to it. As Route1 is recalcitrated, the calibrate Stay Put behavior is applied to maintain Event3's geographic location. Event3's start measure value changes to 5 and end measure value changes to 20 to accommodate the new measures of Route1.

The following image shows the route and events after the retirement:

Route1 and associated events after realignment when Snap is the configured event behavior and a concurrent route exists

The following table provides details about the events after retirement:

EventRoute IDFrom DateTo DateFrom MeasureTo MeasureLocation Error

Event1

Route1

1/1/2000

1/1/2005

0

20

No Error

Event1

Route2

1/1/2005

<Null>

35

55

No Error

Event2

Route1

1/1/2000

1/1/2005

20

30

No Error

Event2

Route1

1/1/2005

<Null>

0

5

No Error

Event2

Route2

1/1/2005

<Null>

30

35

No Error

Event3

Route1

1/1/2000

1/1/2005

30

45

No Error

Event3

Route1

1/1/2005

<Null>

5

20

No Error

Detailed behavior 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. The retirement is set to occur on 1/1/2005 where the entire Route1 and half of Route2 are retired. The Recalibrate route downstream option is chosen, and Route2 is recalibrated after retirement. The images and tables below demonstrate the route information before and after the retirement.

Note:

In all the examples below, the calibrate event behavior for the events is set to Stay Put.

The calibrate event behavior is applied before the retire event behavior, so it is important to verify the event feature layer's calibrate event behavior configuration before checking the Recalibrate route downstream check box.

For other event behaviors for calibration, refer to the calibrate event behavior.

Before route retirement

The following image shows the routes before the retirement:

The four routes on LineA before retirement

The following table provides details about the routes before the retirement:

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

The following image shows the routes after the retirement:

The three routes on LineA after retirement

The following table provides details about the routes after the retirement:

Route NameLine NameLine OrderFrom DateTo DateFrom MeasureTo Measure

Route1

LineA

100

1/1/2000

1/1/2005

0

20

Route2

LineA

200

1/1/2000

1/1/2005

12

22

Route2

LineA

100

1/1/2005

<Null>

12

17

Route3

LineA

300

1/1/2000

1/1/2005

25

35

Route3

LineA

200

1/1/2005

<Null>

25

25

Route4

LineA

400

1/1/2000

1/1/2005

38

48

Route4

LineA

300

1/1/2005

<Null>

38

48

Events before retirement

There are two spanning events on routes on LineA. The following image shows the routes and events before the retirement:

The four routes and associated events before retirement

The following table provides details about the events before the retirement:

Event IDFrom DateTo DateFrom Route NameTo Route NameFrom MeasureTo Measure

Event1

1/1/2000

<Null>

Route1

Route3

0

30

Event2

1/1/2000

<Null>

Route3

Route4

30

48

The following sections describe how event behavior rules are enforced when routes on a line in a line network are retired.

Stay Put event behavior

Although the geographic location of the event is maintained, the measures can change. The event can also split if it crosses the retire region, and portions within the retirement region are retired.

The following table shows the edit activities involved in the route edit and their corresponding event behaviors:

Edit activityEvent behavior

Retire

Stay Put

Calibrate

Stay Put

The route retirement described above has the following effects:

  • Event1 is retired on the date of the retirement because part of it is in the edit section. A new event is created on the post-retirement route with the retirement date as the starting date. The length of the new Event1 is shorter because its start measure value changes to 17 on Route2 and the end measure value changes to 30 on Route3 to accommodate the new measures of Route2.
  • Event2 is not affected because it is not in the retirement region.

The following image shows the routes and events after the retirement:

The three routes and associated events after retirement when Stay Put is the configured event behavior
Note:

The retired event is not drawn in the image above.

The following table provides details about the events after the retirement:

Event IDFrom DateTo DateFrom Route NameTo Route NameFrom MeasureTo MeasureLocation Error

Event1

1/1/2000

1/1/2005

Route1

Route3

0

30

No Error

Event1

1/1/2005

<Null>

Route2

Route3

12

30

No Error

Event2

1/1/2000

<Null>

Route3

Route4

30

48

No Error

Move event behavior

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

The following table shows the edit activities involved in the route edit and their corresponding event behaviors:

Edit activityEvent behavior

Retire

Move

Calibrate

Stay Put

The route retirement described above has the following effects:

  • Event1 is retired on the date of the retirement because part of it is in the edit section. A new event is created on the post-retirement route with the retirement date as the starting date. Because the measures do not change for the Move behavior, the new Event1 gets a location error while trying to locate Route1 for its start measure but Route1 no longer exists. There is a record for the new Event1 in the event table, but it is not drawn because it does not have a length due to the location error.
  • Event2 is not affected because it is not in the retirement region.

The following image shows the routes and events after the retirement:

The three routes and associated events after retirement when Move is the configured event behavior

The following table provides details about the events after the retirement:

Event IDFrom DateTo DateFrom Route NameTo Route NameFrom MeasureTo MeasureLocation Error

Event1

1/1/2000

1/1/2005

Route1

Route3

0

30

No Error

Event1

1/1/2005

<Null>

Route1

Route3

0

30

Route Not Found

Event2

1/1/2000

<Null>

Route3

Route4

30

48

No Error

Retire event behavior

Events intersecting the retire region are retired.

The following table shows the edit activities involved in the route edit and their corresponding event behaviors:

Edit activityEvent behavior

Retire

Retire

Calibrate

Stay Put

The route retirement described above has the following effects:

  • Event1 retires on the date of the retirement because it intersects the retired region.
  • Event2 is not affected because it is not in the retirement region.

The following image shows the routes and events after the retirement:

The three routes and associated events after retirement when Retire is the configured event behavior

The following table provides details about the events after the retirement:

Event IDFrom DateTo DateFrom Route NameTo Route NameFrom MeasureTo MeasureLocation Error

Event1

1/1/2000

1/1/2005

Route1

Route3

0

30

No Error

Event2

1/1/2000

<Null>

Route3

Route4

30

48

No Error

Snap event behavior

Although the geographic location of the event is maintained by snapping to the new route location of retirement, the measures can change. The event can also split if it crosses the retirement where concurrent routes exist.

In this example, there is a Route5 that is concurrent with the routes on LineA. Route5 is on LineB and is in the reversed direction. It has the start measure value of 0 and end measure value of 40.

The following table shows the edit activities involved in the route edit and their corresponding event behaviors:

Edit activityEvent behavior

Retire

Snap

Calibrate

Stay Put

The route retirement described above has the following effects:

  • Event1 is retired on the date of retirement because part of it is in the edit section. It then splits into two event records on the post-retirement routes with the retirement date as the starting date. This is because a concurrent route exists in the retirement section, and the portion of Event1 in the retirement section snaps to Route5, the concurrent route, after retirement. This portion of Event1 is also reversed to accommodate the direction of Route5. As a result, Event1 splits into two pieces to maintain its geographic location. The first event record has the start measure value of 12 on Route2 and end measure value of 30 on Route3 when the calibrate Stay Put behavior is applied. The second event records snaps to Route5 and has the start measure value of 25 and end measure value of 40 on Route5.
  • Event2 is not affected because it is not in the retirement region.

The following image shows the route and events after the retirement:

The three routes and associated events after retirement when Snap is the configured event behavior and a concurrent route exists

The following table provides details about the events after retirement:

Event IDFrom DateTo DateFrom Route NameTo Route NameFrom MeasureTo MeasureLocation Error

Event1

1/1/2000

1/1/2005

Route1

Route3

0

30

No Error

Event1

1/1/2005

<Null>

Route2

Route3

12

30

No Error

Event1

1/1/2005

<Null>

Route5

Route5

25

40

No Error

Event2

1/1/2000

<Null>

Route3

Route4

30

48

No Error