OpenRoads Tip: 5 Things to Know When Working with Superelevations

Published on September 3, 2015

Written by:  Bob Mecham

Working with superelevations in the OpenRoads SS4 release is much different from previous versions of InRoads or GEOPAK. Here are 5 things to know when when you start defining your first superelevations.

1. Superelevation has to be built in its own CAD file

Once the 2D file is created it is referenced and associated with the corridor.

2. Superelevation in a Color Coded Display

After you have created your superelevation sections and lanes you will want to view your superelevation in the MicroStation view.

openroads superelevation color coded display

  • In the View Attributes dialog toggle ON Fill

3. Superelevation Flag

For each template point that you wish to be controlled by superelevation, you need to toggle ON the Superelevation Flag.  Allowing OpenRoads to control the point even during horizontal transitions.

openroads superelevation flag

4. Adjust Superelevation in the view using Textual Manipulators

By selecting the calculated superelevation graphics in the MicroStation view; the Textual Manipulators will appear allowing you to modify either the station value or the superelevation value.

openroads superelevation textual manipulators

5. Place Temporary Dimension Lines to help evaluate your superelevation

In cross section view, consider placing a temporary dimension line to evaluate lane slope and width.

openroads superelevation place temporary dimension lines


Corridor Section Views                        OpenRoads Maintenance Release                             Feature Definition
Civil 3D Tip: Adding Sample Lines in          MS Tip: What’s New in V8i                   OpenRoads Tip:  Change Profile Symbology
the Middle of Existing Sample Group          (SELECTseries 3)Update 2                 of your Terrain



Tags: , ,
Like this article? Share it!

Leave a Comment

XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>

Privacy Policy