Event behavior for route extension
Available with the Linear Referencing license.
When you extend a route, events are impacted depending on the configured event behavior for each event layer.
Note:
Events are not updated until you run the Apply Event Behaviors tool after route edits. If conflict prevention is enabled, you are prompted to run the Apply Event Behaviors tool before posting to the default version.
When you check the Recalibrate route downstream option during route editing, the tool applies the event behavior for route calibration to downstream sections. You can review configured event behaviors by viewing the LRS event properties.
The following sections describe route extension and the corresponding event behaviors.
Route extension scenario
Use the Extend Route tool to extend the beginning or end of a route.
Upstream and downstream sections
Route editing impacts upstream and downstream sections differently.
Refer to the following diagram to understand the upstream and downstream section for the route extension scenario:
The following table details how a route extension impacts upstream and 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:
The network can contain events that span routes in a line network. The behaviors are still applied in the same manner.
Because the linear referencing system (LRS) is time aware, edit activities, such as extending a route, time slice routes and events.
Route extension results
In this example, Route 1 is active from 1/1/2000. The extension is set to occur on 1/1/2005 where a length of 20 is added to the beginning of Route 1 and the Recalibrate route downstream option is checked. The following diagrams and tables demonstrate the route information before and after the extension.
Route before extension
The following diagram shows the route before the extension:
The following table provides details about the route before the extension:
| Route Name | From Date | To Date | From Measure | To Measure |
|---|---|---|---|---|
| Route1 | 1/1/2000 | <Null> | 0 | 55 |
| Route ID | From Date | To Date | From Measure | To Measure |
|---|---|---|---|---|
| Route1 | 1/1/2000 | <Null> | 0 | 55 |
Route after extension
The following diagram shows the route after the extension:
The following table provides details about the route after the extension:
| Route Name | From Date | To Date | From Measure | To Measure |
|---|---|---|---|---|
| Route1 | 1/1/2000 | 1/1/2005 | 0 | 55 |
| Route1 | 1/1/2005 | <Null> | 0 | 75 |
| Route ID | From Date | To Date | From Measure | To Measure |
|---|---|---|---|---|
| Route1 | 1/1/2000 | 1/1/2005 | 0 | 55 |
| Route1 | 1/1/2005 | <Null> | 0 | 75 |
Events before route extension
There are three events on Route 1 and all of them have a start date of 1/1/2000. The following diagram shows the route and events before extension:
The following table provides details about the events before the extension:
| Event | Route Name | From Date | To Date | From Measure | To 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 |
| Event | Route ID | From Date | To Date | From Measure | To 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 |
The following sections detail how event behavior rules are enforced after running the Apply Event Behaviors tool under this route extension scenario.
Stay Put event behavior
Although the geographic location of the event is maintained, the measures can change.
The route extension described above has the following effects:
Event 1 is retired on the date of extension because it is in the downstream portion of the edit section. A new event is created on the post-extension route with the extension date as the start date. The start measure changes to 20 and the end measure changes to 40 to accommodate the new measures of Route 1.
Event 2 is retired on the date of extension because it is in the downstream portion of the edit section. A new event is created on the post-extension route with the extension date as the starting date. The start measure changes to 40 and the end measure changes to 50 to accommodate the new measures of Route 1.
Event 3 is retired on the date of extension because it is in the downstream portion of the edit section. A new event is created on the post-extension route with the extension date as the starting date. The start measure changes to 50 and end measure changes 65 to accommodate the new measures of Route 1.
The following diagram shows the route and events after the extension:
Note:
The retired event is not drawn in the previous diagram.
The following table provides details about the events after the extension when Stay Put is the configured event behavior:
| Event | Route Name | From Date | To Date | From Measure | To Measure | Location 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 |
| Event | Route ID | From Date | To Date | From Measure | To Measure | Location 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
Although the measures of the event are maintained, the geographic location can change.
The route extension described above has the following effects:
Event 1 is retired on the date of extension because it is in the downstream portion of the edit section. A new event is created on the post-extension route with the extension date as the starting date. Because the measures do not change for the Move behavior, the event shifts to the left to maintain its original start measure of 0 and end measure of 20.
Event 2 is retired on the date of extension because it is in the downstream portion of the edit section. A new event is created on the post-extension route with the extension date as the starting date. Because the measures do not change for the Move behavior, the event shifts to the left to maintain its original start measure of 20 and end measure of 30.
Event 3 is retired on the date of extension because it is in the downstream portion of the edit section. A new event is created on the post-extension route with the extension date as the starting date. Because the measures do not change for the Move behavior, the event shifts to the left to maintain its original start measure of 30 and end measure of 45.
The following diagram shows the route and events after the extension:
The following table provides details about the events after the extension when Move is the configured event behavior:
| Event | Route Name | From Date | To Date | From Measure | To Measure | Location 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 |
| Event | Route ID | From Date | To Date | From Measure | To Measure | Location 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
Events in the downstream portion of the extension are retired.
The route extension described above has the following effects:
Event 1 is retired on the date of extension because it is in the downstream portion of the edit section.
Event 2 is retired on the date of extension because it is in the downstream portion of the edit section.
Event 3 is retired on the date of extension because it is in the downstream portion of the edit section.
The following diagram shows the route and events after the extension:
The following table provides details about the events after the extension when Retire is the configured event behavior:
| Event | Route Name | From Date | To Date | From Measure | To Measure | Location 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 |
| Event | Route ID | From Date | To Date | From Measure | To Measure | Location 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
If the event touches the extension, its shape is also extended to cover the extended portion of the route. The measures of the event are also updated to reflect the new shape.
The route extension described above has the following effects:
Event 1 is retired on the date of extension because it is in the downstream portion of the edit section. A new event is created on the post-extension route with the extension date as the start date. Because the event touches the route extension, it is also extended to cover the added length of 20 at the beginning or the route. The start measure updates to 0 and the end measure updates to 40.
Event 2 is retired on the date of extension because it is in the downstream portion of the edit section. A new event is created on the post-extension route with the extension date as the start date. Because the event does not touch the extension, it only updates the start measure to 40 and the end measure to 50 to maintain its location.
Event 3 is retired on the date of extension because it is in the downstream portion of the edit section. A new event is created on the post-extension route with the extension date as the start date. Because the event does not touch the extension, it only updates the start measure to 50 and the end measure to 65 to maintain its location.
The following diagram shows the route and events after the extension:
The following table provides details about the events after the extension when Cover is the configured event behavior:
| Event | Route Name | From Date | To Date | From Measure | To Measure | Location 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 |
| Event | Route ID | From Date | To Date | From Measure | To Measure | Location 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
In this example, there are four routes on the same line and the routes are active from 1/1/2000. The extension is set to occur on 1/1/2005 where a length of 10 is added to the beginning of Route 1, and the Recalibrate route downstream option is chosen. The following diagrams and tables demonstrate the route information before and after the extension.
Routes before extension
The following diagram shows the routes before the extension:
The following table provides details about the routes before the extension:
| 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 |
Routes after extension
The following diagram shows the routes after the extension:
The following table provides details about the routes after the extension:
| Route Name | Line Name | Line Order | From Date | To Date | From Measure | To Measure |
|---|---|---|---|---|---|---|
| Route1 | LineA | 100 | 1/1/2000 | 1/1/2005 | 0 | 10 |
| Route1 | LineA | 100 | 1/1/2005 | <Null> | 0 | 20 |
| 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 extension
There are two spanning events on routes on Line A. The following diagram shows the routes and events before the extension:
The following table provides details about the events before the extension:
| 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 when a route on a line in a line network is extended.
Stay Put event behavior
Although the geographic location of the event is maintained, the measures can change.
The route extension described above has the following effects:
Event 1 is retired on the date of extension because it is in the downstream portion of the edit section. A new event is created on the post-extension route with the extension date as the starting date (From Date). The start measure changes to 10 on Route 1 and the end measure changes to 30 on Route 3 to accommodate the new measures of Route 1.
Event 2 is not affected because it is only associated with Route 3 and Route 4, which are not involved in the extension.
The following diagram shows the routes and events after the extension:
Note:
The retired event is not drawn in the previous diagram.
The following table provides details about the events after the extension when Stay Put is the configured event behavior:
| Event ID | From Date | To Date | From Route Name | From Measure | To Route Name | To Measure |
|---|---|---|---|---|---|---|
| Event1 | 1/1/2000 | 1/1/2005 | Route1 | 0 | Route3 | 30 |
| Event1 | 1/1/2005 | <Null> | Route1 | 10 | Route3 | 30 |
| Event2 | 1/1/2000 | <Null> | Route3 | 30 | Route4 | 48 |
Move event behavior
Although the measures of the event are maintained, the geographic location can change.
The route extension described above has the following effects:
Event 1 is retired on the date of extension because it is in the downstream portion of the edit section. A new event is created on the post-extension route with the extension date as the starting date. Because the measures do not change for the Move behavior, the event also extends to the left to maintain its original start measure of 0 on Route 1 and end measure of 30 on Route 3.
Event 2 is not affected because it is only associated with Route 3 and Route 4, which are not involved in the extension.
The following diagram shows the routes and events after the extension:
The following table provides details about the events after the extension when Move is the configured event behavior:
| Event ID | From Date | To Date | From Route Name | From Measure | To Route Name | To Measure | Location 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
Events in the downstream portion of the extension are retired.
The route extension described above has the following effects:
Event 1 was present in the downstream portion of the extension; it is retired on the date of extension.
Event 2 is not affected because it is only associated with Route 3 and Route 4, which are not involved in the extension.
The following diagram shows the routes and events after the extension:
The following table provides details about the events after the extension when Retire is the configured event behavior:
| Event ID | From Date | To Date | From Route Name | From Measure | To Route Name | To Measure | Location Error |
|---|---|---|---|---|---|---|---|
| Event1 | 1/1/2000 | 1/1/2005 | Route1 | 0 | Route3 | 30 | No Error |
| Event2 | 1/1/2000 | <Null> | Route3 | 30 | Route4 | 48 | No Error |
Cover event behavior
If the event touches the extension, its shape is also extended to cover the extended portion of the route. The measures of the event are also updated to reflect the new shape.
The route extension described above has the following effects:
Event 1 is retired on the date of extension because it is in the downstream portion of the edit section. A new event is created on the post-extension route with the extension date as the starting date. Because the event touches the route extension, it is also extended to cover the added length of 10 at the beginning of the route. The start measure is updated to 0 on Route 1 and the end measure is updated to 30 on Route 3.
Event 2 is not affected because it is only associated with Route 3 and Route 4, which are not involved in the extension.
The following diagram shows the routes and events after the extension:
The following table provides details about the events after the extension when Cover is the configured event behavior:
| Event ID | From Date | To Date | From Route Name | From Measure | To Route Name | To Measure | Location 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, there are two routes: Route 1 on Line B and Route 2 on Line A. There is an Event 1 on Route 2. Route 2 is extended to the start position of Route 1 at the beginning of the route, with the Cover behavior configured as the event behavior. The Route 2 extension uses two centerlines (CL1 and CL2). The route is active from 1/1/2000, and the extension is set to occur on 1/1/2005 with Recalibrate route downstream checked. The following diagrams and tables demonstrate the route information before and after the extension.
In the following scenario, there are two routes: Route 1 and Route 2. There is an Event 1 on Route 2. Route 2 is extended to the start position of Route 1 at the beginning of the route, with the Cover behavior configured as the event behavior. The Route 2 extension uses two centerlines (CL1 and CL2). The route is active from 1/1/2000, and the extension is set to occur on 1/1/2005 with Recalibrate route downstream checked. The following diagrams and tables demonstrate the route information before and after the extension.
Concurrent route before extension
The following diagram shows the routes before the extension:
The following table provides details about the route before the extension:
| Route Name | Line Name | Line Order | From Date | To Date | From Measure | To Measure |
|---|---|---|---|---|---|---|
| Route1 | LineB | 100 | 1/1/2000 | <Null> | 0 | 5 |
| Route2 | LineA | 100 | 1/1/2000 | <Null> | 0 | 15 |
| Route ID | From Date | To Date | From Measure | To Measure |
|---|---|---|---|---|
| Route1 | 1/1/2000 | <Null> | 0 | 5 |
| Route2 | 1/1/2000 | <Null> | 0 | 15 |
Concurrent route after extension
The following diagram shows the routes after the extension:
The following table provides details about the routes after the extension:
| Route Name | Line Name | Line Order | From Date | To Date | From Measure | To Measure |
|---|---|---|---|---|---|---|
| Route1 | LineB | 100 | 1/1/2000 | <Null> | 0 | 5 |
| Route2 | LineA | 100 | 1/1/2000 | 1/1/2005 | 0 | 15 |
| Route2 | LineA | 100 | 1/1/2005 | <Null> | 0 | 30 |
| Route ID | From Date | To Date | From Measure | To Measure |
|---|---|---|---|---|
| Route1 | 1/1/2000 | <Null> | 0 | 5 |
| Route2 | 1/1/2000 | 1/1/2005 | 0 | 15 |
| Route2 | 1/1/2005 | <Null> | 0 | 30 |
Events before extension of a concurrent route with Cover behavior
There is one nonspanning event on Route 2. The following diagram shows the routes and event before extension:
The following table provides details about the event before the extension:
| Event ID | From Route Name | To Route Name | From Date | To Date | From Measure | To Measure | Location Error |
|---|---|---|---|---|---|---|---|
| Event1 | Route2 | Route2 | 1/1/2000 | <Null> | 0 | 15 | No Error |
| Event ID | Route ID | From Date | To Date | From Measure | To Measure | Location Error |
|---|---|---|---|---|---|---|
| Event1 | Route2 | 1/1/2000 | <Null> | 0 | 15 | No Error |
Events after extension of a concurrent route with Cover behavior
After extension, Route 2 is concurrent with the dominant route, Route 1, at the beginning of the extended section. Event 1 is retired on the date of extension because it is in the downstream portion of the edit section. A new event is created on the post-extension route with the extension date as the From Date. Because Event 1 touches the route extension, it extends to the left but it does not cover the section where Route 2 overlaps Route 1 because Route 1 is the dominant route in the concurrent section.
The following diagram provides details about the routes and event after extension.
Note:
The retired event is not drawn in the previous diagram.
The following table provides details about the event after the extension when Cover is the configured event behavior:
| Event ID | From Route Name | To Route Name | From Date | To Date | From Measure | To Measure | Location 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 |
| Event ID | Route ID | From Date | To Date | From Measure | To Measure | Location Error |
|---|---|---|---|---|---|---|
| Event1 | Route2 | 1/1/2000 | 1/1/2005 | 0 | 15 | No Error |
| Event1 | Route2 | 1/1/2005 | <Null> | 5 | 30 | No Error |
Concurrent routes with Cover behavior and spanning events
In the following scenario, there are four routes on two different lines. There is a spanning event Event 1 that goes from measure 0 on Route 2 to measure 17 on Route 3, and another spanning event Event 2 that goes from measure 17 on Route 3 to measure 36 on Route 4. Both events are configured with the Cover behavior. Route 2 is extended to the start position of Route 1 at the beginning of the route. The Route 2 extension uses two centerlines (CL1 and CL2). The route is active from 1/1/2000, and the extension is set to occur on 1/1/2005 with Recalibrate route downstream checked. The following diagrams and tables demonstrate the route information before and after the extension.
Concurrent route before extension
The following diagram shows the routes before the extension:
The following table provides details about the routes before the extension:
| Route Name | Line Name | Line Order | From Date | To Date | From Measure | To Measure |
|---|---|---|---|---|---|---|
| Route1 | LineB | 100 | 1/1/2000 | <Null> | 0 | 5 |
| Route2 | LineA | 100 | 1/1/2000 | <Null> | 0 | 10 |
| Route3 | LineA | 200 | 1/1/2000 | <Null> | 12 | 22 |
| Route4 | LineA | 300 | 1/1/2000 | <Null> | 28 | 38 |
Concurrent route after extension
The following diagram shows the routes after the extension:
The following table provides details about the routes after the extension:
| Route Name | Line Name | Line Order | From Date | To Date | From Measure | To Measure |
|---|---|---|---|---|---|---|
| Route1 | LineB | 100 | 1/1/2000 | <Null> | 0 | 5 |
| Route2 | LineA | 100 | 1/1/2000 | 1/1/2005 | 0 | 10 |
| Route2 | LineA | 100 | 1/1/2005 | <Null> | 0 | 20 |
| Route3 | LineA | 200 | 1/1/2000 | <Null> | 12 | 22 |
| Route4 | LineA | 300 | 1/1/2000 | <Null> | 28 | 38 |
Events before extension of a concurrent route with Cover behavior
There are two spanning events associated with routes on Line A.
The following diagram shows the routes and events before the extension:
The following table provides details about the events before the extension:
| Event ID | From Route Name | To Route Name | From Date | To Date | From Measure | To Measure | Location Error |
|---|---|---|---|---|---|---|---|
| Event1 | Route2 | Route3 | 1/1/2000 | <Null> | 0 | 17 | No Error |
| Event2 | Route3 | Route4 | 1/1/2000 | <Null> | 17 | 36 | No Error |
Events after extension of a concurrent route with Cover behavior
After extension, Route 2 is concurrent with the dominant route, Route 1, at the beginning of the extended section. Event 1 is retired on the date of extension because it is in the downstream portion of the edit section. A new event is created on the post-extension route with the extension date as the starting date. Because Event 1 touches the route extension, it extends to the left but it does not cover the section where Route 2 overlaps Route 1 because Route 1 is the dominant route in the concurrent section.
Event 2 is not affected because it is only associated with Route 3 and Route 4, which are not involved in extension.
The following diagram provides details about the routes and events after extension:
The following table provides details about the events after extension of a concurrent route when Cover is the configured event behavior:
| Event ID | From Route Name | To Route Name | From Date | To Date | From Measure | To Measure | Location 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 | <Null> | 17 | 36 | No Error |