Registering an event by route and measure

This operation requires that you register an event using source data such as a table, feature class, Microsoft Access database, or Excel spreadsheet. If the event being registered is a feature class, Roads and Highways uses the provided feature class and also provides an option to regenerate the shapes or use the existing shapes as is. Once the event feature class is created, it becomes the authoritative source for the event data. If the event being registered is not a feature class, Roads and Highways will create a feature class with the prefix LRSE. This LRSE feature class becomes the authoritative source for the event data and should be used when creating an MXD for use in the Roadway Characteristics Editor. The source event used for registration is no longer needed within Roads and Highways.

During the registration process, Roads and Highways slices events into different features to provide support for temporality and honor the changes in route shape and measures across time. Desktop editing of the event shapes using the ArcGIS editing tools is not supported. Roads and Highways will take care of managing and generating event shapes based on changes to the event's route ID, measures, from date, to date, or changes to the route with which the event is associated.

Note:

If you have the Roads and Highways conflict prevention enabled, it requires your version to have the latest from the lock root version. If you are not working with the lock root version, you might want to reconcile with the lock root version before you start. This will minimize the chances of requiring to reconcile while registering an event.

1. Start ArcMap and open the Catalog window or start ArcCatalog.
2. In the Catalog tree, connect to the geodatabase that contains the ALRS and LRS Network for which you want to register event layers.
3. Expand the ALRS that contains the LRS Network for which you want to add event layers.
4. Right-click the LRS Network and click New > LRS Event.

   The ALRS Event Setup wizard appears.

5. Click Next.

   

6. Click Route and Measure.
7. Click Next.

   The General event properties dialog box appears.

   

8. Type a name for your event layer in the Event Name text box.
9. Verify that the parent network is set to the correct network.
10. Click the browse button next to the Event Table text box.

    The Browse Data dialog box appears.

    

    See Registering an external event source to learn more about setting up database connections to your external event database.

11. Browse to the business table for which you want to create an event layer and click Select.

    If the table you browse to is in the same geodatabase as your LRS Network, you will create a local event. If the table you browse to is outside of the geodatabase, you will create an external event. You must use caution to ensure you are pointing to the correct location when you browse to your business table. For more information about internal and external events, see Event types.

    The General event properties dialog box is populated with information from the event table.

    

12. Verify and update the rest of the information on the General event properties dialog box as needed.
    1. Set the Event ID Field value.
    2. Set the Route ID Field value.
    3. Set the From Date Field value.
    4. Set the To Date Field value.
    5. Set the Time zone value.
    6. Set the event type by choosing either the Point event or the Line event option.

       By default, the Event ID Field value is used as the primary key when the From Date Field and To Date Field values are not defined.

       If the From Date Field and To Date Field values are defined, the primary key uses a combination of the Event ID Field, From Date Field, and To Date Field values.

       If the external table supports the Roads and Highways temporality model at the time the event is created, specify the From Date Field and To Date Field values.

       If the From Date Field and To Date Field values are not provided, Roads and Highways assumes that the external table does not support temporality and expects only one entry per event. In this scenario, the Event ID column is treated as unique.

       Ensure the values in the FromDate and ToDate columns are not conflicting.

    7. Set the From Measure and To Measure fields.
13. Click Next and check Store referent location with event records to optionally set event referent offset field settings.

    For more information about storing referent and offset, see Storing referent and offset information for event location.

    

14. Click Next to set event behavior.

    For more information about setting event behavior, see Event behaviors.

15. Click Next to set perpendicular offset.

    Setting perpendicular offset is supported only for external events. For more information about perpendicular offsets, see Setting perpendicular offsets for event layers.

16. Click Finish.

Note:

• If you have the Roads and Highways conflict prevention enabled, you will need event locks for all the routes when you register the event. The event registration process cannot go further unless it acquires all the required event locks.

  For more information about conflict prevention, see Conflict prevention.

• If a message appears related to acquiring locks, the need to reconcile, or not being able to acquire locks, and so on, then you might have to take appropriate action. For more information about these messages and possible resolution, see Conflict prevention in Roads and Highways for Desktop.

• If you are working in the lock root version, then all the events locks acquired to register an event will be released automatically.
• If you are working in a child version, then all the event locks acquired to register an event will remain until you reconcile and post to the lock root version.