Event behavior for route extension

Available with Location Referencing license.

When routes are extended, 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.

Running the Apply Event Behaviors tool on event features after a corresponding route edit is described below.

Route extension scenario

The following route extension scenario involves one route and three events. The extension is at the beginning of the route.

Before route extension

Stay Put behavior

The geographic location of the events is preserved; the measures are changed.

Stay Put behavior

Move behavior

The event measures on the route are maintained; the geographic location is changed.

Move behavior

Retire behavior

The geographic location and measure of the events are preserved; the events are retired.

Retire behavior

Cover behavior

The event measures on the route are changed; the geographic location is changed to include the extended section at the beginning or end of a route.

Before route extension

Upstream and downstream sections

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

Refer to the following diagrams to understand the upstream and downstream section for the route extension scenario:

Upstream and downstream sections

The following table details how a route editing activity impacts downstream events according to the configured event behavior:

Behavior Events upstream Events intersecting Events downstream

Stay Put

No action.

The shape is regenerated only if the event can be located using route and measures.

If the route is extended, measures are adjusted to retain x,y.

Move

No action.

The shape is regenerated to the new location of route measures.

If the route is extended, measures move to retain x,y.

Retire

No action.

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

If the route is extended, measures change to retain x,y.

Cover

No action.

The shape is regenerated to the new location of route measures.

If the route is extended, measures move to retain x,y.

Note:

Since the LRS is time aware, edit activities—such as extending a route—time slice routes and events.

Detailed behavior results

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

Stay Put event behavior

The route is active from 1/1/2000, and if the extension is set to occur on 1/1/2005, 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 20 to 40, that stay the same geographically.
  • Event2 is represented by two time slices. There is a time slice from 1/1/2000 to 1/1/2005, with the original measures from 20 to 30, and a time slice from 1/1/2005 to <Null>, with measures from 40 to 50, that stay the same geographically.
  • 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 50 to 65, that stay the same geographically.

Before Stay Put event behavior

The following image shows the route before extension:

Before Stay Put event behavior

The following table provides details about the events before extension:

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 image shows the route after extension:

After Stay Put event behavior

The following table provides details about the events after extension 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>

20

40

No Error

Event2

Route1

1/1/2000

1/1/2005

20

30

No Error

Event2

Route1

1/1/2005

<Null>

40

50

No Error

Event3

Route1

1/1/2000

1/1/2005

30

45

No Error

Event3

Route1

1/1/2005

<Null>

50

65

No Error

Move event behavior

The route is active from 1/1/2000, and if the extension is set to occur on 1/1/2005, 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 0 to 20. Since the new time slice can locate both route and measure, events move to preserve measures from 0 to 20.
  • 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. Since the new time slice can locate both route and measure, events move to preserve measures from 20 to 30.
  • 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 has measures from 30 to 45 as well.

Before Move event behavior

The following image shows the route before extension:

Before Move event behavior

The following table provides details about the events before extension:

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 image shows the route after extension:

After Move event behavior

The following table provides details about the events after extension 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

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>

30

45

No Error

Retire event behavior

The route is active from 1/1/2000, and if the extension is set to occur on 1/1/2005, this has the following effects:

  • Since event measures are altered, Event1 retires.
  • Since event measures are altered, Event2 retires.
  • Since event measures are altered, Event3 retires.

Before Retire event behavior

The following image shows the route before extension:

Before Retire event behavior

The following table provides details about the events before extension:

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 image shows the route after extension:

After Retire event behavior

The following table provides details about the events after extension 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

Cover event behavior

The route is active from 1/1/2000, and if the extension is set to occur on 1/1/2005, 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 updated measures from 0 to 40.
  • Event2 is represented by two time slices. There is a time slice from 1/1/2000 to 1/1/2005 with the original measures from 20 to 30, and a time slice from 1/1/2005 to <Null> with updated measures from 40 to 50.
  • 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 updated measures from 50 to 65.

Before Cover event behavior

The following image shows the route before extension:

Before Cover event behavior

The following table provides details about the events before extension:

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 Cover event behavior

The following image shows the route after extension. Since Event1 touches the extension, its measures and location are updated to cover the extended portion of the route.

After Cover event behavior

The following table provides details about the events after extension when Cover 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

40

No Error

Event2

Route1

1/1/2000

1/1/2005

20

30

No Error

Event2

Route1

1/1/2005

<Null>

40

50

No Error

Event3

Route1

1/1/2000

1/1/2005

30

