Data

The pull-down menu looks like this:

• Design Standard

• External Data

• Terrain Setup

• Add Helpline

• Delete Helpline

• Add Active LP as Helpline

Design Standard

Use this function to set the following design standards for alignment design:

• The alignment design can be carried out based on User-Defined Minimum Values or Design Table.

  • Mark the desired radio button.

MOUS_ICO Toolbar: Design Standard

MOUS_ICO Menu: Data > Design Standard

The dialog box Design Standard will pop up.

User-defined minimum values

• You can opt to use either Radius or Length as a controlling factor for the curves of alignment (horizontal or vertical).

• Transition curves can be designed by any of the following methods:

  • Empirical Formulae

  • Parameter as input

  • Length as input

• In the case of empirical formulae, the transition curve length can be rounded to the specified nearest length.

• Different standards for horizontal and vertical can be defined.

The background of the cells in the input table (Input H or Input V) will turn red indicating that the radius/length is less than the design standard.

Curves inserted using the functions Min. Arc where Line-Line, Insert Arc, Inserts transition Curve(s), Missing Transition Curves, Insert Summit Curve, and Insert Sag Curve will be according to the parameters defined in this function.

Vertical Curves: Vertical curves (Summit or Sag) can also be designed using the K - Value.

Design Table

• Select the desired design table from the pull-down menu.

• Select design speed for the pull-down menu.

• Select AADT (Annual Average Daily Traffic) from the pull-down menu.

User-Defined Minimum Values

• Mark the radio button to enable.

• Horizontal Curves - Select either radius or length of curve as input value, use the check box Use Length.

• Transition Curves:

  • Select the desired method using the check box Use Empirical Formulae.

  • Select either Parameter or Length as input value using the check box Use Length.

  • Round off the transition curve length to the nearest length using check box Rounded transition curves.

• Vertical Curves:

  • Horizontal curves, summit curves, and sag curves need not have the same controlling factor.

  • For vertical geometry, you can use different values for Summit and Sag (Valley) curves.

• Define the minimum values at the respective fields.

External Data

Use this function to project external data to the vertical geometry of the alignment.

• Other alignment's vertical geometry can be projected on current vertical geometry in the vertical geometry’s constructional drawing.

• The vertical geometries, which are to be projected, should be saved in the database (Quadri Model) and also have a horizontal geometry (after all "floating" vertical geometry cannot be saved in the database).

• External alignments are calculated as polylines in the vertical geometry’s constructional drawing and can be used as construction lines.

Run the function from the following locations in the user interface Alignment Design:

MOUS_ICO Toolbar: External Data

MOUS_ICO Menu: Data > External Data

The dialog box External Data in Vertical Drawing will pop up which lists alignment and road surfaces available in the active database and road model.

Add

Select the alignment/road surface which is going to be projected on the current vertical geometry from the dialog box. Use Add several times if more than one alignment/road surface is to be added.

Remove/Remove All

Deletes marked alignments, road surfaces/deletes the whole alignment, road surface list.

Calculation step

Activate and determine the projection interval for the alignment. A dense calculation step creates better harmony with the theoretical vertical geometry.

From STA - To STA

It is possible to project only a part of the alignment or surface. The stations are the stationing for current alignment in Alignment Design. 

Enable External Alignments/Road Surfaces

Mark the check box for temporarily hiding the design. This option is to easily hide external alignments/road surfaces from the vertical drawing.

Terrain Setup

Use this function to select the source for presenting a longitudinal profile in the vertical drawing (vertical drawing for designing the profile of alignment).

1. Terrain model - longitudinal profile shall be retrieved from the active terrain model (Quadri Model).

   • Calculation settings for the longitudinal profile are to be defined.

   • The terrain model is the default source.

   • Automatically, the longitudinal profile in the vertical drawing will be updated when the terrain setting is modified.

   • Double click the field TERRAIN in the status bar of the user interface to toggle this feature (automatic update).

   • Alternatively, run the function Display.

2. Road model - longitudinal profile shall be presented as calculated in the road model.

   • Available only when the alignment is the active alignment of the active road model.

Tip: Finish the horizontal geometry of the alignment, save the alignment to the terrain model, start Road Model, define Alignment Properties, define terrain data settings (Subsurface and Terrain Boundaries) and return back to Alignment Design to design the vertical geometry of the alignment.

Run the function from the following locations in the user interface Alignment Design:

MOUS_ICO Toolbar: Terrain Setup

MOUS_ICO Menu: Data > Terrain Setup

The dialog box Terrain Setup will pop up.

Selecting terrain model as source display, the following elements are available in the active groups and feature codes:

• Crossing alignments - Alignments, Reference lines, Alignments as Surface Edges will also be shown in the longitudinal profile with respective text labels (alignment name, elevations, and chainage).

• Existing objects are presented with a circle of radius of 1.0m.

  • The center of the circle represents the crossing point with the alignment.

  • Existing objects are defined in terrain model.

• Crossing Wireframe models - Differentiate the wireframe models and the actual terrain surface beneath the wireframe models in the longitudinal profile presentation.

  • The surface of the wireframe model will be the terrain surface if the option is inactive.

  • Wireframe models are generated using the module Road Design and saved to the Quadri model with data type as Element.

• Terrain Model Properties (Groups, Feature Codes, and Profiles) - Can be used to administrate the data to be used/presented in the longitudinal profile.

  • Transverse Lines: The wireframe models generated using version 16.30 are included with road surface transverse lines (feature code 1234). The program searches the terrain data laterally along the alignment and these transverse lines along with longitudinal road surface edge line enable perfect representation of the wireframe models in longitudinal profile in all situations of alignment intersection with wireframe models (e.g., wireframe model intersecting perpendicularly with the design alignment).

• Calculation width left/right - Define the search width for the terrain data. The program searches for terrain points laterally from the alignment. Define search width.

• Terrain at left/right offset - Longitudinal profile at an offset from the alignment can also be presented (which gives an idea of terrain cross-section profile). Define offset value. The offset cannot be more than the Calculation Width.

• All points/Section Points/Breakpoints:

  • Section Points - Terrain calculations will be carried based on the calculation interval. Breakpoints shall not be considered.

  • Breakpoints - Terrain calculations will be carried at the breakpoints in the terrain model. Calculation interval shall not be considered.

  • All points - Both calculation interval and breakpoints shall be considered for terrain calculations.

Note: Settings for the grid, elevations, slope representation, and element signatures can be defined using Tools Options.

Next topic: Window