MXROAD
MXROAD
MXROAD
Introduction
DAA034400Q/0001
ii
Trademarks
Bentley, the B Bentley logo, and MicroStation are registered trademarks of
Bentley Systems, Incorporated or Bentley Software, Inc.
MX, the MX logo, Infrasoft, Arenium and the Arenium logo are registered
trademarks of Infrasoft.
Adobe, the Adobe logo, Acrobat, the Acrobat logo, Distiller, Exchange and
PostScript are trademarks of Adobe Systems Incorporated.
AutoCAD, and AutoCAD Map are registered trademarks of Autodesk, Inc.
HOOPS is a registered trademark of Tech Soft America.
OpenGL is a registered trademark of Silicon Graphics, Inc.
NetWare is a trademark of Novell, Inc.
Internet Explorer, MDAC, Windows, Windows NT, Windows 2000 and
Windows XP and True Type are registered trademarks of Microsoft
Corporation.
Copyright
DWGdirect
iii
iv
Table of Contents
MX Basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MX Basics Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
What is String Modelling? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MX Environment Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Common Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Windows Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
AutoCAD Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MicroStation Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The Applications Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Starting MX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Starting a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Typical Project Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating a survey model from imported data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Assigning model defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating a working display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Viewing the working display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Producing a design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Analysing the design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modifying the design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating drawings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Producing visualisations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Exporting data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
User Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11
11
12
18
111
115
116
122
128
130
131
133
133
135
136
137
138
140
142
143
144
145
146
146
149
152
MXROAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MXROAD Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Standard String Naming Convention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Options in MXROAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Surface Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Alignment Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Road Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Junction Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Pavement and Subgrade Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modifying the design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Project Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21
21
22
22
22
23
24
27
211
212
213
214
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MXROAD Intr oduction
i1
v
Table of Contents
vi
1
MX Basics
MX Basics Overview
This section gives an overview of MX and describes the basic principles of
operation. In particular, the concepts of string modelling are given together with
a description of how MX data may be manipulated from any of the three MX
environments; Windows, AutoCAD or MicroStation. An overview of each MX
option is also provided in a typical project sequence.
This section covers the following topics:
Starting MX
Starting a project
System administration
User support
11
MX Basics
What is String Modelling?
Survey
Alignment
Isopachyte
Triangulation
Design
Boundary
Sections
Drainage
Survey
Stations
Existing
Ground
Triangulation
Contours
Visualisation
12
MX Basics
What is String Modelling?
Strings and string links
All MX data is held as strings. A string is a series of points, each joined to its
predecessor and successor by a straight or curvefitted line. This is referred to
as a string link. Strings in MX have dimensions at each point, where a
dimension is simply a piece of data such as an X, Y or Z coordinate, or another
attribute such as the bearing at the point.
MX recognises many types of string:
Contour strings represent contours. The dimensions of each point are the
X and Y coordinates, so a contour string is a 2D string. The level of the
contour (the Z value) is only stored once because it is common to all string
points.
Feature strings define either linear ground features such as a ridge or the
base of a hill, or design features such as a carriageway edge or back of
verge. The dimensions of each point in the string are the X,Y and Z
coordinates of the point, so a feature string is a 3D string.
Point strings represent discrete items such as manholes and lamp columns.
A point string records the X,Y and Z coordinates of a set of like items, but
there is no physical continuity from item to item, ie, there is no string link.
MX processes these strings differently from other strings, particularly when
sectioning or triangulating. Point strings generally record detail in survey
models.
Master strings are used to represent road or railway alignment centre lines
and other master design lines. They are 6D strings. The first three
dimensions of each point in the string are the X,Y and Z coordinates,
followed by the chainage along the string, the bearing of the string at that
point, and the radius of curvature.
Volume strings generally contain earthwork volumes. These are 10D strings
and are used to store volumes calculated between successive sections. The
13
MX Basics
What is String Modelling?
first three dimensions of each point are the X,Y and Z coordinates,
followed by the chainage and the volume between the sections of two
specified models (usually ground and design models). The remaining
dimensions record volumes between the various strata, though since this
information is not always available, these dimensions are often zero.
All strings must have a fourcharacter name, but cannot include spaces or
special characters. ABCD, 1234, and XA45 are valid examples, though MX uses
a convention for names to indicate the type of the string. Some string types
such as cross section strings only require a single character MX automatically
allocates the remainder. These conventions are stored in feature sets, which are
described in more detail later.
Points
Within a string, a point is held as a set of dimensions that are associated with
each other. Each point has a set of coordinates and may also have other
information, for example, to define geometry. For example:
A point can have any number of dimensions between 2 and 15, depending on
the information needed to record in addition to its position. The following
illustration shows the dimensions of points on contour, ridge and road centre
line strings.
14
MX Basics
What is String Modelling?
Point numbers
Strings consist of sequences of points and, to address and retrieve individual
points, MX assigns each point a number relative to the start of the string. The
number always remains relative to the start of the string, so if a string has 24
points and point 12 is deleted, the old point 13 becomes point 12, and so on to
the last point.
Discontinuities
There are two types of discontinuity used in MX; a discontinuity between
points on a string, so creating a gap, and a discontinuity of bearing, which
indicates an instantaneous change of direction at a point.
Gaps
It may be that one or more gaps or discontinuities in a string are required, for
instance, to create a break or gate in a fence. In this case, MX creates a string as
a series of part sections of the same string, with a common name.
This technique avoids a profusion or duplication of strings and difficulties in
names.
before
CASI
after
CASI
CASI
gap
15
MX Basics
What is String Modelling?
Bearing discontinuities
These are used to mark a change in direction within a string, such as in estate
roads where kerbs often turn through 90 degrees.
Null levels
In horizontal alignment design, master alignment strings are created without
levels, and the levels are added later in vertical alignment design. Because, the
horizontal alignment is defined as a 6D master alignment string, MX assigns a
null level of 999.0 to every point on the string. In this way MX is able to
register the presence of a level while ignoring its value.
Null levels are also useful when recording feature strings for objects such as
hedges and fences, where levels are often not required. Again, MX
automatically assigns null levels to create a 3D string. Null levels are ignored
when creating a triangulation of a surface.
Feature sets
Feature sets are a means of grouping strings and identifying them with a
description. They are used throughout MX to make it easier for you to select
strings for subsequent operations. The strings belonging to a feature set are
specified using a partial string name.
As an example, a design feature set might include the following:
Feature
Partial Name
String Type
MC??
Master
Carriageway (Edge)
CE??
Feature
CT??
Feature
Shoulders (Edge)
ES??
Feature
Shoulders (Verge)
EV??
Feature
When a model is created, you can associate a feature set with the model using
Tools Model Defaults. This sets up a string naming convention for the model.
Different models can have different feature sets.
Default feature sets are provided with the software.
Style sets
A style set is a collection of styles which is used to draw a complete model or a
selected part of it. Different style sets are used to draw different types of
model. Many style sets are provided with MX and you may add your own style
sets if you wish.
16
MX Basics
What is String Modelling?
For example, there is a style set to draw a complete contour model with all
contours drawn as solid lines and curve fitted. Prominent contours are also
drawn for every 5 normal contours with the contour height embedded in the
contour line.
Another style set draws a plan view of a road design model with different line
styles for each feature type, the alignment with chainage annotation and the
vertical intersection points with their associated levels and gradients.
Style sets rely heavily on the string naming convention used for a model. For
this reason, they are closely associated with feature sets and by convention are
given the same name as the feature set with which they are associated.
Model defaults
You can specify which feature set and which style set to associate with a model
when you create it. You can also specify these defaults for an existing model
using Tools Model Defaults. Once these defaults have been set up, they are
automatically used for every relevant option, such as when you display or create
a string. Another way to assign model defaults is to click the right hand mouse
button in any model name field on a panel, or on the model name field of the
MX Toolbox.
You can also make these assignments automatically if you use a standard model
naming convention.
17
MX Basics
MX Environment Overview
MX Environment Overview
MX can run in any of three environments; Windows, AutoCAD and
MicroStation.
Windows
AutoCAD
MicroStation
Figure 4 MX Environments
When running under Windows, MX uses its own builtin frame and user
interface, presented in the usual way as a series of menus and panels. When
running in either of the other two CAD environments, similar options and
panels are available from an MX menu which is added to the AutoCAD or
MicroStation menu bar. In this way, when you are running in a CAD
environment, you have access to both the MX options and the standard CAD
options at the same time.
18
MX Basics
MX Environment Overview
In MX, there is a fundamental difference between a DPW and a DPF. A DPW
is an elastic area that grows to accommodate changes to the graphics it holds,
and so lets you create, assess, and edit model data to design the project. Once
the design is complete, paged drawings are needed, and it is at this point that a
DPF is created. This file also displays the MX graphics, but does not let you
edit the model data; the only operation available is the addition of lines and text
(enhancements).
19
MX Basics
MX Environment Overview
MX Data
Model file
DPW or DPF
MX Environment
Windows
User Interface
AutoCAD or MicroStation
DWG or DGN
CADonly layers/levels
MX layers/levels
User Interface
110
MX Basics
Common Components
Common Components
Many components of the MX interface are common to all environments, and
these are described in the following paragraphs.
The MX user interface is Windows compliant. This means that many of the
operations you have learned in other Windows software, such as Open, Save
and Browse are just as valid in MX. Help is obtained for an item on a panel by
clicking the question mark icon on the panel header and dragging it onto the
item in question. Whats This Help is then automatically displayed. You can also
press the F1 key.
The following sections do not provide all the answers about how to work with
MX, they do however provide enough information to begin with. Much
MXspecific information is provided as Help and there are many books written
about working in the Windows environment, although there is no substitute for
trying for yourself. Given that all data critical operations require confirmation
before they are carried out, and that Cancel provides an escape route,
experimentation will quickly make you proficient.
The mouse
The mouse is used to interact with the display, the data input panels, toolbars
and menus. Essentially, the lefthand mouse button selects the data under the
position of the cursor. For example if a string name is to be entered in a panel
field, move the cursor over the string on the display and click the lefthand
button.
You can also click and hold the lefthand button to expand menus, display lists,
increment values using spinners and so on. Simple clicking selects items from a
list.
The right hand mouse button presents available options. For example, if you
click in an XY field on a panel to provide focus, and then click the right hand
button the Point Selection Method (PSM) options appropriate to that field are
listed. Click the PSM you require to reposition the tick () marking the current
method.
Three types of cursor are used in MX to help you recognise the type of input
the program is expecting. By default, these are as follows:
the Windows cursor used in panels and for manipulating Windows.
the CAD cursor used when specifying CAD commands in
AutoCAD or MicroStation.
the MX cursor used when specifying MX options
111
MX Basics
Common Components
The keyboard
The keyboard is used for entering data into a field or working in the MX
Linemode panel. Shortcut keys are available, they are marked by _ and activated
by using ALT + the character key. For example, use ALT F to gain access to the
File menu.
Panels
There are many panels, each providing access to one or more MX options. You
will find that, in most cases, you can have more than one MX panel open at any
one time.
Some panels are arranged to appear in sequence, this sequence is known as a
Wizard. A Wizard is a simple means of guiding you through a complex process,
making sure that you provide all the information necessary to complete the
task.
The panel below is typical and shows the key elements, for which explanations
follow;
112
The panel header bar and the title Design a String: Intersection of Two Slopes
defines the function of the panel.
MX Basics
Common Components
2.
To find out more about any of the panel data requirements click the ?
button, place it on the text about which you need to know more, and click
again. Whats This help will be displayed. Whats This help tells you how to
complete the data field, and provides other essential information.
3.
Clicking this button will dismiss the panel without completing the function.
4.
Rather than using 3, use one of these three buttons; OK completes the
function with the data you have supplied and then dismisses the panel,
Apply completes the function with the data you have supplied and keeps
the panel displayed, Cancel dismisses the panel.
5.
These tabs allow you to get at all the data fields for the option. The left or
top tab contains all the mandatory fields, subsequent tabs and their fields
are optional.
6.
Radio buttons permit you to select one of a number of choices, the one
with the black centre is the one currently selected. On this particular panel
changing the option will grey out some of the other data fields as they are
not relevant for the selected option.
7.
Clicking the list button will give you a list of models, strings or options
from which to choose. As you run the cursor down the list, the highlight
moves, and clicking transfers your selection to the data field.
8.
Click and hold the up or down spinner to increment the value in the data
field.
9.
Click either the up or down arrow button to define the direction of the
slope.
10. Click in the check box to apply normal offset. This will change the text
beside the data field beneath, as the value to be entered into the field
changes.
11. The panel id. If ever you have a problem, and need more information than
the help gives, quoting the panel id to your MX support engineer will help
locate where you are and what you are trying to do.
MX menu bar
The standard MX menu or menu bar choices are File, View, Tools, Design,
Analysis, Modify, Display, Draw, Visualise, Report, AddIns and Help. You will
quickly learn which options are available from each of the pull down menus, but
a click on each will display the menu content.
In the CAD environments, MX appears as a separate entry on the AutoCAD or
MicroStation menu bar. Once a project is opened, the MX menu changes to
reveal all the MX options which are available to you. If you wish, you can
display the MX options as an alternative menu bar to the CAD menu bar by
selecting MX MX Menu.
You may find some options are greyed out in the menus. This may be because
they are not installed, you are not licenced to use them or they are not suitable
for use at that particular moment.
113
MX Basics
Common Components
Toolbars
There are a number of MX toolbars which provide shortcuts to the MX
options. You can display the toolbars so that they are docked to the frame, you
can move toolbars to different screen locations, or turn them off using the MX
option View Toolbars.
To dock or undock a toolbar, doubleclick the toolbar header.
The Plan with Tools toolbar is shown below. If an icon needs explanation, rest the
cursor on it to display its tool tip.
Message boxes
If you make a mistake or MX wants to communicate with you, a message box
will be displayed. You will have to acknowledge the message by clicking the OK
button.
Generally, if you have made a mistake, such as missing a mandatory data field,
the message will tell you whats wrong and how to correct the error. You will
have to click OK to dismiss the message before you can reapply focus to the
panel field requiring correction.
114
MX Basics
Windows Environment
Windows Environment
MX in Windows runs within a frame, but has other windows within the frame.
When you start a new project, two windows are displayed within the MX frame,
the display window and the output window. The output window is docked
within the frame, and can be detached and moved to any location.
115
MX Basics
AutoCAD Environment
AutoCAD Environment
MX runs within AutoCAD, so that when you start the program, the only
obvious changes from standard AutoCAD are that there is an extra MX menu
and two extra toolbars, the MX Controls toolbar at the foot of the graphics
window and the MX toolbar. The MX toolbar controls which model an object is
added to when it is drawn, and which type of feature is created. As with
standard AutoCAD, the display reflects the contents of the DWG file, but with
MX in AutoCAD, some or all of the layers in the DWG file contain data which
is linked to the MX model file via an MX drawing file. In this way, you can
create a DWG file containing both MX layers and layers which contain only
AutoCAD data.
116
MX Basics
AutoCAD Environment
MX strings in AutoCAD
You can use either MX options or AutoCAD commands to create and draw
MX model information such as strings in an AutoCAD DWG file. A string is a
sequence of points which represents a physical feature, such as a fence or a
hedge, or it can represent a nonphysical feature such as a contour. MX strings
which are related to each other are stored in models, for example, all strings
which represent a survey are stored in a survey model, and all strings which
represent a proposed design are stored in a design model. The set of features
used by a model is stored in a feature set and associated with the model.
MX model data is displayed on layers created with the same names as the
features or a group of features in the models associated feature set. These
layers are called MX layers, in that anything you draw on them can be linked to
the MX model file. You must associate a feature set with the model before
using the MX options to ensure that the strings are correctly displayed in their
relevant layers.
Using AutoCAD commands, when you create a polyline on an active MX layer,
MX in AutoCAD creates and displays an MX string custom object and a
corresponding string is also written to the MX model file. The string is
automatically given the next name in the feature set corresponding to the name
of the layer.
A custom object is an object such as an MX string which is not a native
AutoCAD object, but is created by another program (in this case, MX in
AutoCAD). When you modify or delete an MX string, both the MX string
custom object in the drawing and the string itself (in the MX model file) are
updated. Custom objects can also be exploded back to equivalent AutoCAD
objects and the corresponding data removed (optionally) from the model file.
You can use layers which are not MX layers for information which is not
required by MX, so you can work in AutoCAD (possibly constructing objects
or adding annotation) on a layer such as layer 0 and the data is not sent to the
MX model file.
The MX Toolbar
The MX toolbar gives you control of the creation of MX strings when using
AutoCAD commands. It has no effect when you use MX options.
For example, in MX in AutoCAD you can use most of the AutoCAD Draw and
Modify commands such as PLINE and MOVE to create and edit MX strings.
With no objects selected, the MX toolbar lets you know what will happen if you
create a new AutoCAD object. It tells you if you can successfully create MX
strings, in which MX model any new strings will be created, and the feature that
will be created.
117
MX Basics
AutoCAD Environment
Traffic Lights
Convert Object
Current Model
Current Feature
118
MX Basics
AutoCAD Environment
If you create an AutoCAD object, it will be created on the layer associated with
this feature.
To create a layer corresponding to a feature, just select the feature from the list.
If you select an object, the current feature list changes to reflect the feature of
the object you have selected.
You can change the feature type of an object by simply selecting the object and
then selecting a feature from the list.
Convert Object Button
If an amber traffic light is displayed, select the object to be converted to an MX
string, then click this button
. The object will be converted to the feature
corresponding to the layer that the object is on.
AutoConvert Mode
Autoconvert allows you to toggle between the automatic and manual modes of
creating MX strings from AutoCAD objects. The autoconvert toggle box is
located at the bottom of the MX frame.
With autoconvert on, if the current layer is an active MX layer, when you create
an AutoCAD object it is automatically converted to an MX string. The traffic
light is green in this case.
With autoconvert off, if the current layer is an active MX layer, when you
create an AutoCAD object it is not converted to an MX string. The traffic light
is amber in this case. To convert it manually, use the Convert Object icon.
A red traffic light indicates a plain AutoCAD layer or an inactive MX layer, ie, a
layer whose corresponding features do not exist in the current model.
The autoconvert setting has no effect if you modify an MX string; the MX
model will be automatically updated.
The autoconvert setting has no effect if you change the layer property of an
object to an active MX layer; the object is automatically converted to an MX
string.
Create New Feature
The Create New Feature button
allows you to add features to your feature set
and to create additional AutoCAD layers from the feature set descriptions. If
you use an MX option to display an MX model (for example, Display Plan
with Style Set), then you will find that the MX layers are automatically created for
you. You only need to use Create New Feature if you want to create a new MX
layer and feature for use with AutoCAD commands.
You can create a new layer from a feature in the current feature set just by
selecting the feature from the MX toolbar.
Any feature you create must have an entry in the corresponding style set so that
MX knows how to draw it. Use the Style Set Editor to modify the appropriate
style set.
119
MX Basics
AutoCAD Environment
Set Active Document
defines which drawing is the current MX
The Set Active Document button
drawing. In AutoCAD, you may have more than one drawing open at any one
time, but MX operates on one drawing only.
MX in AutoCAD configuration
The MX in AutoCAD Configuration panel is used to configure the way in
which MX interacts with AutoCAD. It is available from both the MX View
Configuration option and from the MX tab of AutoCAD Tools Options panel.
There are four tabs on the panel:
File handling
General
Data conversion
Warnings
120
MX Basics
AutoCAD Environment
General
These settings determine whether objects are displayed according to the MX
style set or the current AutoCAD line style and colour settings. There are
several other settings which relate to how MX data is treated following certain
AutoCAD operations.
Data conversion
The data conversion settings allow you to define how block attributes are
converted, the curve step tolerance, the model and paper space scale factors,
and the default autoconvert setting.
Warnings
You can choose to display warnings when strings are modified which indicate
the effects of certain operations. It is recommended that you leave MX in
AutoCAD warnings enabled until you are familiar with MX in AutoCAD.
MX Custom
These settings allow you to view line widths and enable AutoCAD geometry
snaps to MX string points. You can also set geometry snap tolerances to control
how the geometry of an object is reconstructed from an MX string, and define
how null levels are interpreted by AutoCAD.
121
MX Basics
MicroStation Environment
MicroStation Environment
The MicroStation environment
MX runs within MicroStation, so that when you start the program, the only
obvious changes from standard MicroStation are that there is an extra MX
menu, an extra panel called the MX Toolbox and an MX output window. The
MX Toolbox controls which model an element is added to when it is drawn. As
with standard MicroStation, the display reflects the contents of the DGN file,
but with MX in MicroStation, some or all of the levels in the DGN file contain
data which is linked to the MX model file via an MX drawing file. In this way,
you can create a DGN file containing both MX levels and levels which contain
only MicroStation data.
MX output, such as that from commands and reports, is displayed in the MX
output window.
122
MX Basics
MicroStation Environment
MX strings in MicroStation
You can use either MX options or MicroStation tools to create and draw MX
model information such as strings in a MicroStation DGN file. A string is a
sequence of points which represents a physical feature, such as a fence or a
hedge, or it can represent a nonphysical feature such as a contour. MX strings
which are related to each other are stored in models, for example, all strings
which represent a survey are stored in a survey model, and all strings which
represent a proposed design are stored in a design model. The set of features
used by a model is stored in a feature set and associated with the model.
MX model data is displayed on levels created with the same names as the
features or a group of features in the models associated feature set. These
levels are known as MX levels, because anything you draw on them can be
linked to the MX model file. You must associate a feature set with the model
before using the MX options to ensure that the strings are correctly displayed
on their relevant levels.
Using MicroStation tools, when you create a SmartLine on an active MX level,
MX in MicroStation also creates a corresponding string in the MX model file.
The string is automatically given the next name in the feature set corresponding
to the name of the level.
You can use levels which are not MX levels for information which is not
required by MX, so you can work in MicroStation (possibly constructing
elements or adding annotation) and the data is not sent to the MX model file.
123
MX Basics
MicroStation Environment
The MX Toolbox
The MX Toolbox gives you control of the creation of MX strings when using
MicroStation tools. It has no effect when you use MX options.
For example, in MX in MicroStation you can use many of the MicroStation
tools to create and edit MX strings.
With no elements selected, the MX Toolbox lets you know what will happen if
you create a new MicroStation element. It tells you if you can successfully
create MX strings, the MX model in which any new strings will be created, and
their feature type. It also gives you control over whether the elements you draw
are converted to strings automatically or whether the elements are to be
converted later.
Traffic Lights
Convert Element
Current Model
Current Feature
124
MX Basics
MicroStation Environment
To switch between automatic and manual conversion, you click the
autoconvert box on the MX Controls toolbar..
So, if you were to use a MicroStation tool on a level named Carriageway_Edge and
the current models feature set contained the feature description Carriageway
(Edge) then you would see a green (or amber) light and the resultant MX string
would have a string name beginning with CE?? if this were the partial string
name corresponding to the feature.
Show/Hide Current Model
The Show/Hide Current Model icons provide a quick way to hide or redisplay all
the drawn information from the model in the current model field. For example,
you can hide the ground model so that only the design model is displayed.
Current MX Model
The current MX model is the model in which MX strings will be created.
If you select an element, the current model is updated to reflect the model
containing the element you have selected.
Current Feature
The current feature is the feature type which is given to any MX string you
create using MicroStation tools. The field lists all the features in the feature set
associated with the current model.
If you create a MicroStation element, it will be created on the level associated
with this feature.
If you select an element, the current feature is updated to reflect the feature of
the element you have selected.
Convert Element
If an amber traffic light is displayed, select the element to be converted to an
MX string, then click this button
. The element will be converted to the
MX feature corresponding to the level that the element is on.
Create Feature Set
creates a feature set from all the named
The Create Feature Set button
MicroStation levels. This feature is useful if all you have is a MicroStation
drawing and you wish to create a feature set to match. In this way, you can
create a feature set having feature names derived from MicroStation level
names.
Any feature you create must have an entry in the corresponding style set so that
MX knows how to draw it.
125
MX Basics
MicroStation Environment
MX Control
Point Selection Methods
The Point Selection Method mode controls how points are selected from an
MX option on MX strings. As an alternative, you could use MicroStation
tentative points instead of MX Point Selection Methods.
AutoConvert Mode
Autoconvert allows you to toggle between the automatic and manual modes of
creating MX strings from MicroStation elements.
With autoconvert on, if the current level is an active MX level, when you create
a MicroStation element it is automatically converted to an MX string. The
traffic light is green in this case.
With autoconvert off, if the current level is an active MX level, when you
create a MicroStation element it is not converted to an MX string. The traffic
light is amber in this case. To convert it manually, use the Convert Element option.
A red traffic light indicates a standard MicroStation level (ie, a level having no
interaction with MX) or an inactive MX level, ie, a level whose corresponding
feature is not assigned to the current model.
The autoconvert setting has no effect if you modify an MX string; the MX
model will be automatically updated.
126
MX Basics
MicroStation Environment
In MX, there is a fundamental difference between a working display and a
drawing page. A working display, like a DGN, is an elastic area that grows to
accommodate changes to the graphics it holds. A working display lets you
create, assess, and edit model data to design the project. Once the design is
complete, paged drawings are needed, and it is at this point that a DPF is
created. This file also displays the MX graphics, but does not let you edit the
model data; the only operation available is the addition of lines and text
(enhancements). The DPF is therefore similar to a MicroStation sheet file.
Configuration
The Configuration panels are used to configure the way in which MX interacts
with MicroStation. A summary of the available preferences is given below, but
for full details, refer to the online help.
MX to MicroStation
Mappings define how fonts, line styles, macro line styles, line widths and
macro symbols are mapped.
Options you can choose to ignore line widths, and change the seed file
used to create a DGN from MX data. You can also define whether MX
standard point symbols are reproduced as points, and whether elements
defining the geometry of a string are created as individual vectors and arcs
or as complex chains.
MicroStation to MX
Options define whether level overrides are considered, the curve step
tolerance, the default MX drawing scale and whether construction lines are
stored in the MX model file. You can also define whether information is
deleted from the model file when it is erased from the drawing.
Convert elements defines which settings are used when drawing elements
(MX or MicroStation).
General
Mappings defines how colours and line styles are mapped and how
features are mapped to levels.
127
MX Basics
The Applications Toolbar
128
MX Basics
The Applications Toolbar
MXDRAW is used to produce final drawings from working drawings in a rapid
and efficient manner. You can create layouts for plans, profiles, composite plans
and profiles, and cross sections. In addition, because the final drawings are
created using views of a working drawing, any changes you make to the design
are automatically reflected in the final drawings so that they are always
uptodate and ready to plot. MXDRAW also provides a suite of geometric
annotation tools. You can annotate geometric elements such as arcs, transitions,
straights, grades and vertical curves by transferring information from a tool tip
directly to the drawing in a predefined style. Any annotation you add to the
drawing is dynamically updated if the design changes.
A link is provided to the Bentley Home Page on the Web.
Arenium is a technology which enables MX to be used for collaborative
engineering projects over a local or wide area network or the Internet. It
provides all the file management and communication facilities required for
multiple users to create and complete an MX project no matter where they are
located in the world. It also acts as a project control system as it records all
events and actions carried out on data.
For further information on Arenium, refer to the Arenium User Guide.
129
MX Basics
Starting MX
Starting MX
There are several ways of invoking MX. These are:
130
Once you have created and saved a project, you can doubleclick on the
project icon (.mmd) and the project will be opened automatically from
within MX (provided that this was the association you chose at installation
time). Alternatively, create a shortcut to this project and place it in a
convenient location, such as on your desktop.
MX Basics
Starting a Project
Starting a Project
Creating a new project
When you start MX, a startup panel is displayed. The startup panel gives you
quick access to the options on the initial File menu (Windows) or MX menu
(AutoCAD and MicroStation), as well as providing additional facilities for
accessing Help and your project settings.
131
MX Basics
Starting a Project
From either the startup panel or the File/MX menu, you can create a new
project, open an existing project, archive projects using the zip/unzip facility or
access the online Help. In addition, the most recently opened projects are
listed at the bottom of the menu.
MX uses projects to group information which relates to a particular design
scheme, such as the survey and design models, the drawings and the design
parameters used for the project.
To create a new project, click the New Project button on the Startup panel or
select New Project from the MX menu bar, then specify the name of your
project, its location and the location of the design parameters to be used for this
project. If the folder you specify does not already exist, it is created for you.
You are also given the opportunity to edit the default project settings as you
create the project. It is a good idea to look at these even if you do not think you
will want to change them, to familiarise yourself with the settings that are
available.
An empty model file is created in your project folder when you start a new
project. However, if MX finds that there is already a model file in the folder,
you can choose to keep it rather than overwrite it with an empty one. This gives
you the opportunity to move an existing model file in to place so you can
continue with a design.
if you are working on a project on the network, perhaps because several people
need access to the project, you can use the network project facility to copy the
project temporarily to your local disk, work on the project, then copy it back
again when you have finished.
You should only have one project in a folder.
You should not create project folders within the MX program structure, ie,
C:\Program Files\mfw.
132
MX Basics
Typical Project Sequence
NTF
Draw
Alignment
Report
Design
Perspective
Modify
Visualisation
DXF
MIFILE
Plan with Style Set
SURVEY
Plan with Tools
Sections
VOLUMES
GENIO
DXF
Analysis
Plot
IMAGE
Import
GENIO
SETOUT
Display
Design
Output
Export
133
MX Basics
Creating a survey model from imported data
The data describing the survey model can be input to MX in any of the
following formats:
MX Input
MX GENIO
MX Survey
General ASCII
MicroStation DGN
AutoCAD DXF / DWG
Ordnance Survey NTF (UK only)
Softdesk Alignment and DTM
Autodesk LDDT
Eagle Point Triangulation
LandXML
134
MX Basics
Assigning model defaults
To import data in ASCII file format, select File Input for any of the MX
formats (eg, GENIO) or File Import for the external formats. If the imported
file contains drawing information, the survey model will be created and drawn
on the screen; otherwise you will need to create a plan working display. See
Creating a working display for details.
If you already have a model file and wish to use the models in MX, you should
exit MX, copy the model file into your project folder and then restart MX.
To create a new, empty model, use Modify Edit Models Create Model.
135
MX Basics
Creating a working display
136
MX Basics
Viewing the working display
137
MX Basics
Producing a design
MX Toolbar (AutoCAD) or MX Toolbox (MicroStation) gives you control of the
creation of MX strings when using CAD commands. It has no effect when you
use MX options. For example, in MX in MicroStation you can use most of the
MicroStation placement, manipulation and modification tools to create and edit
MX strings.
Configuration is used to configure the way in which MX interacts with AutoCAD
or MicroStation.
You can also correct any discrepancies you find in the model using the Report
and Modify options.
Producing a design
With the survey model in place, you can now begin to create your design. The
design options are located on the Design menu:
138
MX Basics
Producing a design
Alignment is used to create the master string on which the rest of your design is
based; typically, this would be a highway or railway centre line or equivalent.
Firstly, in Alignment, you create your alignment horizontally using any of the
available methods; Element, Intersection Point (IP) or Spline. The Element
method allows you to construct an alignment from a series of elements, either
straights or circular arcs, connected by transition curves as required. The IP
method produces the same end result but allows you to construct the alignment
by entering a series of intersection points. The lines joining these points are
tangential to the curves which connect the straight elements. Transitions can
also be included if required. Finally, the Spline method allows you to specify a
series of points through which a cubic spline curve is fitted.
In all three methods, design and display parameters govern the properties of the
curves and how they are displayed on the screen.
Once the horizontal design is in place, you can do the vertical design, ie, add
levels to the alignment. Again, three methods are available to you, and to assist
you in specifying the levels, a profile of the ground from the survey model is
displayed so you can see where to position the alignment.
When the alignment is completed, two strings are created in your design model;
the master string and its associated geometry string which describes the
geometry of the alignment.
In addition to smooth alignments, nontangential alignments can be created for
the design of car parks, house pads etc.
Design a String options are used to derive additional strings from a master string;
typically, for a highway project, these would be strings such as carriageway edge
or hard shoulder strings. The different options allow you to specify different
information to create the strings, for example, you can specify a horizontal and
a vertical offset from the master string, or a horizontal offset and a crossfall.
Feature sets are particularly useful here as you can select the type of feature you
want (eg, shoulder) and the next available string name is automatically assigned.
Amend a String options are similar to those described above, except that they
amend existing strings rather than create new ones.
The Earthworks Wizard is used to create earthworks strings, ie, strings which
define the intersection between your design and the ground. The earthwork
design relies on the specification of earthwork styles, together with any
alternative strategies to be used when certain criteria are met. These strategies
determine the shape of the earthworks slope in particular situations.
To make the procedure as simple as possible, the Wizard has access to a library
of earthwork styles such as simple slope and slope/berm combination styles,
which can be used immediately. Additionally, you can create your own custom
earthworks styles specific to the current design or your national design rules.
These custom earthwork styles can be saved in your own library for future use.
Once created, the earthworks strings may be drawn with tadpole annotation or
with slope signature strings.
139
MX Basics
Analysing the design
MXDRAINAGE creates a drainage network from manhole positions you
specify by linking them with pipes. You can place manholes individually or
offset them from an existing string. Once the manholes have been linked,
gullies can also be added. Data from the drainage network can be exchanged
between MX and an external program which analyses the data and calculates
pipe sizes and levels according to the layout of the network and the hydraulic
constraints. Total and impervious subcatchment areas can also be calculated
for each pipe in the network.
Drainage proximity checking searches for a clash between manholes and
selected strings. If the distance between the manhole and the string is less than
a specified value the clash position is displayed on screen with a warning, and an
alternative position is offered.
140
MX Basics
Analysing the design
Section is used to create cross sections from a string, and long sections along a
string or a straight line. Both types of section are useful for checking the quality
of a design, and cross sections can also be used to calculate volumes. The
sections created are displayed in a separate viewer which can be docked to the
MX frame. In the viewer, you can add many types of annotation and inspect the
design for any errors or weaknesses. At any time, you can create a working
drawing of the sections you are viewing.
Contour generates height contours from a triangulation. The contours are
categorised as either index contours or normal contours, where index contours
are used to indicate a significant height interval, for example, an index contour
can be generated for every five normal contours.
Generate ridge, valley and flow lines creates ridge and valley strings from which flow
lines can be generated to work out surface water runoff.
The Area options calculate the plan or surface area of a model. You can define
the part of the model whose area is required either by boundary strings or by
means of two strings limited in extent by normals to a reference string.
Volume is used to calculate volumes from either triangulated surfaces or
sections.
Surface Checker is used to check a surface created from surveyed data once it has
been input to MX. It can be used to check any surface in applications such as
landfill and quarrying to identify incorrect or incomplete data. This includes null
levels, zero levels, single point strings, high points, low points, coincident points
and intersection points. The results may be output graphically or as a report.
Surface Analysis is a Wizard which simplifies the analysis processes and displays
the results in graphical form. You can perform analyses to show levels, slopes or
aspect bands, or show all slopes which are less than a specified gradient. You
can also display flat spots and flow arrows. The Wizard also handles sectioning
and triangulation automatically.
Volumetric Analysis is a Wizard for calculating cut and fill areas and volumes,
either between two surfaces, or between a surface and a plane. It has many
potential uses in civil engineering, from the analysis of linear schemes such as
roads and railways, through to quarrying and dredging works. Comparing two
surfaces could be used to analyse the difference between the existing ground
and a pad for a building, or the bottom of a layer of contaminated material.
Comparing a surface with a plane could be used to model navigation channels
(where the plane could be the mean low water level), or to model retaining
structures such as reservoir dams.
Crossfall Checker displays a graphical analysis of the superelevation applied to a
carriageway. The superelevation can be displayed using either drop/rise or
percentage diagrams. A superelevation report is then displayed in a separate
window, which you can save or print.
Visibility checks and dynamically displays the analysis of through visibility,
visibility at junctions and radial visibility. The analysis can then be output as a
report. You can then save or print the report.
141
MX Basics
Modifying the design
Design Checker checks the design statistics of a specified master string (and
associated carriageway edges, if applicable) and outputs them as a report in a
separate window. You can then save or print the report.
Edit Models allows you to create, rename or delete a model as well as providing
trimming, security options, and automated generation of composite models.
Trimming allows you to trim a model to a boundary, while the security options
allow you to provide readonly access to a model.
Edit Strings and Edit Points give you complete control over the strings in your
model. Although you normally design your main strings using the Design
options, you can also create strings with Modify, and you can also edit any part of
a string and the points within a string. You can also automatically generate
boundary strings around a model.
Copy, Move and the Copy Transformation Wizard may be used to copy an entire
model, copy or move information from one model to another, or copy or move
strings within a model. Model information can also be transformed by defining
shift, rotation, scaling, tilt or mirror parameters.
Explorer is a project management tool which allows you to manage the model
file and other information in your project. You use Explorer in the same way as
you would use Windows or Internet Explorer, except that it works on MX files
rather than all files on your disk.
142
MX Basics
Creating drawings
Creating drawings
So far, you have seen how to use Display to draw your model information on the
screen without dividing it up into pages. To create a series of drawing pages
from a working display, you use the Draw options.
143
MX Basics
Producing visualisations
The Final Drawings option uses components of MXDRAW to produce final
drawings from a working drawing in a rapid and efficient manner. You can
create layouts for plans, profiles, composite plans and profiles, and cross
sections. In addition, because the final drawings are created using views of a
working drawing, any changes you make to the design are automatically
reflected in the final drawings so that they are always uptodate and ready to
plot.
Final Drawings also provides a suite of geometric annotation tools. You can
annotate geometric elements such as arcs, transitions, straights, grades and
vertical curves by transferring information from a tool tip directly to the
drawing in a predefined style. Any annotation you add to the drawing is
dynamically updated if the design changes.
You can specify the content of each view with a high degree of flexibility. MX
objects provide access to model information, while MX style sets and layering
techniques define the way in which the information is presented.
Producing visualisations
Visualisation is useful for checking the accuracy of a model at any stage in a
design (provided levels have been assigned to the strings in the model), and also
for presentation of a design when it is complete. The visualisation options are:
Simple Perspective creates a wire frame view from anywhere in a model. You
specify the eye and target points, and whether or not you wish hidden lines to
be removed. The resulting perspective view can be enhanced in the same way as
any other drawing.
For a greater degree of realism, you can use 3D View and Flythrough to produce
full coloured textured renderings of your design. You can also create and save
animated 3D views as AVI files. Alternatively, you can use any of the AutoCAD
or MicroStation 3D viewing and rendering capabilities at any time.
144
MX Basics
Creating reports
Creating reports
Alignment Reports
The alignment report options allow you to create customised reports of
horizontal alignment, vertical alignment and setting out data which can be
output to the screen or to a file. You can also use cut and paste techniques to
copy the data to a spreadsheet.
145
MX Basics
Exporting data
Horizontal Alignment Report provides details of the horizontal geometry of the
alignment, including details of arcs, transitions and straights such as arc length,
radius and intersection point coordinates.
Vertical Alignment Report provide details of the vertical geometry of the
alignment, including details of curves, transitions and grades such as curve
length, radius, chainages and levels.
Many other types of reports can be produced in MX which are written to the
output window. You can then copy and paste these reports using standard
techniques in to any suitable Windows application.
Exporting data
Model and drawing data can be exported in several forms from MX. This allows
your design to be transferred easily between different sites, different computer
types and other drawing packages. Supported file formats are:
MX GENIO
MX MIFILE
DXF
AddIns
You use the AddIn Manager to add or remove applications so that you can
invoke them from within MX for your convenience. For example, you can add
Windows Explorer to the AddIn menu using the AddIn Manager.
AddIn programs (previously known as Bonus Tools) are available to all Bentley
SELECT users from the Bentley website at www.Bentley.com.
Help
The Help menu gives access to the online help, tutorials, Bentley Web Site
information and information about the version of MX currently installed on
your machine.
146
MX Basics
Help
Help About MX gives information about the licence you are using, and the
currently installed version of MX. It also provides access to the security report
which defines the applications that you are authorised to use.
For further details about the online help and tutorials, refer to Using the Online
Help and Tutorials.
Overview
The MX Online Documentation suite links together all the documentation for
the different MX products. You can access the help, tutorials and various online
documents in Adobe PDF format from the relevant Contents page for each
product.
MX Help
The MX Help system dynamically updates depending upon the MX
environment you are using. It contains information on the following:
Linemode contains complete Help for Linemode. The help has enhanced
navigation functions available at the bottom of the frame allowing selection
of help by Major and/or Minor option number.
147
MX Basics
Help
Accessing help and documentation
Help and documentation can be accessed in a variety of ways as follows:
By pressing the F1 key on the current panel (ie, the panel with the highlit
bar at the top). This method provides incontext Help by taking you
directly to the topic associated with the panel.
By clicking on the Help (?) button at the top right of any panel to obtain
Whats This? Help. When you click the button, the cursor changes to a ?
which you can then place and click over any piece of text on the panel for
which you require Help.
Tutorials
The MX tutorials provide stepbystep instructions about how to use many of
the options in MX. They are written in a typical project sequence. You can
access them from the relevant Contents page in the MX Online Documentation
suite.
Online Manuals
These are provided in Adobe PDF format for online viewing and printing. You
can access them from the relevant Contents page in the MX Online
Documentation suite.
148
MX Basics
System Administration
System Administration
Backing up your projects
You should take backup copies of all your project files at regular intervals. You
should also back up any style sets, styles, macro symbols, or macro lines which
you have created. Note that these may not be contained in your project folder;
for example, you may have created a new style set and stored it in the
\??_styles folder in the MXRENEW software structure. It is important that
you organise your work in such a way that you know where all your files are
located so you can back them up.
The options Zip Project and Unzip Project, which are available from the File menu,
create a compressed backup file of an entire project in WinZip compatible
format. See the online help for further details.
It is also a good idea to take a backup copy of your system files (ie, the
MXRENEW software structure) at less frequent intervals.
You should not create any project folders under the MXRENEW software
structure.
2.
Browse the folders to get to your project folder, for example, c:\mx tutorial.
3.
Locate the file model.fil, and click on it with the right mouse button.
149
MX Basics
System Administration
4.
5.
A new file is created, called Copy of model.fil. This is a copy of the MX model file.
Note that there is no problem doing this even though MX is still running,
although you should not have any MX panels open.
1.
From the File pull down, select File Management Report Model file
The results are displayed in the output window; you will probably need to scroll
up a few lines to see it all. It lists the number of records in the model file which
are actually filled with data, out of the total number that have been used, and
also the total space that will be available after compression.
Before you compress the model file, there are two options that you can use to
check that it is OK.
1.
On the Report Model File panel, click Check Model Pointers, followed by Apply.
MX looks through the model file, and checks it to ensure that each of the
models is arranged correctly inside the model file. The results of this are
displayed in the output window again with a summary at the end, where the text
should say END OF POINTER CHECK 0 POINTER ERROR(S)
FOUND, which indicates that the model file is OK. If there is a number here
other than zero, it means that there is a problem with one or more of the
models on the model file, which must be investigated before continuing with
any MX work. Scrolling up the list in the output window will show you which
model(s) and string(s) are affected. These need to be deleted using the MX
options on the Modify pull down, until running this report indicates that there
are no pointer errors.
150
1.
2.
3.
Browse the folders to get back to your project folder, and check the size of
the model file model.fil.
MX Basics
System Administration
4.
Ensure that the Status bar shows there to be at least three times the size of
the model file available as free disk space.
If there is not, you will have to create extra free space on the hard disk before
you can safely compress the model file. Once you have done this:
1.
2.
3.
Click OK.
The option may take a few moments to run, then a note in the output window,
if visible, should say W127 Model file stored & initialissed. If this message is not
given, you should contact your System Administrator, or your MX supplier for
further advice.
Disk maintenance
In order to maintain optimum performance from MXRENEW, you should
manually delete files from your temporary directory (normally C:\temp) to
ensure that it does not become full (you can use Windows Explorer to do this).
You should also empty the Recycle Bin on your desktop at regular intervals.
Select the Recycle Bin, click the right hand mouse button and select Empty
Recycle Bin. Alternatively, doubleclick the Recycle Bin icon and check the
contents first.
151
MX Basics
User Support
User Support
Europe, Middle East, and Africa
For support on this release, please email the Bentley Helpdesk at:
support@Bentley.nl
Alternatively, phone the number below:
(+31) 023 5560555
Elsewhere
For worldwide local contacts, see the contacts list on our Web site at
http://www.bentley.com to contact your local MX supplier.
152
2
MXROAD
MXROAD Overview
MXROAD is an application constructed of a number of modules to permit the
efficient design of a road scheme from the input of the existing ground data
through to the production of drawings and reports defining the scheme.
Throughout the design, tools are available to permit analysis or visualisation of
the design so that you can check and confirm each step of the design process.
The modules that make up MXROAD are:
Quick Alignment
RuleBased Superelevation
Junction Design
Report Generator
21
MXROAD
Standard String Naming Convention
the specific road feature (second character, eg, C for centre line)
the associated master alignment which defines the string group (third
character, eg, 0 for the first alignment)
the side of the master alignment on which the string was created (fourth
character, eg, 0 for the left hand side, I for the right hand side)
Options in MXROAD
This section describes the options which are available from MXROAD. All the
options in MXROAD can be found within the standard menus, such as Design
and Edit. They are also available from the MXROAD toolbar (accessed from
the Applications toolbar) for your convenience to help you with the project
sequence.
For all the options in MXROAD, you can find more detailed information in the
online help.
Import
Although not strictly an MXROAD option, File Import allows you to import
existing ground data on which the road design scheme is to be implemented.
The data may be imported in one of several formats:
22
MXROAD
Surface Analysis
MX GENIO (*.txt)
LandXML
In all cases, a model is created from the ground data. You should assign a
default feature set and style set immediately to the new ground model which
you can then draw using the option Display Plan with Style Set if required.
If you have MX in Windows, but not MX in MicroStation or MX in AutoCAD,
you can still import data from a MicroStation DGN or AutoCAD DWG file.
You can either convert the file to DXF format or use the MX data translator
program MX Change.
NTF file format is used by the United Kingdom Ordnance Survey for map
data.
Surface Analysis
This option lets you perform analyses of the surface on which the design is to
be built. This is essential to confirm that the imported data is correct and
contains no errors. Typically the analysis will highlight errors in level and will
also provide a graphical representation of the existing surface; both of which
can provide essential information for your design.
There are nine different types of analysis each taking you through the necessary
steps in a minimum amount of time. The options are:
Display contours
Level bands
Slope bands
Aspect bands
Flat spots
Steep slopes
Flow arrows
Display triangulation
23
MXROAD
Alignment Design
In MX in Windows, you can also highlight any errors in level by colour filling
the triangulation and illuminating the view from the Zoom toolbar.
Alignment Design
The Alignment Design options enable you to create the alignment for the road
design. You may use either the Quick Alignment options Horizontal Design and
Vertical Profile, or Alignment which gives greater flexibility but may take longer to
learn.
Whichever method is used, the end result is the same, a complete alignment
defined both horizontally and vertically. The alignment is converted to a master
string which is generally used as the centre line along which a carriageway and
other features can be designed.
24
MXROAD
Alignment Design
Quick Alignment
Horizontal Design
Horizontal Design enables you to create horizontal alignments using dynamic
Intersection Point (IP) placement and manipulation.
The following layout options are available:
edit curves
25
MXROAD
Alignment Design
alter the position of a finished alignment
undo up to 20 previous actions.
You can also obtain a printed report of the horizontal alignment.
Vertical Profile
Vertical Profile enables you to create vertical alignments using dynamic IP
placement and manipulation. The backcloth is a vertical profile of an existing
horizontal alignment extracted from the triangulation model of the ground.
The following options are available:
Add IPs
Move IPs
Remove IPs
Insert IPs
Lock IPs
Delete profile
Calculate overall cut and fill
Calculate grade and radius
View details of a curve
Change the vertical exaggeration
Amend design parameters
Set the curve data
Change the view of the display area.
There is also a table editor which you can use instead of dynamic placement to
specify values such as gradient and curve radius using the keyboard.
Alignment
Alignment is used to design alignments for roads and other engineering features.
An alignment describes the basic horizontal and vertical position of a design
from which all other surface features are generated. For a road, the alignment
usually represents the centre line, but may represent a channel or any other
convenient feature.
Alignments are created in two stages: first the horizontal design, then the
vertical design.
For both horizontal and vertical design, there are three design methods; the
Element method, the Intersection Point (IP) method and the Spline method.
The Element method allows you to construct an alignment from a series of
elements, either straights or circular arcs, connected by transition curves as
required. The IP method produces the same end result but allows you to
construct the alignment by entering a series of intersection points. The lines
joining these points are tangential to the curves which connect the straight
elements. Transitions can also be included if required. Finally, the Spline
method allows you to specify a series of points through which a cubic spline
curve is fitted.
26
MXROAD
Road Design
Complete alignments are converted to master strings for use with the other
MXROAD options.
Road Design
Road Design is a series of options that take you through the process of
designing a road from an existing master string. It consists of a number of
stages; Carriageways, Rulebased Superelevation, Road Widening, Shoulder Design and
Kerbs, Verges and Footways.
Carriageways
Carriageways creates a road surface using either a standard template or one you
have customised yourself. The templates contain all the details of the road
surface, including the carriageway width and the crossfall or vertical offset to
the carriageway edge strings. There are standard templates for many different
types of carriageway, including single roads, with a single lane either side, and
dual carriageways with two or three lanes.
The process you follow through the Road Design Carriageways Wizard is as
follows:
Specify the model and master string along which you wish to create the
carriageway. This will generally be the model containing the alignment
created using one of the Alignment options.
27
MXROAD
Road Design
Repeat the operation with another template, if the start and end of the
carriageway was not the whole extent of the alignment.
You should design the carriageway along your alignment in one session of the
Road Design Wizard.
If you change templates along the master string, you can choose to join the
equivalent strings in the two portions of carriageway automatically. The
carriageway strings are joined either linearly or with a reverse curve, both
horizontally and vertically. If you include a central reserve in one carriageway
but not the other, you may need to modify the centre line level string to include
a vertical step at the correct position.
If the results are not what you want, you can remove the carriageway strings
using Modify Design Edit Strings Delete String Groups. This option allows you
to select all the carriageway strings and delete them. Recreating the carriageway
using a modified template is quickly achieved.
Rulebased Superelevation
Rulebased Superelevation provides a simple approach to the application of
superelevation to a road. The superelevation applied is based on parameters
specified in design rules files, which conform to either a local or national
standard.
The process is defined by the following steps:
Specify the master string of the road to which you wish to add
superelevation.
Specify the design rules and design speed to be used. The design rules will
determine whether single or dual carriageway parameters are to be used.
The calculations are then made and a summary of the results is displayed.
Before you apply the superelevation, you can confirm that the superelevation is
correct or amend the calculated values if required. Following the review
process, the superelevation is applied to the carriageway.
28
MXROAD
Road Design
Road Widening
The Road Widening Wizard provides a simple approach to the process of road
widening, and can be used to create extra lanes, laybys, parking areas or
junction widening.
The process is defined by the following steps:
Select the type of taper to apply, either linear (as illustrated below) or
reverse curve.
after
before
Length of
taper
Road centre line
You can retain the original carriageway string along the widening, or you can
delete it.
Shoulder Design
Shoulder Design is used to create shoulders from the edge of the carriageway.
Several different methods are available to apply the crossfall across the
shoulder, and the method can be changed automatically when certain criteria
are met.
The standard shoulder methods are:
Fixed crossfall specify the crossfall from the carriageway edge to the
shoulder.
29
MXROAD
Road Design
Follow carriageway crossfall use the same crossfall for the shoulder as
that used for the carriageway.
There are other methods which you can specify for the outside curve of a
shoulder. These include:
Maximum shoulder break uses the standard shoulder settings until the
carriageway is superelevated and a maximum crossfall difference between
the carriageway and shoulder is reached. At this point, the shoulder
crossfall is set to a specified value or to match the carriageway crossfall,
depending on the option selected. The changeover length between the
maximum crossfall difference and the point at which the new values are in
force may be specified, and may also be offset along the carriageway from
the point of maximum crossfall difference.
Maximum algebraic difference (part width) for this method, the shoulder
is split in two widthways by a new string and crossfall is applied to the
outer portion in the same way as for the maximum algebraic difference
method. For the inner portion, ie, between the carriageway edge and the
new string, the standard shoulder crossfall is applied at the point of
maximum algebraic distance, which gradually changes to the carriageway
crossfall at the point where full superelevation begins. It is also over this
distance that the new string is created.
210
MXROAD
Junction Design
Junction Design
The Junction Design options are used to create a T junction between a through
road and an intersecting road.
Earthworks Wizard
The Earthworks Wizard is a standard MX option which is used to design an
earthworks structure between two models, the design model containing the new
design surface and the existing ground model. The earthwork design relies on
the specification of an earthwork style, together with a number of strategies to
be used when specified criteria are met.
211
MXROAD
Pavement and Subgrade Design
The Wizard guides you through the process of specifying models, section sets,
earthwork styles and strategies, the criteria to trigger the strategies and so on,
until you apply your earthwork design requirement to the models.
The process is defined by the following steps:
Assign styles to the four style definition areas (left and right cut and fill).
To make the procedure as simple as possible, the Wizard has access to a library
of earthwork styles such as simple slope and slope/berm combinations. You
can apply different earthwork styles and strategies to lengths of the road by
specifying the start and end points. Alternatively, you can create your own
custom earthworks styles specific to the current design or your national design
rules. These custom earthwork styles can then be saved in your own library for
future use.
212
existing cross sections for every point on the road centre line (ie, the
master string) for both the ground model and the design model. For
example, if you have generated cross sections at tangent points on the
master string in your design model, these must also exist in the ground
model.
MXROAD
Modifying the design
Figure 37 Modify
213
MXROAD
Project Sequence
Edit Strings and Edit Points
You can use the standard MX Edit options during all stages of an engineering
design as follows:
for the existing surface to correct erroneous levels and the ground
position of points and strings.
Project Sequence
The project sequence is critical in MXROAD. For example, you cannot use road
widening if the carriageway has not been created, and, if you wish to
superelevate the carriageway, you must do this before creating a junction.
The MXROAD project sequence is shown below:
214
Horizontal Alignment
Vertical Alignment
Carriageways
Rulebased Superelevation
MXROAD
Project Sequence
Road Widening
Create Fillet
Regrade Junction
Tidy Junction
Shoulder Design
Earthworks Wizard
Not all steps need to be carried out each time; for details of which options are
mandatory and which are optional at any particular stage, refer to the online
help.
215
MXROAD
Project Sequence
216
Index
Numbers
3D View, 144
3D View and Flythrough, 144
A
AddIn menu, 146
Alignment, creating, 139
Alignment design, 24
Alignment reports, 145
Analysis menu, 140
Analysis options, 140
Applications toolbar, 128
Area calculation, 141
C
Carriageways option, 27
Configuration
MX in AutoCAD, 120
MX in MicroStation, 127
Contours, generating, 141
Cross sections
creating, 141
editing, 214
Crossfall Checker, 141
D
Data interoperability, 18
Deleting strings, 214
Design Checker, 142
Design menu, 138
Design options, 138
Disk maintenance, 151
Disontinuities. See Gaps
Display, Menu, 136
G
Gaps, 15
GENIO format, 134, 23
exporting, 146
H
Help desk, 152
Help menu, 146
Horizontal design, 25
I
Import option, 22
Importing data, 133
J
Junction design, 211
MXROAD Intr oduction
i1
Index
K
Kerbs, verges and footways option, 210
L
LandXML, 134
Long sections, creating, 141
M
Menu, Display, 136
Menu bar, 113
Model defaults, 135
how to assign, 17
Model file, 12
Models, editing, 142
Modify menu, 142
Modify options, 142
Mouse, use of buttons, 111
MX Basics, 11
MX Controls toolbar, 126
MX environments, Windows, 115
MX toolbar, 117
MX Toolbox, 124
MXDRAINAGE, 128
MXDRAW, 129
MXRAIL, 128
MXRENEW, 128
MXROAD, 128
MXSITE, 128
MXURBAN, 128
N
Null levels, 16
O
Ordnance Survey NTF format, importing, 134
Output window, 114
Overview, 21
P
Panels, components of, 112
i2
Quick alignment, 24
R
Raster backcloth, 136
Report menu, 145
Report options, 145
Road design options, 27
Road widening option, 29
Rulebased superelevation, 28
S
Security Report, 147
Shoulder design option, 29
Shoulder rollover, 210
SNC, 22
Softdesk format, importing, 134
Standard string naming convention, 17, 22
Starting MX, 130
Startup panel, 131
Strings
editing, 142
types of, 13
Style set
definition of, 16
using to create a working display, 136
Support, 152
Surface analysis, 141
of the ground, 23
T
Toolbars, 114
Tools menu, 135
Triangulation, creating, 140
Index
U
User support, 152
V
Vertical design, 26
View menu, 137
Visibility, 141
Visualise menu, 144
W
Web page address, 152
Widening, 29
Working display, creating, 136
Working drawings, 143
i3
Index
i4