Mit der Location Referencing-Lizenz verfügbar.
When route calibration occurs, events are impacted, depending on the configured event behavior for each event layer. The following are the results of executing the Apply Event Behaviors geoprocessing tool on event features in the edit activity area on a route with a calibration change.
Hinweis:
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.
Calibration can occur on a route when a calibration point is added, edited, or deleted. These calibration point changes can be made using the calibration tools on the Location Referencing tab in ArcGIS Pro or by checking the Record calibration changes for event location updates option when running the Generate Routes geoprocessing tool.
Route calibration scenario
This route calibration scenario involves one route with two existing calibration points. A calibration point at existing measure 10 will be changed to 15, resulting in recalibrated measures downstream.
Stay Put behavior
The geographic location of the event is maintained; the measures may change.
Move behavior
The measures of the event are maintained; the geographic location may change.
Retire behavior
The geographic location and measures are maintained; the event retires.
Upstream and downstream sections
The following table details how the calibration editing activity impacts upstream and downstream events according to the configured event behavior.
| Behavior | Events upstream of calibration point edit | Events crossing calibration point edit | Events downstream of calibration point edit |
|---|---|---|---|
Stay Put | Measures on an event update to maintain the geographic location, if the event crosses the section between the edited calibration point and the nearest upstream calibration point. | Measures on an event update to maintain the geographic location of the event. | Measures on an event update to maintain the geographic location of the event. If the event crosses the section between the edited calibration point and the nearest upstream calibration point, measures update due to calibration point values changing. |
Move | The event polyline shape updates to the new location of measures on the route if the event crosses the section between the edited calibration point and the nearest upstream calibration point. | The event polyline shape is updated to the new location of measures on the route. | The event polyline shape is updated to the new location of measures on the route if crossing a section of the route with a calibration point with measures is updated. |
Retire | The event retires if the event crosses the section between the edited calibration point and the nearest upstream calibration point. | The event retires; line events crossing the edited calibration point are not split. | The event retires if the event crosses a section of the route with a calibration point with measures updated. |
- Point events follow the same behavior as linear events but don't need to be split.
- Point events follow the same behavior as linear events, but don't need to be split.
- If the option to recalibrate route downstream is selected, 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 calibrating or retiring a route will time slice routes and events.
- If the route is calibrated the same day that it's created, and the event behavior for calibrate is set to retire, the events will be deleted not retired.
Detailed behavior results
The following sections detail how event behavior rules are enforced when a route is calibrated.
Stay Put behavior
A calibration point is added to the route at existing measure 10 with an effective date of 1/1/2000. The added calibration point has a new measure of 15 with recalibrate downstream applied and an effective date of 1/1/2005. This calibration will have the following effects:
- Event1 will be represented by two time slices because the route recalibrated to the nearest upstream calibration point with measure 5. There will be a time slice as of 1/1/2000 to 1/1/2005, with the original measures of 0 to 7, and a time slice as of 1/1/2005 to <null> that will stay in the same location geographically but have the new measures 0 to 9 of Route1.
- Event2 will also be represented by two time slices because it crosses the location where the recalibration took place on the route. There will be a time slice as of 1/1/2000 to 1/1/2005, with the original measures of 7 to 15, and a time slice as of 1/1/2005 to <null> that will stay in the same location geographically but have the new measures 9 to 20 of Route1.
- Event3 will be represented by two time slices because it crosses the location on the route where it was recalibrated downstream. There will be a time slice as of 1/1/2000 to 1/1/2005, with the original measures of 15 to 20, and a time slice as of 1/1/2005 to <null> that will stay in the same location geographically but have the new measures 20 to 25 of Route1.
Before Stay Put event behavior
The following diagram and table provide details about the route and its measures before calibration.
| Event | Route name | From date | To date | From measure | To measure |
|---|---|---|---|---|---|
Event1 | Route1 | 1/1/2000 | <null> | 0 | 7 |
Event2 | Route1 | 1/1/2000 | <null> | 7 | 15 |
Event3 | Route1 | 1/1/2000 | <null> | 15 | 20 |
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 |
|---|---|---|---|---|---|
Event1 | Route1 | 1/1/2000 | 1/1/2005 | 0 | 7 |
Event1 | Route1 | 1/1/2005 | <null> | 0 | 9 |
Event2 | Route1 | 1/1/2000 | 1/1/2005 | 7 | 15 |
Event2 | Route1 | 1/1/2005 | <null> | 9 | 20 |
Event3 | Route1 | 1/1/2000 | 1/1/2005 | 15 | 20 |
Event3 | Route1 | 1/1/2005 | <null> | 20 | 25 |
Move behavior
A calibration point is added to the route at existing measure 10, with an effective date of 1/1/2000. The added calibration point has a new measure of 15 with recalibrate downstream applied and an effective date of 1/1/2005. This calibration will have the following effects:
- Event1 will be represented by two time slices because the route recalibrated to the nearest upstream calibration point with measure 5. There will be a time slice as of 1/1/2000 to 1/1/2005 with the original measures of 0 to 7. The second time slice will be as of 1/1/2005 to <null> with measures of 0 to 7 that will maintain the original event measures but have the geographic x,y location move to the new location of those measures on the route because the route recalibrated to the nearest upstream calibration point with measure 5.
- Event2 will also be represented by two time slices because it crosses the location where the recalibration took place on the route. There will be a time slice as of 1/1/2000 to 1/1/2005 with the original measures of 7 to 15. The second time slice will be as of 1/1/2005 to <null> with measures of 7 to 15 that will maintain the original event measures but have their geographic x,y location move to the new location of those measures on the route.
- Event3 will be represented by two time slices because it crosses the location on the route where it was recalibrated downstream. There will be a time slice as of 1/1/2000 to 1/1/2005 with the original measures of 15 to 20. The second time slice will be as of 1/1/2005 to <null> with measures of 15 to 20 that will maintain the original event measures but have their geographic x,y location move to the new location of those measures on the route.
Before Move event behavior
The following diagram and table provide details about the route and its measures before calibration.
| Event | Route name | From date | To date | From measure | To measure |
|---|---|---|---|---|---|
Event1 | Route1 | 1/1/2000 | <null> | 0 | 7 |
Event2 | Route1 | 1/1/2000 | <null> | 7 | 15 |
Event3 | Route1 | 1/1/2000 | <null> | 15 | 20 |
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 |
|---|---|---|---|---|---|
Event1 | Route1 | 1/1/2000 | 1/1/2005 | 0 | 7 |
Event1 | Route1 | 1/1/2005 | <null> | 0 | 7 |
Event2 | Route1 | 1/1/2000 | 1/1/2005 | 7 | 15 |
Event2 | Route1 | 1/1/2005 | <null> | 7 | 15 |
Event3 | Route1 | 1/1/2000 | 1/1/2005 | 15 | 20 |
Event3 | Route1 | 1/1/2005 | <null> | 15 | 20 |
Retire behavior
A calibration point is added to the route at existing measure 10 with an effective date of 1/1/2000. The added calibration point has a new measure of 15 with recalibrate downstream applied and an effective date of 1/1/2005. This calibration will have the following effects:
- Event1 will retire because the route recalibrated to the nearest upstream calibration point with measure 5.
- Event2 will retire because it crosses the location where the recalibration took place on the route.
- Event3 will retire because it crosses the location on the route where it was recalibrated downstream.
Before Retire event behavior
The following diagram and table provide details about the route and its measures before calibration.
| Event | Route name | From date | To date | From measure | To measure |
|---|---|---|---|---|---|
Event1 | Route1 | 1/1/2000 | <null> | 0 | 7 |
Event2 | Route1 | 1/1/2000 | <null> | 7 | 15 |
Event3 | Route1 | 1/1/2000 | <null> | 15 | 20 |
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 |
|---|---|---|---|---|---|
Event1 | Route1 | 1/1/2000 | 1/1/2005 | 0 | 7 |
Event2 | Route1 | 1/1/2000 | 1/1/2005 | 7 | 15 |
Event3 | Route1 | 1/1/2000 | 1/1/2005 | 15 | 20 |