Event behavior for route reassignment—ArcGIS Pro

Доступно с лицензией Location Referencing.

During route reassignment, events are impacted in the edit activity areas, and upstream and downstream of the reassignment, depending on the configured event behavior for the event layer.

Примечание:

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.

Примечание:

When recalibrate downstream is chosen for an LRS route edit, the configured calibrate event behavior is applied to downstream sections.

The following sections detail the results of executing the Apply Event Behaviors tool on event features after a corresponding route edit.

Route reassignment scenario

This route reassignment scenario involves two routes. A portion of Route1 is reassigned to Route2.

Stay Put behavior

Although the geographic location of the event outside the reassign region is maintained, the measures can change. The event can also split if it crosses the reassign region. Portions in the reassign region are removed.

Move behavior

Although the measures of the event are maintained, the geographic location can change.

Retire behavior

Events intersecting the reassignment region are retired.

Snap behavior

Although the geographic location of the event is maintained by snapping to the route that it was reassigned to, the measures can change. The event can also split if it crosses the reassign region.

Cover behavior

Although the measures of the event are maintained, the geographic location can change.

Upstream and downstream sections

Route editing impacts upstream and downstream sections differently.

The following diagram shows the upstream and downstream section for the route reassignment scenario:

The following table details how the reassignment editing activity impacts upstream and downstream events according to the configured event behavior:


Behavior	Events upstream reassignment	Events intersecting reassignment	Events downstream reassignment
Stay Put	No action	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 the new location of route measures.	If route calibration is changed, the recalibrate event behavior is applied; otherwise, no action.
Retire	No action	Retire event. Line events crossing the reassignment region do not split.	If route calibration is changed, the recalibrate event behavior is applied; otherwise, no action.
Snap	No action	Geographic location (x,y) is maintained. The event is migrated to the reassigned route. Line events crossing the edit section are split.	If route calibration is changed, the recalibrate event behavior is applied; otherwise, no action.

Примечание:

Point events follow the same behavior as line events but don't need to be split.
If the Recalibrate route downstream option is chosen, calibrate route event behaviors are applied to the events downstream of the edited portion of the route.
The network can contain events that span multiple routes in a line network; the behaviors are still applied in the same manner.
Since the LRS is time aware, edit activities—such as reassigning a route—time slice routes and events.

Detailed behavior results

The following sections detail how event behavior rules are enforced when a route is reassigned.

Stay Put behavior

If the reassignment is set to occur on 1/1/2005 with target values of 0 to 5 and Recalibrate route downstream is 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 from 0 to 7, and a time slice from 1/1/2005 to <Null>, with measures from 0 to 5 that stay in the same location geographically but have the new measures from Route1.
Event2 retires to maintain geographic location.

Before Stay Put event behavior

The following diagram provides details about the routes before reassignment:

The following table provides details about the events before reassignment:


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	10

After Stay Put event behavior

The following diagram provides details about the routes after reassignment:

The following table provides details about the events after reassignment 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	7	No Error
Event1	Route1	1/1/2005	<Null>	0	5	No Error
Event2	Route1	1/1/2000	1/1/2005	7	10	No Error

Move behavior

If the reassignment is set to occur on 1/1/2005 with target values of 0 to 5 and Recalibrate route downstream is 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 from 0 to 7, and a time slice from 1/1/2005 to <Null> with measures from 0 to 7 that move geographically to maintain the original event measures. This new time slice only partially locates since the event time slice has measures from 0 to 7, but the underlying route only has measures from 0 to 5. 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 from 7 to 10, and a time slice from 1/1/2005 to <Null> with measures from 7 to 10 that move geographically to maintain the original event measures. This new time slice does not locate since the event time slice has measures from 7 to 10, but the underlying route only has measures from 0 to 5. The event has the same measures but different geometry in the new time slice.

Before Move event behavior

The following diagram provides details about the routes before reassignment:

The following table provides details about the events before reassignment:


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	10

After Move event behavior

The following diagram provides details about the routes after reassignment:

The following table provides details about the events after reassignment 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	7	No Error
Event1	Route1	1/1/2005	<Null>	0	7	Partial match for the To Measure
Event2	Route1	1/1/2000	1/1/2005	7	10	No Error

Retire behavior

If the reassignment is set to occur on 1/1/2005 with target values of 0 to 5 and Recalibrate route downstream is chosen, this has the following effects:

Event1 retires.
Event2 retires.

Before Retire event behavior

The following diagram provides details about the routes before reassignment:

The following table provides details about the events before reassignment:


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	10

After Retire event behavior

The following diagram provides details about the routes after reassignment:

The following table provides details about the events after reassignment 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	7	No Error
Event2	Route1	1/1/2000	1/1/2005	7	10	No Error

Snap behavior

If the reassignment is set to occur on 1/1/2005 with target values of 0 to 5 and Recalibrate route downstream is 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 from 0 to 7, and a time slice from 1/1/2005 to <Null> with two event records. The first Event1 event record after reassignment has measures from 0 to 5 that snap to the new measures from Route1; and the second event record has measures from 0 to 2 that snap to the new measures of Route2.
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 7 to 10, and a time slice from 1/1/2005 to <Null> with measures from 2 to 5 that snap to the new measures of Route2.

