Event behavior for route realignment

Available with Location Referencing license.

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.

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

Route realignment scenario

The Realign tool can be used to realign a single route or several adjoining routes that are part of the same line. For a line network, you can reassign the route segments in the realignment area to abandoned routes.

Refer to the Realign with abandonment scenario in a line network with spanning event section below for details.

Upstream and downstream sections

Route editing impacts upstream and downstream sections differently.

The following image illustrates the upstream and downstream sections for the route realignment scenario:

The following table provides more information about how events are impacted by a realignment depending on the configured event behavior:

Behavior	Events upstream realignment	Events intersecting realignment	Events downstream realignment
Stay Put	No action.	Retire event; line events crossing the edit section 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	No action.	Shape is regenerated to a 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.	If route calibration is changed, the calibrate event behavior is applied; otherwise, no action is taken.
Cover	No action.	Retire event; line events crossing the edit section are not split and are proportionally moved to new route locations	If route calibration is changed, the calibrate event behavior is applied; otherwise, no action is taken.
Snap	No action.	Retire event; 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, routes and events are time sliced with edit activities, such as reassigning a route.

Route realignment results

In this example, Route1 is active from 1/1/2000. The realignment is set to occur on 1/1/2005, where the middle of Route1 is rerouted to a new location with the Recalibrate route downstream check box checked. The images and tables below demonstrate the route information before and after the realignment.

Before route realignment

The following image shows the route before realignment:

The following table provides details about the route before realignment:

Route ID	From Date	To Date	From Measure	To Measure
Route1	1/1/2000	<Null>	0	20

After route realignment

The following image shows the route after realignment.

The following table provides details about the route after realignment:

Route ID	From Date	To Date	From Measure	To Measure
Route1	1/1/2000	1/1/2005	0	20
Route1	1/1/2005	<Null>	0	24

Events before route realignment

Three events are on Route1 and all of them have a starting date (From Date) of 1/1/2000. The following image shows the route and events before realignment:

The following table provides details about the events before realignment:

Event	Route ID	From Date	To Date	From Measure	To 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

The following sections describe how event behavior rules are enforced after running the Apply Event Behaviors tool under this route realignment 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 realign region. Portions of events in the realign region are retired.

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

Edit activity	Event behavior
Realign	Stay Put
Calibrate	Stay Put

Note:

For any route edit in which the Recalibrate route downstream check box is checked, any portion of the route downstream of the edited section is recalibrated. The calibrate event behavior is applied in these recalibrated sections.

The route realignment described above has the following effects:

• Event1 is retired on the date of realignment because part of it is in the edit section. A new event is created on the postrealignment route with the realignment date as the starting date (From Date). The start measure (From Measure) value changes to 0 and the end measure (To Measure) value changes to 6 to accommodate the new measures of Route1.
• Event2 is retired on the date of realignment because it is completely within the edit section.
• Event3 is retired on the date of realignment because part of it is in the edit section. A new event is created on the postrealignment route with the realignment date as the starting date. The start measure value changes to 18 and the end measure value changes to 24 to accommodate the new measures of Route1.

The following image shows the route and events after realignment:

Note:

The retired event is not drawn in the image above.

The following table provides details about the events after realignment:

Event	Route ID	From Date	To Date	From Measure	To Measure	Location 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 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 activity	Event behavior
Realign	Move
Calibrate	Stay Put

The route realignment described above has the following effects:

• Event1 is retired on the date of realignment because part of it is in the edit section. A new event is created on the postrealignment route with the realignment 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 and end measure values of 0 to 8.
• Event2 is retired on the date of realignment because it is completely in the edit section. A new event is created on the postrealignment route with the realignment 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 and end measure values of 8 to 12.
• Event3 is retired on the date of realignment because part of it is in the edit section. A new event is created on the postrealignment route with the realignment 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 and end measure values of 12 to 20.

The following image shows the route and events after realignment:

The following image shows the route and events after realignment:

Event	Route ID	From Date	To Date	From Measure	To Measure	Location 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 event behavior

Events intersecting the realignment region are retired. All three events are retired.

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

Edit activity	Event behavior
Realign	Retire
Calibrate	Stay Put

The route realignment described above has the following effects:

