Skip to main content

Events data model

Available with the Linear Referencing license.

ArcGIS Linear Referencing manages events in feature classes in the same geodatabase as the linear referencing system (LRS).

ArcGIS Linear Referencing manages the shape of the feature based on the route, measure, and start and end dates. The required source event data differs depending on the event type being registered. The following sections list the required fields for each event type.

Note:

Event feature classes can be modeled in advance or created when registering the event in the LRS. If modeled in advance, ensure that the spatial reference and x,y-, z-, and m-tolerance and resolution of the event feature class match that of the network in which it's registered.

Learn more about tolerance and resolution settings for the LRS

Minimum event fields

The minimum event fields are as follows:

Field Data type Length Is nullable Description
Event ID String Between 32 and 255 No The unique ID for each event record.
Route ID String or GUID Same type and length as the route ID field in the centerline sequence table No The unique ID for each route in the network.
Route Name (if configured) String 255 No The unique name for the route.
To Route ID (required for event feature classes that store events that span routes) String or GUID Same type and length as the route ID field in the centerline sequence table No The unique ID for the ending route in the network.
From Date Date 8 Yes The date that the event becomes active on the route.
To Date Date 8 Yes The date that the event is retired on the route.
Measure (point events only) Any Numeric N/A No The measure on the route where the event is located.
From Measure (line events only) Any Numeric N/A No The measure on the route where the beginning of the event is located.
To Measure (line events only) Any Numeric N/A No The measure on the route where the end of the event is located.
Location Error String 100 Yes The location error for the event.
Field Data type Length Is nullable Description
Event ID String Between 32 and 255 No The unique ID for each event record.
Route ID String Same length as the route ID field in the centerline sequence table No The unique ID for each route in the network.
Route Name (if configured) String 255 No The unique name for the route.
From Date Date 8 Yes The date that the event becomes active on the route.
To Date Date 8 Yes The date that the event is retired on the route.
Measure (point events only) Any Numeric N/A No The measure on the route where the event is located.
From Measure (line events only) Any Numeric N/A No The measure on the route where the beginning of the event is located.
To Measure (line events only) Any Numeric N/A No The measure on the route where the end of the event is located.
Location Error String 100 Yes The location error for the event.

Event referent fields

When registering events, you can store the event location based on its offset from another location. The offsets can be based on x- and y-coordinates, a station, the distance from the beginning of an event, other LRS events, intersections, or another point feature class.

You can use the Enable Referent Fields tool to enable storing referent locations with an event. The following fields are required:

Field Data type Length Is nullable Description
Referent Method (point events only) Short Integer 5 Yes The method for referencing the offset feature. This can be x,y coordinates, stationing, length, LRS Network, event, intersection, or other point feature classes.
Referent Location (point events only) String Between 50 and 255 Yes The location of the offsetting feature. This can be an x,y coordinate, feature or event ID, or intersection ID.
Referent Offset (point events only) String Between 50 and 255 Yes The offset measure. This is saved in the unit of measure configured when registering an event and configuring the offset fields.
From Referent Method (line events only) Short Integer 5 Yes The method for referencing the offset feature. This can be x,y coordinates, stationing, length, LRS Network, event, intersection, or other point feature classes.
From Referent Location (line events only) String Between 50 and 255 Yes The location of the offsetting feature. This can be an x,y coordinate, feature or event ID, or intersection ID.
From Referent Offset (line events only) String Between 50 and 255 Yes The offset measure. This is saved in the unit of measure configured when configuring offset fields.
To Referent Method (line events only) Short Integer 5 Yes The method for referencing the offset feature. This can be x,y coordinates, stationing, length, LRS Network, event, intersection, or other point feature classes.
To Referent Location (line events only) String Between 50 and 255 Yes The location of the offsetting feature. This can be an x,y coordinate, feature or event ID, or intersection ID.
To Referent Offset (line events only) String Between 50 and 255 Yes The offset measure. This is saved in the unit of measure configured when configuring offset fields.

Derived network event fields