Before Snap event behavior

The following diagram provides details about the routes before reassignment:

The following table provides details about the events before reassignment:


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	10

After Snap event behavior

The following diagram provides details about the routes after reassignment:

The following table provides details about the events after reassignment when Snap 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	7	No Error
Event1	Route1	1/1/2005	<Null>	0	5	No Error
Event1	Route2	1/1/2005	<Null>	0	2	No Error
Event2	Route1	1/1/2000	1/1/2005	7	10	No Error
Event2	Route2	1/1/2005	<Null>	2	5	No Error

Detailed behavior results on routes in a line network with events that span routes

The following sections detail how event behavior rules are enforced when routes on a line in a line network are reassigned.

Stay Put behavior

The routes are active from 1/1/2000, and if the reassignment is set to occur on 1/1/2005 from measure 25 on Route3 to 48 on Route4 and Recalibrate route downstream is not chosen, this has the following effects:

Reassignment is used for merging Route3 and Route4 to create a new route, Route3A.
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 0 on Route1 to 30 on Route3, and a time slice from 1/1/2005 to <Null> with measures from 0 on Route1 to 22 on Route2, as it stays the same geographically. The portion of the event on Route3 is retired since there is no Route3 to build the event shape on any longer.
Event2 retires. as the event is completely within the reassigned portion. There is no longer a Route3 or Route4 on which to build the event shape.

Before Stay Put behavior

The following diagram provides details about the routes before reassignment:

The following table provides details about the events before reassignment:


Event ID	From Date	To Date	From Route ID	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

The following diagram provides details about the routes after reassignment:

The following table provides details about the events after reassignment when Stay Put is the configured event behavior:


Event ID	From Date	To Date	From Route ID	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	22	No Error
Event2	1/1/2000	1/1/2005	Route3	Route4	30	48	Route Not Found

Move behavior

The routes are active from 1/1/2000, and if the reassignment is set to occur on 1/1/2005 from measure 25 on Route3 to 48 on Route4 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 from 0 on Route1 to 30 on Route3, and a time slice from 1/1/2005 to <Null> with measures from 0 on Route1 to 30 on Route3, but since Route3 has been reassigned, the shape can’t be built in that location. In the new time slice, the event has the same measures but different geometry.
Event2 is represented by two time slices. There is a time slice from 1/1/2000 to 1/1/2005with the original measures from 30 on Route3 to 48 on Route4. The second time slice, from 1/1/2005 to <Null>, has measures from 30 on Route3 to 48 on Route4, but Route3 and Route4 have been reassigned, so there is no shape for this event.

Before Move behavior

The following diagram provides details about the routes before reassignment:

The following table provides details about the events before reassignment:


Event ID	From Date	To Date	From Route ID	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

The following diagram provides details about the routes after reassignment:

The following table provides details about the events after reassignment when Move is the configured event behavior:


Event ID	From Date	To Date	From Route ID	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/1/2005	Route3	Route4	30	48	No Error
Event2	1/1/2005	<Null>	Route3	Route4	30	48	Route Not Found

Примечание:

Event2 exists after the Apply Event Behavior tool is run but has no shape.

Retire behavior

Event1 retires since it is located in the reassigned region.
Event2 retires since it is located in the reassigned region.

Before Retire behavior

The following diagram provides details about the routes before reassignment:

The following table provides details about the event before reassignment:


Event ID	From Date	To Date	From Route ID	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

The following diagram provides details about the routes after reassignment:

The following table provides details about the events after reassignment when Retire is the configured event behavior:


Event ID	From Date	To Date	From Route ID	To Route ID	From Measure	To Measure	Location Error
Event1	1/1/2000	1/1/2005	Route1	Route3	0	30	No Error
Event2	1/1/2000	1/1/2005	Route3	Route4	30	48	No Error

Snap behavior

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 0 on Route1 to 30 on Route3, and a second time slice from 1/1/2005 to <Null> with two event records. Because the reassignment took place in the middle of the event, it splits. The first Event1 record after reassignment has measures from 0 on Route1 to 22 on Route2, while the second Event1 record has measures from 25 on Route3A to 30 on Route3A. Both events stay in the same location geographically, but the second event snaps to the new route at the location, Route3A.
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 30 on Route3 to 48 on Route4, and a time slice from 1/1/2005 to <Null> with measures from 30 on Route3A to 48 on Route3A. The event stays in the same location geographically, but snaps to the new route at the location, Route3A.

Before Snap event behavior

The following diagram provides details about the routes before reassignment:

The following table provides details about the events before reassignment:


Event ID	From Date	To Date	From Route ID	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 Snap event behavior

The following diagram provides details about the routes after reassignment:

The following table provides details about the events after reassignment when Snap is the configured event behavior:


Event	From Date	To Date	From Route ID	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	22	No Error
Event1	1/1/2005	<Null>	Route3A	Route3A	25	30	No Error
Event2	1/1/2000	1/1/2005	Route3	Route4	30	48	No Error
Event2	1/1/2005	<Null>	Route3A	Route3A	30	48	No Error

Отзыв по этому разделу?