Event behavior for route reversal

Available with Location Referencing license.

When one or more routes are reversed, events are impacted 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:

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 reversal and corresponding event behaviors are described below.

Route reversal scenario

Single or multiple adjoining routes that belong to the same line can be reversed in one edit.

In the following scenario, Route 1 is active from 1/1/2000. The reversal is set to occur to reverse the entire route on 1/1/2005. The graphics and tables below demonstrate the route information before and after the reversal.

Before route reversal

The following image shows the route before the reversal:

Route 1 before reversal

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

Route IDFrom DateTo DateFrom MeasureTo Measure

Route1

1/1/2000

<Null>

0

20

After route reversal

The following image shows the route after the reversal:

Route 1 after reversal

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

Route IDFrom DateTo DateFrom MeasureTo Measure

Route1

1/1/2000

1/1/2005

0

20

Route1

1/1/2005

<Null>

0

20

Events before route reversal

There are two events on Route 1 that have a start date (From Date) of 1/1/2000. The following image shows the route and events before the reversal.

Route 1 and associated events before route reversal

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

EventRoute IDFrom DateTo DateFrom MeasureTo Measure

Event1

Route1

1/1/2000

<Null>

5

12

Event2

Route1

1/1/2000

<Null>

12

20

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

Stay Put event behavior

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

The route reversal described above has the following effects:

  • Event 1 is retired on the date of reversal because it is within the edit section. A new event is created with the reversal date being the start date (From Date). The start measure (From Measure) value changes to 8 and the end measure (To Measure) value changes to 15 to accommodate the reversed measures of Route 1.
  • Event 2 is retired on the date of reversal because it is within the edit section. A new event is created with the reversal date being the start date. The start measure value changes to 0 and the end measure value changes to 8 to accommodate the reversed measures of Route 1.

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

Note:

The retired event is not drawn in the following image.

Route 1 and associated events after reversal when Stay Put is the configured event behavior

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

EventRoute IDFrom DateTo DateFrom MeasureTo MeasureLocation Error

Event1

Route1

1/1/2000

1/1/2005

5

12

No Error

Event1

Route1

1/1/2005

<Null>

8

15

No Error

Event2

Route1

1/1/2000

1/1/2005

12

20

No Error

Event2

Route1

1/1/2005

<Null>

0

8

No Error

Move event behavior

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

The route reversal described above has the following effects:

  • Event 1 is retired on the date of reversal because it is within the edit section. A new event is created with the reversal date being the start date. Because the measures do not change for the Move behavior, the event maintains its original start measure of 5 and the end measure of 12.
  • Event 2 is retired on the date of reversal because it is within the edit section. A new event is created with the reversal date being the start date. Because the measures do not change for the Move behavior, the event maintains its original start measure of12 and end measure of 20.

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

Route 1 and associated events after reversal when Move is the configured event behavior

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

EventRoute IDFrom DateTo DateFrom MeasureTo MeasureLocation Error

Event1

Route1

1/1/2000

1/1/2005

5

12

No Error

Event1

Route1

1/1/2005

<Null>

5

12

No Error

Event2

Route1

1/1/2000

1/1/2005

12

20

No Error

Event2

Route1

1/1/2005

<Null>

12

20

No Error

Retire event behavior

Events intersecting the reversal region are retired.

  • Event 1 retires on the date of reversal because it is completely inside the edit section.
  • Event 2 retires on the date of reversal because it is completely inside the edit section.

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

Route 1 and associated events after reversal when Retire is the configured event behavior

The following table details the events after the reversal when Retire is the configured event behavior:

EventRoute IDFrom DateTo DateFrom MeasureTo Measure

Event1

Route1

1/1/2000

1/1/2005

5

12

Event2

Route1

1/1/2000

1/1/2005

12

20

Detailed route reversal behavior on routes in a line network with events that span routes

In this example, there are three routes on the same line and the routes are active from 1/1/2000. The reversal is set to occur on 1/1/2005, where all three routes are reversed. The following graphics and tables demonstrate the route information before and after the reversal.

Before route reversal

The following image shows the routes before reversal:

