When routes are realigned, events are impacted depending on the event behavior that is configured for each event layer.
The cover event behavior modifies the geometric location and measure of a line event to make the event go across the newly modified section. The following scenarios describe the results of the Apply Updates tool on event features in the edit activity region for the cover event behavior.
Event covering the entire route
When realigning a route, any event with cover behavior configured will be stretched to cover the newly realigned portion of the route.
In the following example, the initial from and to measures for Route1 and Event1 are 0 and 20, respectively. The route is realigned between measures 6 and 12, and after realignment the from and to measures of Route1 become 0 and 24, respectively.
Upon applying the event behaviors, Event1 will cover the entire route including the newly realigned portion. The from and to measures of Event1 also become 0 and 24.
Event covering the entire route with a time slice
In the following example, the route is active from 1/1/2000 and a realignment is set to occur on 1/1/2005.
Table 1: Before realignment covering entire route with time slice
Event | Route name | From date | To date | From measure | To measure |
---|---|---|---|---|---|
Event1 | Route1 | 1/1/2000 | <null> | 0 | 20 |
After realignment, Event1 will be represented by two time slices, one from 1/1/2000 to 1/1/2005 with the original measures of 0 to 20 and another from 1/1/2005 to <null> with measures of 0 to 24, that cover the entire route.
Table 2: After Realignment covering entire route with time slice
Event | Route name | From date | To date | From measure | To measure |
---|---|---|---|---|---|
Event1 | Route1 | 1/1/2000 | 1/1/2005 | 0 | 20 |
Event1 | Route1 | 1/1/2005 | <null> | 0 | 24 |
Event partially covering the route
When realigning a route, any partial event with cover behavior configured will be stretched proportionally in the newly realigned portion of the route.
In the following example, the from and to measures for Route1 are 0 and 20, respectively. The route is realigned between measures 6 and 12, and after realignment the from and to measures of Route1 become 0 and 24, respectively.
The initial from and to measures for Event1 are 0 and 9. Upon applying the event behaviors, Event1 will proportionally cover the route and the from and to measures for Event1 become 0 and 11.
Event partially covering the route with a time slice
In the following example, the route is active from 1/1/2000 and a realignment is set to occur on 1/1/2005.
Table 3: Before realignment covering partial route with time slice
Event | Route name | From date | To date | From measure | To measure |
---|---|---|---|---|---|
Event1 | Route1 | 1/1/2000 | <null> | 0 | 9 |
After realignment, Event1 will be represented by two time slices, one from 1/1/2000 to 1/1/2005 with the original measures of 0 to 9, and another from 1/1/2005 to <null> with measures of 0 to 11 that cover the entire route.
Table 4: After realignment covering partial route with time slice
Event | Route name | From date | To date | From measure | To measure |
---|---|---|---|---|---|
Event1 | Route1 | 1/1/2000 | 1/1/2005 | 0 | 9 |
Event1 | Route1 | 1/1/2005 | <null> | 0 | 11 |
Creating concurrent routes during realignment
In the following example, the from and to measures for Route1 and Event1 are 0 and 20, the from and to measures for Route2 and Event2 are 0 and 6, and the from and to measures for Route3 and Event3 are 0 and 6.
Table 5: Before realignment with concurrent routes
Event | Route Name | From Date | To Date | From Measure | To Measure |
---|---|---|---|---|---|
Event1 | Route1 | 1/1/2000 | <null> | 0 | 20 |
Event2 | Route2 | 1/1/2000 | <null> | 0 | 6 |
Event3 | Route3 | 1/1/2000 | <null> | 0 | 6 |
After realignment, the route is realigned between measures 6 and 12 and the from and to measures of Route1 after realignment become 0 and 24, respectively.
The realignment creates concurrent sections along Route2 and Route3. In this example, Route2 is most dominant followed by Route1 and Route3.
Upon applying the event behaviors, Event1 will cover the Route including the newly realigned portion and excluding the concurrent portion of Route2, and Event3 from the non-dominant section will be retired.
Table 6: After realignment with concurrent routes
Event | Route Name | From Date | To Date | From Measure | To Measure |
---|---|---|---|---|---|
Event1 | Route1 | 1/1/2000 | 1/1/2005 | 0 | 20 |
Event1 | Route1 | 1/1/2005 | <null> | 0 | 6 |
Event1 | Route1 | 1/1/2005 | <null> | 11 | 24 |
Event2 | Route2 | 1/1/2000 | <null> | 0 | 6 |
Event3 | Route3 | 1/1/2000 | 1/1/2005 | 0 | 6 |