45

No Error

Event3

Route1

1/1/2005

<Null>

50

65

No Error

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

The following sections describe how event behavior rules are enforced when a route on a line in a line network is extended.

Stay Put event behavior

The routes are active from 1/1/2000 and if the extension is set to occur on 1/1/2005, 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 on Route1 to 30 on Route3, and a time slice from 1/1/2005 to <Null>, with measures from 10 on Route1 to 30 on Route3 with the same geographic location.
  • Event2 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 on Route3 to 48 on Route4, and a time slice from 1/1/2005 to <Null>, with measures from 30 on Route3 to 48 on Route4 with the same geographic location.

Before Stay Put event behavior

The following image shows the routes before extension:

Before Stay Put event behavior

The following table provides details about the events before extension:

Event IDFrom DateTo DateFrom RouteIDFrom MeasureTo RouteIDTo Measure

Event1

1/1/2000

<Null>

Route1

0

Route3

30

Event2

1/1/2000

<Null>

Route3

30

Route4

48

After Stay Put event behavior

The following image shows the routes after extension:

After Stay Put event behavior

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

Event IDFrom DateTo DateFrom RouteIDFrom MeasureTo RouteIDTo MeasureLocation Error

Event1

1/1/2000

1/1/2005

Route1

0

Route3

30

No Error

Event 1

1/1/2005

<Null>

Route1

10

Route3

30

No Error

Event2

1/1/2000

<Null>

Route3

30

Route4

48

No Error

Move event behavior

The route is active from 1/1/2000 and if the extension is set to occur on 1/1/2005, 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 on Route1 to 30 on Route3, and a time slice from 1/1/2005 to <Null>, with measures from 0 on Route1 to 30 on Route3. Since the new time slice can locate both route and measure, the event moves to preserve measures from 0 to 30.
  • 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 30 on Route3 to 48 on Route4.

Before Move event behavior

The following image shows the routes before extension:

Before Move event behavior

The following table provides details about the events before extension:

Event IDFrom DateTo DateFrom RouteIDFrom MeasureTo RouteIDTo Measure

Event1

1/1/2000

<Null>

Route1

0

Route3

30

Event2

1/1/2000

<Null>

Route3

30

Route4

48

After Move event behavior

The following image shows the routes after extension:

After Move event behavior

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

Event IDFrom DateTo DateFrom RouteIDFrom MeasureTo RouteIDTo MeasureLocation Error

Event1

1/1/2000

1/1/2005

Route1

0

Route3

30

No Error

Event1

1/1/2005

<Null>

Route1

0

Route3

30

No Error

Event2

1/1/2000

<Null>

Route3

30

Route4

48

No Error

Retire event behavior

The routes are active from 1/1/2000 and if the extension is set to occur on 1/1/2005, this has the following effects:

  • Since event measures are altered on one of the routes where Event1 is located, Event1 retires.
  • Since event measures are not altered on any of the routes where Event2 is located, Event2 is unaffected.

Before Retire event behavior

The following image shows the routes before extension:

Before Retire event behavior

The following table provides details about the events before extension:

Event IDFrom DateTo DateFrom RouteIDFrom MeasureTo RouteIDTo Measure

Event1

1/1/2000

<Null>

Route1

0

Route3

30

Event2

1/1/2000

<Null>

Route3

30

Route4

48

After Retire event behavior

The following image shows the routes after extension:

After Retire event behavior

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

Event IDFrom DateTo DateFrom Route IDFrom MeasureTo RouteIDTo MeasureLocation Error

Event1

1/1/2000

1/1/2005

Route 1

0

Route 3

30

No Error

Event2

1/1/2000

<Null>

Route 3

30

Route 4

48

No Error

Cover event behavior

The routes are active from 1/1/2000 and if the extension is set to occur on 1/1/2005, this has the following effects:

  • Event1 is represented by two time slices since event measures are altered on one of the routes where Event1 is located. There is a time slice from 1/1/2000 to 1/1/2005, with the measures from 0 on Route1 to 30 on Route3, and a time slice from 1/1/2005 to <Null>, with measures from 0 on Route1 to 30 on Route3.
  • Event2 is unchanged since event measures are not altered on any of the routes where Event2 is located.

Before Cover event behavior

The following image shows the routes before extension:

Before Cover event behavior

The following table provides details about the events before extension:

Event IDFrom DateTo DateFrom RouteIDFrom MeasureTo RouteIDTo Measure

Event1

1/1/2000

