Route dominance configuration

Available with Location Referencing license.

Route concurrency occurs when two or more pipeline routes share a section. When two or more routes share a section, this means that they share a centerline in the LRS Network.

Concurrent routes provide some challenges to an LRS Editor, since events reference sections rather than route designations. Events along a concurrent route section are associated with only one route, so route loading and route editing can impact associated events.

If a segment of a concurrent route is retired or realigned, the existing event records on that segment may be assigned to another concurrent route (depending on the event behavior assigned to the event layer). By configuring route dominance rules, we can provide a set of rules to determine which of these routes is the new parent route for an event after an edit has taken place.

The need to have events locate on a dominant route in a concurrent section is managed by applying rules that determine the dominant route in a section. Dominance rules are based on fields in an LRS Event table or feature class, or in the LRS Network itself, that can be compared to order concurrent routes.

In ArcGIS Pipeline Referencing, concurrent routes share the same centerline feature, but are modeled with different measures that belong to the route.

Route dominance scenario

The following scenario demonstrates the use of route dominance rules to find the dominant routes on concurrent sections.

The following table identifies the concurrent sections in the above diagram:

Section	Concurrent routes
1	R1, R2
2	R2, R3

The following table shows the route ID and route name for the concurrent routes in the above diagram.

Route ID	Route Name
{D9D2-}	R1
{E6M1-)	R2
{G3N4-)	R3

Note:

• Concurrent routes in a section share a SectionId in each concurrent group.
• The network feature class or any nonspanning line event that is registered to the Network can be used to calculate concurrencies.
• The exceptions can be listed separated by a comma.
• Multiple attribute fields can be used to create a rule.
• Multiple rules can be used to determine the dominance.

Here is the workflow for the application of rules:

In this example, two rules are used to find the dominant route:

Rule	Fields	Order Method	Order Type	Exceptions
Rule1	Route Name	Lesser	Alphanumeric	R3

The dominant route in a concurrent section gets the Dominant Flag value of 1, the non-dominant routes get a value of 0. The Dominant Error column has the following five potential values.

Dominant Error	Description
0	No error when calculating the dominant route in the concurrent section.
1	Two or more routes have the same attribute value for the concurrent section. The dominant route was randomly selected.
2	Null or no values were present for the attribute, or attributes, used to calculate the dominant route in the concurrent section.
3	Too many values were present for the attribute, or attributes, used to calculate the dominant route in the concurrent section.
4	One of two conditions are present in the concurrent section: the route is not calibrated in the concurrent section or the centerline that composes the concurrent section doesn't align with the geometry of the route.

Here is the result after calculating route dominance using the rule provided above:

Section ID	RouteName	Dominance Flag	Dominance Error	Details
1	R1	1	0	The Route Name value of this route is lesser than that of route Route2, so this route is the dominant route using Rule1.
1	R2	0	0
2	R2	0	0
3	R3	1	0	The Route Name value of this route is defined as an exception, so this route is the dominant route using Rule1.