Disponible con licencia de Location Referencing.
When routes are extended, events are impacted, depending on the configured event behavior for each event layer.
Nota:
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.
Route extension scenario
The following route extension scenario involves one route and three events. The extension (depicted with a dashed line) is at the beginning of the route.
Stay Put behavior
The geographic location of the events is preserved; the measures are changed.
Move behavior
The event measures on the route are maintained; the geographic location is changed.
Retire behavior
The geographic location and measure of the events are preserved; the events are retired.
Upstream and downstream sections
Route editing impacts upstream and downstream sections differently. Use the following diagrams and table to understand this impact for the configured event behavior.
Refer to the following diagram to understand the upstream and downstream section for the route extension scenario.
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. |
Nota:
- Point events follow the same behavior as linear events but don't need to be split.
- If the option to Recalibrate the route downstream is chosen, the events downstream of the edited portion of the route have calibrate route event behaviors applied.
- Since the LRS is time aware, edit activities such as extending a route will time slice routes and events.
Route extension scenario
The following route extension scenario involves one route and three events. The extension (depicted with a dashed line) is at the beginning of the route.
Stay Put behavior
The geographic location of the events is preserved; the measures are changed.
Move behavior
The event measures on the route are maintained; the geographic location is changed.
Retire behavior
The geographic location and measure of the events are preserved; the events are retired.
Upstream and downstream sections
Route editing impacts upstream and downstream sections differently. Use the following diagrams and table to understand this impact for the configured event behavior.
Refer to the following diagram to understand the upstream and downstream section for the route extension scenario.
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. |
Nota:
- Point events follow the same behavior as linear events but don't need to be split.
- If the option to recalibrate route downstream is chosen, the events downstream of the edited portion of the route will have calibrate route event behaviors applied.
- Since the LRS is time aware, edit activities such as extending a route will 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 behavior
The route is active from 1/1/2000, and if the extension is set to occur on 1/1/2005, this will have the following effects:
- Event1 will be represented by two time slices. There will be a time slice as of 1/1/2000 to 1/1/2005, with the original measures of 0 to 20, and a time slice as of 1/1/2005 to <null>, with measures of 20 to 40 that will stay the same geographically.
- Event2 will be represented by two time slices. There will be a time slice as of 1/1/2000 to 1/1/2005, with the original measures of 20 to 30, and a time slice as of 1/1/2005 to <null> with measures of 40 to 50 that will stay the same geographically.
- Event3 will be represented by two time slices in the same way as Event1. There will be a time slice as of 1/1/2000 to 1/1/2005, with the original measures of 30 to 45, and a time slice as of 1/1/2005 to <null> with measures of 50 to 65 that will stay the same geographically.
Before Stay Put event behavior
The following diagram and table provide details about the route and its measures before 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 |
After Stay Put event behavior
The following diagram and table detail how event behavior rules are enforced after 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 |
Move behavior
The route is active from 1/1/2000, and if the extension is set to occur on 1/1/2005, this will have the following effects:
- Event1 will be represented by two time slices. There will be a time slice as of 1/1/2000 to 1/1/2005 and a time slice as of 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 will move to preserve measures of 0 to 20.
- Event2 will be represented by two time slices. There will be a time slice as of 1/1/2000 to 1/1/2005 and a time slice as of 1/1/2005 to <null>, both with the measures of 20 to 30. Since the new time slice can locate both route and measure, events will move to preserve measures of 20 to 30.
- Event3 will be represented by two time slices. There will be a time slice as of 1/1/2000 to 1/1/2005 and a time slice as of 1/1/2005 to <null>, both with the original measures 30 to 45. This new time slice will have measures 30 to 45 as well.
Before Move event behavior
The following diagram and table provide details about the route and its measures before 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 |
After Move event behavior
The following diagram and table detail how event behavior rules are enforced after 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 |
Retire behavior
The route is active from 1/1/2000, and if the extension is set to occur on 1/1/2005, this will have the following effects:
- Since event measures are altered, Event1 will retire.
- Since event measures are altered, Event2 will retire.
- Since event measures are altered, Event3 will retire.
Before Retire event behavior
The following diagram and table provide details about the route and its measures before 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 |
After Retire event behavior
The following diagram and table detail how event behavior rules are enforced after 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 |