Add multiple line events by route and measure

Available with Pipeline Referencing license.

Characteristics of a route can be represented as a line event with start and end measure information along the route. Use the Add Multiple Line Events tool to add multiple line events at the same time.

The example in the following workflow demonstrates adding multiple line events.

The following diagram shows the routes and their attributes:

The following table provides details about attributes for the routes (R1, R2, and R3) that belong to LineA. Events are added between R1 and R3.

Route ID	From Date	To Date
R1	1/1/2000	<Null>
R2	1/1/2000	<Null>
R3	1/1/2000	<Null>

Add multiple line events by route and measure

Complete the following steps to add multiple line events by route and measure:

1. Open the map in ArcGIS Pro and zoom in to the location where you want to add the line events.
2. Click the Location Referencing tab, and in the Events group, click Add > Multiple Line Events .

   The Add Multiple Line Events pane appears with the Route and Measure default value as the From Measure and To Measure values.

   

   Using the Route and Measure method, the measure location is based on the measure values from the selected route.

3. Click Next.

   The From: Route and Measure, To: Route and Measure and Dates sections appear in the Add Multiple Line Events pane.

   

4. Click the Network drop-down arrow and choose the LRS Network of the route where you want to add line events.

   The network serves as the source linear referencing method (LRM) to define the input measures for the event.

   The network is an LRS Network published as a layer in the feature service.

5. If the selected network is a line network, click Choose line from map and choose a line from the map to populate the Line Name text box.

   Alternatively, provide the line name in the Line Name text box.

6. In the From: Route and Measure section, click Choose route from map and click the from route on the map.

   Alternatively, provide the route name in the Route Name text box.

   Tip:

   After clicking or Choose measure from map , hover over routes on the map to see the route and measure at the location of the pointer.

   You can set map scale options for display of route and measure information on the Options dialog box on the Location Referencing tab.

   Note:

   If a message regarding acquiring locks or reconciling appears, conflict prevention is enabled.

7. In the From: Route and Measure section, specify the start measure for the new line events along the route by doing one of the following to populate the Measure text box:
   • Click Choose measure from map and click the route on the map where you want the start measure placed.
   • Check the Use route start measure check box.
   • Provide the start measure value in the Measure text box.

   A green point appears at the selected location on the map.

8. In the To: Route and Measure section, click Choose route from map and click the to route on the map.

   Alternatively, provide the route name in the Route Name text box.

9. In the To: Route and Measure section, specify the end measure for the new line events along the route by doing one of the following to populate the Measure text box:
   • Click Choose measure from map and click the route on the map where you want to place the end measure value.
   • Check the Use route end measure check box.
   • Provide the end measure value in the Measure text box.

   A red point appears at the selected location on the map.

   The new events are created between the green and red dots.

10. Specify the start date of the line events by doing one of the following:
    • Provide the start date in the Start Date text box.
    • Double-click in the Start Date text box to use today's date.
    • Check the Route start date check box.

    The start date default value is today's date, but you can choose a different date using the date picker.

11. Optionally, specify the end date of the event by doing one of the following:
    • Click Calendar and choose the end date.
    • Provide the end date in the End Date text box.
    • Double-click in the End Date text box to use today's date.

    If no end date is provided, the event remains valid from the event start date into the future.

12. Choose a data validation option to prevent erroneous input while characterizing a route with line events.
    • Retire overlaps—The measure, start date, and end date of existing events are adjusted to prevent overlaps with respect to time and measure values once the new line event or events have been created. Refer to the retire overlaps scenarios for more examples.

      

    • Merge coincident events—When all attribute values for a new event are exactly the same as an existing event, and if the new event is adjacent to or overlapping an existing event in terms of its measure values, and its time slices are coincident or overlapping, the new event is merged with the existing event and the measure range is expanded accordingly. Refer to the merge coincident events scenarios for more examples.

      

13. Click Next.

    Manage Attributes appears in the pane with the default attribute set in the Attribute Set drop-down list.

    The Attribute Set drop-down list includes other attribute sets if configured.

    Learn more about configuring attribute sets

