The storage model for organizations looking to migrate to Roads and Highways is not the same for all: some have a spatial LRS with geometry, and some do not; some use the geodatabase, and some do not. The general steps to migrate are as follows:

1. First, understand the Roads and Highways minimum schema for common centerline storage (two tables and two feature classes).

   Learn more about the LRS data model

2. Understand the data requirements for event data to map against a Roads and Highways LRS.

   Learn more about registering an event in the LRS geodatabase

3. Translate your LRS and centerline storage model into these tables.

   This process is different for each organization. In some cases, where multiple linear referencing methods and networks need to be supported, centerline conflation may need to take place. Look at the LRMs your organization currently has and see if there are opportunities to consolidate and reduce the number of linear referencing methods and networks. If you can get your networks into an ArcGIS PolylineMZ feature class, there are scripts on the Roads and Highways community that can help with migration.

   Learn more about the Roads and Highways community

4. Once the LRS data is migrated, configure the LRS using the LRS data model.
5. Decide which event tables or data to model in the geodatabase under the management of Roads and Highways, migrate these tables into the geodatabase, then register them with the network they reference.

   Learn more about registering an event in the LRS geodatabase

The precision and scale for the networks comes from the settings on the measure column of the calibration point feature class. This information is propagated to each network.

The precision and scale for events comes from the settings on the From Measure and To Measure columns on the event feature class.

You can get them from the Roads and Highways community.

Learn more about the Roads and Highways community

View the LRS hierarchy from the Location Referencing tab in the Contents pane or from the geodatabase node in the Catalog pane. If the LRS needs an upgrade, the (Upgrade) text appears next to it in the LRS hierarchy. Run the Modify LRS tool to upgrade the LRS. The operation can take several minutes. Find the version of the LRS Dataset to verify that the LRS has been upgraded.

The system requirements for Roads and Highways include the system requirements for ArcGIS Server; however, Roads and Highways is only supported on Windows Server platforms (not Linux or UNIX).

The memory (RAM), disk space, and processor power need to be adjusted based on the data volumes being worked with. In addition, the number of machines in a cluster need to be scaled to handle the number of concurrent requests being requested from the deployment.

For working with linear referencing data in Roads and Highways, it is recommended that you at least double the minimum RAM requirements specified by ArcGIS Server to allow for some of the memory requirements needed by the ArcGIS event feature layer, if you are publishing external event tables in your map services.

Learn more about ArcGIS Server system requirements

Yes, but you must have Roads and Highways installed and licensed on each machine participating in the cluster.

Yes. To access the tools on ArcGIS Server, the tools need to be published as part of a geoprocessing model. Refer to the toolbox located in the Roads and Highways installation directory for an example of how to build a model to incorporate the geoprocessing tools.

External events in Roads and Highways use the ArcGIS event feature layer. This layer locates events and draws them on a map at map request time. Though this feature is powerful and spatially enables data that does not maintain a shape, it is not as fast as a feature class. You may need to set your map scale dependencies so these layers only draw at certain scales.

Additionally, ensure these tables have the route ID columns indexed. The ArcGIS event feature layers query all events on all routes that intersect the viewed map extent. Indexing allows the queries to execute faster.

Not directly. Event Editor was developed to edit the event data modeled in the geodatabase registered with Roads and Highways. The only way external event tables that are not modeled in the geodatabase can be edited from the Event Editor is to create equivalent event feature classes in the geodatabase and register them with Roads and Highways. Event data could then be edited, but a process would need to be developed to move edited data from those event feature classes into the external event tables to provide the updates to the external system.

• Firefox
• Google Chrome

The Event ID, LocError, and ST_length fields are not editable.

Event Editor can't determine the single version name to display if you have at least one of the layers in map service that was not versioned or if you have layers from multiple versions in a map service.

Ensure that any Roads and Highways and ArcGIS Server licenses haven’t expired.

There could be a number of causes:

• Ensure that the user has access to the web map.
• Ensure the map service with linear referencing capability is running on ArcGIS Server.
• Ensure Roads and Highways is installed on all machines in the ArcGIS Server cluster hosting the map services with linear referencing capability.
• Ensure Event Editor config.json file is properly formatted (compare it in a file compare tool with the original version to ensure the JSON syntax didn’t get corrected).
• Ensure the web map configuration in the config.json file points to the correct web map.

Ensure that m- and z-support is not enabled on the redline feature class and that map services with linear referencing capability have the feature service capability enabled.