Deprecated: Methods with the same name as their class will not be constructors in a future version of PHP; About_Widget has a deprecated constructor in /var/www/vhosts/lmnarchitects.com/httpdocs/tech-studio/wp-content/themes/nrgblog/framework/include/custom-widgets.php on line 275
Generative Components Speed Ramps | LMNts

Generative Components Speed Ramps

In urban contexts, parking often means parking ramps.  While not the most glamorous part of a building, parking speed-ramps are one of the most common.  Even on a reasonably rectilinear project, parking speed ramps almost always have inner-slopes and outer-slopes, sometimes banking downward or upward as the case may be.  Figuring out the slope is not mathematically difficult, but modeling is tedious…and re-modeling is a waste of time.  This is a perfect opportunity to do some scripting.

Before you begin, understand that this only does the modeling work for you, not the work of figuring out your rise, run, slopes, etc.  You will need to know these before you start.  All the units are in decimal feet.  As you play around with the transactions, you may want to make rise a function of run, or lock the turning radius…feel free to modify the code as you see fit.  These are just a starting point.

This speed-ramp component kit was built in Generative Components V8i.  This gives you control over inner, outer and cross slopes, width, depth, rise, run, curb and wall dimensions.  It generates well-formed “SmartSolids” (though you can feed it parameters that will break the “water-tightness” of the model).  The transactions are broken down into 3 files.  Though it is possible to do this with one transaction  (a straight line being a degree-zero curve), this was a quick-and-dirty approach that was necessitated by a deadline.  However, breaking it down  creates simple, easy-to-understand transactions without burdening the user too much.  If you are constructing complex speed-ramp structures, you will want to link these together into multiple components.  Since each scenario is different, the kit-of-parts approach seems wise.

The simplest transaction is the straight ramp.  However, this build allows you to control both the inner and the outer slopes, allowing you to create “kinked” ramps – sloping in two directions – that can meet up with sloping slabs.  This is not a frequent condition, but it does sometimes happen.  Otherwise, the parameters are fairly straightforward.

Transaction: [download id=”5″]

The second transaction creates a simple quarter-turn.  You can control the turn-radius (often dictated by code), the inner-slope, the width and the rise and run.  It may be useful to introduce a Z-axis offset somewhere in the definition to control uneven banking, but in the name of simplicity, the outer-slope is a function of the run.

Transaction: [download id=”4″]

The third transaction is much like the second, but creates a right-angled outside corner (instead of a curve).  This is a condition that happens most often when the ramp meets another load-bearing structure, like a structural foundation wall.  The parameters for this transaction are similar to the SimpleTurn example above.

Transaction: [download id=”3″]

Obligatory disclaimer: the author does not guarantee that these parametric models are bug-free or that they will solve all of your problems.  If you find bugs or have suggestions for improvements, please let me know.

Category

0 comments