Add line events by location offset

Available with Location Referencing license.

Characteristics of a route can be represented as a line event offset from a location. The location offset method is an optional method in the Add Line Events pane and the Add Multiple Line Events pane that is applicable when intersections are found in the active map.

Location offset scenarios

In the examples below, the from measure and to measure of a line event are located using the location offset method.

Nonspanning line event

In the following diagram, the route has measures from 0 to 10 miles. The Event1 from measure is located 2 miles from the intersection on the left and the to measure is -4 miles from the intersection on the right.

Since the direction of calibration of the route is from left to right, the offset distance is calculated in the reverse direction (from right to left) and the offset distance in the second case is shown as a negative number. Alternatively, the to measure in this case can be located by an offset distance of 6 miles from the intersection on the left.

Spanning line event

In the following diagram, a line event spans routes on a line in a line network. Event1 has a from measure of 5 on Route1 and a to measure of 35 on Route3. Because the from measure is upstream of the intersection, the offset distance is -10 miles, and the offset distance of the to measure is 10 miles. In this case, both measures refer to the same intersection.

Add a line event by location offset

Complete the following steps using the Add Line Event tool to create a single line event using location offset:

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

   The Add Line Event pane appears. The From Method and To Method drop-down lists are populated with the Route and Measure value by default.

3. In the From Method drop-down list, choose Location Offset.
4. In the To Method drop-down list, choose Location Offset.

   Using the Location Offset method, the measure location is based on an offset from a specified location.

   

5. Click Next.

   The Event Layer and Network options and the Location Offset sections appear in the Add Line Event pane.

6. Click the Event Layer drop-down arrow and choose the line event layer.

   The parent LRS Network is populated based on the Event Layer value.

7. In the From: Location Offset section, specify the route by doing one of the following:
   • Type the route ID in the Route ID text box.
   • Click Choose route from map and click to select the route from the map.
   
8. Click the Location drop-down arrow and choose an intersection layer name.

   All the intersection layers that are published with the map service and are registered with the parent LRS Network are listed.

9. Specify the name of the intersection record by doing one of the following:
   • Type the intersection name in the Name text box.

     Tip:

     The name will automatically complete if found.

   • Click the Choose location from map tool and click an intersection point feature on the map.
10. Specify the Offset value for the location by doing one of the following:
    • Choose the offset direction from the Offset drop-down list, type the measure value, and choose the units.
    • Type the measure value and choose the units.
    • Click Choose offset from map and click a location along the route on the map.

    A green dot appears at the offset location along the route on the map. This is the location of the from measure value for the event.

    Note:

    • This value is the distance between the chosen intersection and the proposed from measure on the selected route.
    • The direction is an optional selection.
    • If no direction is selected, a positive offset value places the from measure location along the direction of calibration from the selected point feature.
    • If no direction is selected, a negative offset value places the from measure location opposite the direction of calibration from the selected point feature.
11. In the To: Location Offset section, specify the route by doing one of following:
    • Type the route ID in the Route ID text box.
    • Click Choose route from map and click the route on the map.
12. Click the Location drop-down arrow and choose an intersection layer name.
13. Specify the name of the intersection record by doing one of the following:
    • Type the intersection name in the Name text box.

      Tip:

      The name will automatically complete if found.

    • Click the Choose location from map tool and click an intersection point feature on the map.
14. Specify the Offset value for the reference offset by doing one of the following:
    • Choose the offset direction from the Offset drop-down list, type a measure, and choose the units.
    • Type the measure value and choose the units.
    • Click the Choose offset from map tool and click a location along the route on the map.

    A red dot appears at the offset location along the route on the map. This is the location of the to measure value for the events.

    Note:

    • This value is the distance between the chosen intersection and the proposed to measure on the selected route.
    • The direction is an optional selection.
    • If no direction is selected, a positive offset value places the from measure location along the direction of calibration from the selected point feature.
    • If no direction is selected, a negative offset value places the from measure location opposite the direction of calibration from the selected point feature.
15. Specify the date that defines the start date of the events by doing one of the following:
    • Type the start date in the Start Date text box.
    • Click Calendar and choose the start date.
    • Check the Route start date check box to use the route start date.

    Note:

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