• Part of Event1 was present in the realignment portion; Event1 is retired on the date of realignment.
• Event2 was completely present in the realignment portion; it is retired on the date of realignment.
• Part of Event3 was present in the realignment portion; Event3 is retired on the date of realignment.

The following image shows the route and events after realignment:

The following table provides details about the events after realignment:

Event	Route ID	From Date	To Date	From Measure	To Measure	Location 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

Cover event behavior

If the event is in the realignment area, its shape is changed proportionally to cover the realigned portion of the route. The measures of the event are also updated to reflect the new shape.

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

Edit activity	Event behavior
Realign	Cover
Calibrate	Stay Put

The route realignment described above has the following effects:

• Event1 is retired on the date of realignment because part of it is in the edit section. A new event is created on the postrealignment route with the realignment date as the starting date. Because part of the event is in the realignment area, this portion of Event1 is lengthened proportionally to cover the increased length of the route due to realignment. The start and end measure values are updated to 0 to 9.
• Event2 is retired on the date of realignment because it is completely in the edit section. A new event is created on the postrealignment route with the realignment date as the starting date. Because the event is located within the realignment area, the entire event is lengthened proportionally to cover the increased length of the route due to realignment. The start and end measure values are updated to 9 to 15.
• Event3 is retired on the date of realignment because part of it is in the edit section. A new event is created on the postrealignment route with the realignment date as the starting date. Because part of the event is in the realignment area, this portion of Event3 is lengthened proportionally to cover the increased length of the route due to realignment. The start and end measure values are updated to 15 to 24.

The following image shows the route and events after realignment:

The following table provides details about the events after realignment:

Event	Route ID	From Date	To Date	From Measure	To Measure	Location Error
Event1	Route1	1/1/2000	1/1/2005	0	8	No Error
Event1	Route1	1/1/2005	<Null>	0	9	No Error
Event2	Route1	1/1/2000	1/1/2005	8	12	No Error
Event2	Route1	1/1/2005	<Null>	9	15	No Error
Event3	Route1	1/1/2000	1/1/2005	12	20	No Error
Event3	Route1	1/1/2005	<Null>	15	24	No Error

Snap event behavior

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

In this example, Route2 is concurrent with Route1. Route2 is in the reverse direction and has the start and end measure values of 0 to 20.

Note:

For more examples of concurrent route scenarios, refer to the Detailed realign event behaviors with concurrent routes section.

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

Edit activity	Event behavior
Realign	Snap
Calibrate	Stay Put

The route realignment described above has the following effects:

• Event1 is retired on the date of realignment because part of it is in the edit section. It then splits into two event records on the postrealignment routes with the realignment date as the starting date. This is because a concurrent route exists in the realignment section, and the portion of Event1 in the realignment section snaps to Route2, the concurrent route, after realignment. It is also reversed to accommodate the direction of Route2. As a result, Event1 splits into two pieces to maintain its geographic location. The first event record has the start and end measure values of 0 to 6 on Route1. The second event record snaps to Route2 and has the start and end measure values of 12 to 14 on Route2.
• Event2 is retired on the date of reassignment because it is completely within the edit section. As a concurrent route exists in the realignment section, Event2 snaps to Route2, the concurrent route, after realignment. It is also reversed to accommodate the direction of Route2. The new event record has the realignment date as the starting date. The new start and end measure values of Event2 become 8 to 12 on Route2 to maintain the geographic location of Event2.
• Event3 is retired on the date of realignment because part of it is in the edit section. It then splits into two event records on the postrealignment routes with the realignment date as the starting date. This is because a concurrent route exists in the realignment section, and the portion of Event3 in the realignment section snaps to Route2, the concurrent route, after realignment. It is also reversed to accommodate the direction of Route2. As a result, Event3 splits into two pieces to maintain its geographic location. The first event record has the start and end measure values of 18 to 24 on Route1. The second event record snaps to Route2 and has the start and end measure values of 6 to 8 on Route2.

The following image shows the route and events after realignment:

The following image shows the route and events after realignment:

