Event behavior for route calibration—ArcGIS Pro

Available with Location Referencing license.

When route calibration occurs, events are impacted, depending on the configured event behavior for each event layer.

Note:

Events are not updated until the Apply Event Behaviors tool is run after route edits. If you are using conflict prevention on branch versioned data, you are prompted to run Apply Event Behaviors before posting to the default version.

Calibration can occur on a route when one or more calibration points are added, edited, deleted, or when recalibration downstream is selected for LRS route editing tools.

Calibration point changes can be made using Location Referencing tab calibration tools, by creating or editing calibration points using create features in ArcGIS Pro, by using Apply downstream recalibration in Location Referencing route editing tools, or by checking the Record calibration changes for event location updates option when running the Generate Routes tool.

Route calibration scenario

This route calibration scenario involves one route with two existing calibration points. A calibration point at existing measure 10 is changed to 15, resulting in recalibrated measures downstream.

Stay Put behavior

The geographic location of the event is maintained; the measures can change.

Move behavior

The measures from the event are maintained; the geographic location can 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 line events but don't need to be split.
If the option to recalibrate route downstream is selected, calibrate route event behaviors are applied to the events downstream of the edited portion of the route.
Since the LRS is time aware, edit activities such as calibrating or retiring a route result in time-sliced 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 are deleted and not retired.

Detailed behavior results

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

Stay Put event 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 has the following effects:

Event1 is represented by two time slices because the route recalibrated to the nearest upstream calibration point with measure 5. 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> that stays in the same location geographically but has the new measures 0 to 9 of Route1.
Event2 is represented by two time slices because it crosses the location where the recalibration took place on the route. There is a time slice from 1/1/2000 to 1/1/2005 with the original measures from 7 to 15, and a time slice from 1/1/2005 to <Null> that stays in the same location geographically but has the new measures 9 to 20 of Route1.
Event3 is represented by two time slices because it crosses the location on the route where it was recalibrated downstream. There is a time slice from 1/1/2000 to 1/1/2005 with the original measures from 15 to 20, and a time slice from 1/1/2005 to <Null> that stays in the same location geographically but has the new measures 20 to 25 of Route1.

Before Stay Put event behavior

The following image shows the route before calibration:

The following table provides details about the events 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 image shows the route after calibration:

The following table provides details about the events after calibration 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 event behavior

Event1 is represented by two time slices because the route recalibrated to the nearest upstream calibration point with measure 5. 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> that retains the original event measures from 0 to 7, but for which the geographic x,y location moves to the new location of those measures on the route because the route recalibrated to the nearest upstream calibration point with measure 5.
Event2 is represented by two time slices because it crosses the location where the recalibration took place on the route. There is a time slice from 1/1/2000 to 1/1/2005 with the original measures from 7 to 15, and a time slice from 1/1/2005 to <Null> with the same measures from 7 to 15 that move to their new location on the route.
Event3 is represented by two time slices because it crosses the location on the route where it was recalibrated downstream. There is a time slice from 1/1/2000 to 1/1/2005 with the original measures from 15 to 20, and a time slice from 1/1/2005 to <Null> with measures from 15 to 20 that move to their new location on the route.

Before Move event behavior

The following image shows the route before calibration:

The following table provides details about the events 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 image shows the route after calibration:

The following table provides details about the events after calibration 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 event behavior

Event1 retires because the route recalibrated to the nearest upstream calibration point with measure 5.
Event2 retires because it crosses the location where the recalibration took place on the route.
Event3 retires because it crosses the location on the route where it was recalibrated downstream.

Before Retire event behavior

The following image shows the route before calibration:

The following table provides details about the events 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 image shows the route after calibration:

The following table provides details about the events after calibration 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

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

The following sections describe how event behavior rules are enforced when a route on a line in a line network is calibrated.

Note:

Stay Put event behavior

A calibration point is added to the route at existing measure 28 with a new measure value of 31 and an effective date of 1/1/2005. Recalibrate downstream is not applied. This calibration 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, and a time slice from 1/1/2005 to <Null> that stays in the same location geographically but has the new measures 0 on Route1 to 33 on Route3.
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, and a time slice from 1/1/2005 to <Null> that stays in the same location geographically but has the new measures 33 on Route3 to 48 on Route4.

Before Stay Put event behavior

The following image shows the routes before calibration:

Note:

Calibration points affect only the route on which they are added or updated.

The following table provides details about the events before calibration:


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 event behavior

The following image shows the routes after calibration:

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


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
Event1	1/1/2005	<Null>	Route1	Route3	0	33
Event2	1/1/2000	1/1/2005	Route3	Route4	30	48
Event2	1/1/2005	<Null>	Route3	Route4	33	48

Move event behavior

A calibration point is added to the route at existing measure 28 with an effective date of 1/1/2005. The added calibration point has a new measure of 31 without recalibration downstream applied.

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, and a time slice from 1/1/2005 to <Null>, also with measures 0 on Route1 to 30 on Route3. The measure 30 moves to the new geographic location of the measure on Route3.
Event2 is also 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, and a time slice from 1/1/2005 to <Null>, also with measures of 30 on Route3 to 48 on Route4. The measure 30 moves to the new geographic location of the measure on Route3.

Before Move event behavior

The following image shows the routes before calibration:

The following table provides details about the events before calibration:


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 event behavior

The following image shows the routes after calibration:

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


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
Event1	1/1/2005	<Null>	Route1	Route3	0	30
Event2	1/1/2000	1/1/2005	Route3	Route4	30	48
Event2	1/1/2005	<Null>	Route3	Route4	30	48

Retire event behavior

Event1 retires because it intersects the route that is recalibrated.
Event2 retires because it intersects the route that is recalibrated.

Before Retire event behavior

The following image shows the routes before calibration:

The following table provides details about the events before calibration:


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 event behavior

Both events are impacted so both events are retired.

The following image shows the routes after calibration:

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


Event	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

Feedback on this topic?