Events data model

Events are registered, or created, in Esri Roads and Highways in feature classes called event feature classes. For internal events, Esri Roads and Highways manages the shape of the feature based on the route, measure, and to and from dates. This provides increased performance in ArcGIS for Desktop for mapping and spatial query of the event data. For external events, a read-only connection with the source event data is established, and a feature class for that event is created, but changes are not written to the source event data. When registering an event, you can register either a feature class or event table. Depending on the type of event being registered, different fields are required in the source event data. The required fields for each event type are below.

Route and Measure events

Registering an event based on Route and Measure requires the records in the source data to have a route in the network and measure value to locate properly. In addition to those fields, the following fields are required in the source event data.

Field	Data Type	Length	IsNullable	Description
EventID	String	Between 32 and 255	Yes	Unique ID for each event record
RouteID	String	Length of the Network RouteID field or greater	Yes	Unique ID for each route in the network
FromDate	Date	8	Yes	The date the event became active on the route
ToDate	Date	8	Yes	The date the event was retired on the route
Measure (point events)	Any Numeric		Yes	The measure on the route where the event will be located
FromMeasure (line events)	Any Numeric		Yes	The measure on the route where the beginning of the event will be located
ToMeasure (line events)	Any Numeric		Yes	The measure on the route where the end of the event will be located

Storing Referent Location with events

When registering Route and Measure events, the option to store the event location based on its offset from another location is possible. These offsets can be based on x- and y-coordinates, a station, length from the beginning of an event, other LRS events, intersections, or another point feature class. To enable storing referent locations with a Route and Measure event, the following fields should be in the source event data.

Field	Data Type	Length	IsNullable	Description
ReferentMethod (point events)	Short Integer	5	Yes	Method of referencing the offset feature. Can be X,Y coordinates, Stationing, Length, LRS Network, Event, Intersection, or other point feature class.
ReferentLocation (point events)	String	Between 50 and 255	Yes	Location of the offsetting feature. Can be an X,Y coordinate, Feature/EventID, or IntersectionID.
ReferentOffset (point events)	String	Between 50 and 255	Yes	The offset measure. Saved in the unit of measure configured when configuring offset fields.
FromReferentMethod (linear events)	Short Integer	5	Yes	Method of referencing the offset feature. Can be X,Y coordinates, Stationing, Length, LRS Network, Event, Intersection, or other point feature class.
FromReferentLocation (linear events)	String	Between 50 and 255	Yes	Location of the offsetting feature. Can be an X,Y coordinate, Feature/EventID, or IntersectionID.
FromReferentOffset (linear events)	String	Between 50 and 255	Yes	The offset measure. Saved in the unit of measure configured when configuring offset fields.
ToReferentMethod (linear events)	Short Integer	5	Yes	Method of referencing the offset feature. Can be X,Y coordinates, Stationing, Length, LRS Network, Event, Intersection, or other point feature class.
ToReferentLocation (linear events)	String	Between 50 and 255	Yes	Location of the offsetting feature. Can be an X,Y coordinate, Feature/EventID, or IntersectionID.
ToReferentOffset (linear events)	String	Between 50 and 255	Yes	The offset measure. Saved in the unit of measure configured when configuring offset fields.

Stationing events

When registering a stationing event, all of the fields from a Route and Measure event are required in the source event data. In addition, the following fields should be present in the source event data.

Field	Data Type	Length	IsNullable	Description
AheadStation	String	Between 10 and 255	Yes	Stationing value for the station.
BackStation	String	Between 10 and 255	Yes	Back stationing value for the station. This value would be populated if an equation point is present at the station location.
Direction	Any Numeric or String		Yes	Field used to designate if stationing values increase in the opposite direction of the increase in measure on routes.