Configure continuous measure networks and events to update with an engineering network

Location Referencing ライセンスで利用可能です。

As you configure your LRS and load data for use in ArcGIS Pipeline Referencing, you can maintain a network and events with both engineering and continuous measures.

Pipeline Referencing supports the configuration of an engineering stationing network, called a line network, and a continuous measure network based on the line network, called a derived network, in the same LRS. When both the line and derived networks are configured, you can make your edits to the line network and apply edits to the derived network using the Generate Routes geoprocessing tool.

With this configuration, route edits made on the line network are applied automatically to the derived network. Configuring your continuous measure network as a derived network is optional; the two networks can be registered and managed separately in the LRS.

The following image shows the ArcGIS Pro Catalog pane view of P_ContinuousNetwork, a derived network in the LRS, and P_EngineeringNetwork, a line network in the LRS:

Events can also be configured to store the route and measure for both the line and derived networks. When event behaviors are applied to events, their shapes and measures are updated. Use the Derive Event Measures geoprocessing tool to update derived network measures on the event. This allows you to see the measures for both networks on a single event record.

Using derived event measures allows the storage of a single event for both line and derived networks. This reduces the number of records and the amount of data being managed in your database. Configuring derived measures on events is optional. A derived network can be configured in an LRS without derived measures being stored on the events.

The following image shows the Coating event attribute table with both line and derived network measures configured:

Configure a continuous (derived) network that can be updated based on edits to a stationing (line) network

A derived network needs to be configured from a line network. When route edits occur in the line network, the edits can be applied to the derived network so the shapes, dates, and measures changes remain in alignment between the two networks.

メモ:

The derived network is based on the line network, which must be present before configuring the derived network with the LRS.

1. Follow the steps outlined in Create and modify an LRS Network to create and configure a line network in your LRS.
2. Check the Include Fields to Support Lines check box in either the Create LRS Network or Create LRS Network From Existing Dataset geoprocessing tool.

   A line network must include the following fields:

   • Line ID Field
   • Line Name Field
   • Line Order Field
   • Measure Unit

3. Check the Derive From Line Network check box in either the Create LRS Network or Create LRS Network From Existing Dataset geoprocessing tool.

   A derived network must be created from an existing line network.

4. Once the event is created, add the required fields to support the derived route ID, derived measures, and derived route name if configured to the event feature class.
5. Choose the line network from which the network will be derived by clicking the Line Network Name drop-down arrow.

   

The network feature class is mapped to the selected fields.

メモ:

Route edits can only be applied to the line network in an LRS when a derived network is configured.

Configure events to store both engineering (line) and continuous (derived) measures

Events that are configured to store both engineering and continuous measures need to be registered with the engineering (line) network. Because route edits are applied to the line network before the derived network is updated, the events need to be registered with the line network so their event behaviors are applied before the derived measures are updated.

1. Configure a line and derived network in your LRS using the steps in the previous section.
2. Create your event.

   See Create and modify LRS Events for steps.

3. Once the event is created, add the required fields to support the derived route ID, derived measures, and derived route name if configured to the event feature class.
4. Once the fields are correctly added to the event, run the Enable Derived Measure Fields geoprocessing tool to configure those fields on the event.

Update a derived (continuous) network and events

A derived network and derived event measures are updated using geoprocessing tools. These tools can be run one by one or combined using the Apply Event Behaviors geoprocessing tool in a model or Python script. The model or script can be executed on demand or at scheduled intervals to apply event behaviors based on route edits, and to update the derived network and derived event measures.

The workflow below outlines the order tools must be run to update a derived network and derived events.

1. Complete any route edits in the line network.
2. Execute the Apply Event Behaviors geoprocessing tool and choose the line network for the Input Route Features parameter.

   This updates the event shapes and line network measures.

3. Execute the Generate Routes geoprocessing tool and choose the derived network for the Input Route Features parameter.

   This updates the derived network shapes and measures.

4. Execute the Derive Event Measures geoprocessing tool and choose the line network for the Input Route Features parameter.

   You can choose to run the tool on all or some events registered to the line network. This will update the derived network measures on the events.

   Once the tools are executed, the line and derived networks along with events and their measures remain updated and in sync as route edits are made.