Data performance tips

Proper tuning of the database and the implementation of attribute and spatial indexes during the data loading operation will enhance the performance of any application. This is especially true for Esri Roads and Highways because of the extensive data processing steps involved.

To get optimal performance from mapping events in Roads and Highways, please ensure that your database has the appropriate indexes created.

Table Name	Multicolumn attribute index fields
Route	Route ID column or columns if a multifield Route ID
LRS Network feature class	<RouteID field>, a single field that is the concatenated version of all the fields from the route table in the LRS network feature class (LRSN_<Network Name>)
Calibration Point feature class	Route ID, NetworkID, From Date, and To Date
Centerline feature class	RoadwayIDGUID, From Date, and To Date
Centerline Sequence	Route ID, NetworkID, From Date, To Date, and RoadwayIDGUID
Event	EventID in the Event feature class (LRSE_<event layer name>) Route ID, EventID, From Date, and To Date for map navigation Route ID, EventID, From Date, To Date, and Measure (for point event) or From Measure and To Measure (for line events) for LRS editing workflows

If multiple columns from the route table are used to define the RouteID, then during the process of creating the LRS network feature class (LRSN_<Network Name>), an attribute index is added automatically to the From Date, To Date, and the single field that is the concatenated version of all the fields from the route table. Similarly when event feature class layers are created, an attribute index is added automatically to the From Date, To Date, RouteID and Event ID fields.

Since the calibration point and centerline feature class are stored in a geodatabase, spatial indexes are automatically created and maintained for you. In some circumstances, recalculating a spatial index may improve performance, as described in Modifying a spatial index.