Skip to main content

Create and modify LRS events

Available with the Linear Referencing license.

ArcGIS Linear Referencing allows you to create a new point or line event feature class for an existing LRS Network; modify an existing event feature class; or load event records from a table, layer, or feature class into an existing event feature class.

Events in the same geodatabase as the LRS are managed as feature classes. Event geometry is based on route, measure, and start and end dates.

Learn more about the events data model

Create an LRS event

Use the Create LRS Event tool to create line or point event feature classes for an existing LRS Network. If the event feature class is not modeled in advance, you can create it as an output of this tool while the event is registered in the LRS geodatabase.

To add derived measure fields to the event feature class, run the Enable Derived Measure Fields tool.

To add referent fields to the event feature class, run the Enable Referent Fields tool. Use this tool to register existing fields as referent fields.

To create an LRS event, complete the following steps:

  1. In ArcGIS Pro, open the Create LRS Event tool.

  2. Click the Browse button next to Parent LRS Network and browse to the LRS Network feature class to which the event is registered.

    The Event ID Field, Route ID Field, From Date Field, To Date Field, Location Error Field, and Measure Field parameters are populated from the specified Parent LRS Network value.

    Note:

    If an LRS Network feature class doesn't exist in your LRS, you must create one.

  3. Provide the name of the event in the Event Name parameter.

    An event feature class is created if it is not registered with the LRS Network.

  4. Click the Geometry Type drop-down arrow and choose Point or Line.

  5. Use the default name or provide a name for the event ID field in the Event ID Field parameter.

  6. Use the default name or provide a name for the route ID field in the Route ID Field parameter.

  7. Use the default name or provide a name for the start date field in the From Date Field parameter.

  8. Use the default name or provide a name for the end date field in the To Date Field parameter.

  9. Use the default name or provide a name for the location error field in the Location Error Field parameter.

  10. Use the default name or provide a name for the measure field in the Measure Field parameter.

    The Measure Field parameter options depend on the specified Geometry Type value:

    • If you're creating a point event, provide the name of the measure field in the event feature class.

    • If you're creating a line event, provide the name of the start measure field in the Measure Field parameter and provide the name of the end measure field in the To Measure Field parameter.

  11. Optionally, check the Event Spans Routes check box to store events that span routes.

    Note:

    This parameter is only available for line events.

  12. Optionally, check the Store Route Name check box to store the route name with the event records.

  13. Click Run.

The event feature class is created.

Create an LRS event from an existing dataset

Use the Create LRS Event From Existing Dataset tool to create line or point events for an LRS Network using an existing feature class.

To add referent fields to the event feature class, run the Enable Referent Fields tool. Use this tool to register existing fields as referent fields.

  1. In ArcGIS Pro, open the Create LRS Event From Existing Dataset tool.

  2. Click the Browse button next to Parent LRS Network and browse to the LRS Network feature class to which the event is registered.

    Note:

    If an LRS Network feature class doesn't exist in your LRS, you must create one.

  3. Click the Event Feature Class drop-down arrow and choose the event feature class.

    The remaining parameters are populated based on the chosen event feature class.

    Note:

    The event feature class must reside in the same feature dataset that contains the LRS.

  4. Use the default field or choose another event ID field from the Event ID Field drop-down menu.

  5. Use the default field or choose another route ID field name from the Route ID Field drop-down menu.

  6. Use the default field or choose another start date field name from the From Date Field drop-down menu.

  7. Use the default field or choose another end date field name from the To Date Field drop-down menu.

  8. Use the default field or choose another location error field name from the Loc Error Field drop-down menu.

  9. Use the default field or choose another measure field name from the Measure Field drop-down menu.

    If you're creating a line event, choose the start measure field by clicking the Measure Field drop-down arrow.

  10. For line events only, use the default field or choose another end measure field from the To Measure Field drop-down menu.

  11. Optionally, check the Event Spans Routes check box to store events that span routes.

    Note:

    This parameter is only available for line events.

  12. Optionally, check the Store Route Name check box to store the route name with the event records.

  13. Click Run.

The event feature class is created.

Modify an LRS event