16. Specify the date that defines the end date of the events by doing one of the following:
    • Type the end date in the End Date text box.
    • Click Calendar and choose the end date.
    • Check the Route end date check box to use the route end date.

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

17. 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. Optionally, refer to the retire overlaps scenarios for more detailed examples.

      

    • Merge coincident events—The new event is merged with the existing event and the measure range is expanded accordingly 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. Optionally, refer to the merge coincident events scenarios for more detailed examples.

      

18. Click Next.

    Manage Attributes appears.

19. Provide attribute information for the new event using the Manage Attributes settings.

    Note:

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

    

20. Click Run.

    The new line event is created and appears on the map. A confirmation message appears at the top of the pane once the newly added line event is created.

Add multiple line events by location offset

Complete the following steps using the Add Multiple Line Events tool to create line events using location offset:

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

   The Add Multiple Line Events pane appears with the default Route and Measure value.

3. In the From Method drop-down list, choose Location Offset.
4. In the To Method drop-down list, choose Location Offset.

   

5. Click Next.

   The Network and Location Offset sections appear in the Add Multiple Line Events pane.

   

6. Click the Network drop-down arrow and choose the parent LRS Network of the line event layer.
7. In the From: Location Offset section, specify the route by doing one of the following:
   • Type the route ID in the Route ID text box.
   • Click Choose route from map and click the route on the map.
8. Click the Location drop-down arrow and choose an intersection layer name.
9. Specify the name of the intersection record by doing one of the following:
   • Type the intersection name in the Name text box.

     Tip:

     The name will automatically complete if found.

   • Click the Choose location from map tool and click an intersection point feature on the map.
10. Specify the Offset value for the location by doing one of the following:
    • Choose the offset direction from the Offset drop-down list, type the measure value, and choose the units.
    • Type the measure value and choose the units.
    • Click Choose offset from map and click a location along the route on the map.

    A green dot appears at the offset location along the route on the map. This is the location of the from measure value for the event.

    Note:

    • This value is the distance between the chosen intersection and the proposed from measure on the selected route.
    • The direction is an optional selection.
    • If no direction is selected, a positive offset value places the from measure location along the direction of calibration from the selected point feature.
    • If no direction is selected, a negative offset value places the from measure location opposite the direction of calibration from the selected point feature.
11. In the To: Location Offset section, specify the route by doing either of the following:
    • Type the route ID in the Route ID text box.
    • Click Choose route from map and click the route on the map.

    A red dot appears at the offset location along the route on the map. This is the location of the to measure value for the events.

12. Click the Location drop-down arrow and choose an intersection layer name.
13. Specify the name of the intersection record by doing one of the following:
    • Type the intersection name in the Name text box.

      Tip:

      The name will automatically complete if found.

    • Click the Choose location from map tool and click an intersection point feature on the map.
14. Specify the Offset value for the reference offset by doing one of the following:
    • Choose the offset direction from the Offset drop-down list, type a measure, and choose the units.
    • Type the measure value and choose the units.
    • Click the Choose offset from map tool and click a location along the route on the map.

    A red dot appears at the offset location along the route on the map. This is the location of the to measure value for the events.

    Note:

    • This value is the distance between the chosen intersection and the proposed to measure on the selected route.
    • The direction is an optional selection.
    • If no direction is selected, a positive offset value places the from measure location along the direction of calibration from the selected point feature.
    • If no direction is selected, a negative offset value places the from measure location opposite the direction of calibration from the selected point feature.
15. Specify the date that defines the start date of the events by doing one of the following:
    • Type the start date in the Start Date text box.
    • Click Calendar and choose the start date.
    • Check the Route start date check box to use the route start date of the events.

    Note:

    The start date cannot be before the start date of the selected route.

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

16. Specify the date that defines the end date of the events by doing one of the following:
    • Type the end date in the End Date text box.
    • Click Calendar and choose the end date.
    • Check the Route end date check box to use the route end date of the event.

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

17. Choose a data validation option to prevent erroneous input while characterizing a route with linear 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. Optionally, refer to the retire overlaps scenarios for more detailed examples.

      

    • Merge coincident events—The new event is merged with the existing event and the measure range is expanded accordingly 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. Optionally, refer to the merge coincident events scenarios for more detailed examples.

      

