Available with Location Referencing license.
Characteristics of a route can be represented as a line event offset from an intersection, an LRS point event, or a non-LRS point feature. 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, point events, or non-LRS point features are found in the active map.
Location offset scenarios
In the examples below, the start measure and end 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 start measure is located 2 miles from the intersection on the left and the end 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 end 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 start measure of 2 on Route1 and an end measure of 37 on Route3. Because the start measure is upstream of the intersection, the offset distance is -3 miles, and the offset distance of the end measure is 2 miles. In this case, the first offset refers to the intersection of Route1 and Route11, while the second offset refers to the intersection of Route3 and Route13.
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:
- Open the map in ArcGIS Pro and zoom to the location where you want to add the line event.
- 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.
- Click the From Method drop-down arrow and choose Location Offset.
- Click the To Method drop-down arrow and choose Location Offset.
Using the Location Offset method, the measure location is based on an offset from a specified location.
- Click Next.
The Event Layer drop-down menu, the Network drop-down menu, the Location Offset sections, and the Dates section appear in the Add Line Event pane.
- 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.
- If the network is a line network, specify the name of the line feature on which the events is located by doing one of the following:
- Type the line name in the Line Name text box.
- Click Choose line from map
and select the line from the map.
The line is highlighted in light blue. The arrow at the end shows the direction of calibration of the line.
- In the From: Location Offset section, specify the route by doing one of the following:
- Click the Route Name drop-down arrow and choose the route on which the event's from measure will be located.
- Type the route name in the Route Name text box.
- Click Choose route from map and click the route on the map.
Tip:
If the parent LRS Network is a line network, you can also choose the route from the Route Name drop-down menu. Only routes that are part of the chosen line can be selected.
- Click the Point Layer drop-down arrow and choose the intersection, LRS point event, or non-LRS point layer name.
Note:
All the point layers that are published with the feature service are listed. LRS point events from a network other than the one specified under Network will not be listed. The LRS calibration point layer is not supported.
- For the text box below the Point Layer drop-down menu, specify the point feature's name by doing one of the following:
- Type the point feature's name in the text box.
- Click the Choose location from map tool
and click a point feature on the map.
Note:
- The name of the text box below the Point Layer drop-down menu is dependent on the point layer's display field. For intersections, the name of the text box will always be IntersectionName.
- If more than one point feature exists at the clicked location, the Select Feature dialog box appears.
- Specify the Offset value for the location by doing one of the following:
- Click the Offset drop-down arrow to choose the offset direction, provide the measure value, and choose the units.
- Provide 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 start measure value for the event.
Note:
- The offset value is the distance between the chosen point layer and the proposed start measure on the selected route.
- The direction is an optional selection.
- If no direction is selected, a positive offset value places the start measure location along the direction of calibration from the selected point feature.
- If no direction is selected, a negative offset value places the start measure location opposite the direction of calibration from the selected point feature.
- In the To: Location Offset section, specify the route by doing one of the following:
- Click the Route Name drop-down arrow and choose the route on which the event's to measure will be located.
- Type the route name in the Route Name text box.
- Click Choose route from map and click the route on the map.
If the routes are on a line in a line network, only routes that are part of the specified line can be selected.
- Click the Point Layer drop-down arrow and choose the intersection, LRS point event, or non-LRS point layer name.
Note:
All the point layers that are published with the feature service are listed. LRS point events from a network other than the one specified under Network will not be listed. The LRS calibration point layer is not supported.
- For the text box below the Point Layer drop-down menu, specify the point feature's name by doing one of the following:
- Type the point feature's name in the text box.
- Click the Choose location from map tool and click a point feature on the map.
Note:
- The name of the text box below the Point Layer drop-down menu is dependent on the point layer's display field. For intersections, the name of the text box will always be IntersectionName.
- If more than one point feature exists at the clicked location, the Select Feature dialog box appears.
- Specify the Offset value for the referent offset by doing one of the following:
- Click the Offset drop-down arrow to choose the offset direction, provide a measure, and choose the units.
- Provide 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 end measure value for the events.
Note:
- The offset value is the distance between the chosen point layer and the proposed end measure on the selected route.
- The direction is an optional selection.
- If no direction is selected, a positive offset value places the end measure location along the direction of calibration from the selected point feature.
- If no direction is selected, a negative offset value places the end measure location opposite the direction of calibration from the selected point feature.
- Specify the date that defines the start date of the events by doing one of the following:
- Provide 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 cannot be before the start date of the selected route.
The start date default is today's date, but you can choose a different date.
- Specify the date that defines the end date of the events by doing one of the following:
- Provide 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.
- 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—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. Optionally, refer to the merge coincident events scenarios for more detailed examples.
- 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.
- Click Next.
Attributes for the chosen event layer appear under Manage Attributes appears.
Note:
Check the Go to next measure upon run check box to start your next edit at the end measure location of the previous edit. The To Method value and its populated information from the previous edit carry over to the next edit as the From Method value and its populated information.
For example, if you use a From Method value of Location Offset and a To Method value of Coordinates to add a line event, enabling this option will start your next edit with From Method and To Method values of Coordinates with the coordinates information from the previous edit in the From: Coordinates section.
- Provide attribute information for the new event using the Manage Attributes section.
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.
- 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:
- Open the map in ArcGIS Pro and zoom to the location where you want to add the line events.
- 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.
- Click the From Method drop-down arrow and choose Location Offset.
- Click the To Method drop-down arrow and choose Location Offset.
- Click Next.
The Network and Location Offset sections appear in the Add Multiple Line Events pane.
- Click the Network drop-down arrow and choose the parent LRS Network of the line event layer.
- If the network is a line network, specify the name of the line feature on which the events will be located by doing one of the following:
- Type the line name in the Line Name text box.
- Click Choose line from map
The line is highlighted in light blue. The arrow at the end shows the direction of calibration of the line.
- In the From: Location Offset section, specify the route by doing one of the following:
- Provide the route name.
- Click the Route Name drop-down arrow and choose the route on which the event's from measure will be located.
- Click Choose route from map and click the route on the map.
If the routes are on a line in a line network, only routes that are part of the chosen line can be selected.
- Click the Point Layer drop-down arrow and choose the intersection, LRS point event, or non-LRS point layer name.
Note:
All the point layers that are published with the feature service are listed. LRS point events from a network other than the one specified under Network will not be listed. The LRS calibration point layer is not supported.
- For the text box below the Point Layer drop-down menu, specify the point feature's name by doing one of the following:
- Type the point feature's name in the text box.
- Click the Choose location from map tool and click a point feature on the map.
Note:
- The name of the text box below the Point Layer drop-down menu is dependent on the point layer's display field. For intersections, the name of the text box will always be IntersectionName.
- If more than one point feature exists at the clicked location, the Select Feature dialog box appears.
- Specify the Offset value for the location by doing one of the following:
- Click the Offset drop-down arrow to choose the offset direction, provide the measure value, and choose the units.
- Provide 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 start measure value for the event.
Note:
- The offset value is the distance between the chosen point layer and the proposed start measure on the selected route.
- The direction is an optional selection.
- If no direction is selected, a positive offset value places the start measure location along the direction of calibration from the selected point feature.
- If no direction is selected, a negative offset value places the start measure location opposite the direction of calibration from the selected point feature.
- In the To: Location Offset section, specify the route by doing one of the following:
- Click the Route Name drop-down arrow and choose the route on which the event's to measure will be located.
- Type the route name in the Route Name text box.
- Click Choose route from map and click the route on the map.
If the routes are on a line in a line network, only routes that are part of the specified line can be selected.
- Click the Point Layer drop-down arrow and choose the intersection, LRS point event, or non-LRS point layer name.
Note:
All the point layers that are published with the feature service are listed. LRS point events from a network other than the one specified under Network will not be listed. The LRS calibration point layer is not supported.
- For the text box below the Point Layer drop-down menu, specify the point feature's name by doing one of the following:
- Type the point feature's name in the text box.
- Click the Choose location from map tool and click a point feature on the map.
Note:
- The name of the text box below the Point Layer drop-down menu is dependent on the point layer's display field. For intersections, the name of the text box will always be IntersectionName.
- If more than one point feature exists at the clicked location, the Select Feature dialog box appears.
- Specify the Offset value for the referent offset by doing one of the following:
- Click the Offset drop-down arrow to choose the offset direction, provide a measure, and choose the units.
- Provide 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 end measure value for the events.
Note:
- The offset value is the distance between the chosen point layer and the proposed end measure on the selected route.
- The direction is an optional selection.
- If no direction is selected, a positive offset value places the end measure location along the direction of calibration from the selected point feature.
- If no direction is selected, a negative offset value places the end measure location opposite the direction of calibration from the selected point feature.
- Provide 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 cannot be before the start date of the selected route.
The start date default is today's date, but you can choose a different date.
- Specify the date that defines the end date of the events by doing one of the following:
- Provide 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.
The end date is optional If no end date is provided, the events remain valid from the event start date into the future.
- 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—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. Optionally, refer to the merge coincident events scenarios for more detailed examples.
- 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.
- 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.
Note:
Enable the Go to next measure upon run option to start your next edit at the end measure location of the previous edit. The To Method and its populated information from the previous edit will carry over into the next edit as the From method and its populated information.
For example, if you use a From Method of Location Offset and a To Method of Coordinates to add a line event, enabling this option would start your next edit with a From and To Method of Coordinates with the coordinates information from the previous edit in the From: Coordinates section.
- 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. - 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 Pipeline Referencing 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 point layer's name is used as the RefMethod value. The RefLocation value is IntersectionID if the point layer used is an intersection; otherwise, the value is Object ID.
If either measure of a line event is updated, the corresponding offset value updates to reflect the new measure.
Note:
To offset an event from a point feature class that is not part of the LRS (but is in the feature service) and you want to capture the non-LRS point feature used in the referent fields, you must manually add that feature class's code and description (name) to the dReferentMethod domain.
Learn more about the properties of manually added referent and offset fields in an event layer
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 routes before event creation:
The following table provides details about the routes:
| Route ID | From Measure | To Measure | From Date | To Date |
|---|---|---|---|---|
R1 | 0 | 5 | 1/1/2000 | <Null> |
R2 | 2 | 12 | 1/1/2000 | <Null> |
R3 | 13 | 18 | 1/1/2000 | <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, and the intersection is used as the FromRefLocation and ToRefLocation values.
| FromRefMethod | FromRefLocation | FromRefOffset | ToRefMethod | ToRefLocation | ToRefOffset |
|---|---|---|---|---|---|
Intersection | Intersection1 | -4 | Intersection | Intersection1 | 4 |
The following table provides details about the default event fields after event creation:
| Event ID | FromRouteID | ToRouteID | From Date | To Date | From Measure | To Measure |
|---|---|---|---|---|---|---|
Event1 | R2 | R2 | 1/1/2000 | <Null> | 3 | 11 |
You can edit the event using the attribute table so that it uses referents other than the default values. If subsequent route edits are made, the RefMethod and RefLocation values revert to the parent LRS Network and the route, respectively.
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 Measure | To Measure | From Date | To Date |
|---|---|---|---|---|
R1 | 0 | 5 | 1/1/2000 | <Null> |
R2 | 2 | 12 | 1/1/2000 | <Null> |
R3 | 13 | 18 | 1/1/2000 | <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 | FromRefOffset | ToRefMethod | ToRefLocation | To RefOffset |
|---|---|---|---|---|---|
Anomaly | 106 | -4 | Anomaly | 106 | 4 |
The following tables provide details about the default event fields after event creation:
ConsequenceSegment
| Event ID | FromRouteID | ToRouteID | From Date | To Date | From Measure | To Measure |
|---|---|---|---|---|---|---|
Event1 | R2 | R2 | 1/1/2000 | <Null> | 3 | 11 |
DOTClass
| Event ID | FromRouteID | ToRouteID | From Date | To Date | From Measure | To Measure |
|---|---|---|---|---|---|---|
Event1 | R2 | R2 | 1/1/2000 | <Null> | 3 | 11 |
ExcavationDamage
| Event ID | FromRouteID | ToRouteID | From Date | To Date | From Measure | To Measure |
|---|---|---|---|---|---|---|
Event1 | R2 | R2 | 1/1/2000 | <Null> | 3 | 11 |
You can edit the event using the attribute table so that it uses referents other than the default values. 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 option 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 EventA before the edit:
| Event ID | Route Name | From Measure | To Measure | From Date | To Date | Speed |
|---|---|---|---|---|---|---|
EventA | Route1 | 3 | 7 | 1/1/2000 | <Null> | 65 |
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 EventB after the edit:
| Event ID | Route Name | From Measure | To Measure | From Date | To Date | Speed |
|---|---|---|---|---|---|---|
EventB | Route1 | 5 | 7 | 1/1/2005 | <Null> | 45 |
The following diagram shows the impact of checking the Retire overlaps option:
The following table provides details about both events after the second event is created:
| Event ID | Event Layer | Class Type |
|---|---|---|
EventA | DOT Class | Class 1 |
EventB | DOT Class | Class 2 |
The following table provides details after the Retire overlaps option is checked:
| Event ID | Route Name | From Measure | To Measure | From Date | To Date | Speed |
|---|---|---|---|---|---|---|
EventA | Route1 | 3 | 7 | 1/1/2000 | 1/1/2005 | 65 |
EventA | Route1 | 3 | 5 | 1/1/2005 | <Null> | 65 |
EventB | Route1 | 5 | 7 | 1/1/2005 | <Null> | 45 |
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 tables provide details about EventA and EventC before the edit:
Speed Limit
| Event ID | Route Name | From Measure | To Measure | From Date | To Date | Speed Limit |
|---|---|---|---|---|---|---|
EventA | Route1 | 3 | 7 | 1/1/2000 | <Null> | 65 |
Parking
| Event ID | Route Name | From Measure | To Measure | From Date | To Date | Parking |
|---|---|---|---|---|---|---|
EventC | Route1 | 2 | 7 | 1/1/2000 | <Null> | Left Only |
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 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 tables provide details about EventB and EventD:
Speed Limit
| Event ID | Route Name | From Measure | To Measure | From Date | To Date | Speed Limit |
|---|---|---|---|---|---|---|
EventB | Route1 | 5 | 7 | 1/1/2005 | <Null> | 45 |
Parking
| Event ID | Route Name | From Measure | To Measure | From Date | To Date | Parking |
|---|---|---|---|---|---|---|
EventD | Route1 | 5 | 7 | 1/1/2005 | <Null> | Both |
The following diagram shows the route and events after the Retire overlaps option is checked:
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 tables provide details after the Retire overlaps option is checked:
Speed Limit
| Event ID | Route Name | From Measure | To Measure | From Date | To Date | Speed Limit |
|---|---|---|---|---|---|---|
EventA | Route1 | 3 | 7 | 1/1/2000 | 1/1/2005 | 65 |
EventA | Route1 | 3 | 5 | 1/1/2005 | <Null> | 65 |
EventB | Route1 | 5 | 7 | 1/1/2005 | <Null> | 45 |
Parking
| Event ID | Route Name | From Measure | To Measure | From Date | To Date | Parking |
|---|---|---|---|---|---|---|
EventC | Route1 | 3 | 7 | 1/1/2000 | 1/1/2005 | Left Only |
EventC | Route1 | 3 | 5 | 1/1/2005 | <Null> | Left Only |
EventD | Route1 | 5 | 7 | 1/1/2005 | <Null> | Both |
Merge coincident events scenarios
The examples below demonstrate adding line events that have coincident measures when the Merge coincident events option 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 EventA:
| Event ID | Event Layer | Class Type |
|---|---|---|
Event A | DOT Class | Class 1 |
The following table provides details about EventA before the edit:
| Event ID | Route Name | From Measure | To Measure | From Date | To Date | Speed |
|---|---|---|---|---|---|---|
EventA | Route1 | 0 | 4 | 1/1/2000 | <Null> | 65 |
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 new input:
| Event ID | Event Layer | Class Type |
|---|---|---|
[NewEvent input] | DOT Class | Class 1 |
The following table provides details about the new input:
| Event ID | Route Name | From Measure | To Measure | From Date | To Date | Speed |
|---|---|---|---|---|---|---|
[NewEvent input] | Route1 | 4 | 8 | 1/1/2000 | <Null> | 65 |
The following diagram shows the impact of checking the Merge coincident events option when adding the new event:
The following table provides details after event creation:
| Event ID | Event Layer | Class Type |
|---|---|---|
EventA | DOT Class | Class 1 |
The following table provides details after the new event measures are merged with EventA:
| Event ID | Route Name | From Measure | To Measure | From Date | To Date | Speed |
|---|---|---|---|---|---|---|
EventA | Route1 | 0 | 8 | 1/1/2000 | <Null> | 65 |
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 tables provide details about EventA and EventB before the edit:
Speed Limit
| Event ID | Route Name | From Measure | To Measure | From Date | To Date | Speed Limit |
|---|---|---|---|---|---|---|
EventA | Route1 | 0 | 4 | 1/1/2000 | <Null> | 65 |
Parking
| Event ID | Route Name | From Measure | To Measure | From Date | To Date | Parking |
|---|---|---|---|---|---|---|
EventB | Route1 | 0 | 5 | 1/1/2000 | <Null> | Left Only |
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 new event inputs:
| Event ID | Event Layer | Custom Value |
|---|---|---|
[NewEvent1 input] | DOT Class | Class 1 |
[NewEvent2 input] | Operating Pressure Range | Design |
The following tables provide details about the new event inputs:
Speed Limit
| Event ID | Route Name | From Measure | To Measure | From Date | To Date | Speed Limit |
|---|---|---|---|---|---|---|
[NewEvent1] | Route1 | 4 | 8 | 1/1/2005 | <Null> | 65 |
Parking
| Event ID | Route Name | From Measure | To Measure | From Date | To Date | Parking |
|---|---|---|---|---|---|---|
[NewEvent2] | Route1 | 4 | 8 | 1/1/2005 | <Null> | Left Only |
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 tables provide details after events are merged:
Speed Limit
| Event ID | Route Name | From Measure | To Measure | From Date | To Date | Speed Limit |
|---|---|---|---|---|---|---|
EventA | Route1 | 0 | 4 | 1/1/2000 | 1/1/2005 | 65 |
EventA | Route1 | 0 | 8 | 1/1/2005 | <Null> | 65 |
Parking
| Event ID | Route Name | From Measure | To Measure | From Date | To Date | Parking |
|---|---|---|---|---|---|---|
EventB | Route1 | 0 | 5 | 1/1/2000 | 1/1/2005 | Left Only |
EventB | Route1 | 0 | 8 | 1/1/2005 | <Null> | Left Only |