Event	Route ID	From Date	To Date	From Measure	To Measure	Location Error
Event1	Route1	1/1/2000	1/1/2005	0	8	No Error
Event1	Route1	1/1/2005	<Null>	0	6	No Error
Event1	Route2	1/1/2005	<Null>	12	14	No Error
Event2	Route1	1/1/2000	1/1/2005	8	12	No Error
Event2	Route2	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>	18	24	No Error
Event3	Route2	1/1/2005	<Null>	6	8	No Error

Realign in a line network

If the selected network is a line network, you can provide new measures to the route segment in the realignment area. The new measures and the Recalibrate route downstream option determine whether new routes will be created on the line of the realigned route.

In the example below, Route1 belongs to Line1 and is active from 1/1/2000. The realignment is set to occur on 1/1/2005, where the middle of Route1 is rerouted to a new location. The subsections below illustrate different scenarios of realignment measures and recalibration. The images and tables demonstrate the route and event information before the realignment.

Before route realignment

The following image shows the route before realignment:

The following table provide details about the route before realignment:

Route Name	Line Name	Line Order	From Date	To Date	From Measure	To Measure
Route1	Line1	100	1/1/2000	<Null>	0	20

Events before realignment

Three events are on Route1 and all of them have a starting date (From Date) of 1/1/2000. The following image shows the route and events before realignment:

The following table provides details about the events before realignment:

Event	Route Name	From Date	To Date	From Measure	To 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

The following sections describe how measures and downstream recalibration play a role in realignment when the Stay Put event behavior is configured.

Note:

In all of the examples below, both the realign event behavior and the calibrate event behavior are set to Stay Put.

The calibrate event behavior is applied before the realign 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.

To review other event behaviors for calibration, refer to the Event behavior for route calibration topic.

When events are configured with realign Stay Put behavior, the geographic location of the event is maintained, but the measures can change. The event can also split if it crosses the realign region. Portions of events in the realign region are retired.

Realignment with no new route creation and with downstream recalibration

In this scenario, the Recalibrate route downstream check box is checked. The realignment starts with measure 6 and ends with measure 18 on Route1, as an additional length of 4 is added due to shape change. The realigned portion of Route1 does not use new measures, so it can remain monotonically calibrated after realignment, and no new route is created.

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

Edit Activity	Event Behavior
Realign	Stay Put
Calibrate	Stay Put

The following image shows the route after realignment:

The following table provides details about the route after realignment:

Route Name	Line Name	Line Order	From Date	To Date	From Measure	To Measure
Route1	Line1	100	1/1/2000	1/1/2005	0	20
Route1	Line1	100	1/1/2005	<Null>	0	24

The route realignment described above has the following effects:

• Event1 is retired on the date of realignment since part of it is in the edit section. A new event is created on the postrealignment route with the realignment date as the starting date. The start measure (From Measure) value changes to 0 and the end measure (To Measure) value changes to 6 to accommodate the new measures of Route1.
• Event2 is retired on the date of realignment since it is completely within the edit section.
• Event3 is retired on the date of realignment since part of it is in the edit section. A new event is created on the postrealignment route with the realignment date as the starting date. The start measure value changes to 18 and the end measure value changes to 24 to accommodate the new measures of Route1.

The following image shows the routes and events after realignment:

Note:

The retired event is not drawn in the image above.

The following table provides details about the events after realignment:

Event	Route Name	From Date	To Date	From Measure	To Measure	Location 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

Realignment with new route creation and with downstream recalibration

In this scenario, the Recalibrate route downstream check box is checked. The realignment starts with measure 6 and ends with measure 18 on Route1 as an additional length of 4 is added due to shape change. However, the realigned portion of Route1 has new measures from 0 to 12. In this case, Route1 cannot remain monotonically calibrated after realignment, so a new route is created. The new route is named RouteNew.

Since the Recalibrate route downstream check box is checked, RouteNew is recalibrated downstream, and it replaces the original downstream portion of Route1. The new measures of RouteNew are determined by the length of the realignment.

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

Edit Activity	Event Behavior
Realign	Stay Put
Calibrate	Stay Put

The following image shows the routes after realignment:

The following tables provide details about the routes after realignment:

Route Name	Line Name	Line Order	From Date	To Date	From Measure	To Measure
Route1	Line1	100	1/1/2000	1/1/2005	0	20
Route1	Line1	100	1/1/2005	<Null>	0	6
RouteNew	Line1	200	1/1/2005	<Null>	0	18