The three routes on Line A before reversal

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

Route IDLine NameLine OrderFrom DateTo DateFrom MeasureTo Measure

Route1

LineA

100

1/1/2000

<Null>

0

10

Route2

LineA

200

1/1/2000

<Null>

15

25

Route3

LineA

300

1/1/2000

<Null>

30

40

After route reversal

The following image shows the routes after the reversal:

The three routes on Line A after reversal

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

Route IDLine NameLine OrderFrom DateTo DateFrom MeasureTo Measure

Route1

LineA

100

1/1/2000

1/1/2005

0

10

Route1

LineA

100

1/1/2005

<Null>

0

10

Route2

LineA

200

1/1/2000

1/1/2005

15

25

Route2

LineA

200

1/1/2005

<Null>

15

25

Route3

LineA

300

1/1/2000

1/1/2005

30

40

Route3

LineA

300

1/1/2005

<Null>

30

40

Events before reversal

There are two spanning events on routes on Line A. The following image shows the routes and events before the reversal:

The three routes and associated events before reversal

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

Event IDFrom DateTo DateFrom Route NameFrom MeasureTo Route NameTo Measure

Event1

1/1/2000

<Null>

Route1

7

Route2

18

Event2

1/1/2000

<Null>

Route2

18

Route3

35

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

Stay Put event behavior

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

The route reversal described above has the following effects:

  • Event 1 is retired on the date of reversal because it is within the edit section. A new event is created with the reversal date being the start date (From Date). The start measure (From Measure) value changes to 22 on Route 22 and the end measure (To Measure) value changes to 3 on Route 1 to accommodate the new measure of the reversed routes.
  • Event 2 is retired on the date of reversal because it is within the edit section. A new event is created with the reversal date being the From Date. The From and To Measures are changed from measure 35 on Route 3 to measure 22 on Route 2 to accommodate the new measure of the reversed routes.

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

Note:

The retired event is not drawn in the following image.

The three routes and associated events after the reversal when Stay Put is the configured event behavior

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

Event IDFrom DateTo DateFrom Route NameFrom MeasureTo Route NameTo MeasureLocation Error

Event1

1/1/2000

1/1/2005

Route1

7

Route2

18

No Error

Event1

1/1/2005

<Null>

Route2

22

Route1

3

No Error

Event2

1/1/2000

1/1/2005

Route2

18

Route3

35

No Error

Event2

1/1/2005

<Null>

Route3

35

Route2

22

No Error

Move event behavior

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

The route reversal described above has the following effects:

  • Event 1 is retired on the date of reversal because it is within the edit section. A new event is created with the reversal date being the start date. Because the measures do not change for the Move behavior, the event maintains its original start measure value of 18 on Route 2 and end measure value of 7 on Route 1. Note that the route start and end locations also switch to accommodate the event direction after route reversal.
  • Event 2 is retired on the date of reversal because it is within the edit section. A new event is created with the reversal date being the start date. Because the measures do not change for the Move behavior, the event maintains its original start measure value of 35 on Route 3 and end measure value of 18 on Route 2. Note that the route start and end locations also switch to accommodate the event direction after route reversal.

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

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

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

Event IDFrom DateTo DateFrom Route NameFrom MeasureTo Route NameTo MeasureLocation Error

Event1

1/1/2000

1/1/2005

Route1

7

Route2

18

No Error

Event1

1/1/2005

<Null>

Route2

18

Route1

7

No Error

Event2

1/1/2000

1/1/2005

Route2

18

Route3

35

No Error

Event2

1/1/2005

<Null>

Route3

35

Route2

18

No Error

Retire event behavior

Events intersecting the reversal region are retired.

  • Event 1 retires on the date of reversal because it is completely inside the edit section.
  • Event 2 retires on the date of reversal because it is completely inside the edit section.

The following image shows the routes after the reversal:

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

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

Event IDFrom DateTo DateFrom Route NameFrom MeasureTo Route NameTo Measure

Event1

1/1/2000

1/1/2005

Route1

5

Route2

20

Event2

1/1/2000

1/1/2005

Route2

20

Route3

35