Overview of the Roadway Characteristics Editor deployment guide

Getting your organization's event and route data into the Roadway Characteristics Editor (RCE) is a straightforward process. Follow the steps below to deploy your application in a secure and stable manner.


It is strongly recommended that you follow the steps in the order outlined below.

  1. Install Esri Roads and Highways for Server

    To learn more about how to install Esri Roads and Highways for Server, see Installing Esri Roads and Highways for Server.

  2. Create a map document (MXD) with the appropriate routes, event layers, and redline layer using ArcGIS for Desktop and Esri Roads and Highways for Desktop.

    Make sure that the redline feature class has its m- and z-values disabled. For more information, see Deploying redline routes.


    Prior to publishing your web map, you must remove all time definition filters from internal event layers, LRS networks, intersection feature classes, and calibration points to allow for the viewing and editing of routes and events at specific dates. Time filters can be added and removed on your desktop. Once the time filters have been removed, you can use the time view widget in RCE to add and edit events on historical and future versions of LRS routes. The time setting in RCE only applies to Roads and Highways layers. Other layers published in the RCE map will not be impacted or changed as a result of changing the time view.

  3. Publish the map document with ArcGIS for Server and enable the Roads and Highways for Server Linear Referencing capability.

    For more information, see Enabling the linear referencing capability.

  4. Author a web map that includes the map service created in the previous step and the appropriate basemaps.
  5. Using Windows Explorer, browse to and copy the contents of $INSTALL_DIR$\Server\Web\RoadwayCharacteristics into the web folder of the web server.

    For example, in Internet Information Services (IIS), the web folder may be located at C:\inetpub\wwwroot\RoadwayCharacteristics.


    The actual location of the IIS wwwroot directory could differ on your server machine. Use the IIS Management Console to get the location of the IIS wwwroot directory.

  6. Open the configuration (config.json) file within the RoadwayCharacteristics web folder and modify it to use the web map and geoprocessing services created from previous steps. Optionally, you can choose to change some default administrative settings like user authentication, map selection symbology, and attribute sets while modifying the configuration file. Use the following guides to deploy: Adding DGN and DWG data: Deployment guide, Attribute sets configuration, and Deploying redline routes.
  7. Optionally, you can add the following configurations to the Roadway Characteristics Editor:

Event IDs when adding or editing events

The Roadway Characteristics Editor requires an Event ID column in each of the event layers it is configured to edit. When new events are created by the Roadway Characteristics Editor, an event ID must be provided for each record. The RCE can generate and provide event IDs if the Event ID column is a string and greater than 32 characters in length. It will generate a globally unique identifier (GUID) as a string and use that.

If the Event ID column is not a string greater than 32 characters, the application will not specify an event ID. If the database is not configured to generate a value, a null value will be stored. You can provide an event ID by placing this column in the attribute set used for the edit and provide a value, but this approach is not recommended because you would need to provide an event ID for each and every record, and the value must be unique.


If a null value is stored for an event ID, the RCE will not support editing the record.