Available with Location Referencing license.
ArcGIS Location Referencing allows you to create line or point events in a new event feature class for an existing LRS Network; modify an existing event feature class in an existing LRS Network; 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. The shape of the event features is managed based on the route, measure, and start and end dates.
Create an LRS event
You can use the Create LRS Event tool to create line or point events 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.
Learn more about the event feature class and its fields and properties
To add derived measure fields to the event feature class, run the Enable Derived Measure Fields geoprocessing tool.
To add referent fields to the event feature class, run the Enable Referent Fields tool. This tool enables the referent fields by allowing you to register existing fields as referent fields.
When the Create LRS Event tool is run with these options, a feature class is created in the geodatabase and is registered with the LRS.
- In ArcGIS Pro, open the Create LRS Event tool.
- Click the Browse button
next to Parent LRS Network and browse to the LRS network feature class in the geodatabase where the event will be 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.
- Provide the name of the event to be registered in the Event Name parameter.
If the event feature class doesn't exist in the LRS Network, it is created.
- Click the Geometry Type drop-down arrow and choose Point or Line.
- Use the default name or provide a name for the event ID event feature class field in the Event ID Field parameter.
- Use the default name or provide a name for the route ID event feature class field in the Route ID Field parameter.
- Use the default name or provide a name for the starting date event feature class field in the From Date Field parameter.
- Use the default name or provide a name for the ending date event feature class field in the To Date Field parameter.
- Use the default name or provide a name for the location error event feature class field in the Location Error Field parameter.
- Use the default name or provide a name for the measure event feature class 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 starting measure field in the event feature class and specify an ending measure field in the To Measure Field parameter.
- Optionally, check the Store Route Name parameter to store the route name with the event records.
- Optionally, check the Event Spans Routes parameter to enable spanning routes for this event.
Note:
This parameter is active only if Geometry Type is Line.
- Click Run to run the tool.
The event feature class is mapped to the selected fields.
Create an LRS event from an existing dataset
You can 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. This tool enables the referent fields by allowing you to register existing fields as referent fields.
Learn more about the event feature class and its fields and properties
- In ArcGIS Pro, open the Create LRS Event From Existing Dataset tool.
- Click the Browse button
next to Parent LRS Network and browse to the LRS network feature class in the geodatabase where the event will be registered.
Note:
If an LRS Network feature class doesn't exist in your LRS, you must create one.
- 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.
- Use the default name or choose the event ID feature class field from the Event ID Field drop-down menu.
- Use the default name or choose the route ID feature class field name from the Route ID Field drop-down menu.
- Use the default name or choose the starting date feature class field name from the From Date Field drop-down menu.
- Use the default name or choose the ending date feature class field name from the To Date Field drop-down menu.
- Use the default name or choose the location feature class field name from the Loc Error Field drop-down menu.
- Use the default name or choose the measure feature class field name from the Measure Field drop-down menu.
If you're creating a line event; choose the starting measure field in the event feature class by clicking the Measure Field drop-down arrow. The To Measure Field parameter is active for line events.
- For line events only, use the default ending measure feature class field or choose it from the To Measure Field drop-down menu.
- Optionally, check the Event Spans Routes parameter to enable spanning routes for this event.
Note:
This parameter is active only if Geometry Type is Line.
- Optionally, check the Store Route Name parameter to store the route name with the event records.
- Click Run to run the tool.
The event feature class is mapped to the selected fields.
Modify an LRS event
You can modify existing LRS events using the Modify LRS Event tool by remapping 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.
Note:
Any new fields that will be used for field mapping should be created in the underlying LRS event feature class before using this tool and must have the properties outlined in the events data model.
- In ArcGIS Pro, open the Modify LRS Event tool.
- 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 selected event feature class.
Tip:
You can also choose the event feature class by clicking Browse
.
- Choose the replacement field or fields you created in the LRS event feature class.
- Click Run to run the tool.
The event feature class is remapped to the selected fields.
Load event data
You can load event records from a table, layer, or feature class into an existing event feature class using the Append Events tool.
- In ArcGIS Pro, open the Append Events tool.
- Click the Input Event drop-down arrow and choose the table, layer, or feature class that contains the events you want to load.
Tip:
You can also click Browse
next to Input Event to choose the input table, layer, or feature class.
- Click the Target Event drop-down arrow and choose the existing event layer or feature class that contains the source event records you want to load.
- Click the Load Type drop-down arrow in the Field Map section and choose a method 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 appended events with measure or temporality overlap with identical Event IDs. Target event records are loaded into the event feature class.
- 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:
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.
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/2000 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
- Click Run to run the tool.
The event features are loaded.