14. Optionally, click the Attribute Set drop-down arrow and choose the attribute set.
15. Provide attribute value information for the events in the attribute set.

    

    Note:

    Click the Copy attribute values by selecting event on the map button and click an existing line event belonging to the same event layer on the map to copy event attributes from that event.

    Note:

    Coded values, range domains, subtypes, contingent values, and attribute rules are supported when configured for a field in an Attribute Value table.

16. Click Run.

    A confirmation message appears once the line events are added and appear on the map.

The following tables provide details about the line events by event layer:

Consequence Segment

Event	From Route ID	To Route ID	From Date	To Date	From Measure	To Measure	Location Error	Consequence Area Type
Event1	R1	R3	1/1/2000	<Null>	1	18	No Error	High Consequence

DOT Class

Event	From Route ID	To Route ID	From Date	To Date	From Measure	To Measure	Location Error	Class Type
Event1	R1	R3	1/1/2000	<Null>	1	18	No Error	Class 3

Excavation Damage

Event	From Route ID	To Route ID	From Date	To Date	From Measure	To Measure	Location Error	Damage Type
Event1	R1	R3	1/1/2000	<Null>	1	18	No Error	Puncture

Inspection Range

Event	From Route ID	To Route ID	From Date	To Date	From Measure	To Measure	Location Error	Inspection Type
Event1	R1	R3	1/1/2000	<Null>	1	18	No Error	Aerial Survey

Operating Pressure Range

Event	From Route ID	To Route ID	From Date	To Date	From Measure	To Measure	Location Error	Pressure Type
Event1	R1	R3	1/1/2000	<Null>	1	18	No Error	Design

Test Pressure Range

Event	From Route ID	To Route ID	From Date	To Date	From Measure	To Measure	Location Error	Test Medium
Event1	R1	R3	1/1/2000	<Null>	1	18	No Error	Water

The following diagram shows the route and the associated line events that begin at 1 on R1 and end at 18 on R3 after the edit:

Referent offset when using the route and measure method

The Pipeline Referencing events data model supports the configuration of referent event fields and their enablement using the Enable Referent Fields tool. Once referent fields are configured and enabled in a layer, referent locations are populated and persisted in that layer when events are added or edited.

When events are created using route and measure in a referent-enabled layer, the parent LRS Network is used as the FromRefMethod and ToRefMethod values by default, and the route is used as the FromRefLocation and ToRefLocation values. The from and to measures of the new line events are used as the FromRefOffset and ToRefOffset values.

If either measure of a line event is updated, the corresponding offset value updates to reflect the new measure.

The examples below demonstrate the impact of adding multiple line events that have referent values enabled.

Before adding multiple line events with referents

The following diagram shows the routes before event creation:

The following table provides details about the routes:

Route ID	From Date	To Date	From Measure	To Measure
R1	1/1/2000	<Null>	0	5
R2	1/1/2000	<Null>	7	12
R3	1/1/2000	<Null>	13	18

The following table provides details about the event referent fields before event creation:

FromRefMethod	FromRefLocation	FromRefOffset	ToRefMethod	ToRefLocation	ToRefOffset
<Null>	<Null>	<Null>	<Null>	<Null>	<Null>

After adding multiple line events with referents

The following diagram shows multiple line events that have referents enabled:

The following table provides details about the event referent fields after event creation:

FromRefMethod	FromRefLocation	FromRefOffset	ToRefMethod	ToRefLocation	ToRefOffset
PipeSeriesNetwork	R1	0	PipeSeriesNetwork	R3	18

The following tables provide details about the default event fields after event creation:

ConsequenceSegment

Event ID	From Date	To Date	From Measure	To Measure
Event1	1/1/2000	<Null>	0	18

DOTClass

Event ID	From Date	To Date	From Measure	To Measure
Event1	1/1/2000	<Null>	0	18

ExcavationDamage

Event ID	From Date	To Date	From Measure	To Measure
Event1	1/1/2000	<Null>	0	18

You can edit the event using the attribute table so that it uses referents other than the default. If subsequent route edits are made, the RefMethod and RefLocation values revert to the parent LRS Network and the route, respectively.

