Location Referencing ライセンスで利用可能です。
1 つ以上のルートが反転されると、イベントが、各イベント レイヤーに対して構成されたイベントの振舞いに応じて影響を受けます。
注意:
Events are not updated until the Apply Event Behaviors tool is applied after route edits. If you are using conflict prevention, you are prompted to run Apply Event Behaviors before posting can be completed.
注意:
下流部分の再キャリブレーションが選択されている LRS ルートの編集では、構成されたキャリブレーション イベントの振舞いが下流セクションに適用されます。 構成されたイベントの振舞いは、LRS イベント プロパティを表示することで確認できます。
Route reversal scenario
The following route reversal scenario involves one route and two events:
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.
Detailed behavior results
The following sections detail how event behavior rules are enforced when a route is reversed.
Stay Put behavior
If the route is active from 1/1/2000 and the reversal is set to occur on 1/1/2005, 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 from 5 to 12, and a time slice of 1/1/2005 to <Null>, with the measures 8 to 15 in the reverse direction.
- Event2 is represented by two time slices. There is a time slice from 1/1/2000 to 1/1/2005, with the original measures from 12 to 20, and a time slice of 1/1/2005 to <Null> with the measures 0 to 8 in the reverse direction.
Before Stay Put event behavior
The following diagram provides details about the route before reversal:
The following table provides details about the events before reversal:
| Event | Route Name | From Date | To Date | From Measure | To Measure |
|---|---|---|---|---|---|
Event1 | Route1 | 1/1/2000 | <Null> | 5 | 12 |
Event2 | Route1 | 1/1/2000 | <Null> | 12 | 20 |
After Stay Put event behavior
The following diagram provides details about the route after reversal:
The following table provides details about the events after reversal 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 | 5 | 12 | No Error |
Event1 | Route1 | 1/1/2005 | <Null> | 8 | 15 | No Error |
Event2 | Route1 | 1/1/2000 | 1/1/2005 | 12 | 20 | No Error |
Event2 | Route1 | 1/1/2005 | <Null> | 0 | 8 | No Error |
Move behavior
If the route is active from 1/1/2000 and the reversal is set to occur on 1/1/2005, 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 from 5 to 12, and a time slice of 1/1/2005 to <Null>, with the same measures but in the reverse direction.
- Event2 is represented by two time slices. There is a time slice from 1/1/2000 to 1/1/2005, with the original measures from 12 to 20, and a time slice of 1/1/2005 to <Null> with the same measures but in the reverse direction.
Before Move event behavior
The following diagram provides details about the route before reversal:
The following table provides details about the events before reversal:
| Event | Route Name | From Date | To Date | From Measure | To Measure |
|---|---|---|---|---|---|
Event1 | Route1 | 1/1/2000 | <Null> | 5 | 12 |
Event2 | Route1 | 1/1/2000 | <Null> | 12 | 20 |
After Move event behavior
The following diagram provides details about the route after reversal:
The following table provides details about the events after reversal 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 | 5 | 12 | No Error |
Event1 | Route1 | 1/1/2005 | <Null> | 5 | 12 | No Error |
Event2 | Route1 | 1/1/2000 | 1/1/2005 | 12 | 20 | No Error |
Event2 | Route1 | 1/1/2005 | <Null> | 12 | 20 | No Error |
Retire behavior
If the realignment is set to occur on 1/1/2005 and the route reversal is set to occur on 1/1/2005, this has the following effects:
- Event1 retires.
- Event2 retires.
Before Retire event behavior
The following diagram provides details about the routes before reversal:
The following table provides details about the events before reversal:
| Event | Route Name | From Date | To Date | From Measure | To Measure |
|---|---|---|---|---|---|
Event1 | Route1 | 1/1/2000 | <Null> | 5 | 12 |
Event2 | Route1 | 1/1/2000 | <Null> | 12 | 20 |
After Retire event behavior
The following diagram provides details about the route after reversal:
The following table provides details about the events after reversal 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 | 5 | 12 |
Event2 | Route1 | 1/1/2000 | 1/1/2005 | 12 | 20 |
Detailed route reversal 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 in a line network is reversed. In this example, the routes are reversed, including the intermediate route (Route2) between the from route (Route1) and to route (Route3). There are two events (Event1 and Event2) that are impacted by route reversal.
Stay Put behavior
The routes are active from 1/1/2000, and if the reversal is set to occur on 1/1/2005, 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 measures from 7 on Route1 to 18 on Route2, and a time slice from 1/1/2005 to <Null>, with measures from 22 on Route2 to 3 on Route1.
- Event2 is represented by two time slices. There is a time slice from 1/1/2000 to 1/1/2005, with measures from 18 on Route 2 to 35 on Route3, and a time slice from 1/1/2005 to <Null>, with measures from 35 on Route 3 to 20 on Route2.
Before Stay Put event behavior
The following diagram provides details about the routes before reversal:
The following table provides details about the events before reversal:
| Event ID | From Date | To Date | From RouteID | From Measure | To RouteID | To Measure |
|---|---|---|---|---|---|---|
Event1 | 1/1/2000 | <Null> | Route1 | 7 | Route2 | 18 |
Event2 | 1/1/2000 | <Null> | Route2 | 18 | Route3 | 35 |
After Stay Put event behavior
The following diagram provides details about the routes after reversal:
The following table provides details about the events after reversal when Stay Put is the configured event behavior:
| Event ID | From Date | To Date | From RouteID | From Measure | To RouteID | To Measure | Location Error |
|---|---|---|---|---|---|---|---|
Event1 | 1/1/2000 | 1/1/2005 | Route1 | 7 | Route2 | 18 | No Error |
Event1 | 1/1/2005 | <Null> | Route2 | 22 | Route1 | 3 | No Error |
Event2 | 1/1/2000 | 1/1/2005 | Route2 | 18 | Route3 | 35 | No Error |
Event2 | 1/1/2005 | <Null> | Route3 | 35 | Route2 | 22 | No Error |
Move behavior
The route is active from 1/1/2000, and if the reversal is set to occur on 1/1/2005, 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 measures from 7 on Route1 to 18 on Route2, and a time slice from 1/1/2005 to <Null>, with measures from 18 on Route2 to 7 on Route1.
- Event2 is represented by two time slices. There is a time slice from 1/1/2000 to 1/1/2005, with measures from 18 on Route 2 to 35 on Route3, and a time slice from 1/1/2005 to <Null>, with measures from 35 on Route 3 to 18 on Route2.
Before Move event behavior
The following diagram provides details about the routes before reversal:
The following table provides details about the events before reversal:
| Event ID | From Date | To Date | From RouteID | From Measure | To RouteID | To Measure |
|---|---|---|---|---|---|---|
Event1 | 1/1/2000 | <Null> | Route1 | 7 | Route2 | 18 |
Event2 | 1/1/2000 | <Null> | Route2 | 18 | Route3 | 35 |
After Move event behavior
The following diagram provides details about the routes after reversal:
The following table provides details about the events after reversal when Move is the configured event behavior:
| Event ID | From Date | To Date | From RouteID | From Measure | To RouteID | To Measure | Location Error |
|---|---|---|---|---|---|---|---|
Event1 | 1/1/2000 | 1/1/2005 | Route1 | 7 | Route2 | 18 | No Error |
Event1 | 1/1/2005 | <Null> | Route2 | 18 | Route1 | 7 | No Error |
Event2 | 1/1/2000 | 1/1/2005 | Route2 | 18 | Route3 | 35 | No Error |
Event2 | 1/1/2005 | <Null> | Route3 | 35 | Route2 | 18 | No Error |
Retire behavior
The routes are active from 1/1/2000, and if the reversal is set to occur on 1/1/2005, this has the following effects:
- Event1 retires.
- Event2 retires.
Before Retire event behavior
The following diagram provides details about the routes before reversal:
The following table provides details about the events before reversal:
| Event ID | From Date | To Date | From RouteID | From Measure | To RouteID | To Measure |
|---|---|---|---|---|---|---|
Event1 | 1/1/2000 | <Null> | Route1 | 5 | Route2 | 20 |
Event2 | 1/1/2000 | <Null> | Route2 | 20 | Route3 | 35 |
After Retire event behavior
The following diagram provides details about the routes after reversal:
The following table provides details about the events after reversal when Retire is the configured event behavior:
| Event ID | From Date | To Date | From RouteID | From Measure | To RouteID | To Measure |
|---|---|---|---|---|---|---|
Event1 | 1/1/2000 | 1/1/2005 | Route1 | 5 | Route2 | 20 |
Event2 | 1/1/2000 | 1/1/2005 | Route2 | 20 | Route3 | 35 |