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 applied after route edits. If you are using conflict prevention, you are prompted to run Apply Event Behaviors before posting can be completed.

Note:

For any LRS route edit where recalibrate downstream is selected, the configured calibrate event behavior will be applied to downstream sections. You can review configured event behaviors by viewing LRS event properties.

The following sections detail the results of executing the Apply Event Behaviors tool on event features after a corresponding route edit.

Route retirement scenario

The following retirement scenario involves one route and three events. The retirement (depicted with a dashed line) starts in Event1, completely spans Event2, and ends in Event3.

Before Retirement

Stay Put behavior

The geographic location of the event outside of the retire region is preserved; the measures can change. The event can also split if it crosses the retire region. Portions of the reassign region are retired.

Stay Put behavior

Move behavior

The measures and route of the event are maintained; the geographic location can change.

Move behavior

Retire behavior

The geographic location and measure of the event are preserved; the event is retired. Events intersecting the retire region are retired.

Retire behavior

Upstream and downstream sections

Route editing impacts upstream and downstream sections differently based on the configured event behavior.

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

Upstream and downstream sections

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

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

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 recalibrate event behavior is applied; otherwise, no action.

Retire

No action.

Retire event; line events crossing edit region are not split.

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

Note:
  • Point events follow the same behavior as line events but don't need to be split.
  • If the option to recalibrate route downstream is selected, calibrate route event behaviors are applied to the events downstream of the edited portion of the route.
  • Since the LRS is time aware, edit activities such as retiring a route will time slice routes and events.

Detailed behavior results

The following sections detail how event behavior rules are enforced when a route is retired.

Stay Put behavior

The route is active from 1/1/2000, and if the retirement is set to occur on 1/1/2005 and Recalibrate route downstream is not chosen, this has the following effects:

  • Event1 is represented by two time slices. There is a time slice from 1/1/2000 to 1/1/2005, with the original measures from 0 to 20, and a time slice from 1/1/2005 to <Null>, with measures from 0 to 15, that stay the same location geographically.
  • Event2 retires to maintain geographic location.
  • Event3 is represented by two time slices. There is a time slice from 1/1/2000 to 1/1/2005, with the original measures from 30 to 45, and a time slice from 1/1/2005 to <Null>, with measures from 35 to 45, that stay the same geographically.

Before Stay Put event behavior

The following diagram provides details about the route before retirement:

Before Stay Put event behavior

The following table provides details about the events before retirement:

EventRoute NameFrom 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

After Stay Put event behavior

The following diagram provides details about the route after retirement:

After Stay Put event behavior

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

EventRoute NameFrom DateTo DateFrom MeasureTo MeasureLocation Error

Event1

Route1

1/1/2000

1/1/2005

0

20

No Error

Event1

Route1

1/1/2005

<Null>

0

15

No Error

Event3

Route1

1/1/2000

1/1/2005

30

45

No Error

Event3

Route1

1/1/2005

<Null>

35

45

No Error

Move behavior

The route is active from 1/1/2000, and if the retirement is set to occur on 1/1/2005 and Recalibrate route downstream is not chosen, this has the following effects:

  • Event1 is represented by two time slices. There is a time slice from 1/1/2000 to 1/1/2005 and a time slice from 1/1/2005 to <Null>, both with the original measures from 0 to 20. This new time slice will only partially locate since the event time slice has measures from 0 to 20, but the underlying route time slice only has measures from 0 to 15 and 35 to 55, with a physical gap created due to retirement.
  • Event2 is represented by two time slices. There is a time slice from 1/1/2000 to 1/1/2005 and a time slice from 1/1/2005 to <Null>, both with the measures from 20 to 30. This new time slice will not locate since the event time slice has measures from 20 to 30, but the underlying route does not have a route with those measures.
  • Event3 is represented by two time slices. There is a time slice from 1/1/2000 to 1/1/2005 and a time slice from 1/1/2005 to <Null>, both with the original measures 30 to 45. This new time slice only partially locates since the event time slice has measures from 30 to 45, but the underlying route time slice only has measures from 0 to 15 and 35 to 55, with a physical gap created due to retirement.

Before Move event behavior

The following diagram provides details about the route before retirement:

Before Move event behavior

The following table provides details about the events before retirement:

EventRoute NameFrom 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

After Move event behavior

The following diagram provides details about the route after retirement:

After Move event behavior

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

EventRoute NameFrom 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

Partial match for the To measure

Event3

Route1

1/1/2000

1/1/2005

30

45

No Error

Event3

Route1

1/1/2005

<Null>

30

45

Partial match for the From measure

Retire behavior

The route is active from 1/1/2000, and if the retirement is set to occur on 1/1/2005 and Recalibrate route downstream is not chosen, this has the following effects:

  • Event1 retires since it intersects the retired region.
  • Event2 retires since it is completely inside the retired region.
  • Event3 retires since it intersects the retired region.

Before Retire event behavior

The following diagram provides details about the route before retirement:

Before Retire event behavior

The following table provides details about the events before retirement:

EventRoute NameFrom 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

After Retire event behavior

The following diagram provides details about the route after retirement:

After Retire event behavior

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

EventRoute NameFrom 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