<Null>

Route1

0

Route3

30

Event2

1/1/2000

<Null>

Route3

30

Route4

48

After Cover event behavior

The following image shows the routes after extension:

After Cover event behavior

The following table provides details about the events after extension when Cover is the configured event behavior:

Event IDFrom DateTo DateFrom RouteIDFrom MeasureTo RouteIDTo MeasureLocation Error

Event1

1/1/2000

1/1/2005

Route1

0

Route3

30

No Error

Event1

1/1/2005

<Null>

Route1

0

Route3

30

No Error

Event2

1/1/2000

<Null>

Route3

30

Route4

48

No Error

Detailed behavior on concurrent routes with Cover behavior

The following sections detail how the Cover event behavior rule is enforced when concurrent routes result after extension.

Concurrent routes with Cover behavior and a nonspanning event

In the following scenario, Route2 on LineA is extended at the beginning with the Cover behavior configured as the event behavior:

The Route2 extension uses two centerlines (CL1 and CL2).

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

  • Event1 is represented by two time slices after extension. There is a time slice from 1/1/2000 to 1/1/2005 with the original measures from 0 to 15, and a time slice from 1/1/2005 to <Null> with updated measures from 5 to 30.

Before extension of concurrent routes with Cover behavior and a nonspanning event

The following image shows the routes before extension:

Before extension of a concurrent route with Cover behavior and a nonspanning event

The following table provides details about the event before extension:

Event IDFrom Route NameTo Route NameFrom DateTo DateFrom MeasureTo MeasureLocation Error

Event1

Route2

Route2

1/1/2000

<Null>

0

15

No Error

After extension of concurrent routes with Cover behavior and a nonspanning event

After extension, Route2 is concurrent with the dominant route, Route1 on LineB, at the beginning of the extended section.

Event1 does not cover the section where Route2 overlaps Route1 since Route1 is the dominant route in the concurrent section.

The following image shows the routes after extension:

After extension of a concurrent route with Cover behavior and a nonspanning event

The following table provides details about the event after extension when Cover is the configured event behavior:

Event IDFrom Route NameTo Route NameFrom DateTo DateFrom MeasureTo MeasureLocation Error

Event1

Route2

Route2

1/1/2000

1/1/2005

0

15

No Error

Event1

Route2

Route2

1/1/2005

<Null>

5

30

No Error

Concurrent routes with Cover behavior and spanning events

In the following scenario, Route2 on LineA is extended at the beginning with the Cover behavior configured as the event behavior.

The Route2 extension uses two centerlines (CL1 and CL2) and there are two events that span routes.

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

  • Event1 is represented by two time slices after extension. There is a time slice from 1/1/2000 to 1/1/2005 with the original measures from 0 on Route2 to 17, and a time slice from 1/1/2005 to <Null> with updated measures from 5 on Route2 to 17 on Route3.
  • Event2 is represented by two time slices after extension. There is a time slice from 1/1/2000 to 1/1/2005 with the original measures from 17 on Route3 to 36 on Route4, and a time slice from 1/1/2005 to <Null> with the same measures from 17 on Route3 to 36 on Route4.

Before extension of concurrent routes with Cover behavior and spanning events

The following image shows the routes before extension:

Before extension of a concurrent route with Cover behavior and spanning events

The following table provides details about the events before extension:

Event IDFrom Route NameTo Route NameFrom DateTo DateFrom MeasureTo MeasureLocation Error

Event1

Route2

Route3

1/1/2000

<Null>

0

17

No Error

Event2

Route3

Route4

1/1/2000

<Null>

17

36

No Error

After extension of concurrent routes with Cover behavior and spanning events

After extension, Route2 is concurrent with the dominant route, Route1 on LineB, at the beginning of the extended section.

Event1 does not cover the section where Route2 overlaps Route1 since Route1 is the dominant route in the concurrent section.

The following image shows the routes after extension:

After extension of a concurrent route with Cover behavior and spanning events

The following table provides details about the events after extension of a concurrent route when Cover is the configured event behavior:

Event IDFrom Route NameTo Route NameFrom DateTo DateFrom MeasureTo MeasureLocation Error

Event1

Route2

Route3

1/1/2000

1/1/2005

0

17

No Error

Event1

Route2

Route3

1/1/2005

<Null>

5

17

No Error

Event2

Route3

Route4

1/1/2000

1/1/2005

17

36

No Error

Event2

Route3

Route4

1/1/2005

<Null>

17

36

No Error