ORD 2021 R2 Template Controls - Template preview vs. modelled result

This question is a result of attempting to model daylighted subbase (where possible) so we would be interested if others have found methods to accomplish this.

Background:

We are attempting to create a roadway rehab template that is full width to avoid having component quantity reports that need to be summed across a number of corridors. 

The template would have one full width subbase component that "daylights" at the end condition that is current (yes there are a few variables)

The problem is the template modeler and preview seems to provide a different result than what ends up in the model when applied.

We have been attempting to use tools we've seldomly utilized before such as a project to design component on a vector offset (at max cut depth say for concrete removal) that would daylight by terminating at the left or right end condition/component.  The template modeler allows the use of this tool and terminates at the end condition currently being used, and the preview looks correct.

However, when the template is applied to the project the projected design component finds the closest end condition component option regardless of if it's active at that location. (Always the closest)

Do the templates need to be simplified to only have one end condition option in order for these tools to work properly?

Why is there a disconnect between the template modeler's depicted result and the actual modeled result and how can we rectify this?

Is there any better training on using the template control options...I haven't found anything on these more advanced options.

Lots of questions...thanks for your help!!

  • To target another proposed design you may want to try the Corridor type Point Control option.  That will give you a list of points in an adjacent Corridor.  Another option is to use Target Alias to target specific linear named graphics.  Over the years, the "Project to Design" hasn't been all that useful for me.  Maybe lack of time spent testing its use... but typically resort to things I know have worked... "if it's not broke, don't fix it" mentality.  I'll also note that the Vector Offset functionality is hit and miss sometimes.  Try using the = sign out to the right of a point constraint's value field to specify a slope or distance of two totally separate points in the template.  This works wonders for points that tend to overlap or meet at zero.  A few tips there that you can use to aid your search for "better training".  Those topics should lend some additional options to things you'll need to accomplish... since there isn't really a one-size-fits-all approach.  

    ORD 2021 R1 (10.10), 2022 R1 (10.11.00.115), 2022 R3 (10.12.02.04) | MS 10.16

     Bentley Accredited Road Designer Bentley Accredited Road Modeler

     

      colliersengineering.com