The Pipeline Referencing 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 Pipeline Referencing sample data.

Yes. It is important to ensure that the virtualized environment meets the minimum system requirements needed by Pipeline Referencing. In the case of local virtualization, or running a virtual machine player on a local machine (not a cloud), it's important to note that the minimum system requirements are what the emulated environment needs to provide to Pipeline Referencing. This is in addition to the virtualization environment's minimum system requirements to support the virtualization software.

The storage model for organizations looking to migrate to Pipeline Referencing 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 Pipeline Referencing minimum schema for common centerline storage (two tables and two feature classes).

   For more information, see LRS data model.

2. Understand the data requirements for event data to map against a Pipeline Referencing LRS.

   For more information, see Create and modify LRS events.

3. Translate your LRS and centerline current 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 PolylineM feature class, there are scripts on the Pipeline Referencing community that can help with the migration.

   For more information, see Pipeline Referencing community.

4. Once the LRS data is migrated, configure the LRS.

   For more information, see LRS data model.

5. Decide which event tables or data will be modeled in the geodatabase under the management of Pipeline Referencing, migrate these tables into the geodatabase, then register them with the network they reference.

   For more information, see Create and modify LRS events..

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 Pipeline Referencing community.

For more information, see the Pipeline Referencing community.

There is a context menu option in the Catalog window in ArcMap on the ALRS node of the geodatabase. Click the command to upgrade the ALRS and upgrade your event tables to event feature classes. The operation can take several minutes.

If your ALRS was using a 10.2.2 or earlier version of Pipeline Referencing, you will be presented with the option to enable conflict prevention in the ALRS when you upgrade, which is disabled by default. For more information about conflict prevention, see Conflict prevention.

The system requirements for Pipeline Referencing for Server include the system requirements for ArcGIS Server; however, Pipeline Referencing for Server 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 Pipeline Referencing, 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.

For more information, see the ArcGIS for Server system requirements.

Yes, but you must have Pipeline Referencing for Server 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 Pipeline Referencing for Server installation directory for an example of how to build a model to incorporate the geoprocessing tools.

External events in Pipeline Referencing 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.

In addition, 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 Pipeline Referencing. 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 Pipeline Referencing. 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.

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 Pipeline Referencing for Server is installed on all machines participating in the cluster hosting the map service with linear referencing capability.
• Ensure that any Pipeline Referencing for Server licenses haven’t expired and that the ArcGIS Server licenses haven’t expired.
• Ensure that Pipeline Referencing for Server 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, Pipeline Referencing has a command in the Catalog window in ArcMap on the geodatabase for the LRS event node that is registered with Pipeline Referencing. Click Update Event Shapes to correct the shapes of the events.

For more information, see Updating event shapes.

If you accidentally edit and save changes on a route or set of routes in an LRS Network, the change can be repaired by using the Generate Routes geoprocessing tool, or by right-clicking the LRS Network in the geodatabase in ArcCatalog and in the Catalog window in ArcMap, then clicking Generate Routes.

For more information, see Generating routes.

There could be a number of causes:

• Ensure the web map is published as public on ArcGIS.com.
• Ensure the map service with linear referencing capability is running on ArcGIS Server.
• Ensure Pipeline Referencing for Server 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 feature service capability enabled.