Adding linear events to dominant routes

The Event Editor allows you to add linear events to dominant routes where route concurrences exist.

Concurrent routes

Concurrent routes are routes that share the same centerlines; that is, they travel the same pavement but are modeled with different measures. This relationship may exist to model two routes with different directions of calibration, to model different directions of travel on the highway, or to model locations on highways where multiple routes converge into a common roadway for a subset of their paths. Where these concurrent routes exist, you can choose a route that's considered dominant using a set of rules.

The Event Editor app allows you to add linear events to dominant routes. For example, in the following image, there are three routes with route IDs: 100 with Name A, 200 with Name B, and 300 with Name B.

The route dominance rule is set as the lesser the Route Name, the more dominant the route. Using this condition, route 100 is the most dominant route, and routes 200 and 300 have the same order in dominance.

If you want to add linear events from the start of route 200 to the end of route 200, that process is done in four sections.

• Section 1—Route 200 is the dominant route, since no other route exists in this section; therefore, the event will be added to route 200.
• Section 2—Route 100 has the greater order of dominance; therefore, the event will be added to route 100.
• Section 3—Both route 200 and route 300 have the same order of dominance; therefore, the event will be added to the route of your choice.
• Section 4—Route 200 is the dominant route, since no other route exists in this section; therefore, the event will be added to route 200.

注：

• Route dominance rules should be configured to access this functionality.
• Events in the Attribute Set should belong to the same network for which the Route ID is selected.
• You can add events to one route at a time.

To add linear events to dominant routes, complete the following steps:

1. Open Event Editor and, if prompted, sign in to Portal for ArcGIS or ArcGIS Online.
2. Click the Edit tab.
3. In the Edit Events group, click the Line Events button .

   The Add Linear Events widget appears.

   注：

   The selections for the network to and from method and measure can be configured in advance when configuring, creating, or editing the default settings for attribute sets.

   Learn more about configuring and creating and editing default settings for attribute sets.

4. Click the Network drop-down arrow and choose the network that will serve as a source linear referencing method (LRM) for defining the input measures for the new events.

   The network is an LRS Network published as a layer in the Event Editor.

   You can specify the LRS Network to be used as the linear referencing method (LRM) for defining the start and end measures of the new linear event.

5. Type the route name on which the event's From measure will be located.

   提示：

   You can also click the Select a Route on the Map button to select the route on the map.

   

6. In the From section, choose the first option (with the suffix Network) in the Method drop-down list.
7. Provide the intended start location for the new linear event along the route using any of the following options:
   • Type the value in the Measure text box.
   • Click the Select From Measure on the Map button and choose the From measure value along the route on the map.
   • Click the Measure drop-down arrow and choose either Use the Route Start or Use the Route End as the From measure value for the event.

   If you type the From measure value, you can choose the unit for that value using the drop-down arrow. The From measure value will be converted into LRS units before saving the newly added events. For example, if the LRS is in miles and you've typed 528 feet as the From measure value, the newly added events will have a From measure value of 0.1 miles, because 528 feet equals 0.1 miles.

   A green plus symbol appears at the selected location on the map.

8. For the To measure value, repeat steps 4 through 6 for the To section.

   A red x symbol appears at the selected location on the map.

9. Choose the date that will define the start date of the events by doing one of the following:
   • Type the start date in the Start Date text box.
   • Click the Start Date drop-down arrow and choose the start date.
   • Check the Use route start date check box.

   The start date defaults to today's date, but you can choose a different date using the date picker. The end date is optional, and if it is not provided, the event remains valid now and into the future.

   注：

   If you configured your Event Editor instance to not allow dates prior to the start date of the route, and you enter a date prior to the start date of the selected route in Start Date, a warning message appears alerting you to choose a date on or after the start date of the selected route.

10. Choose the date that will define the end date of the events by doing one of the following:
    • Type the end date in the End Date text box.
    • Click the End Date drop-down arrow and choose the end date.
    • Check the Use route end date check box.
11. Choose from the following data validation options to prevent erroneous input while characterizing a route with linear events:
    • Retire overlaps—The system adjusts the measure and start and end dates of existing events in such a way that the new event does not cause an overlap with respect to time and measure values.

      

    • 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 the existing event in terms of measure values, the new event is merged into the existing event and the measure range is expanded accordingly.

      

    • Prevent measures not on route—This data validation option ensures that the input measure values for from measure and to measure values fall in the minimum and maximum range of measure values on the selected route.
    • Save events to dominant routes—Events are added to the dominant route in a section with concurrent routes. If enabled, any concurrent sections on the route selected allow you to choose which route the events will be added to on each concurrent section. This option is available when the network selected has dominance rules configured.
12. Check the Save events to dominant routes check box.

    This dominant routes option can be configured to be checked or not checked by default using the Event Editor configuration file.

13. Click Next.

    The route dominance table appears.

    

    The From Measure and To Measure columns show the values for each section of the chosen route from the previous pane. The From Measure and To Measure boxes under Route ID show the value for each dominant route where the events will be added.

    A black route ID without a drop-down arrow signifies that there was a single route in that section. A blue route ID with a drop-down arrow signifies that there are concurrent routes in that section, and the blue route is selected by the software based on the route dominance rules. You can select any other route using the drop-down arrow.

    

    A yellow route ID box with a drop-down arrow signifies that there is an ambiguous situation in selecting the dominant route, as there is a tie in the route names of route 200 and route 300. In this case, you need to manually select a route ID using the drop-down arrow. The yellow color disappears once you've manually selected a route.

    

    Select route 200. If you check the Merge adjacent records check box, the records in sections 3 and 4 will be merged since they have the same route ID.

    

14. Click Next.

    The tab showing the attribute set for the events opens. The event fields are shown under attribute group G1.

    

    注：

    You can check the check boxes to add data for specific events within the attribute set. No records are added for the events that are not checked. As shown in the following image, no records are added to the County_A and City_A events.

    

15. Provide the attribute information for the new event in the tables defined by attribute sets.

    You can use the Copy Attribute Values tool to copy event attributes from another route. Click the tool and click a route on the map to copy the event attributes.

    Event Editor uses a default attribute set, as seen on the Edit tab. You can modify the attribute set to create custom attribute sets or use the administrator-configured attribute set.

16. Use the following options to access more information on the attribute set:
    • Check the Show network name check box to show the LRS Network associated with the selected event layer.
    • The list of attributes in the tables defined by attribute sets can be from more than one event layer. If you want to identify the source event layer for each attribute, check the Show layer names check box.
    • Check the Go to the next measure upon save check box to prepopulate the From measure value using the To Measure value of the present section to continue the event creation process.
17. Click Save.

    The new linear events are created and appear on the map. A confirmation message appears at the lower right once the newly added line events are saved.

After an event has been successfully created, you have the following two options to continue characterizing the route:

• Click New Edit to clear all the input entries in the widget and restore the default values from the geodatabase to the attribute table.
• Click Next Edit to retain all the existing entries in the widget and the attribute table for the convenience of quick editing of similar characteristics.

Concurrent routes with different time ranges

The following image shows concurrent routes with different time ranges:

Route 200 has the From Date value of 1/1/2000, whereas route 100 and route 300 have the From Date value of 1/1/2010. Therefore, if the selected start date of the event is 1/1/2000, there are two route time ranges:

1. 1/1/2000 to 1/1/2010, when only route 200 existed.

   

2. 1/1/2010 to Null, when all three routes existed.