Merge events

Available with Location Referencing license.

ArcGIS Pipeline Referencing supports merging two or more adjoining linear events that are part of the same LRS event feature class to reduce fragmentation in the LRS.

You can use the Merge Events tool to combine multiple adjoining events into a target event. All the input events retire on the from date of the merged event.

By default, the merged event acquires its from measure value from the first input event in the direction of digitization and its to measure value from the last input event in the direction of digitization. You can edit the attributes of the merged layer before committing the merge.

Event merging scenarios

The following examples demonstrate merging events into a single output event.

Before merge

The diagram below shows three line events on a route before merge is applied.

The following table details the events before the edit.

Event ID	From Date	To Date	Route ID	From Measure	To Measure
Event1	1/1/2000	<Null>	Route1	0	6
Event2	1/1/2000	<Null>	Route1	6	13
Event3	1/1/2000	<Null>	Route1	13	20

After merge

After merging, only the preserved Event ID (Event1) remains. In this example, the measures of the merged event match the from measure value of Event1 and the to measure value of Event3. Different from and to measures can be specified for the merged event using the Merged Event Attributes table in the Merge Events pane.

The following table details the merged event after the edit.

Event ID	From Date	To Date	Route ID	From Measure	To Measure
Event1	1/1/2000	<Null>	Route1	0	20

Before merging with referent offset values

If the selected events have referent offset values configured, those values are honored if the measure values are unchanged in the Merge Events pane. If the measure values are changed using the Merge Events pane, the referent offset values are disregarded and the specified measures are used.

The following diagram shows the routes before the edit.

The following table details the events before the edit. In this case, the events have referent offset values configured using the Intersection offset method as the FromRefMethod and ToRefMethod values with IntersectionX set as the FromRefLocation and ToRefLocation values.

Event ID	From Date	To Date	Route ID	From Measure	FromRefOffset	To Measure	To Ref Offset
EventA	1/1/2000	<Null>	Route1	0	10	10	0
EventB	1/1/2000	<Null>	Route1	10	0	20	10

After merging with referent offset values

After the merge of EventA and EventB, there are two possible outcomes that depend on whether the measures are changed in the Merge Events pane.

If the two events are merged using the existing measures, the resulting merged event (EventA) honors the referent offset values.

Event ID	From Date	To Date	Route ID	From Measure	FromRefOffset	To Measure	ToRefOffset
EventA	1/1/2000	<Null>	Route1	0	10	20	10

If the from measure is changed to 5 and the to measure is changed to 15 using the Merge Events pane, the specified measures are used to update the from measure and to measure of the output event.

Since IntersectionX is no longer used as the referent location, the FromRefMethod and ToRefMethod values become <Null>. The EventA measures are now based on the route measures, so the FromRefLocation and ToRefLocation values change to the LRS Network name, and the FromRefOffset and ToRefOffset values are replaced by the specified measures.

Event ID	From Date	To Date	Route ID	From Measure	From Ref Offset	To Measure	To Ref Offset
EventA	1/1/2000	<Null>	Route1	5	5	15	15

Merge two or more events

Complete the following steps to merge events using the Merge Events pane:

1. Open the map in ArcGIS Pro and zoom to the location where you want to merge events.
2. On the Location Referencing tab, and in the Events group, click Merge Events .

   The Merge Events pane appears.

   

3. Choose the event layer that has the events you want to merge in the Event Layer drop-down list.

   In the example below, DOT Class is the chosen event layer.

4. Select the events on the map by drawing a bounding box.

   Tip:

   You can select events on the map using any of the selection tools. You can also select rows in the event layer attribute table while the Merge Events pane is active to populate the Events To Merge table.

   In either case, the events must belong to the same event layer selected in the Event Layer drop-down list to populate the Events To Merge table.

   Each of the selected events is placed in a row in the Events To Merge table using its Object ID and in the order of calibration on the route.

   

5. Optionally, change the dates in the Start Date and End Date text boxes.

   The start date default is today's date.

6. Optionally, edit the attributes in the Merged Event Attributes table.

   LRS fields such as the event ID or route ID are not editable.

   Note:

   Coded value, range domains, subtypes, and attribute rules are supported when configured for any field in the Merged Event Attributes table.

7. Click Run to merge the events.

   A confirmation message appears at the top of the pane once the events are merged.

Editing with conflict prevention enabled

You can merge two or more adjoining events after acquiring locks under these conditions:

• No one has a lock on the event layer in any versions of the feature service for the route on which the events will be located.
• You have an event lock on the event layer in which you're currently working.
• You have a lock in the current version on the route on which the event lies.
• You have a lock on the concurrent route of another network in the same version in which you're currently working.
• You can edit an event layer if other events along the same route have locks acquired by different people in different versions.

You can't merge two or more adjoining events under these conditions:

• The event layer is locked by another person for the route on which the event is located.
• The event layer is locked by you for the route on which the event is located but in a different version.
• The route on which the event is located is locked by another person.
• The route on which the event is located is locked by you but on a different version.
• The concurrent route on another network is locked by you in another version or by a different person in a different version.