The route realignment described above has the following effects:

• Event1 is retired on the date of realignment since part of it is in the edit section. A new event is created on the postrealignment Route1 with the realignment date as the starting date. The start measure value changes to 0 and the end measure value changes to 6 to accommodate the new measures of Route1.
• Event2 is retired on the date of realignment since it is completely within the edit section.
• Event3 is retired on the date of realignment since part of it is in the edit section. Since RouteNew has replaced Route1 at the location of Event3, Event3 cannot be created when the calibrate Stay Put behavior is applied.

The following image shows the routes and events after realignment:

The following table provides details about the events after realignment:

Event	Route Name	From Date	To Date	From Measure	To Measure	Location 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

Note:

For events to stay on the routes downstream of the realignment, the routes must not be retired.

Realignment with new route creation and without downstream recalibration

In this scenario, the Recalibrate route downstream check box is not checked. The realignment starts with measure 6 and ends with measure 12 on Route1. However, the realignment is done using the reverse direction of the chosen centerlines. In this case, Route1 cannot remain monotonically calibrated after realignment, as the realigned portion is reversed, so a new route is created. The new route is named RouteNew. RouteNew has a start measure of 12, because the realignment starts with measure 12 on Route1, and an end measure of 24, because the length of the realignment is 12.

Since the Recalibrate route downstream check box is not checked, the right portion of Route1 has become a new route, Route1b. Route1b has a start measure of 12, because the downstream starts with the original measure 12 on Route1, and an end measure of 18, because the length of the right arm is 6.

The following table shows the edit activity involved in the route edit and its corresponding event behavior:

Edit Activity	Event Behavior
Realign	Stay Put

The following image shows the routes after realignment:

The following table provides details about the routes after realignment:

Route Name	Line Name	Line Order	From Date	To Date	From Measure	To Measure
Route1	Line1	100	1/1/2000	1/1/2005	0	20
Route1	Line1	100	1/1/2005	<Null>	0	6
RouteNew	Line1	200	1/1/2005	<Null>	12	24
Route1	Line1	300	1/1/2005	<Null>	12	18

The route realignment described above has the following effects:

• Event1 is retired on the date of realignment since part of it is in the edit section. A new event is created on the postrealignment Route1 with the realignment date as the starting date. The start measure value changes to 0 and the end measure value changes to 6 to accommodate the new measures of Route1.
• Event2 is retired on the date of realignment since it is completely within the edit section.
• Event3 is retired on the date of realignment since part of it is in the edit section. Since Route1b has replaced Route1 at the location of Event3, Event3 cannot be created when the calibrate Stay Put behavior is applied.

The following image shows the routes and events after realignment:

The following table provides details about the events after realignment:

Event	Route Name	From Date	To Date	From Measure	To Measure	Location 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

Realign in a line network with spanning events

The following sections describe how event behavior rules are enforced that span routes when a route on a line in a line network is realigned.

In this example, four routes are on LineA and the routes are active from 1/1/2000. The realignment is set to occur on 1/1/2005 from the middle of Route2 to the middle of Route4. Subsections below illustrate scenarios with different Recalibrate route downstream and Reassign to abandoned route options. In this section, the graphics and tables demonstrate the route and event information before the realignment.

Before route realignment

The following image shows the routes before realignment:

The following table provides details about the routes before realignment:

Route Name	Line Name	Line Order	From Date	To Date	From Measure	To 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

Events before route realignment

Two events are on LineA and both of them have a starting date (From Date) of 1/1/2000. The following image shows the routes and events before realignment:

The following table provides details about the events before realignment:

Event ID	From Date	To Date	From Route Name	To Route Name	From Measure	To 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 after running the Apply Event Behaviors tool under scenarios with different Recalibrate route downstream and Reassign to abandoned route options.

Realign with abandonment scenario in a line network with spanning events with Stay Put event behavior

If the selected network is a line network, you can reassign the route portion in the realignment area to the abandoned route, which is a new route on a new line. Any event in the realign section follows the reassign event behavior. If you want the events to transfer to the abandoned route, configure the Snap behavior for the reassign route editing type.

