Доступно с лицензией Location Referencing.
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. Pipeline Referencing has options to retire a realigned route, or to reassign the realigned portion of the route to an abandoned route with a new route name and route ID.
Примечание:
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.
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.
Move behavior
The measures of the event are maintained; the geographic location may change.
Retire behavior
Events intersecting the realignment region are retired.
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.
| 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 |
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.
| 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 |
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.
| 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 | 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.
| 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 |
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 with abandonment scenario (reassign to abandoned route)
The route section in the realign region is reassigned to a new route on a new line, and any event in the realign region follows the reassign event behavior. Stay Put, Move, and Retire reassign event behavior settings result in the same behavior as the previous diagrams show. If you want your events to transfer to the abandoned route, you should configure the Snap behavior for reassign route.
Примечание:
The reassign event behavior is applied before the realign event behavior, so it is important to verify the event feature class reassign event behavior configuration when using the Reassign to abandoned route functionality.
Stay Put behavior (with reassign set to Snap 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 the event in the realign region are snapped to the reassigned route.
Move behavior (with reassign set to Snap behavior)
The measures of the event are maintained; the geographic location may change. Portions of the event in the realign region are snapped to the reassigned route.
Retire behavior (with reassign set to Snap behavior)
Events intersecting the realignment region are retired. Portions of the event in the realign region are snapped to the reassigned route.
The following table gives more information to understand how events are impacted by a realignment:
| Behavior | Events upstream realignment | Events intersecting realignment | Events downstream realignment |
|---|---|---|---|
Stay Put | Up to closest upstream calibration point; one or more measures adjusted to retain x, y if needed. | Retire event; line events crossing the edit section are split and the original event retired. | If route calibration is changed, the recalibrate event behavior is applied. Otherwise, no action. |
Move | Shape regenerated, if needed, to new location of route measures. | Shape regenerated to new location of route measures. | If route calibration is changed, the recalibrate event behavior is applied. Otherwise, no action. |
Retire | Up to closest upstream calibration point; retire event if needed. | Retire event; line events crossing the edit section are not split. | If route calibration is changed, the recalibrate event behavior is applied. Otherwise, no action. |
Примечание:
- 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.
- The following diagram shows the upstream and downstream section for the edit.
- The network may contain events that span multiple routes in a line network. In that case, the behaviors are still applied in the same manner.
- When the LRS is time aware, edit activities such as realigning a route will time slice routes and events.
Detailed behavior results with realigned abandonment
The following sections detail how event behavior rules are enforced when a route is realigned with abandonment.
Before realignment with abandonment
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 with abandonment are detailed in the following sections.
| 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 |
Stay Put behavior (with reassign set to Snap behavior)
If the realignment is set to occur on 1/1/2005 with realigned route values of 6 to 18, and both Recalibrate route downstream and Reassign to abandoned route(s) are chosen, it has the following effects:
- Event1 is represented by three time slices. There is a time slice from 1/1/2000 to 1/1/2005, with the original measures of 0 to 8, and a time slice from 1/1/2005 to <null> with measures of 0 to 6 that stay in the same location geographically but have the new measures of Route1. There is also a time slice from 1/1/2005 to <null> located on Route1_Ab, which is on a new line, Line1_Ab, with measures of 6 to 8 that has snapped to the abandoned route.
- 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, and a time slice from 1/1/2005 to <null> located on Route1_Ab, which is on a new line, Line1_Ab, with measures of 8 to 12 that has snapped to the abandoned route.
- Event3 is represented by three time slices. There is a time slice from 1/1/2000 to 1/1/2005, with the original measures of 12 to 20, and a time slice from 1/1/2005 to <null>, with measures of 18 to 24 that stay in the same location geographically but have the new measures of Route1. There is also a time slice from 1/1/2005 to <null> located on Route1_Ab, which is on a new line, Line1_Ab, with measures of 12 to 14 that has snapped to the abandoned route.
| 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 |
Event1 | Route1_Ab | 1/1/2005 | <null> | 6 | 8 | No Error |
Event2 | Route1 | 1/1/2000 | 1/1/2005 | 8 | 12 | No Error |
Event2 | Route1_Ab | 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 | Route1_Ab | 1/1/2005 | <null> | 12 | 14 | No Error |
Move behavior (with reassign set to Snap behavior)
If the realignment is set to occur on 1/1/2005 with realigned route values of 6 to 18, and both Recalibrate route downstream and Reassign to abandoned route(s) are selected, it has the following effects:
- Event1 is represented by three time slices. There is a time slice from 1/1/2000 to 1/1/2005, with the original measures of 0 to 8, and a time slice from 1/1/2005 to <null> with measures of 0 to 6 that move geographically to maintain the original event measures. The event has the same measures but different geometry in the new time slice. There is also a time slice from 1/1/2005 to <null> located on Route1_Ab, with measures of 6 to 8 that has snapped to the abandoned route.
- 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, and a time slice from 1/1/2005 to <null> located on Route1_Ab with measures of 8 to 12 that has snapped to the abandoned route.
- Event3 is represented by three time slices. There is a time slice from 1/1/2000 to 1/1/2005, with the original measures of 12 to 20, and a time slice from 1/1/2005 to <null>, with measures of 14 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. There is also a time slice from 1/1/2005 to <null>, located on Route1_Ab, with measures of 12 to 14 that has snapped to the abandoned route.
| 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 | 8 | Partial match for To Measure |
Event1 | Route1_Ab | 1/1/2005 | <null> | 6 | 8 | No Error |
Event2 | Route1 | 1/1/2000 | 1/1/2005 | 8 | 12 | No Error |
Event2 | Route1_Ab | 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> | 14 | 20 | No Error |
Event3 | Route1_Ab | 1/1/2005 | <null> | 12 | 14 | No Error |
Retire behavior (with reassign set to Snap behavior)
If the realignment is set to occur on 1/1/2005 with realigned route values of 6 to 18, and both Recalibrate route downstream and Reassign to abandoned route(s) are selected, it has the following effects:
- Event1 is represented by three time slices. There is a time slice from 1/1/2000 to 1/1/2005, with measures of 0 to 8, and a time slice from 1/1/2005 to <null> with measures of 0 to 6. This time slice is created because the reassign edit behavior is processed prior to the realign edit behavior, causing the upstream linear event that crossed the realign region to split and time slice rather than retire. There is also a time slice from 1/1/2005 to <null>, located on Route1_Ab, with measures of 6 to 8 that has snapped to the abandoned route.
- Event2 is represented by two time slices. There is a time slice from 1/1/2000 to 1/1/2005, with measures of 8 to 12. There is also a time slice from 1/1/2005 to <null>, located on Route1_Ab, with measures of 8 to 12 that has snapped to the abandoned route.
- Event3 is represented by two time slices. There is a time slice from 1/1/2000 to 1/1/2005, with measures of 12 to 20. There is also a time slice from 1/1/2005 to <null>, located on Route1_Ab, with measures of 12 to 14 that has snapped to the abandoned route.
| Event | Route Name | From Date | To Date | From Measure | To Measure | Location Error |
|---|---|---|---|---|---|---|
Event1 | Route1 | 1/1/2000 | <null> | 0 | 8 | No Error |
Event1 | Route1_Ab | 1/1/2005 | <null> | 6 | 8 | No Error |
Event2 | Route1 | 1/1/2000 | 1/1/2005 | 8 | 12 | No Error |
Event2 | Route1_Ab | 1/1/2005 | <null> | 8 | 12 | No Error |
Event3 | Route1 | 1/1/2000 | 1/1/2005 | 12 | 20 | No Error |
Event3 | Route1_Ab | 1/1/2005 | <null> | 12 | 14 | No Error |
Detailed behavior on routes in a line network with events that span routes
The following sections detail how event behavior rules are enforced when a route on a line in a line network is realigned.
Stay Put behavior (with Reassign set to Snap for abandonment)
If the realignment with abandonment is set to occur on 1/1/2005, from measure 17 on Route2 to measure 43 on Route 4 and Recalibrate route downstream is unchecked, this has the following effects:
- For the abandoned portions of Route2, Route3, and Route4, the following routes are created: Route2_Ab, Route3_Ab, Route4_Ab.
- 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 on Route1 to 30 on Route3. The second time slice is from 1/1/2005 to <null> with two different records. Because the realignment with abandonment took place in the middle of the event, it will split with one record having measures of 0 on Route1 to 17 on Route2 and the second record having measures of 17 on Route2_Ab to 30 on Route3_Ab. Both events stay in the same location geographically.
- 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 30 on Route3 to 48 on Route4. The second time slice is from 1/1/2005 to <null> with two different records. Because the realignment with abandonment took place in the middle of the event, it will split, one record having measures 30 on Route3_Ab to measure 43 on Route4_Ab and the second record having measures of 43 on Route4 to 48 on Route 4. Both events stay in the same location geographically.
Before Stay Put behavior
The following diagram and table provide details about the routes, measures, and events before realignment.
| Event ID | From Date | To Date | From RouteID | To Route ID | From Measure | To Measure |
|---|---|---|---|---|---|---|
Event1 | 1/1/2000 | <null> | Route1 | Route3 | 0 | 30 |
Event2 | 1/1/2000 | <null> | Route3 | Route4 | 30 | 48 |
After Stay Put behavior (with Reassign set to Snap for abandonment)
For the abandoned portions of Route2, Route3, and Route4, the following routes are created: Route2_Ab, Route3_Ab, Route4_Ab.
| Event ID | From Date | To Date | From RouteID | To Route ID | 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> | Route2AB | 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 |
Event2 | 1/1/2005 | <null> | Route4 | Route4 | 43 | 48 | No Error |
Move behavior (with Reassign set to Move for abandonment)
- If the realignment with abandonment is set to occur on 1/1/2005, from measure 17 on Route2 to measure 43 on Route 4 and Recalibrate route downstream is unchecked, 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 on Route1 to 30 on Route3. The second time slice is from 1/1/2005 to <null> with measures of 0 on Route1 to 30 on Route3, but it will only partially locate because part of Route2 and all of Route3 have been retired. 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 30 on Route3 to 48 on Route4. The second time slice from 1/1/2005 to <null>, has measures of 30 on Route3 to 48 on Route4, but it will only partially locate because all of Route3 and part of Route4 have retired. The event has the same measures but different geometry in the new time slice.
Before Move behavior
The following diagram and table provide details about the routes, measures, and events before realignment.
| Event ID | From Date | To Date | From RouteID | To Route ID | From Measure | To Measure |
|---|---|---|---|---|---|---|
Event1 | 1/1/2000 | <null> | Route1 | Route3 | 0 | 30 |
Event2 | 1/1/2000 | <null> | Route3 | Route4 | 30 | 48 |
After Move behavior (with Reassign set to Move for abandonment)
For the abandoned portions of Route2, Route3, and Route4, the following routes are created: Route2_Ab, Route3_Ab, Route4_Ab.
| Event ID | From Date | To Date | From RouteID | To Route ID | 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 | Route3 | 0 | 30 | Partial Match for the To Measure |
Event2 | 1/1/2000 | /1/2005 | Route3 | Route4 | 30 | 48 | No Error |
Event2 | /1/2005 | <null> | Route3 | Route4 | 30 | 48 | Partial Match for the From Measure |
Retire behavior (with Reassign set to Retire for abandonment)
- If the realignment with abandonment is set to occur on 1/1/2005, from measure 17 on Route2 to measure 43 on Route 4 and Recalibrate route downstream is unchecked, this has the following effects:
- Event1 will retire since it is located within the realigned or abandoned region.
- Event2 will retire since it is located within the realigned or abandoned region.
Before retire behavior
The following diagram and table provide details about the routes, measures, and events before realignment.
| Event ID | From Date | To Date | From RouteID | To Route ID | From Measure | To Measure |
|---|---|---|---|---|---|---|
Event1 | 1/1/2000 | <null> | Route1 | Route3 | 0 | 30 |
Event2 | 1/1/2000 | <null> | Route3 | Route4 | 30 | 48 |
After retire behavior (with Reassign set to Retire)
For the abandoned portions of Route2, Route3, and Route4, the following routes are created: Route2_Ab, Route3_Ab, Route4_Ab.
The events on LineA are retired.
| Event ID | From Date | To Date | From RouteID | To Route ID | From Measure | To Measure |
|---|---|---|---|---|---|---|
Event1 | 1/1/2000 | 1/1/2005 | Route1 | Route3 | 0 | 30 |
Event2 | 1/1/2000 | 1/1/2005 | Route3 | Route4 | 30 | 48 |