Event behavior for route realignment

Mit der Location Referencing-Lizenz verfügbar.

When a route realignment occurs, events are impacted in the edit activity area, as well as upstream and downstream of the realignment, depending on the configured event behavior for each event layer.

Hinweis:

Events are not updated until the Apply Event Behaviors geoprocessing tool is applied after route edits. If you are using conflict prevention, you are prompted to run Apply Event Behaviors, which must be done before posting can be completed.

The following sections detail the results of executing this tool on event features.

Realignment scenario

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

Before realignment

Stay Put behavior

The geographic location of the event outside the realign region is maintained; the measures may change. The event may also split if it crosses the realign region. Portions of events in the realign region are retired.

Stay Put event behavior

Move behavior

The measures of the event are maintained; the geographic location may change.

Move event behavior

Retire behavior

Events intersecting the realignment region are retired.

Retire event behavior

Detailed behavior results

Event behaviors for route realignment are discussed in the following sections.

The following scenario involves one route and three events. The realignment (depicted with a gray line) starts in Event1, completely spans Event2, and ends in Event3. The resulting behaviors, time slices, and measures are detailed in the following sections.

Before realignment

EventRoute nameFrom dateTo dateFrom measureTo measure

Event1

Route1

1/1/2000

<null>

0

8

Event2

Route1

1/1/2000

<null>

8

12

Event3

Route1

1/1/2000

<null>

12

20

Stay Put behavior

If the realignment is set to occur on 1/1/2005, with realigned route values of 6 to 18 and Recalibrate route downstream 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 of 0 to 8. The second time slice is from 1/1/2005 to <null>, with measures of 0 to 6 that stay the same geographically but have the new measures of Route1.
  • 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 of 12 to 20. The second time slice is from 1/1/2005 to <null>, with measures of 18 to 24 that stay the same geographically but have the new measures of Route1.

Stay Put event behavior

EventRoute nameFrom dateTo dateFrom measureTo measureLocation error

Event1

Route1

1/1/2000

1/1/2005

0

8

No error

Event1

Route1

1/1/2005

<null>

0

6

No error

Event2

Route1

1/1/2000

1/1/2005

8

12

No error

Event3

Route1

1/1/2000

1/1/2005

12

20

No error

Event3

Route1

1/1/2005

<null>

18

24

No error

Move behavior

If the realignment is set to occur on 1/1/2005, with realigned route values of 6 to 18 and Recalibrate route downstream 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 of 0 to 8. The second time slice is from 1/1/2005 to <null> with measures of 0 to 8 that move geographically to maintain the original event measures. The event has the same measures but different geometry in the new time slice.
  • Event2 is represented by two time slices. There is a time slice from 1/1/2000 to 1/1/2005, with the original measures of 8 to 12. The second time slice is from 1/1/2005 to <null>, with measures of 8 to 12 that move geographically to maintain the original event measures. The event has the same measures but different geometry in the new time slice.
  • Event3 is represented by two time slices. There is a time slice from 1/1/2000 to 1/1/2005, with the original measures of 12 to 20. The second time slice is from 1/1/2005 to <null>, with measures of 12 to 20 that move geographically to maintain the original event measures. The event has the same measures but different geometry in the new time slice.

Move event behavior

EventRoute nameFrom dateTo dateFrom measureTo measureLocation error

Event1

Route1

1/1/2000

1/1/2005

0

8

No Error

Event1

Route1

1/1/2005

<null>

0

8

No Error

Event2

Route1

1/1/2000

1/1/2005

8

12

No Error

Event2

Route1

1/1/2005

<null>

8

12

No Error

Event3

Route1

1/1/2000

1/1/2005

12

20

No Error

Event3

Route1

1/1/2005

<null>

12

20

No Error

Retire behavior

If the realignment is set to occur on 1/1/2005, with realigned route values of 6 to 18 and Recalibrate route downstream chosen, this has the following effects:

  • Event1 retires.
  • Event2 retires.
  • Event3 retires.

Retire event behavior

EventRoute nameFrom dateTo dateFrom measureTo measureLocation error

Event1

Route1

1/1/2000

1/1/2005

0

8

No error

Event2

Route1

1/1/2000

1/1/2005

8

12

No error

Event3

Route1

1/1/2000

1/1/2005

12

20

No error