Retire overlaps scenarios

The examples below demonstrate adding line events that overlap when the Retire overlaps check box is checked.

Single event scenario

In this example, Route1 has an existing DOT Class event that has dates from 1/1/2000 to <Null>. The impact of adding a second DOT Class event with overlapping measures is demonstrated.

The following diagram shows the route and the existing event:

The following table provides details about the custom values for EventA before the edit:

Event ID	Event Layer	Class Type
Event A	DOT Class	Class 1

The following table provides details about the default field values for EventA before the edit:

Event ID	Route Name	From Measure	To Measure	From Date	To Date
EventA	Route1	3	7	1/1/2000	<Null>

The following diagram shows the route and a second event that is added with dates from 1/1/2005 to <Null>:

The following table provides details about the custom values for EventB:

Event ID	Event Layer	Class Type
EventB	DOT Class	Class 2

The following table provides details about the default field values for EventB after the edit:

Event ID	Route Name	From Measure	To Measure	From Date	To Date
EventB	Route1	5	7	1/1/2005	<Null>

The following diagram shows the impact of checking the Retire Overlaps check box on the route and both events:

The following table provides details about the custom values for both events after event creation:

Event ID	Event Layer	Class Type
EventA	DOT Class	Class 1
EventB	DOT Class	Class 2

Tip:

EventA has two event records with identical custom values with different dates (and different from and to measures).

The following table provides details about the default values after retire overlaps is applied:

Event ID	Route Name	From Measure	To Measure	From Date	To Date
EventA	Route1	3	7	1/1/2000	1/1/2005
EventA	Route1	3	5	1/1/2005	<Null>
EventB	Route1	5	7	1/1/2005	<Null>

Multiple events scenario

In this example, Route1 has two existing events, a DOT Class event and an Operating Pressure Range event, both of which have dates from 1/1/2000 to <Null>. The impact of adding a second pair of events in the same event layers that have overlapping measures is demonstrated.

The following diagram shows the route and the existing events:

The following table provides details about the custom values for EventA and EventC. The DOT Class layer has the custom fields Class Type and Class Source, and the Operating Pressure Range layer has the custom fields Pressure Type and Pressure Value.

Event ID	Event Layer	Custom Value 1	Custom Value 2
EventA	DOT Class	Class 1	Calculated
EventC	Operating Pressure Range	Design	500

The following table provides details about the default field values for EventA and EventC before the edit:

Event ID	Route Name	From Measure	To Measure	From Date	To Date
EventA	Route1	3	7	1/1/2000	<Null>
EventC	Route1	2	7	1/1/2000	<Null>

The following diagram shows the route and two new events in the same event layers that are added with dates from 1/1/2005 to <Null>:

The following table provides details about the custom values for EventB and EventD:

Event ID	Event Layer	Custom Value 1	Custom Value 2
EventB	DOT Class	Class 2	Calculated
EventD	Operating Pressure Range	Certificate	700

The following table provides details about the default field values for EventB and EventD:

Event ID	Route Name	From Measure	To Measure	From Date	To Date
EventB	Route1	5	7	1/1/2005	<Null>
EventD	Route1	5	7	1/1/2005	<Null>

The following diagram shows the route and events after retire overlaps has been applied:

The following table provides details about the custom values for EventA and EventB in DOT Class, as well as EventC and EventD in Operating Pressure Range:

Tip:

Each event has multiple custom fields whose values are shown in the Custom Value 1 and Custom Value 2 columns in the following table. Values in these columns correspond to the Event Layer value in the same row.

Event ID	Event Layer	Custom Value 1	Custom Value 2
EventA	DOT Class	Class 1	Calculated
EventB	DOT Class	Class 2	Calculated
EventC	Operating Pressure Range	Design	500
EventD	Operating Pressure Range	Certificate	700

The following table provides details about the default values after retire overlaps is applied:

Event ID	Route Name	From Measure	To Measure	From Date	To Date
EventA	Route1	3	7	1/1/2000	1/1/2005
EventC	Route1	2	7	1/1/2000	1/1/2005
EventA	Route1	3	5	1/1/2005	<Null>
EventC	Route1	2	5	1/1/2005	<Null>
EventB	Route1	5	7	1/1/2005	<Null>
EventD	Route1	5	7	1/1/2005	<Null>

