Top Level:

ITL: Wall Templates

KHA-SD Help Group Policy SD Config Client Management CAD Info & Help Projects Site Map

Peer Level: Up ITL: Widening ITL: Wall Templates ITL: "Phantom" Pivot Points

Child Level:
Up

Templates - Ramps: Search and Build

There are a wide variety of ways to build walls in the model.  The list below starts with the

Method Pros Cons
Quick and Dirty Walls using GLF each wall really fast each step is manual for each ramp
Wall Template (no "branching") easy to make templates a template for each variation, user must determine which template to use where
Wall Template ("branching") less "thinking" during revisions longer set up time: must program the logic within the template up-front
Totally Automatic fastest, no thinking, just push have to set up horizontal wall locations, no thinking
     

I've set up a "mostly automatic" template in the main template library: "_end_conditions/wall_at_feature" which can be a included in a "mainline" or ramp template or pushed along a graphic (an existing hinge point, for example).

Here’s what it is designed for:

If you have intermittent cut or fill retaining walls along a corridor you can push this template the whole way without having to know where the retaining walls begin or end or whether they are cut or fill. 

You can  incorporate this solution into a mainline/ramp template by replacing the 2:1 Cut and Fill components with this template.

 

The what make this template work is the "wall_check" End Condition component which searches for any feature in the active surface with a style of "struc_Wall_horizontal".

Other methods require setting up specific horizontal alignments or named features, which requires a lot more data management and requires using Roadway Designer rather than the simple "Apply Template" command.

Pre-requisites

You must have a surface with the horizontal locations of the walls (vertical is not necessary).  The Feature Styles of the wall features must be "struc_Walls_horizontal." 

Note: The template looks for that Style (feature names are not important, nor are the location, sequence or continuity of the features).

How it Works

During a template drop, the template

checks for a feature style called “struc_Wall_horizontal” in the active surface.

If it finds one,

it first places a wall perch point at a cut slope of 2:1 at the horizontal wall feature location

it then tries to tie in upwards to the "existing...." dtm (not the <Active> dtm).

If it fails it

 it first places a wall perch point at a fill slope of -2:1 at the horizontal wall feature location

it then tries to tie in downwards to the "existing...." dtm (not the <Active> dtm).

If no wall feature is found it directly targets the "exist..." surface at 2:1 (cut or fill).

Creating the "wall horizontals" surface

How do you get a surface with “struc_Wall_horizontal” features in it?

  1. Get the latest horizontal graphics of the retaining walls (no vertical info is necessary).
  2. InRoads>Import>Surface>>From Graphics
  3. Key in a new surface name (make is clear that it’s a surface for Wall Horizontals).
  4. Use a fence, select “struc_Wall_horizontal” as the Feature Style (this is available in the master .xin).
  5. You’re good to go.

 

 

The Beauty of Cross Section Wall Components

The cut and fill wall components are superfluous outside of the beauty they add to the cross sections.  The have two points that tie into the "work" components (cut_wall and fill_wall).  Feel free to make even more beautiful walls by adding points and moving them around as necessary.  Note: the underground features should have a feature style like "struc_Wall_subgrade" so that they are easily filtered out of displays.

Also, it's relatively simple to have the wall foundations scale automatically with the height of the wall, so if that's a need on your sheets, keep that in mind.

Quirks and Caveats

The template searches the Active Surface for the feature styles.  If you have a "wall horizontals" surface and it's not Active, the wall search will fail and the template will use the typical 2:1 solution.

Because the Active Surface has to be the "wall horizontals" surface, the target surface for the wall daylights had to be specified by Name rather than <Active>.  If your walls don't intersect it's because the end condition components are targeting the <Active>.  This is rectified, by selecting the existing surface in the Component target list.

If you're using InRoads Apply Template the "Design Surface" (the destination or recipient surface) field tends to default to the active surface.  You'll dump your new stuff into the "wall horizontals" surface accidentally.

If you're editing it will be much easier visually if you edit the "wall_check" point and set the offset to something like 8 ft.  It's currently set very tight because the template only works if the wall horizontal is to the outside of the check point (hence the visually ugly tightness).

 

 

Site Map       Contact Jeff Martin with comments/concerns.        KHA San Diego Transportation Group.                    this page last edited: 2008-01-17 16:26