In this example, the events are configured with the realign Stay Put event behavior, reassign Snap event behavior, and calibrate Stay Put event behavior. Both Recalibrate route downstream and Reassign to abandoned route are checked in this edit.

Note:

The reassign event behavior is applied before the realign event behavior, so it is important to verify the event feature layer's reassign event behavior configuration before checking the Reassign to abandoned route check box.

The calibrate event behavior is applied before the realign 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.

To explore other event behaviors for reassignment and calibration, refer to the Event behavior for route reassignment and Event behavior for route calibration topics.

After route realignment

Since Reassign to abandoned route is checked, the routes and the portions of routes that are within the realign region have become new, abandoned routes on a line named LineB. Route2_Ab has a start measure of 17 and an end measure of 22. Route3_Ab has a start measure of 25 and an end measure of 35. Route4_Ab has a start measure of 38 and an end measure of 43. These measures are from the original measures on the realigned routes.

Route2 becomes the only route in the realignment area, as the realignment starts on Route2. Since Recalibrate route downstream is checked, Route2 is recalibrated downstream, and it retires the original Route4. The new measures of Route2 are determined by the length of realignment.

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

Edit Activity	Event Behavior
Realign	Stay Put
Reassign	Snap
Calibrate	Stay Put

The following image shows the routes after realignment:

The following table provides details about the routes after realignment:

Route Name	Line Name	Line Order	From Date	To Date	From Measure	To Measure
Route1	LineA	100	1/1/2000	<Null>	0	10
Route2	LineA	200	1/1/2000	1/1/2005	12	22
Route2	LineA	200	1/1/2005	<Null>	12	50
Route3	LineA	300	1/1/2000	1/1/2005	25	35
Route4	LineA	400	1/1/2000	1/1/2005	38	48
Route2_Ab	LineB	100	1/1/2005	<Null>	17	22
Route3_Ab	LineB	200	1/1/2005	<Null>	25	35
Route4_Ab	LineB	300	1/1/2005	<Null>	38	43

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 realign region. When Snap is set as the reassign event behavior, the events and portions of events that are within the realign region will snap to the abandoned route to maintain their geographic locations.

The route realignment described above has the following effects:

• Event1 is retired on the date of realignment since part of it is in the edit section. It then splits into two event records on the postrealignment route with the realignment date as the starting date. As the reassign event behavior is applied before the realign event behavior, the portion of Event1 that is in the realignment section splits from the original Event1 and snaps to the abandoned routes. The other portion of Event1 that stays on LineA is shortened to the length of the left portion of LineA before the realign Stay Put event behavior is applied. When the realign Stay Put event behavior is applied, this event does not need to change its measures to maintain its geographic location. As a result, Event1 splits into two events. One event stays on LineA with a start measure of 0 on Route1 and an end measure of 17 on Route2. The other event snaps to the abandoned routes with a start measure of 17 on Route2_Ab and an end measure of 30 on Route3_Ab.
• Event2 is retired on the date of realignment because part of it is in the edit section. As the reassign event behavior is applied first, the portion of Event2 that is in the realignment section splits from the original Event2 and snaps to the abandoned routes. The other portion of Event2 that was downstream of realignment cannot be created when the calibrate Stay Put behavior is applied, because Route2 has replaced Route4 at this location. As a result, there is only one new event record for Event2 that starts from measure 30 on Route3_Ab and ends at measure 43 on Route4_Ab.

The following image shows the routes and events after realignment:

Note:

The retired event is not drawn in the image above.

The following table provides details about the events after realignment:

Event ID	From Date	To Date	From Route Name	To Route Name	From Measure	To Measure	Location Error
Event1	1/1/2000	1/1/2005	Route1	Route3	0	30	No Error
Event1	1/1/2005	<Null>	Route1	Route2	0	17	No Error
Event1	1/1/2005	<Null>	Route2_Ab	Route3_Ab	17	30	No Error
Event2	1/1/2000	1/1/2005	Route3	Route4	30	48	No Error
Event2	1/1/2005	<Null>	Route3_Ab	Route4_Ab	30	43	No Error

Realignment without abandonment scenario in a line network with spanning events

