My template is set up with priorities to solve for several cut and fill conditions. The guardrail end condition has the highest numerical priority and solved last. Naturally, this creates "pockets" of the guardrail shoulder condition along a corridor - ultimately leading to the use of an end condition exception or multiple parametric constraints to model the end condition appropriately.
Image showing the “pocket” as explained above:
The question: Why is a lower priority linear feature still showing in my model both visually and mathematically?
CASE 1: End condition exception is used to force guardrail shoulder conditions.
CASE 2: Multiple parametric constraints are used for shallow fill conditions.
What would be the best way to keep the linear feature from showing up or more critically, having only one linear feature definition for construction limits?
My first thought is adding display rules to the other components conditional to if the guardrail condition is applied; but would cause an additional parametric constraint-switch to force the shallow fill condition. I realize that there are probably several ways to go about achieving this but I would really appreciate any guidance or experience.
Thank you
What version are you running?
ORD - 2019 Release 2 Update 7 - 10.07.01.32
Another example of this occurrence.
Image showing the use of a corridor clipping shape and resulting linear feature that remains. occurrence was not consistent with other clipped areas.
I'm assuming my order of operations might be causing the problem.