18. Click Next.

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

    The Attribute Set list includes other attribute sets if configured.

19. Provide attribute information for the events in the Manage Attributes settings.

    

    Note:

    Click Copy attribute values by selecting event on the map and click a route on the map to copy event attributes from another route.

20. Click Run.

    The new line events are created and appear on the map. A confirmation message appears at the top of the pane once the newly added line events are created.

Referent offset when using the location offset method

The Roads and Highways events data model supports the configuration of referent 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 line events are created using the location offset method in a referent-enabled layer, the intersection layer's name is used as the From RefMethod and ToRefMethod values and the intersection ID is used as the FromRefLocation and ToRefLocation values.

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

The examples in the subsections below demonstrate the impact of adding a line event that has referent values enabled.

Before adding a line event with referents

The following diagram shows the route before event creation:

The following table provides details about the route:

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

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 a line event with referents

The following diagram shows a line event that has been added to an event layer that has referents enabled:

The following table provides details about the event referent fields in Event1 after event creation. The Intersection layer is used as the FromRefMethod and ToRefMethod values, while the intersection is used as the FromRefLocation and ToRefLocation values.

FromRefMethod	FromRefLocation	FromRefOffset	ToRefMethod	ToRefLocation	ToRefOffset
IntersectionLayer	Intersection1	-3	IntersectionLayer	Intersection1	17

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

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

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

Before adding multiple line events with referents

The following diagram shows the route before event creation:

The following table provides details about the route:

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

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 in Event1 after event creation:

FromRefMethod	FromRefLocation	ToRefMethod	ToRefLocation	FromRefOffset	To RefOffset
IntersectionLayer	Intersection1	IntersectionLayer	Intersection1	-3	17

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

CounterPeakLanes

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

CrackingPercent

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

DirectionalFactor

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

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

Retire overlaps scenarios

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

Single event scenario

In the following example, Route1 has an existing Speed Limit event that has dates from 1/1/2000 to <Null>. The impact of adding a second Speed Limit event with overlapping measures is shown.

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	Speed
Event A	Speed Limit	65

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	Speed
EventB	Speed Limit	45

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:

Tip:

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

Event ID	Event Layer	Speed
EventA	Speed Limit	65
EventB	Speed Limit	45

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 Speed Limit event and a Parking 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 shown.

The following diagram shows the route and the existing events:

The following table details custom values for EventA and EventC. The Speed Limit layer has the custom fields Speed and Units, and the Parking layer has the custom fields Side and Type.

Event ID	Event Layer	Custom Value 1	Custom Value 2
EventA	Speed Limit	65	Miles per hour
EventC	Parking	Left Only	Diagonal

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	Speed Limit	45	Miles per hour
EventD	Parking	Both	Parallel

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 details custom values for EventA and EventB in Speed Limit, as well as EventC and EventD in Parking. Each event layer has two custom fields in this case: Speed Limit has the custom fields Speed and Units, and Parking has the custom fields Side and Type.

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	Speed Limit	65	Miles per hour
EventB	Speed Limit	45	Miles per hour
EventC	Parking	Left Only	Diagonal
EventD	Parking	Both	Parallel

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 Speed Limit event that has dates from 1/1/2000 to <Null>. The impact of adding a Speed Limit event that has coincident measures when Merge coincident events is checked is shown.

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	Speed
Event A	Speed Limit	65

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	Speed
[NewEvent input]	Speed Limit	65

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	Speed
EventA	Speed Limit	65

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 Speed Limit event (EventA) and a Parking 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 shown.

The following diagram shows the route and the existing events:

The following table details custom values for EventA and EventB before the edit. The Speed Limit layer has the custom field Speed with the value 65, and the Parking layer has the custom field Side with the value Left Only.

Event ID	Event Layer	Custom Value 1
EventA	Speed Limit	65
EventB	Parking	Left Only

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]	Speed Limit	65
[NewEvent2 input]	Parking	Left Only

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 details custom values for EventA in Speed Limit and EventB in Parking. Speed Limit has two event records with the Speed value of 65. Parking also has two event records with the custom Side value of Left Only.

Event ID	Event Layer	Custom Value
EventA	Speed Limit	65
EventA	Speed Limit	65
EventB	Parking	Left Only
EventB	Parking	Left Only

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>