The following sections describe the realign Cover and Snap event behaviors for the route realignment activity above. The Recalibrate route downstream check box is checked but Reassign to abandoned route is not checked. As a result, routes in the realignment area will retire without being reassigned to a line of abandonment.

The events are configured with the calibrate Stay Put event behavior.

Note:

The calibrate event behavior is applied before the realign 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.

To see other event behaviors for calibration, refer to the Event behavior for route calibration topic.

After route realignment

Route2 becomes the only route in the realignment area, as the realignment starts on Route2. Since Recalibrate route downstream is checked, Route2 is recalibrated downstream, and it retires the original Route4. The new measures of Route2 are determined by the length of realignment. No abandoned route is created as Reassign to abandoned route is not checked.

The following image shows the routes after realignment:

The following table provides details about the routes after realignment:

Route Name	Line Name	Line Order	From Date	To Date	From Measure	To Measure
Route1	LineA	100	1/1/2000	<Null>	0	10
Route2	LineA	200	1/1/2000	1/1/2005	12	22
Route2	LineA	200	1/1/2005	<Null>	12	50
Route3	LineA	300	1/1/2000	1/1/2005	25	35
Route4	LineA	400	1/1/2000	1/1/2005	38	48

The following sections describe how the realign Cover and Snap event behavior rules are enforced after running the Apply Event Behaviors tool under this route realignment scenario.

Cover event behavior

If the event is in the realignment area, its shape is changed proportionally to cover the realigned portion of the route. The measures of the event are also updated to reflect the new shape. For events in the downstream portion of realignment, calibrate event behavior is applied.

Note:

Use the Cover realign event behavior if the events need to stay on realigned route portions. Cover is the only event behavior that prevents events from splitting by reassigning event behaviors.

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

Edit Activity	Event Behavior
Realign	Cover
Calibrate	Stay Put

The route realignment described above has the following effects:

• Event1 is retired on the date of realignment since part of it is in the edit section. A new event is created on the postrealignment route with the realignment date as the starting date. Because part of the event is in the realignment area, this portion of Event1 is lengthened proportionally to cover the increased length of the route due to realignment. The new Event1 has a start measure of 0 on Route1 and an end measure of 31 on Route2.
• Event2 is retired on the date of realignment since part of it is in the edit section. A new event is created on the postrealignment route with the realignment date as the starting date. Because part of the event is in the realignment area, this portion of Event2 is lengthened proportionally to cover the increased length of the route due to realignment. The new Event2 has a start measure of 31 on Route2 and an end measure of 50 on Route2.

The following image shows the routes and events after realignment:

The following table provides details about the events after realignment:

Event ID	From Date	To Date	From Route Name	To Route Name	From Measure	To Measure	Location Error
Event1	1/1/2000	1/1/2005	Route1	Route3	0	30	No Error
Event1	1/1/2005	<Null>	Route1	Route2	0	31	No Error
Event2	1/1/2000	1/1/2005	Route3	Route4	30	48	No Error
Event2	1/1/2005	<Null>	Route2	Route2	31	50	No Error

Snap event behavior

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

For events in the downstream portion of realignment, the calibrate event behavior is applied.

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

Note:

For more examples of concurrent routes, refer to the Detailed realign event behaviors with concurrent routes section.

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

Edit activity	Event behavior
Realign	Snap
Calibrate	Stay put

The route realignment described above has the following effects:

• Event1 is retired on the date of realignment since part of it is in the edit section. It then splits into two event records on the postrealignment routes with the realignment date as the starting date. This is because a concurrent route exists in the realignment section, and the portion of Event1 in the realignment section snaps to Route5, the concurrent route, after realignment. It 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 0 on Route1 and end measure value of 17 on Route2. The second event record snaps to Route5 and has the start measure value of 15 on Route5 and end measure value of 25 on Route5.
• Event2 is retired on the date of realignment since part of it is in the edit section. As the reassign event behavior is applied first, the portion of Event2 that is in the realignment section splits from the original Event2 and snaps to the concurrent route, Route5. It is also reversed to accommodate the direction of Route5. The other portion of Event2 that was at the downstream of realignment cannot be created when calibrate Stay Put behavior is applied, because Route2 has replaced Route4 at this location. As a result, there is only one new event record for Event2 that starts from measure 5 on Route5 and ends at measure 15 on Route5.