Merge coincident events scenarios

The examples below demonstrate adding line events that have coincident measures when the Merge coincident events check box is checked.

Single event scenario

In this example, Route1 has an existing DOT Class event that has dates from 1/1/2000 to <Null>. The impact of adding a DOT Class event that has coincident measures when Merge coincident events is checked is demonstrated.

The following diagram shows the route and the existing event:

The following table provides details about the custom values for EventA:

Event ID	Event Layer	Class Type
Event A	DOT Class	Class 1

The following table provides details about the default field values for EventA before the edit:

Event ID	Route Name	From Measure	To Measure	From Date	To Date
EventA	Route1	0	4	1/1/2000	<Null>

The following diagram shows the route and a second event that is added with dates from 1/1/2000 to <Null>:

The following table provides details about the custom values for the new input:

Event ID	Event Layer	Class Type
[NewEvent input]	DOT Class	Class 1

The following table provides details about the default field values for the new input:

Event ID	Route Name	From Measure	To Measure	From Date	To Date
[NewEvent input]	Route1	4	8	1/1/2000	<Null>

The following diagram shows the impact of checking the Merge coincident events check box when adding the new event:

The following table provides details about the custom values for the event after event creation:

Event ID	Event Layer	Class Type
EventA	DOT Class	Class 1

The following table provides details about the default values after the new event measures are merged with EventA:

Event ID	Route Name	From Measure	To Measure	From Date	To Date
EventA	Route1	0	8	1/1/2000	<Null>

Multiple events scenario

In this example, Route1 has two existing events, a DOT Class event (EventA) and an Operating Pressure Range event (EventB), both of which have dates from 1/1/2000 to <Null>. The impact of adding a second pair of events that have coincident measures in the same event layers, but different from and to dates, is demonstrated.

The following diagram shows the route and the existing events:

The following table provides details about the custom values for EventA and EventB before the edit. The DOT Class layer has the custom field Class Type with the value Class 1, and the Operating Pressure Range layer has the custom field Pressure Type with the value Design.

Event ID	Event Layer	Custom Value 1
EventA	DOT Class	Class 1
EventB	Operating Pressure Range	Design

The following table provides details about the default field values for EventA and EventB before the edit:

Event ID	Route Name	From Measure	To Measure	From Date	To Date
EventA	Route1	0	4	1/1/2000	<Null>
EventB	Route1	0	5	1/1/2000	<Null>

The following diagram shows the route and input for the new events that are added with dates from 1/1/2005 to <Null>:

The following table provides details about the custom values in the new event inputs:

Event ID	Event Layer	Custom Value
[NewEvent1 input]	DOT Class	Class 1
[NewEvent2 input]	Operating Pressure Range	Design

The following table provides details about the default field values in the new event inputs:

Event ID	Route Name	From Measure	To Measure	From Date	To Date
[NewEvent1]	Route1	4	8	1/1/2005	<Null>
[NewEvent2]	Route1	4	8	1/1/2005	<Null>

The following diagram shows the route and events after the new events have been merged based on the coincident measures. In this case, the dates result in a new event record, or new time slice, for the existing events with the updated measures.

The following table provides details about the custom values for EventA in DOT Class and EventB in Operating Pressure Range. DOT Class has two event records with the custom Class Type value, Class 1. Operating Pressure Range also has two event records with the custom Pressure Type value, Design.

Event ID	Event Layer	Custom Value
EventA	DOT Class	Class 1
EventA	DOT Class	Class 1
EventB	Operating Pressure Range	Design
EventB	Operating Pressure Range	Design

The following table provides details about the default values after events are merged:

Event ID	Route Name	From Measure	To Measure	From Date	To Date
EventA	Route1	0	4	1/1/2000	1/1/2005
EventA	Route1	0	8	1/1/2005	<Null>
EventB	Route1	0	5	1/1/2000	1/1/2005
EventB	Route1	0	8	1/1/2005	<Null>