Design rule purpose

This design rule allows Optioneer to deal with situations where the route evaluated is following a linear feature. This happens fairly often for onshore cables and pipelines - especially in densely populated areas, following roads might be the only way to go.

The trick is to be able to identify crossings with linear features that an option is crossing while keeping in mind that some features might be followed rather than crossed.

The centerline might cross the feature followed, but that shouldn't be counted as a crossing. If drawings were perfect, there would be no issue. In reality however, lines drawn intersect with 'followed' lines multiple times. This would lead Optioneer to counting additional crossings.

To address this, Optioneer detects if it follows a linear feature within a user-specified distance. If the majority of the feature falls within this distance, it will be ignored - any crossings with this feature are removed from the final count. If the feature isn't entirely within the distance, Optioneer will determine that a linear crossing is required.

How to configure

The configuration of this design rule is pretty simple. It uses the 'linear features' dataset and requires the user to specify 'distance within which Optioneer should consider a linear feature as followed'. Otherwise, the design rule will run automatically after the main Optioneer run is finished and refine the results.

Important notes

  1. This design rule might sometimes accidentally remove actual crossings. Sometimes linear features consist of 'sections' which might be very short - often happens when the position of utilities buried in a road is denoted with only the section that is in the road.

    If the entire crossed feature falls within the 'ignore crossings if linear feature is entirely within this range', the crossing will be ignored. There is a simple remedy, however - try to make the drawing of new alignment more precisely follow the centerline of the linear feature and decrease the 'ignore' range.

  2. If you actually do want to cross the linear feature that you also want to follow, such as 'getting a cable to the other side of the road', you have to take note of that manually. Optioneer can not be configured to support that as of yet.

Input / output summary

Input parameters

This design rule requires a 'linear features' dataset.

Name

Example value

Unit

Distance within which linear features are considered as followed

100

meters

Output parameters

This design rule doesn't output anything. If it works fine, the user will not see any results of its work (as it's mainly focused on removing excess crossings detected by Optioneer).

Did this answer your question?