Use the Modify LRS Event tool to remap one or more LRS event fields in an LRS event feature class. You can use this tool to add or remove properties from a line or point event.

Before using this tool, create any fields needed for field remapping in the underlying LRS event feature class. The field properties must adhere to the events data model.

  1. In ArcGIS Pro, open the Modify LRS Event tool.

  2. Click the LRS Event Feature Class drop-down arrow and choose the LRS event feature class you want to modify.

    The feature class must represent an LRS event.

    The remaining parameters are populated based on the chosen event feature class.

    Tip:

    You can also choose the event feature class by clicking Browse .

  3. Remap the LRS event fields as necessary.

  4. Click Run.

The LRS event fields are remapped.

Load event data

Use the Append Events tool to load event records from a table, layer, or feature class into an existing event feature class.

To load event data, complete the following steps:

  1. In ArcGIS Pro, open the Append Events tool.

  2. Click the Input Event drop-down arrow and choose the table, layer, or feature class that contains the source event records you want to load.

    Tip:

    You can also click Browse next to Input Event to choose the input table, layer, or feature class.

  3. Click the Target Event drop-down arrow and choose the existing event layer or feature class to which the source event records are appended.

  4. Click the Load Type drop-down arrow in the Field Map section and choose one of the following methods for loading the events:

    • Add—Appends input event records to the Target Event value. No changes are made to target event records.

    • Retire overlaps—Appends input event records to the Target Event value and retires any records in the Target Event value with measure or temporality overlaps as the appended events. If the appended event eclipses the Target Event value, it is deleted. This option should only be used for linear events.

    • Retire by event ID—Appends input event records to the Target Event value and retires any records in the Target Event value with the same event ID and temporality overlaps as the appended events. If the appended event eclipses the Target Event value with the same event ID, it is deleted.

    • Replace by event ID—Appends input event records to the Target Event value and deletes any records in the Target Event value with the same event ID as the appended events.

    The Field Map parameter value controls how the attribute information in the fields of the Input Event parameter value is transferred to the target event. Because the input event data is appended to an existing event that has a predefined schema (field definitions), fields cannot be added or deleted from the target dataset. While it is possible to set merge rules for each output field, the tool ignores those rules.

    The Load Type parameter value specifies how the tool handles appended events with measure or temporality overlap and identical event IDs.

  5. Optionally, check the Append events to dominant routes parameter to append events to the dominant routes where concurrencies exist.

    Note:

    The Append events to dominant routes parameter works with all load types—Add, Retire overlaps, Retire by event ID, and Replace by event ID.

    The following example illustrates a scenario in which point and line events are appended to the dominant route. In the following graphics and tables, there are multiple routes across two lines, L1 and L2. The concurrent route has opposite directions and different ranges in time.

    In this example, L2R1 is the dominant route in the concurrent section. The following diagram and table show routes before appending events:

    Before appending events

    Route Name Line Name From Date To Date
    L1R1 L1 1/1/2000 <Null>
    L1R2 L1 1/1/2000 <Null>
    L1R3 L1 1/1/2000 <Null>
    L1R4 L1 1/1/2000 <Null>
    L2R1 L2 1/1/2010 <Null>

    The following table shows the input point events:

    Event ID Route Name From Date To Date Measure Note Type
    InspectionNote1 L1R1 1/1/2000 <Null> 5 ILI Verification Dig
    InspectionNote2 L1R3 1/1/2005 <Null> 30 Gas Facility

    The following table shows the input line event:

    Event ID From Route Name To Route Name From Date To Date From Measure To Measure Class Type
    DOTclass1 L1R1 L1R4 1/1/2000 <Null> 0 70 Class 4

    Two point events are appended at two locations—one on L1R1, and the other on L1R3. At location 1, the InspectionNote1 event is appended to L1R1 because no other route exists at that location.

    After appending events

    At location 2, L1R3 is the only route that exists up until 1/1/2010, so the InspectionNote2 event is appended to L1R3 from 1/1/2005 to 1/1/2010. Starting from 1/1/2010, L2R1 is the dominant route, so the InspectionNote2 event is appended to L2R1.

    Similarly, a spanning line event, DOTclass1, is appended to all routes in L1 from 1/1/2000. From 1/1/2000 to 1/1/2010, the line event is appended to all routes in L1 because no concurrent routes exist in this time slice. Starting from 1/1/2010, the line event is split and appended to the dominant route, L2R1, at the concurrent route sections. The appended line events honor their corresponding route direction and measures.

    The following table provides details about the point event layer after appending point events:

    Event ID Route Name From Date To Date Measure Location Error Note Type
    InspectionNote1 L1R1 1/1/2000 <Null> 5 No Error ILI Verification Dig
    InspectionNote2 L1R3 1/1/2005 1/1/2010 30 No Error Gas Facility
    InspectionNote2 L2R1 1/1/2010 <Null> 112 No Error Gas Facility

    The following table provides details about the line event layer after appending line events:

    Event ID From Route Name To Route Name From Date To Date From Measure To Measure Location Error Class Type
    DOTclass1 L1R1 L1R4 1/1/2000 1/1/2010 0 70 No Error Class 4
    DOTclass1 L1R1 L1R2 1/1/2010 <Null> 0 17 No Error Class 4
    DOTclass1 L2R1 L2R1 1/1/2010 <Null> 108 123 No Error Class 4
    DOTclass1 L1R4 L1R4 1/1/2010 <Null> 40 70 No Error Class 4
  6. Optionally, check the Append events to dominant routes parameter to append events to the dominant routes where concurrencies exist.

    Note:

    The Append events to dominant routes parameter works with all load types—Add, Retire overlaps, Retire by event ID, and Replace by event ID.

    The following example illustrates a scenario in which point and line events are appended to the dominant route. In the following graphics and tables, there are routes named Route1 and Route2. The concurrent route has opposite directions and different ranges in time.

    In this example, Route2 is the dominant route in the concurrent section. The following diagram and table show routes before appending events:

    Before appending events

    Route ID From Date To Date
    Route1 1/1/2000 <Null>
    Route2 1/1/2010 <Null>

    The following table shows the input point events:

    Event ID Route ID From Date To Date Measure Severity
    Crash1 Route1 1/1/2000 <Null> 2 Minor
    Crash2 Route1 1/1/2005 <Null> 5 Fatal

    The following table shows the input line event:

    Event ID Route ID From Date To Date From Measure To Measure Functional Class Type
    FunctionalClass1 Route1 1/1/2000 <Null> 0 10 Arterial

    Two point events are appended at two locations on Route1. At location 1, the Crash1 event is appended to Route1 because no other route exists at that location.

    After appending events

    At location 2, Route1 is the only route that exists up until 1/1/2010, so the Crash2 event is appended to Route1 from 1/1/2005 to 1/1/2010. Starting from 1/1/2010, Route2 is the dominant route, so the Crash2 event is appended to Route2.

    Similarly, a line event, FunctionalClass1, is appended to Route1 from 1/1/2000. From 1/1/2000 to 1/1/2010, the line event is appended to Route1 because no concurrent routes exist in this time slice. Starting from 1/1/2010, the line event is split and appended to the dominant route, Route2, at the concurrent route section. The appended line events honor their corresponding route direction and measures.

    The following table provides details about the point event layer after appending point events:

    Event ID Route ID From Date To Date Measure Location Error Severity
    Crash1 Route1 1/1/2000 <Null> 2 No Error Minor
    Crash2 Route1 1/1/2005 1/1/2010 5 No Error Fatal
    Crash2 Route2 1/1/2010 <Null> 32 No Error Fatal

    The following table provides details about the line event layer after appending line events:

    Event ID Route ID From Date To Date From Measure To Measure Location Error Functional Class Type
    FunctionalClass1 Route1 1/1/2000 1/1/2010 0 10 No Error Arterial
    FunctionalClass1 Route1 1/1/2010 <Null> 0 3 No Error Arterial
    FunctionalClass1 Route2 1/1/2010 <Null> 30 45 No Error Arterial
    FunctionalClass1 Route1 1/1/2010 <Null> 6 10 No Error Arterial
  7. Click Run.

The event features are loaded.