The Roads and Highways community contains a download that has a sample dataset to use for evaluation based on the State of New York's LRS and Highway Performance Monitoring System (HPMS) event data.

Download Roads and Highways sample data.

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 to 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, make sure 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 ArcGIS 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 4.0 or later
• Internet Explorer 9 or later
• Safari 4.0 or later

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

ArcGIS 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.

There could be a number of reasons:

• Ensure that Roads and Highways is installed on all machines participating in the cluster hosting the map service with linear referencing capability.
• Ensure that any Roads and Highways
• licenses haven’t expired and that the ArcGIS Server licenses haven’t expired.
• Ensure that Roads and Highways is licensed on all machines participating in the cluster hosting the map service with linear referencing capability.

If you accidentally edit an event feature class shape and save the changes, use the Update Event Shapes command to correct the shapes of those events. Browse to the Catalog window and right-click the LRS event node of the geodatabase that is registered with Roads and Highways in ArcMap.

Learn more about updating event shapes

There could be a number of causes:

• Ensure that the user has access to the webmap.
• 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.