The following image shows the routes and events after realignment:

The following table provides details about the events after realignment:

Event ID	From Date	To Date	From Route Name	To Route Name	From Measure	To Measure	Location Error
Event1	1/1/2000	1/1/2005	Route1	Route3	0	30	No Error
Event1	1/1/2005	<Null>	Route1	Route2	0	17	No Error
Event1	1/1/2005	<Null>	Route5	Route5	15	25	No Error
Event2	1/1/2000	1/1/2005	Route3	Route4	30	48	No Error
Event2	1/1/2005	<Null>	Route5	Route5	5	15	No Error

Detailed realign event behaviors with concurrent routes

The following sections describe how realign Cover and Snap event behavior rules are enforced when routes that have a concurrent section with dominant routes are realigned.

Nonline network scenario

In this example, three routes are active from 1/1/2000: Route1, Route2, and Route3. Route3 is concurrent with the middle part of Route2, and it is in the reverse direction. Route3 is the subordinate route. The realignment is set to occur on 1/1/2005 where the middle of Route2 is realigned in a section that overlaps the dominant concurrent Route1. The Recalibrate route downstream check box is checked.

The graphics and tables below demonstrate the route information before and after the realignment.

Before route realignment

The following image shows the routes before realignment:

The following table provides details about the routes before realignment:

Route ID	From Date	To Date	From Measure	To Measure
Route1	1/1/2000	<Null>	0	10
Route2	1/1/2000	<Null>	0	30
Route3	1/1/2000	<Null>	10	20

After route realignment

The following image shows the routes after realignment:

The following table provides details about the routes after realignment:

Route ID	From Date	To Date	From Measure	To Measure
Route1	1/1/2000	<Null>	0	10
Route2	1/1/2000	1/1/2005	0	30
Route2	1/1/2005	<Null>	0	40
Route3	1/1/2000	<Null>	10	20

Events before route realignment

Event1 is on Route2 and it has a starting date (From Date) of 1/1/2000. The following image shows the routes and event before realignment:

The following table provides details about the event before realignment:

Event	Route ID	From Date	To Date	From Measure	To Measure
Event1	Route2	1/1/2000	<Null>	0	30

Cover event behavior

If the event is in the realignment area, its shape is changed to cover the realigned portion of the route. The measures of the event are also updated to reflect the new shape.

If the event is created on the dominant route and route concurrencies are formed by realignment, the event continues to cover the entire dominant route. If the event is created on the subordinate route and route concurrencies are formed by realignment, the event does not cover the segment on the subordinate route where the dominant route is present.

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

Edit Activity	Event Behavior
Realign	Cover
Calibrate	Stay Put

Note:

For any route edit in which the Recalibrate route downstream check box is checked, any portion of the route downstream of the edited section is recalibrated. Calibrate event behavior is applied in these recalibrated sections.

The route realignment described above has the following effect:

• Event1 is retired on the date of realignment because part of it is in the edit section. It then forms two event records on the postrealignment route with the realignment date as the starting date. This is because Event1 is associated with the subordinate route, Route2, and after realignment, it does not cover the segment on Route2 where the dominant Route1 is present. The upstream event record has the start measure value of 0 and end measure value of 15 to cover the portion of Route2 until the concurrency with Route1, and the downstream event record has the start measure value of 25 and end measure value of 40 to cover Route2 after the concurrency with Route1.

The following image shows the routes and event after realignment:

Note:

The retired event is not drawn in the image above.

The following table provides details about the event after realignment:

Event	Route ID	From Date	To Date	From Measure	To Measure	Location Error
Event1	Route2	1/1/2000	1/1/2005	0	30	No Error
Event1	Route2	1/1/2005	<Null>	0	15	No Error
Event1	Route2	1/1/2005	<Null>	25	40	No Error

Snap event behavior

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

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

Edit activity	Event behavior
Realign	Snap
Calibrate	Stay Put

The route realignment described above has the following effects:

• Event1 is retired on the date of realignment because part of it is in the edit section. It then forms three event records on the postrealignment route with the realignment date as the starting date. This is because there is a concurrent route that exists in the realignment section, and the portion of Event1 in the realignment section snaps to Route3, the concurrent route, after realignment. It is also reversed to accommodate the direction of Route3. As a result, Event1 splits into three pieces to maintain its geographic location.
• The first event record has the start measure value of 0 and end measure value of 10 on Route2, the second event record snaps to Route3 and has the start measure value of 10 and end measure value of 20 on Route3, and the downstream event record has the start measure value of 30 and end measure value of 40 on Route2.

The following image shows the routes and event after realignment:

The following table provides details about the event after realignment:

Event	Route ID	From Date	To Date	From Measure	To Measure	Location Error
Event1	Route2	1/1/2000	1/1/2005	0	30	No Error
Event1	Route2	1/1/2005	<Null>	0	10	No Error
Event1	Route2	1/1/2005	<Null>	30	40	No Error
Event1	Route3	1/1/2005	<Null>	10	20	No Error

Line network scenario

In this example, two routes on LineA are active from 1/1/2000: Route1 and Route2, and Route3 on LineB is in the reverse direction. The realignment is set to occur on 1/1/2005 where half of Route1 and half of Route2 are realigned.

Route1 becomes the only route on LineA in the realignment area, as the realignment starts on Route1. Since Recalibrate route downstream is checked, Route1 is recalibrated downstream, and it retires the original Route2. The new measures of Route1 are determined by the length of realignment. No abandoned route is created as Reassign to abandoned route is not checked.

Route1 has a higher rank than Route3 after realignment.

Note:

You can reverse the direction for centerlines in a route editing activity using the Flip the direction of the centerlines button .

The images and tables below demonstrate the route information before and after the realignment.

Before route realignment

The following image shows the routes before realignment:

The following table provides details about the routes before realignment:

Route Name	Line Name	Line Order	From Date	To Date	From Measure	To Measure
Route1	LineA	100	1/1/2000	<Null>	0	14
Route2	LineA	200	1/1/2000	<Null>	17	28
Route3	LineB	100	1/1/2000	<Null>	0	10

After route realignment

The following image shows the routes after realignment:

The following table provides details about the routes after realignment:

Route Name	Line Name	Line Order	From Date	To Date	From Measure	To Measure
Route1	LineA	100	1/1/2000	1/1/2005	0	14
Route1	LineA	100	1/1/2005	<Null>	0	35
Route2	LineA	200	1/1/2000	1/1/2005	17	28
Route3	LineB	100	1/1/2000	<Null>	0	10

Events before route realignment

Event1 is on LineA and it has a starting date (From Date) of 1/1/2000. The following image shows the routes and event before realignment:

The following table provides details about the event before realignment:

Event ID	From Date	To Date	From Route Name	To Route Name	From Measure	To Measure	Location Error
Event1	1/1/2000	<Null>	Route1	Route2	0	28	No Error

Cover event behavior

If the event is in the realignment area, its shape is changed proportionally to cover the realigned portion of the route. The measures of the event are also updated to reflect the new shape.

If the event is created on the dominant route and route concurrencies are formed by realignment, the event continues to cover the entire dominant route. If the event is created on the subordinate route and route concurrencies are formed by realignment, the event does not cover the segment on the subordinate route where the dominant route is present.

Note:

For any route in which the Recalibrate route downstream check box is checked, any portion of the route downstream of the edited section is recalibrated. Calibrate event behavior is applied in these recalibrated sections.

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

Edit Activity	Event Behavior
Realign	Cover
Calibrate	Stay Put

The Realign route edit activity with the Cover event behavior has the following effect:

• Event1 is retired on the date of realignment because part of it is in the edit section. A new event is created on the postrealignment route with the realignment date as the starting date. Because Route1 is dominant over Route3, Event1 continues to cover the entire Route1. Its start measure value changes to 0 and end measure value changes to 35 on Route1.

The following image shows the routes and event after realignment:

The following table provides details about the event after realignment:

Event ID	From Date	To Date	From Route Name	To Route Name	From Measure	To Measure	Location Error
Event1	1/1/2000	1/1/2005	Route1	Route2	0	28	No Error
Event1	1/1/2005	<Null>	Route1	Route1	0	35	No Error