When an event is registered with a line network, you can also store the derived network route and measure information. This allows you to store the route ID and measure from both a line and a derived network on the same event feature class.

To store derived network route and measure values on an event, add the following fields:

Field Data type Length Is nullable Description
Derived Route ID Text or GUID Same type and length as the route ID field in the centerline sequence table No The unique ID of the route in the derived network.
Derived Route Name Text Same length as the LineName field in Line Network Yes The name of the route in the derived network.
Derived Measure (point event only) Double N/A Yes The measure on the route in the derived network where the event is located.
Derived From Measure (line event only) Double N/A Yes The measure on the route in the derived network where the event begins.
Derived To Measure (line event only) Double N/A Yes The measure on the route in the derived network where the event ends.

Learn more about using derived networks in ArcGIS Linear Referencing

Stationing event fields

ArcGIS Linear Referencing supports the registration of point events with stationing measures in a geodatabase using the Enable Stationing Fields tool. Registering a stationing event allows you to locate stations with ahead and back station values at any measure along a route in the LRS Network.

When combined with referents and offsets, you can use a stationing event as an additional method for creating and editing the location of other events in the LRS.

When registering an event that uses stationing, include all fields from a route and measure point event in the source event data. The following fields are also required:

Field Data type Length Is nullable Description
Station String Any Yes The stationing value for the station.
Back Station String Any Yes The back stationing value for the station. This value is populated when an equation point is present at the station location.
Station Value Direction String Any Yes The field used to designate if stationing values increase in the opposite direction of the increase in measure on routes.

Event types

ArcGIS Linear Referencing has two types of events: those stored in the same geodatabase as the LRS and those stored in external databases. Events in the geodatabase are stored as feature classes; external events can be configured with or without a connection file.

Events can be registered as line or point events in a geodatabase for an existing LRS Network using the Create LRS Event tool.

External events from an external data source can be registered as line or point events for an existing LRS Network using the Configure External Event With LRS tool. If a connection cannot be made to the external data source, you can configure external events without a connection file using the Configure External Event Behaviors With LRS tool.

It is also recommended that you index project items to improve event table performance when registering events.

Note:

If an event feature class is modeled in advance, its spatial reference, x,y-, z-, and m-tolerance and resolution must match its associated network.

Learn more about tolerance and resolution in ArcGIS Linear Referencing

Events in a geodatabase

In addition to the location of the data source, internal and external events differ in how ArcGIS Linear Referencing manages them after registration.

ArcGIS Linear Referencing stores events in a geodatabase as feature classes and manages the shape of event features based on the route, measure, and start and end dates. This provides increased performance for mapping and spatial query of the event data.

When registering an event, you can model the feature class in a geodatabase in advance or create a new feature class. You can also copy the schema from another table or feature class to the new feature class in a geodatabase.

Learn more about creating and modifying LRS events

After registration, ArcGIS Linear Referencing automatically manages the event. When you make edits to a route, ArcGIS Linear Referencing applies the changes directly to the event feature class using the event measure behavior configuration. When the event layer is refreshed in the map, which is automatically triggered by an edit activity, you can see the updates immediately.

After performing and saving edits using the tools on the Linear Referencing tab, run the Apply Event Behaviors tool to update the event locations.

External events

External events can be configured with or without a connection file.

You can use the Configure External Event With LRS tool to establish a read-only connection to the external system. When you register an event table or feature class outside the geodatabase as an external event table, ArcGIS Linear Referencing does not write changes directly to the external event table because the connection is read-only. Business rules in the external system may govern measure updates, so ArcGIS Linear Referencing does not directly modify events in external systems.

You can also use the Configure External Event Behaviors With LRS tool to create external events without linking to a source table or feature. This creates an external event without any route or event information.

ArcGIS Linear Referencing supports pushing updates to both types of external events and maintains a log of all the edits performed that impact event measures. You can use web services to send these updates to the external table or feature class to apply measures. The required parameters and data in web services vary based on the type of external event.

Learn more about registering an external event