Trimble Business Center

 View Only
Expand all | Collapse all

Corridor Instructions - Weird Connections at the start of cut slopes when part of conditional statement

  • 1.  Corridor Instructions - Weird Connections at the start of cut slopes when part of conditional statement

    Posted 02-11-2019 12:27
      |   view attached

    I am getting weird results for connections at the beginning of cut side slope instructions when they are part of conditional statements. The instructions seem to be connecting to the centerline at the previous whole interval instead of perpendicular to the centerline. I just deleted the conditional statement and the cut slope commands performed as they should.

     

    I am using a 5ft interval for my corridor.

     

    Data for Investigating:

    View Filter: Design

    Corrdior: Hetnar's Way Typical

     

     

    Is there a way to control this or is this a bug?

     

     

    Attachment(s)



  • 2.  Re: Corridor Instructions - Weird Connections at the start of cut slopes when part of conditional statement

    Posted 02-11-2019 12:51

    Video for further explanation.

     



  • 3.  Re: Corridor Instructions - Weird Connections at the start of cut slopes when part of conditional statement

    Posted 02-12-2019 06:16

    If you look at the Template Editor in this area I can almost guarantee that the model is correct, it is just the Surface Model output which is incorrect Pat - this is because the Surface Model is created using Surface Model Rules based on data that is interpolated from the template Model. Where you get Hard Stops of elements at a specific station, and then you get Interval Locations e.g. every 5' you will see this sometimes in the Corridor Surface Model. If you eg reduce the interval you will see it improves the situation (never entirely fixes it), 

     

    I have some requests in the system for this as I agree that it is an issue that the Surface which is what you will ultimately use to run the machines etc. is important, and while it is an interpolated model from the template Model, these locations where things start and stop or where you define Tables need to be generated more accurately. If you drop a copy template into the model at that station you will likely see further improvements because the Template Drops get forced into the model as a priority.

     

    If I see these types of issue that the Surface Model looks wrong, I will just create a Reference Template Drop at the station where I want to see the change and you should see that it fixes the problem. Currently Tables have a tolerance of I believe 0.33' longitudinally and they do not 100% honor the Table Contents if there are lateral, vertical or slope steps in the tables that are closer than that tolerance of 0.33' (that creates issues in e.g. MSE Wall or Gabian Wall footings and that is where I see it most and that is where using additional Template Drops at the start and end of the steps gets me what I need.

     

    I have development looking at this currently

     

    Hope this helps

     

    Alan



  • 4.  Re: Corridor Instructions - Weird Connections at the start of cut slopes when part of conditional statement

    Posted 02-12-2019 07:13

    Alan,

     

    That was exactly it. I dropped some copied templates like you recommended and that fixed the issue. Thanks for the tip.

     

    * It looked like it fixed the issue in plan view but not in 3D.

     

     

    Spoke prematurely. It tighten up where the surface was attaching to but I am still getting a bad connection even with the addition of a reference template.

     

     

    The difference between the copied reference drop and the start of the template instructions is .007. Just enough to cause some chaos. 

     

     

     



  • 5.  Re: Corridor Instructions - Weird Connections at the start of cut slopes when part of conditional statement

    Posted 02-12-2019 09:50

    I did some file management on my instruction set and cut down on some superfluous nodes (I initially added unnecessary conditional statements. Correct but unnecessary.). Once I got rid of these everything worked like a charm. Maybe something was nested that was causing issues. 

     

    I have a few more road way projects that I will be working on this week and will make sure to try the template drop trick if a run into issues.