PDMS11 5-Manual-11 2

PDMS DRAFT
User Guide
Part 2: Drawing Annotation
Version 11.5
pdms1151/man11/doc2
issue 140403
PLEASE NOTE:
AVEVA Solutions has a policy of continuing product development: therefore, the
information contained in this document may be subject to change without notice.
AVEVA SOLUTIONS MAKES NO WARRANTY OF ANY KIND WITH REGARD TO
THIS DOCUMENT, INCLUDING BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE.
While every effort has been made to verify the accuracy of this document, AVEVA
Solutions shall not be liable for errors contained herein or direct, indirect, special,
incidental or consequential damages in connection with the furnishing, performance or
use of this material.
This manual provides documentation relating to products to which you may not have
access or which may not be licensed to you. For further information on which Products
are licensed to you please refer to your licence conditions.
 Copyright 1991 through 2003 AVEVA Solutions Limited

All rights reserved. No part of this document may be reproduced, stored in a retrieval
system or transmitted, in any form or by any means, electronic, mechanical,
photocopying, recording or otherwise, without prior written permission of AVEVA
Solutions.
The software programs described in this document are confidential information and
proprietary products of AVEVA Solutions or its licensors.
For details of AVEVA's worldwide sales and support offices, see our website at
http://www.aveva.com
AVEVA Solutions Ltd, High Cross, Madingley Road, Cambridge CB3 0HB, UK
Revision History
Date Version Notes

March 2003 11.5 Manual divided into two Parts:
Part 1: Basic Drawing Creation & Output
Part 2: Drawing Annotation (this manual)
VANTAGE PDMS DRAFT User Guide

Version 11.5
Contents
1 Introducing PDMS DRAFT ............................................................................ 1-1

1.1 What does DRAFT do? ...............................................................................................1-1
1.2 The DRAFT Database ................................................................................................1-1
1.3 Who Should Read This Manual .................................................................................1-2
1.4 Organisation of the DRAFT User Guide ...................................................................1-2
1.5 Organisation of this User Guide................................................................................1-2
2 Introduction to Annotation ........................................................................... 2-1
2.1 Layers..........................................................................................................................2-2
2.2 Autoblanking ..............................................................................................................2-2
3 Dimensioning................................................................................................. 3-1
3.1 Introduction ................................................................................................................3-1
3.2 Dimension Element Types .........................................................................................3-2
3.3 Layer Attributes for Dimensioning ...........................................................................3-2
3.3.1 Linear Dimensions .......................................................................................3-2
3.3.2 Radial Dimensions........................................................................................3-2
3.4 Linear Dimensions .....................................................................................................3-3
3.4.1 Linear Dimensions and How to Create Them.............................................3-3
3.4.2 Multi-valued Dimensions .............................................................................3-7
3.4.3 Principal Attributes of Linear Dimensions ...............................................3-10
3.4.4 Detail Attributes of Linear Dimensions ....................................................3-14
3.5 Radial Dimensions ...................................................................................................3-24
3.5.1 Creating Radial Dimensions ......................................................................3-27
3.5.2 Appearance of Radial Dimensions - Specific Attributes...........................3-27
3.5.3 Appearance of Radial Dimensions - General Attributes ..........................3-35
3.5.4 Appearance of Radial Dimensions - Ancillary Graphics Attributes ........3-35
3.5.5 Creating Radial Dimensions using the Cursor .........................................3-36
3.5.6 Modifying Radial Dimensions through Graphical Interaction ................3-36
3.6 Pitch Circle Dimensions...........................................................................................3-37
3.6.1 Creating Pitch Circle Dimensions .............................................................3-38
3.7 Angular Dimensions.................................................................................................3-40
3.7.1 Angular Dimensions and How to Create Them ........................................3-40
3.7.2 Principal Attributes of Angular Dimensions ............................................3-43
3.7.3 Detail Attributes of Angular Dimensions .................................................3-44
3.8 Identifying Dimensions ............................................................................................3-44
3.9 Suppressing the Display of Dimension and Projection Lines ................................3-44
3.10 Dimensioning Skewed Pipe in Isometric Views......................................................3-45
3.11 Updating Dimensions...............................................................................................3-45
VANTAGE PDMS DRAFT User Guide Contents-i

Version 11.5
Contents
4 Labelling ........................................................................................................ 4-1

4.1 Introduction................................................................................................................ 4-1
4.2 Creating and Manipulating Labels........................................................................... 4-3
4.2.1 Creating Labels and Label Text.................................................................. 4-3
4.2.2 Labelling Views............................................................................................ 4-5
4.2.3 Positioning and Orienting Labels ............................................................... 4-5
4.2.4 Label Frame Manipulation.......................................................................... 4-7
4.2.5 Hiding Labels ............................................................................................... 4-7
4.2.6 Autoblanking................................................................................................ 4-8
4.2.7 Label Text Manipulation ............................................................................. 4-8
4.2.8 Leader Lines............................................................................................... 4-11
4.2.9 Varying the Leader Line Connection Point .............................................. 4-14
4.2.10 Leader Line Gaps....................................................................................... 4-15
4.2.11 Modifying Labels through Graphical Interaction .................................... 4-16
4.3 Label Templates And Special Labels...................................................................... 4-16
4.3.1 Introduction................................................................................................ 4-16
4.3.2 Text Label Templates and Special Labels ................................................ 4-16
4.3.3 SLAB Leaderline Connection Points ........................................................ 4-19
4.3.4 Special Label Templates and Special Labels............................................ 4-20
4.3.5 Scaling and Mirroring Special Labels....................................................... 4-21
4.4 Autotagging .............................................................................................................. 4-22
4.4.1 Introduction................................................................................................ 4-22
4.4.2 Defining the Autotagging Hierarchy and Rules....................................... 4-24
4.4.3 Controlling Label Appearance and Elements to be Tagged .................... 4-24
4.4.4 Querying ..................................................................................................... 4-25
4.4.5 Label Generation ....................................................................................... 4-25
4.4.6 Tracking the Autotagging Process ............................................................ 4-27
4.4.7 Label Editing and Copying ........................................................................ 4-27
4.4.8 Tag Rule Editing ........................................................................................ 4-28
4.4.9 DATAL Transfer ........................................................................................ 4-28
4.4.10 Schedule Generation.................................................................................. 4-28
4.5 Intelligent Label Placement .................................................................................... 4-29
5 Intelligent Text............................................................................................... 5-1
5.1 Introduction................................................................................................................ 5-1
5.2 Code Words................................................................................................................. 5-1
5.3 Accessing Data from the Design or Catalogue Databases....................................... 5-2
5.3.1 P-point data .................................................................................................. 5-3
5.3.2 P-line Data ................................................................................................... 5-3
5.3.3 Accessing Data in Catalogue Datasets ....................................................... 5-5
5.4 Accessing Data from the DRAFT Database.............................................................. 5-5
5.5 Accessing Dimensioning Data ................................................................................... 5-6
5.6 Accessing UDA Data.................................................................................................. 5-7
5.7 Accessing Administrative Data ................................................................................. 5-7
5.8 Codewords with Special Functions ........................................................................... 5-8
5.8.1 The Template Codeword.............................................................................. 5-8
5.8.2 The Tab Generator Codeword ..................................................................... 5-8
5.8.3 New Line Generator..................................................................................... 5-9
Contents-ii VANTAGE PDMS DRAFT User Guide

Version 11.5
Contents
5.8.4 # Character ...................................................................................................5-9

5.8.5 Underlining...................................................................................................5-9
5.9 Substrings .................................................................................................................5-10
5.9.1 String Definition by Characters ................................................................5-10
5.9.2 Substring Definition by Parts ....................................................................5-10
5.10 Array Indexing..........................................................................................................5-11
5.11 Transforming Position/Direction Data ....................................................................5-12
5.12 Extracting Attribute Data from any Specified Element.........................................5-13
5.13 Distance, Position and Bore Data Output...............................................................5-15
5.13.1 General........................................................................................................5-15
5.13.2 Mixed Units within Intelligent Text Strings ............................................5-15
5.13.3 Controlling the Precision of the Generated Output..................................5-16
5.14 Customising Error Text ...........................................................................................5-17
5.15 Intelligent Text Syntax - Summary.........................................................................5-17
5.16 Notes .........................................................................................................................5-19
6 Miscellaneous Text Facilities ....................................................................... 6-1
6.1 Text Fonts ...................................................................................................................6-1
6.2 Multiple Fonts within Text Strings...........................................................................6-2
6.3 Alternative Character Set..........................................................................................6-2
6.4 Editing Text ................................................................................................................6-4
6.5 Text Quality ................................................................................................................6-5
6.6 Character Height........................................................................................................6-5
7 Annotating Structural Elements in DRAFT ................................................. 7-1
7.1 Basic Annotation ........................................................................................................7-1
7.2 3D Position from a P-line ...........................................................................................7-1
7.3 3D Direction from a P-line .........................................................................................7-2
7.4 Angle from a P-line.....................................................................................................7-3
7.5 P-line Attributes .........................................................................................................7-3
7.5.1 P-line Design Element..................................................................................7-4
7.5.2 P-line Name ..................................................................................................7-4
7.5.3 P-line Distance..............................................................................................7-4
7.5.4 P-line Direction.............................................................................................7-5
7.5.5 P-line Position...............................................................................................7-5
7.5.6 P-line Angle...................................................................................................7-5
7.6 Representation of SCTN Ends ...................................................................................7-5
8 Underlays and Overlays................................................................................ 8-1
8.1 Introduction ................................................................................................................8-1
8.2 Using Plotfiles ............................................................................................................8-1
8.3 Database Elements for Underlays and Overlays......................................................8-3
9 2D Drafting ..................................................................................................... 9-1
9.1 Introduction ................................................................................................................9-1
9.2 Where 2D Drafting is Used........................................................................................9-1
9.2.1 Backing and Overlay Sheets ........................................................................9-1
9.2.2 Symbol Templates ........................................................................................9-3
VANTAGE PDMS DRAFT User Guide Contents-iii

Version 11.5
Contents
9.3 The Drafting Elements .............................................................................................. 9-4

9.4 2D Drafting Primitives .............................................................................................. 9-5
9.4.1 Creating and Manipulating Drafting Primitives - Common Operations .. 9-6
9.4.2 Re-use of Drafting Points .......................................................................... 9-15
9.4.3 Visibility of Drafting Primitives................................................................ 9-16
9.4.4 Enhancing Drafting Primitives ................................................................. 9-16
9.4.5 Creating and Manipulating Drafting Primitives - Specific Operations .. 9-17
9.5 Text Strings.............................................................................................................. 9-35
9.5.1 Entering Text from DRAFT....................................................................... 9-35
9.5.2 Displaying Text from a File on the Drawing ............................................ 9-35
10 ISODRAFT Symbols.................................................................................... 10-1
10.1 Creating ISODRAFT Symbol Templates................................................................ 10-1
10.1.1 Attributes of ISODRAFT Symbol Templates ........................................... 10-2
10.1.2 Wildcards in SKEYs................................................................................... 10-3
10.1.3 Example...................................................................................................... 10-3
10.2 Outputting ISODRAFT Symbols............................................................................. 10-4
10.3 Querying ISODRAFT Symbol Templates............................................................... 10-4
11 Point and Line Construction ...................................................................... 11-1
11.1 Introduction.............................................................................................................. 11-1
11.2 X, Y Filtering............................................................................................................ 11-2
11.3 Construction of 3D Positions ................................................................................... 11-4
11.4 A Midpoint Position ................................................................................................. 11-4
11.4.1 The Midpoint of Two Defined Points ........................................................ 11-4
11.4.2 The Midpoint of an Existing Straight Line or Arc ................................... 11-5
11.5 A Quadrant Point Position ...................................................................................... 11-5
11.6 An Endpoint Position............................................................................................... 11-6
11.7 A Centre or Focus Position ...................................................................................... 11-7
11.8 A ‘Nearest To’ Position ............................................................................................ 11-9
11.9 An Intersection....................................................................................................... 11-10
11.10A Tangency Point ................................................................................................... 11-11
11.11Tangent Lines ........................................................................................................ 11-13
11.12A Perpendicular Intersection Point ...................................................................... 11-14
11.13Reflected Points ..................................................................................................... 11-16
11.14Fillet Arcs ............................................................................................................... 11-16
11.15Constructed Lines, Ray Lines and Bisector Lines ............................................... 11-16
11.15.1 Constructed Lines .................................................................................... 11-16
11.15.2 Ray Lines.................................................................................................. 11-17
11.15.3 Bisector Lines........................................................................................... 11-17
11.16Chamfer Lines........................................................................................................ 11-18
11.17Non-Drafting Applications of Point Construction................................................ 11-18
11.17.1 Labelling................................................................................................... 11-18
11.17.2 Dimensioning ........................................................................................... 11-19
11.17.3 Overlay Sheets ......................................................................................... 11-19
11.17.4 Drawing the Design ................................................................................. 11-19
11.17.5 Other Non-Drafting uses of Point Construction..................................... 11-19
11.17.6 The Point Construction Option Form ..................................................... 11-20
Contents-iv VANTAGE PDMS DRAFT User Guide

Version 11.5
Contents
Index
VANTAGE PDMS DRAFT User Guide Contents-v

Version 11.5
1 Introducing PDMS DRAFT
1.1 What does DRAFT do?
DRAFT produces fully annotated scale drawings showing selected parts of the design
model created in PDMS DESIGN. DRAFT is fully integrated with DESIGN.
A model can be viewed from any direction, with hidden detail automatically removed or
shown in a different linestyle, as required. A drawing may contain more than one view
of a 3D model; for example, a plan view, a front elevation and an isometric view may be
displayed simultaneously.
In DRAFT an annotated drawing is made up of different types of graphics:
• Graphics that represent the 3D model.
• Graphics to provide backing and overlay sheets which will be common to a number
of drawings.
• Graphics providing annotation, including not only dimensioning and text but also
such items as leader lines and label boxes.
All the graphic items exist as, or are defined by, elements in the DRAFT database.
1.2 The DRAFT Database
The DRAFT database contains a complete definition of a DRAFT drawing. The DRAFT
database does not contain information describing the geometry of the graphics that
make up a drawing, but gives a description of how those graphics should be presented
on a drawing.
From this database definition (together with the Design and Catalogue databases which
describe the appropriate 3D model) a drawing is generated which reflects the state of
the design at that particular time. The drawing can be displayed on the screen and
processed to produce a hard copy plotfile.
VANTAGE PDMS DRAFT User Guide 1-1

Version 11.5
Introducing PDMS DRAFT
1.3 Who Should Read This Manual
This is a command-level manual, written for people who are writing or customising their
own graphical user interface. It describes all the DRAFT commands, with worked
examples where appropriate. It is assumed that you are familiar with the normal way of
using DRAFT, via the supplied Graphical User Interface (GUI).
For an introduction to using DRAFT via the GUI, see Drawing Production Using
VANTAGE PDMS, and for further information, see the online help. For information
about DRAFT System Administration, see the VANTAGE PDMS DRAFT Administrator
Application User Guide.
For general information about customising the graphical user interface, see the
VANTAGE Plant Design Software Customisation Guide and VANTAGE Plant Design
Software Customisation Reference Manual.
1.4 Organisation of the DRAFT User Guide
The DRAFT User Guide has two parts:

Part 1, Basic Drawing Creation & Output, describes all aspects of producing a drawing
in DRAFT that do not relate to annotations.
Part 2, (this volume), describes all aspects of DRAFT relating to annotations.
1.5 Organisation of this User Guide
This manual, Part 2 of the User Guide, is divided into the following chapters:
• Chapter 2, Introduction to Annotation, describes the part of the DRAFT database
that stores annotation elements.
• Chapter 3, Dimensioning, describes how dimensions are added to drawings in
DRAFT. It also describes the part of the DRAFT database that stores dimensions.
• Chapter 4, Labelling, describes labels, how they are created and the part of the
DRAFT database that stores them.
• Chapter 5, Intelligent Text, describes the use of code words to automatically extract
data from the Design, Catalogue or Drawing databases.
• Chapter 6, Miscellaneous Text Facilities, describes how the following text parameters
can be manipulated in DRAFT; font selection, using multiple fonts within a text
string, inserting symbols using the alternative character set, editing text attributes,
text quality, character height.
• Chapter 7, Annotating Structural Elements in DRAFT, describes how to label and
dimension structural elements, and how to use structural elements in 2D drafting. It
also describes how to apply 3D data to annotation elements.
1-2 VANTAGE PDMS DRAFT User Guide

Version 11.5
Introducing PDMS DRAFT
• Chapter 8, Underlays and Overlays, describes the use of underlays and overlays on a
Sheet to add standard elemnts such as borders, title blocks, keyplans, etc.
• Chapter 9, 2D Drafting, describes DRAFT's two dimensional drafting facilities and
explains how these can be used to complement its main drawing production
facilities.
• Chapter 10, ISODRAFT Symbols, describes how ISODRAFT Symbols can be created
in DRAFT and exported to an ISODRAFT Symbol File.
• Chapter 11, Point and Line Construction, describes how a drafting position can be
defined by reference to other positions rather than explicitly.

Version 11.5
2 Introduction to Annotation
This Section describes the part of the Draft database used to store annotation
elements, that is dimensioning elements, labelling elements, and 2D drafting elements
(i.e. geometric primitives, symbols, and text). This part of the database hierarchy is
shown below:
SHEE
NOTE VIEW
LAYE
2D Drafting Dimensioning Labelling

VNOT elements
elements elements
TEXP ADIM SLAB
SYMB LDIM GLAB
CIRC
ELLI PDIM
RECT
TABL RDIM
ETRI
DMND
HEXA
MRKP
STRA
ARC
OUTL
Figure 2-1 Annotation Elements

Dimensioning and Labelling elements are owned by Layers. Other text, symbols and
graphics are owned by Notes. There are two types of Note:
• Sheet Notes (NOTEs) owned by Sheets
• View Notes (VNOTs) owned by Views.

Version 11.5
Introduction to Annotation
2.1 Layers
Layers (LAYE) are owned by VIEWs and are administrative elements used to group
together annotation elements. Layers may own Dimension elements, Label elements
and View Note elements. Usually, different Layers are used for different functions, and
the function of a Layer is defined by its PURPose attribute. The PURP attribute is used
to control the types of element which the Layer can own.
The PURP (Purpose) attribute of a Layer is set to a (four character) word, for example:
PURP DIMS
The PURP attribute may also be used to identify the Layer in other commands. For
example:
UPDATE LAYE DIMS
HIGhlight PURPose DIMS - highlight the Layer in the current view
with its PURP attribute set to DIMS
For more information on the HIGHLIGHT command, see Section 6.6, Part 1, Basic
Drawing Creation & Output.
The LVIS attribute controls the visibility of a Layer. It can be set to TRUE or FALSE.
This enables different types of annotation to be switched on and off.
The UCOD (Units Code) Layer attribute controls the display of units used for
dimensions and labels. For example:
UCOD FINCH DIST
- set distance units to ‘PDMS style’ feet and inches, e.g. 5’5.13/16
The default is mm for distances and bores. See Section 5.13.1 for full details of UCOD.
The PCOD (Precision Code) attribute controls the precision of output used with
Dimensions and Labels. See Section 5.13.3
Where Layers and Layer members have common attributes, the values of those
attributes are cascaded down from the Layer.
2.2 Autoblanking
You can use autoblanking to remove an area of graphics from a drawing and leave a
clear area. Generally, graphics added later will be drawn in this clear area. The main
purpose is to allow annotation to be shown clearly in crowded parts of a drawing. The
geometry of the blanked areas is defined by the geometry of the annotation element, for
example, a circular annotation element can define a circular blanked area where no 3D
design graphics will appear. Overlapping 2D, text and other annotation graphics will not
be hidden by blanking.
When autoblanking is switched on, the geometry will be hidden in the blanked areas
immediately the annotation that defines them is drawn or modified. When autoblanking
is switched off, the blanks will not be generated on the screen, but switching

Version 11.5
Introduction to Annotation
autoblanking on will generate all blanks immediately. Blanks will always be generated
in plot files generated from DRAFT, even when Autoblanking is off. The advantage of
working with Autoblanking switched off is that view control operations such as zooming
and panning will be slightly faster.
The command to switch autoblanking ON or OFF for a DRAFT session is:
AUTOBLANKING ON/OFF
Autoblanking can be used for the following annotation elements: LDIM, ADIM, RDIM,
PDIM, GLAB, SLAB, VNOT, and NOTE. The attribute BLNK specifies whether
autoblanking is required, and attribute BMAR specifies the blanking margin to be
applied.
BLNK TRUE/FALSE
BMAR value
where value is a real value which is greater than or equal to 0.0. If BMAR is set to 0.0
then a blanked region will be drawn with no blanking margin.

Version 11.5
3 Dimensioning
3.1 Introduction
DRAFT dimensions are a form of drawing annotation consisting of both text and
geometric elements; they may be either linear, radial (two types) or angular. Linear and
radial dimensions show the distances between particular points in the design model
whilst angular dimensions show the angles between directions.
DRAFT allows dimensions to be created quickly and easily (using the cursor), with
many attributes of the database dimension elements being assigned automatically.
A simplified view of that part of the DRAFT Database hierarchy which relates to
dimensioning is shown below.
VIEW
LAYE
LDIM RDIM PDIM ADIM
(Dimension Directions)
(Dimension Points) (Dimension Points)
Figure 3-1 Hierarchy of Dimension and Related Elements

Version 11.5
Dimensioning
3.2 Dimension Element Types
Linear Dimension (LDIM) elements (see Section 3.4) exist for each linear dimension
that appears on a drawing. LDIM elements own Dimension Point elements, which
specify the points between which dimensions are drawn. Two other types of linear
dimension are:
Radial Dimension (RDIM) elements (see Section 3.5) exist for each radial dimension
that appears on a drawing, being defined by a database element and an attribute (e.g.
DIAM of a CYLI).
Pitch Circle Dimension (PDIM) elements (see Section 3.6) exist for each pitch circle
dimension that appears on a drawing. PDIM elements own Dimension Point elements,
which specify the points between which dimensions are drawn. The graphics for an
PDIM are similar to those for an RDIM.
Angular Dimension (ADIM) elements (see Section 3.7) exist for each angular
dimension that appears on a drawing. ADIM elements own Dimension Direction
elements, which specify the end points of the dimension arc and its origin.
NOTE: When a Pipe element is dimensioned directly, the Pipe origin is assumed to be
the position of the HEAD of the first Branch visible in the VIEW region, if any.
If no Branch HEADs are visible in the VIEW region, then the position of the
HEAD of the first Branch is used.
3.3 Layer Attributes for Dimensioning

Dimensioning elements are created on Layers, and some of the Layer attributes are
cascaded down to the dimensioning elements. For general information about Layers, see
Section 2.
3.3.1 Linear Dimensions

The value of the DIR (direction) attribute of a Layer is cascaded down to Linear
Dimension (LDIM) elements. The initial setting is East.
3.3.2 Radial Dimensions

The default values of the following attributes will be cascaded down to radial
dimensions.
Marker Pen MPEN - settings OFF or integer value; default OFF. This controls the pen
used for the optional marker at the circle centre. See Section 8, Part 1, Basic Drawing
Creation & Output, for further details of MPEN.
Crosshairs Line Pen CHPN - settings OFF or integer value; default OFF. This
controls the pen used for the optional horizontal and vertical fixed crosshair markers
which mark the centre of the circle/arc being dimensioned.

Version 11.5
Dimensioning
Crosshairs Overshoot distance CHOSHT - default value 6. This controls the distance
by which the crosshairs overshoot the circle circumference. This value can be negative.
Angle Subtended ASUB - default 0. This controls the angle subtended by the optional
projection arcs at the circle circumference. For DFLAG DIAMETER two arcs are
drawn, one at each end of the dimension-line; for DFLAG RADIUS only one arc is
drawn. The midpoint of these arcs will intersect the dimension-line. Note that
ASUB=180 generates a circle for a diameter dimension.
Projection Line Pen PLPN. This pen is used to draw the optional projection arcs.
3.4 Linear Dimensions
3.4.1 Linear Dimensions and How to Create Them

The simplest kind of Linear Dimension consists of a pair of points on a drawing, each of
which relates to a point in the Design model. From each of these Dimension Points on
the drawing, a projection line is drawn in a user-definable direction; between these
parallel projection lines, dimension lines are drawn. Each dimension and projection
line may have text associated with it. An illustration of a simple linear dimension
between two Equipments is shown in Figure 3-2.
Figure 3-2 Single Value Linear Dimension

Such a dimension could be produced by typing the following commands, starting at
Layer level:

Version 11.5
Dimensioning
NEW LDIM - Create new linear dimension element

FROM ID @
TO ID @
TO ID @ - Use cursor to nominate (three) items to dimension from/to
The Dimension will appear on the display. If only two elements are hit a pair of
Dimension Point elements will have been automatically created, with the last point
becoming the current element.
In the above example the Dimension Points will be DPPT elements - the Dimension
Point is defined by a p-point of the Design element, in this case the origin. Any p-point
can be nominated as a dimension point by replacing the FROM ID @ syntax above by
FROM IDP @/TO IDP @. The Dimension may also be defined explicitly, for example
FROM /1501A TO /1501B
The other two types of Dimension Point that may be owned by an LDIM element are:
• DPOI - allows you to dimension to/from any given 3D positions
• DPBA - allows you to dimension to/from ‘before’ or ‘after’ a Design element (in
the Dimension direction).
DPOI elements would be created by a sequence such as:
NEW LDIM
FR POS @ TO POS @
DPBA elements would be created by a sequence such as:
NEW LDIM
FR BEFORE ID @ TO AFTER ID @
The effect of such a command will depend upon the dimension direction - see Section
3.4.3. Figure 3-3 shows an example of such a linear dimension, produced by the same
command but with different dimension directions.
Constructed points (see Section 11) may also be used to create Dimension Points.
NOTE: In cases where the dimension value is less than 0.01 mm, the display of all
dimension point graphics (see Figure 3-2) will be suppressed.
When dimensioning BEFORE or AFTER elements such as EQUI, STRU or SUBS,
DRAFT will ignore those primitives with OBST (obstruction level) set to 0 or 1. When
dimensioning BEFORE or AFTER a primitive, its OBST value will be ignored.

Version 11.5
Dimensioning
Figure 3-3 Single Value ‘Before/After’ Linear Dimensions

Figure 3-4 shows examples of using ‘before/after’ linear Dimensions with a single
element. (See subsection 3.4.3 for details of DOFF and OSHT.)
Note: Under some circumstances the length of the projection line for a DPBA may be
unsatisfactory. In this case changing the value of the NPPT attribute (which
supplies a reference p-point) will correct the situation.

Version 11.5
Dimensioning
Figure 3-4 ‘Before/After’ Linear Dimensions on a Single Element

NOTE: Use of Radial Dimensions would provide a simpler method of drawing the two
dimensions shown on the right-hand side of Figure 3-4 - see Section 3.5.
Note that any combination of the above three Dimension-creating commands is
permissible, for example:
FROM ID @ TO BEFORE ID @
FROM POS @ TO ID @
FR AFT ID @ TO POS @
Each FROM command sets the Dimension Point’s DDNM (Design Data Name) attribute
to the Name of the Design element. The DDNM attribute may be reset immediately to
define a new Dimension Point. If the DDNM is set to refer to an element which is not in
the Id List referenced from the current VIEW, the Dimension will still be drawn.

Version 11.5
Dimensioning
The command
CHECK REFS WARN
will cause a warning to be output in this situation, and the command
CHECK REFS FULL
will result in such Dimensions not being drawn. The default reference checking mode
(i.e. no checking) is given by
CHECK REFS OFF
Reference checking is also available for Labels - see Section 4.
It is possible to draw a Dimension which contains Dimension Points which are
incompletely defined (for example, a DPPT with an unset/illegal DDNM).The Dimension
is now treated as only containing the significant Dimension Points for both drawing the
Dimension and for commands which rely on the drawn dimension (such as PLCL @ (see
Figure 3-9) and DTOF @ (see Section 3.4.4).
3.4.2 Multi-valued Dimensions

The preceding examples have dealt with single-valued dimensions; where more than
two Dimension Points are involved, the Dimension is said to be multi-valued. Two
classes of multi-valued Dimensions exist, namely chained and parallel. An example of
a chained Dimension is shown in Figure 3-5.
Figure 3-5 Chained Linear Dimension

Such a dimension (which is still represented by a single LDIM element) is created by
repeating the TO part of the FROM . . . TO command line, moving the cursor crosshairs
to each Dimension Point in turn. The example shown in Figure 3-4 would have been
created by a command sequence such as
NEW LDIM
FR ID @ TO ID @ TO ID @
An additional ‘link’ can be inserted in or added to a chained Dimension (or a single-
valued Dimension can be ‘converted’ to a chained Dimension) through use of the INSERT
command. This is done simply by typing
INSERT ID @

Version 11.5
Dimensioning
and using the cursor to nominate the link element. P-points, p-lines, dimension points or
3D points may also be used as links using
INSE IDP @
INSE IDPL @
INSE IDPD @ or
INSE POS @
A Dimension Point may be constructed using DRAFT’s point construction facilities
(see Section 11). For example:
INSE POS OF @
INSE POS OF ENDP OF @
Other constructions such as INTERSECTION and MIDPOINT can be used. The facility
(which is only valid in a plan or elevation View) enables Dimension Points to be
positioned on any line of the Design graphics. The constructed Dimension Point will
have a 3D position (i.e. it is a DPOI) but will not be associated with the identified Design
element.
The effect of the INSERT command is to create a new Dimension Point of the
appropriate type at the correct position in the owning LDIM’s member list. INSERT can
be used at Dimension Point or LDIM level. Figure 3-6 illustrates the use of the INSERT
command.
Figure 3-6 Use of the INSERT Command

Dimensions will be drawn in the same order as the LDIM’s member list order. If the
elements get out of the correct order then the display of the Dimension will become
confused. This situation can be corrected by the SORT DIMENSIONPOINTS command
(minimum abbreviation SORT DIM), which can be used at Dimension or Dimension
Point level. The effect of the command is shown in Figure 3-7.

Version 11.5
Dimensioning
Figure 3-7 Use of the SORT DIM Command

An example of a parallel Dimension is shown in Figure 3-8.
Figure 3-8 Parallel (or Tail) Linear Dimension
A parallel Dimension can be produced simply by setting the LCHA attribute of an LDIM
as appropriate:
LCHA PARA - parallel dimension
LCHA CHA - chained dimension

Version 11.5
Dimensioning
3.4.3 Principal Attributes of Linear Dimensions

Those attributes of a linear Dimension which most affect its general appearance are
shown in Figure 3-9. (Default values are shown in brackets.)
Figure 3-9 Key Attributes of a Linear Dimension

Note that OSHT, PLCL and DOFF are given initial default values at Layer level when
the Layer is created. These values are cascaded down to Dimension level when those
elements are created subsequently. Following this initial setting, an attribute set to
‘default’ at Dimension Point level will take its value from the same attribute of its
owning Dimension element (if appropriate).
The Projection Line Clearance (PLCL) is the distance between the dimension point
and the projection line at the dimension point end. Negative clearances may be
specified. Examples of setting this attribute are:
PLCL 5 - set PLCL to 5mm
PLCL @ - set using cursor
PLCL DEF - (at Dimension Point level): set to owning Dimension PLCL
value
PLCL may be set at Dimension or Dimension Point level. PLCL set at Dimension level
(which becomes the ‘default’ PLCL) will apply to all subsequently created Dimension
Points. PLCL set at Dimension Point level can only be reset from the same Dimension
Point, not from Dimension level. When setting PLCL with the cursor, the resulting
(paper) coordinate which does not lie in the same axis direction as the projection line is
ignored. These comments also apply to the OSHT attribute (see below).

Version 11.5
Dimensioning
The Projection Line Overshoot (OSHT) is the distance by which the projection line
‘overshoots’ the end of the dimension line. Negative overshoots may not be specified.
Examples of setting this attribute are:
OSHT 5 - set OSHT to 5mm
OSHT @ - set using cursor
OSHT @ - set using cursor
OSHT TOP /CIRCLE1 - OSHT defined by a ‘constructed point’ -
see Section 11.
OSHT DEF - (at Dimension Point level): set to owning Dimension
OSHT value
(See PLCL description for further comments relating to OSHT.)
The other three attributes shown on Figure 3-9 are:
Dimension Line Offset (DOFF) - the distance by which the dimension line is
offset (in the projection line direction) from the
2D position of the first dimension point.
Projection Line Direction (PLDI) - the angle between the projection line and the
dimension line.
Dimension Line Direction (DIR) - the direction of the dimension line (an explicit
compass direction, p-point or p-line direction).
Default East.
An important feature of the above attributes is that they can be set at Dimension
Point level, removing the need to move back up the hierarchy having just created a new
LDIM.
DOFF has a related attribute DPOS - the dimension line position. DPOS is a fixed
2D paper coordinate through which the dimension line will pass. If a dimensioned
element is moved, then if DOFF is used the whole Dimension will also move; if DPOS is
used then the dimension line will still pass through the same point (but the projection
lines will be adjusted to suit).
DOFF and DPOS both control the position of the dimension line and so are mutually
exclusive - setting one will unset the other. Examples of the relevant commands are:
DOFF 20 - set DOFF to 20mm
DPOS @ - set DPOS using cursor
DIM ABSOLUTE - convert DOFF to DPOS
DIM OFFS - convert DPOS to DOFF
When setting DPOS, the resulting (paper) coordinate which does not lie in the same
axis direction as the required offset is ignored.
The projection line direction is set by commands such as:
PLDI 75 - set PLDI to 75 degrees

Version 11.5
Dimensioning
PLDI N10W - set PLDI to explicit compass direction

PLDI @ - set PLDI with cursor
PLDI @ - set PLDI to nominated p-point direction
NOTE: Projection line direction is treated as 90 degrees when it is nearly but not quite
90 degrees. This avoids an unexpected flip in the projection line text orientation.
The dimension direction can be set explicitly by a commands such as:
DIR E10N
Another method is to set the ‘true length’ attribute (TLIN) using the command:
DIR TRUE
This will set the dimension direction as being that from the first to the second dimension
point (TLIN is set to TRUE and DIR is unset). See Figure 3-10 and Figure 3-11.
P2 DOWN P2
P1 P1
(i) (ii)
DIR TRUE gives distance as in (i) not as in (ii)
Figure 3-10 Definition of ‘True Length’

Version 11.5
Dimensioning
Figure 3-11 Effect of True Length Attribute Settings
The true length facility can be useful when it is not clear what explicit direction to set in
order to achieve the desired result. The bottom left-hand dimension in Figure 3-11 has
been created without regard for the Dimension direction, which turns out to be
inappropriate; setting TLIN TRUE produces the desired picture.
Points to note about the true length facility are:
• The true length is 2D, i.e. the length is orthographic, not a slope length - ‘uppings’
are ignored.

Version 11.5
Dimensioning
• True length is meaningless for a Dimension with more than two points, unless the
points are in line.
• Since a DPBA Dimension Point relies on the existence of a predefined dimension

direction, such a point cannot be used as one of the first two points of a true length.
It is possible to set the dimension direction to that of a p-point, using the command:
DIR IDP @
(This command will set the DDNM attribute to the name or reference number of the
primitive concerned, and the PPDI attribute to the appropriate p-point number; DIR will
be unset and TLIN set to FALSE.)
3.4.4 Detail Attributes of Linear Dimensions

To save space on the paper, a parallel dimensions may be produced in a truncated
form. Figure 3-12 shows the truncated form of the dimension shown in Figure 3-8.
Figure 3-12 Truncated Parallel Dimension

The truncation is produced by the TRUNCATE command which has two forms as shown
in the examples below.
TRUNCATE BY 5 - truncate affected dimension lines by 5%
TRUN TO 10 - truncate dimension lines to 10mm from nearest
dimension point
TRUN OFF - turn off truncation
For non-truncated parallel dimensions, the spacing between each dimension line is
given an initial default value calculated to be sufficient to allow room for the dimension
value (or a single line of dimension line text). The spacing is controlled by the Dimension
Line Separator Attribute (DMSP).
For example:
DMSP 30 - set separation to 30mm

Version 11.5
Dimensioning
DMSP @ - set separation with cursor

In a macro, the separation can also be set in terms of Sheet or screen coordinates. Note
that the minimum separation is governed by the DMSP attribute - the calculated
spacing cannot be less than this minimum. Figure 3-13 shows the effect of varying the
spacing.
Figure 3-13 Parallel Dimension Line Spacing

The initial value of DMSP is cascaded down from LAYE level
Dimension line text (DMTX) is set by a command of the form:
DMTX ’text’
For example:
DMTX ’ACCESS SPACE’ - (see Figure 3-14, left hand)
DMTX ’ACCESS SPACE #/#DIM’ - (see Figure 3-14, right hand)
Figure 3-14 Dimension Line Text

#DIM in the example above takes the value of the dimension. #DIM is a simple case of
intelligent text - see Section 5. Note that in the case of non-truncated parallel
dimensions, the dimension line spacing will automatically be adjusted to accommodate
two or more lines of text if these are input. Dimension line text may be set at Dimension
Point or Dimension level, although in the latter case the text input will attached to all
the dimension lines involved. Associated commands are:
DMTX DEFAULT - (at Dimension Point level): set dimension text to that
of owning Dimension

Version 11.5
Dimensioning
Dimension text is automatically centre-justified, but its position relative to the

dimension line may be varied by changing the setting of the dimension text offset
(DTOF) attribute. For example:
DTOF 0 5 - move dimension text origin 5mm along axis parallel to
projection line in text upvector direction (= perpendicular
to dimension line in most cases)
DTOF @ - move dimension text origin to cursor position
DTOF N 1 @ - move x coordinate of dimension text origin to cursor
position (y - coordinate not changed)
DTOF N 2 5 - change y coordinate of dimension text origin by 5mm
(x coordinate not changed)
Note also
DTOF DEF - use default Dimension offset value, not Dimension Point
value
DTOF STAN - equivalent to DTOF 0 0, the standard position
DTOF ENDP OF /LINE1 QUAL X500 Y500 - DTOF defined by a
‘constructed point’ – see
Section 11.
The dimension text origin is at the centre of and approximately half a character height
‘below’ the text.
Note that if there is insufficient space between the ends of two projection lines to enable
the dimension line text to be fitted in parallel to the dimension line it will be
automatically rotated by 90 degrees. Reducing the text character size (see below) may
result in their being enough room to display the text parallel to the dimension line.
Dimension text angle can be controlled using the DTANGLE attribute. This is available
both at dimension and dimension point level. Possible settings are:
DTANGLE STANDARD
DTANG HORIZ
DTANG VERT
DTANG EXTERNAL
DTANG PARALLEL
PTANG DEFAULT
The STANDARD setting gives dimension line text parallel to the dimension line except
when there is insufficient room for it, when it is drawn parallel to the projection-line -
i.e. external dimension line text. STANDARD is the default setting for Dimension
elements. The text is positioned by default just above the middle of the dimension line
except that external text is centred on the centre of the dimension line. If the text is not
external, then its position is constrained to lie between the projection lines.
The HORIZONTAL and VERTICAL settings cause the dimension line text to be drawn
respectively horizontally or vertically in the VIEW. By default the text is centred on
middle of the dimension line.

Version 11.5
Dimensioning
The EXTERNAL setting forces the dimension line text to be drawn parallel to the
projection line even though there is room for it to be drawn parallel to the dimension
line. By default the text is centred on middle of the dimension line. If the text would not
be external in the STANDARD case, then its position is constrained to lie between the
projection lines.
The PARALLEL setting forces the dimension line text to be drawn parallel to the
dimension line even though there may be insufficient space for it to fit. By default the
text is positioned just above the middle of the dimension line. If the text would not be
external in the STANDARD case, then its position is constrained to lie between the
projection lines.
The DEFAULT setting is only available at Dimension Points. This allows the DTANGLE
value to be taken from the Dimension element (LDIM or ADIM). Otherwise the setting
at the Dimension Point is used. This is the default setting for Dimension Points.
Figure 3-15 Dimension Line Text Angle

Projection line text (PLTX) is set and manipulated in a similar way. For example, the
commands
PLTX ’PUMP /1501A’
PLTX ’PUMP /1501B’

Version 11.5
Dimensioning
(each at the appropriate dimension point level) could be used to give the text shown in
Figure 3-16.
Figure 3-16 Projection Line Text

Note also
PLTX STAN - no projection line text (the standard option)
PLTX DEF - use default Dimension setting, not Dimension Point setting
Projection line text axes are oriented relative to the projection line. The orientation is
controlled by the setting the PTOF attribute. For example:
PTOF -5 -5
See Figure 3-17 for an example of changing the projection line text offset.

Version 11.5
Dimensioning
Figure 3-17 Projection Line Text Offset

Other options are:
PTOF @ Set PTOF by cursor
PTOF STAN Equivalent to PTOF 0 0, the standard position
PTOF DEF Use default Dimension value, not Dimension Point value
PTOF CENTRE OF /CIRCLE1 PTOF defined by a constructed point.
See Section 6.
PTOF N 1 @ Move x coordinate of projection line text origin to
cursor position (y coordinate not changed)
PTOF N 2 5 Change y coordinate of projection line text origin by
5mm (x coordinate not changed)
Projection line text is justified ‘towards’ the appropriate dimension point by default, but
may be justified ‘away’ from the dimension point or may be centred on the projection
line, using the commands:
PJUST AWAY
PJUST CENTRE

Version 11.5
Dimensioning
Figure 3-18 Projection Line Text Justification

The initial value of PJUS is cascaded down from LAYE level.
Projection text angle can be controlled using the PTANGLE attribute. This is available
both at dimension and dimension point level. Possible settings are:
PTANGLE HORIZ
PTANG VERT
PTANG STAN
PTANG DEF
The HORIZONTAL and VERTICAL settings cause the projection line text to be drawn
respectively horizontally or vertically in the VIEW. In these cases, the projection line is
not extended automatically to underline the text but only overshoots the dimension line
by the distance specified by the OSHT attribute.
The STANDARD setting gives the projection line text parallel to the projection line. This
is the default value for Dimension elements.
The DEFAULT setting is only available at Dimension Points. This allows the PTANG
setting to be taken from the Dimension element (LDIM or ADIM), otherwise the setting
at the Dimension Point is used. This is the default setting for Dimension Points.

Version 11.5
Dimensioning
Figure 3-19 Projection Line Text Angle

The standard character height for dimension line and projection line text is 4mm
(cascaded from LAYE level), but this may be varied by commands such as:
DTCH 2 - set dimension line text character height (DTCH) to 2mm
PTCH 2 - set projection line text character height (PTCH) to 2mm
Initial settings of these attributes are cascaded down from LAYE level.
Other text attributes (present at Dimension and Dimension Point level) are:
PLSP Projection text line-spacing
PFON Projection text Font
DFON Dimension text Font
PTLH Projection text letter height (0.8* character height)
DTLH Dimension text letter height (0.8* character height)
Initial settings of these attributes are cascaded down from LAYE level. See Section 6 for
details of letter height and text fonts.
Dimension line and projection line text can be edited through use of the EDTEXT
command. In the following examples, the target string is ‘ACCESS DPACE’, = ‘ACCESS
SPACE’ mistyped:

Version 11.5
Dimensioning
EDTEXT DMTX ’DPACE’ ’SPACE’

Change dimension line text to ‘ACCESS SPACE’
EDTEXT PLTX ’DPACE’ ’SPACE’
Change projection line text to 'ACCESS SPACE'
Note that when editing intelligent text the intelligent text code itself must be specified,
not the resultant text. See Section 6 for full details of the EDTEXT command.
Dimension line terminators are arrowheads by default, but may be obliques, dots, or
absent altogether - see Figure 3-20.
Figure 3-20 Dimension Line Terminators

The terminators (DTER attribute) are set by the commands:
DTER ARROWS
DTER OBLIQUES
DTER DOTS
DTER OFF
Note: The first terminator of a truncated dimension (see Figure 3-12) can be set
independently using the FTER attribute. The first terminator will be drawn
25% larger than the remainder.
FTER can have any of the same settings as DTER, or can be DEFAULT, in which case
FTER assumes the same setting as DTER. FTER is applicable to LDIMs and ADIMs, or
can be set at LAYE level, in which case its setting will be cascaded down to newly-
created dimensions.
The size of the terminator is controlled by the TSIZ attribute:

Version 11.5
Dimensioning
TSIZ 4 - set size to 4mm (default 3mm)

The initial settings of DTER and TSIZ are cascaded down from LAYE level.
The linestyles used for dimension and projection lines may be set by
DLPN number
PLPN number
The initial settings of DLPN and PLPN are cascaded down from LAYE level. See Section
8, Part 1, Basic Drawing Creation & Output for details of pens and linestyles.
Gaps in projection lines are most easily defined using the cursor, with either the
start and end points or a mid point and a length being specified. Examples of the
relevant commands are:
GAP @ Specify gap by giving start and end points
GAP AT @ Specify a default length gap (2mm) centred on given
point
SETDEF GAP 15 Set default gap length to be 15mm
GAP AT @ L 10 Specify a 10mm gap centred on given point
GAP OVER @ Specify gap start and end points with cursor, and
delete all other gaps in line
GAP DELETE @ Delete gap specified by cursor
GAP DELETE ALL Delete all gaps on the current projection line
or dimension line
Up to ten gaps may be inserted in the projection line. Note that if the position of a
Dimension is changed so as to substantially alter the path of the projection line then it
will be redrawn solid until the gaps are redefined.
Gaps may be highlighted by giving the command:
SKETCH GAPS
(at any element which contains gaps). A circle will be drawn with diameter equal to the
gap length, centred on the gap centre. The command:
ERASE GAPS
will remove the circles. Either of the above commands may have an element name after
the main command if the required element is not the current element.

Version 11.5
Dimensioning
3.5 Radial Dimensions
A Radial Dimension (RDIM) is a form of linear dimension which may be used to draw
radius and diameter dimensions of circular elements. A Radial Dimension does not own
Dimension Point elements, but is defined by a database reference to an element type
(the one to be dimensioned) and an attribute taken from that element which defines
whether a diameter or a radius is to be drawn. For example, DIAM of a CYLI (the
diameter of a cylinder) or FRAD of a PAVE (fillet radius of a Panel Vertex). Figure 3-21
shows the principal features of an RDIM, Figure 3-22 shows examples of types of RDIM.
A Pitch Circle Dimension (PDIM) is another form of radial dimension - see section
3.6.
Dimension Text
Dimension Origin
Leader Line (optional)
Dimension Line
Terminator
Figure 3-21 Radial Dimension - Principal Features

Version 11.5
Dimensioning
Diameter dimension on a CYLI, Radius dimension on a CYLI,

no leader line no leader line
Diameter dimensions on filleted

Panel Vertex (PAVE) elements, with
leader lines
Figure 3-22 Radial Dimensions - Examples

Radial Dimensions have a dimension centre, defined by the DDNM (Design Data
Name) attribute. This is an attribute of the RDIM itself, and is normally defined by the
origin of the element dimensioned. (See Section 3.5 for exceptions to this.) This could be
(for example) the origin of a CYLI or of a (filleted) PAVE (Panel Vertex).
The other principal attribute of an RDIM is the dimension attribute key, AKEY. This
is a word attribute which stores the code of a dimensional attribute of the DESIGN
element type which is to be dimensioned. The default value of AKEY is DIAM.

Version 11.5
Dimensioning
The following table shows which attributes of which DESIGN element types may be
dimensioned using an RDIM.
Element Type Attributes

CYLI DIAM
NCYL DIAM
SLCY DIAM
NSLC DIAM
DISH DIAM RADI CRAD
NDIS DIAM RADI CRAD
RTOR DIAM RINS ROUT
NRTO DIAM RINS ROUT
CTOR DIAM RINS ROUT
NCTO DIAM RINS ROUT
SNOU DIAM DTOP DBOT
NSNO DIAM DTOP DBOT
CONE DIAM DTOP DBOT
NCON DIAM DTOP DBOT
VERT DIAM FRAD
PAVE DIAM FRAD
SEVE DIAM FRAD
The command
Q AKEYLIST
(at a Design element) returns the list of possible AKEY settings.
Most of the AKEY settings allowed above are genuine database attributes; however, the
DIAM keyword has different meanings at different elements. For some Design elements
it is a genuine attribute, for others it is derived:
• DIAM is a genuine attribute of Dishes (DISH, NDIS) and all Cylinders (CYLI,
NCYL, SLCY, NSLC).
• For Toruses (RTOR, NRTO, CTOR, NCTO), DIAM gives the centreline diameter of
the element - i.e. twice the average of RINS and ROUT.
• For Snouts (SNOU, NSNO) and Cones (CONE, NCON), DIAM is taken to be DBOT,
the bottom diameter.
• For Structural Vertices (VERT, PAVE, SEVE), DIAM is taken to be twice the fillet
radius (FRAD) if it is set. The origin is normally the position of p9 of the vertex.

Version 11.5
Dimensioning
The centre of a Radial Dimension is normally defined by the origin of the element
dimensioned, except for the following AKEY settings:
• For DTOP and DBOT, the dimension centre will be the centre of the appropriate
end of the primitive. This also applies to DIAM for Snouts and Cones.
• For FRAD, the centre of the fillet radius is defined by one of the many p-points of
the Vertex (p8 or p9). This also applies to DIAM if the FRAD value is being used.
• The RADI attribute of a dish (DISH, NDIS) is the knuckle radius. The CRAD
attribute of a dish is the cap radius. The centre of these radii are derived. Both
these AKEY settings are only sensible for a sideways view of a tori-spherical dish.
3.5.1 Creating Radial Dimensions

The RDIM is defined by the ON command plus optional AKEY syntax, for example:
NEW RDIM - create RDIM element
ON ID @ - use cursor to define dimension centre
AKEY RADI - change AKEY to give a radius dimension
In many cases it will be unnecessary to define AKEY explicitly, since the DIAM setting
will give a sensible result.
Although RDIM elements do not have p-point or p-line attributes it is possible to use p-
point or p-line syntax to select the Design element. This is necessary for vertices (VERT,
SEVE, PAVE) which cannot be picked directly by cursor. However the Design element
can be picked using the IDP @ command.
3.5.2 Appearance of Radial Dimensions - Specific Attributes

The Radius/Diameter flag (DFLAG) attribute controls whether the RADIUS or
DIAMETER is evaluated by the AKEY attribute as well as whether the dimension line
is drawn from the centre (Radius) or across the diameter (Diameter). The default setting
is RADIUS.
120 240
DFLAG RADI DFLAG DIAM
Figure 3-23 Radial Dimensions - DFLAG Setting

Version 11.5
Dimensioning
The Dimension Text (DMTX) attribute has the initial setting #DIM, which gives the
value of the dimension controlled by DLFAG. For example for AKEY RINS and DFLAG
DIAM, the text ’#DIM’ will be evaluated as the inside diameter of the element identified.
The resulting value will be output on the drawing in place of this codeword. #DIM is a
simple case of intelligent text - see Section 5.
The Dimension Line Angle (DDEG) attribute controls the angle at which the
dimension line is shown, relative to the 2D coordinate system of the VIEW. The default
value is 0 (horizontal in the VIEW). Note that this is only horizontal in the Sheet when
the VIEW has RCOD UP. DDEG may be set explicitly or by using the cursor (i.e. DDEG
@).
The Text Radius Flag (DTFLAG) attribute controls whether the text radius DTRAD
(see below) is measured from the CENTRE, MIDPOINT or CIRCUMFERENCE of the
radial dimension. The default setting is CENTRE. For radius dimensions, MIDPOINT is
the midpoint between centre and circumference; for diameter dimensions MIDPOINT is
the same as CENTRE.
The Text Radius (DTRAD attribute) is a signed distance (in Sheet units) which defines
the radial position of the dimension text origin from the centre or circumference
(according to the DTFLAG setting) of the dimensioned object. In the latter case, DTRA=
0 (the default value) means that the text origin is positioned at the 2D projection of the
circumference of the object dimensioned.
If the text origin lies outside the circumference then the text is justified towards the
centre of the circle. If the text lies inside the circumference then the text is centre
justified unless the DSTYL is LEADER. In this last case, the justification is towards the
circumference.
Text radius can be negative. For DTFLAG CIRCUMFERENCE, a negative value means
inside the circumference. For DTFLAG CENTRE, a negative value places the text on the
opposite side of the centre to its usual position. This is equivalent to reversing DDEG
with a positive DTRA value.

Version 11.5
Dimensioning
240 240
DTRA 0 DTRA 0
DTFLA CENTRE DTFLA CIRCUM
240 240
DTRA -10 DTRA 10

DTFLA CIRCUM DTFLA CIRCUM
240 240
DTRA 10 DTRA -10

DTFLA CENTRE DTFLA CENTRE
240 120
DFLAG DIAM DFLAG RADIUS

DTFLA MIDPOINT DTFLA MIDPOINT
Figure 3-24 Radial Dimensions - DTRA Setting

The Dimension Text Angle (DTANGLE) attribute controls the Dimension text angle.
Possible settings are:
DTANGLE STANDARD
DTANG HORIZ
DTANG VERT
The default setting of DTANG is STANDARD. In this case the text is orientated
radially. See Figure 3-25 for the effects produced by changing DTANG.

Version 11.5
Dimensioning
DTANG STAN DTANG HORIZ DTANG VERT
Figure 3-25 Radial Dimensions - DTANG Setting

The Dimension Text Offset (DTOF) attribute defines the displacement of the text
position from the text radial position. DTOF is a 2-dimensional array attribute. DTOF(1)
defines the displacement along the text path direction (i.e. Radial, Horizontal or Vertical
depending on the DTANG setting), and DTOF(2) in the text ‘upvector’ direction. The
default/initial value of DTOF is (0,0).
Further control of the text position in the upvector direction is given by use of the
vertical alignment attribute ALIG. The actual position of the text for DTOF(2)=0 will
depend on the value of ALIG. This allows you to align text independently of the
character height DTCH. See Section 4.2.7 for further details of ALIG.
The second component of text offset, DTOF(2), is always applied in the upvector
direction. Its value may be positive, zero or negative. See Figure 3-26 for the effects
produced by changing DTOF(2).
As an alternative to entering two values, DTOF may be set using the cursor, i.e.
DTOF @
NOTE: In Figure 3-26, ALIG=BBODY unless otherwise indicated.

Version 11.5
Dimensioning
DTANG STAN DTANG STAN DTANG STAN DTANG STAN

DTOFF 0 0 DTOFF 0 5 DTOFF 0 -5 DTOFF 0 -5
ALIG TBODY
DTANG HORIZ DTANG HORIZ DTANG HORIZ DTANG HORIZ

ALIG TBODY
DTANG VERT DTANG VERT DTANG VERT DTANG VERT

ALIG TBODY
Figure 3-26 Radial Dimensions - DTOF(2) Setting

The definition of the direction of application of the first component, DTOF(1), is more
complex:
For DTANG STANDARD and text outside the circumference (i.e. DTFLAG CIRCUM,
positive DTRAD), DTOF(1) is in the direction of the radial displacement outwards from
the text radial position. (In this case, it is preferable to modify the text radius (DTRAD)
rather than DTOF(1); DTOF(1) is best left set to zero).
For DTANG HORIZONTAL and text outside the circumference, DTOF(1) is horizontal
from the text radial position. In this case, the sign of DTOF(1) is determined by the
DDEG attribute; for DDEG between -90 and +90, positive DTOF(1) adjusts the text
position to the right of the radial position of the dimension text; for DDEG between 90
and 270, positive DTOF(2) adjusts the text position to the left. See Figure 3-27.
Similarly, for DTANG VERTICAL and text outside the circumference, DTOF(1) moves
the text up for DDEG between 0 and 180; and down for DDEG greater than 180 and
less than 360.

Version 11.5
Dimensioning
DTANG STAN DTANG STAN DTANG STAN

DTRAD 50 DTRAD 55 DTRAD 45
DTANG HORIZ DTANG HORIZ DTANG HORIZ

DDEG 45 DDEG 45 DDEG 45
DTOFF 0 0 DTOFF 5 0 DTOFF -5 0

Figure 3-27 Radial Dimensions - DTOF(1) Setting - Text Outside Circumference

In all three DTANG cases, if the text lies inside the circumference, the direction in
which DTOF(1) is applied is reversed. DTOF(1) is always applied in the direction away
from the Circumference.
Thus for DTANG Horizontal and DDEG=45, when the text is outside the circumference
then DTOF(1) adjusts text to the right. However when text is inside the circumference,
then DTOF(1) adjusts text to the left.
For DTANG Standard, then DTOF(1) would move text radially outwards for text outside
the circumference; and inwards for text inside the circumference. However in this case it
is better to leave DTOF(1) set to zero and modify the text radial position DTRAD. See
Figure 3-28.

Version 11.5
Dimensioning


Figure 3-28 Radial Dimensions - DTOF(1) Setting - Text Inside Circumference

The Dimension Style (DSTYLE) attribute, combined with DTANG, controls the overall
dimension style. Possible settings are:
DSTYLE DIMLINE
DSTYLE LEADERLINE
DSTYLE EXTERNAL
The default setting of DSTY is DIMLINE. This style shows a radial dimension line with
terminators. For DFLAG DIAM this is drawn across the diameter with two terminators;
for DFLAG RADI this is drawn from the centre to the circumference with a single
terminator. (See Figure 3-23.) If the dimension text lies inside the circumference, then
the dimension line will be gapped if the text crosses it. The position of dimension text is
controlled by the Dimension Text Offset (DTOFF) attribute - see earlier in this Section.
The dimension line will be extended beyond the circumference of the object dimensioned
if the text radial position (DTRAD attribute - see earlier in this Section) lies outside the
circumference. If the text is horizontal, then a horizontal line will be drawn from the
radial dimension line to the actual text position. Whatever the text orientation, the line
will be extended to underline the text if indicated by the DTUL attribute (see below).
The LEADERLINE style shows a radial leaderline from the circumference to the text
radial position . If the text is horizontal, then the leaderline will be extended
horizontally to the text offset position. No dimension-line will be drawn.
Text underlining will be controlled by the Dimension Text Underlining attribute,
DTUL. This indicates whether the leaderline is extended to underline the text or not. If
DTUL is ON, the leaderline will always be extended to underline the text even if this
causes it to pass through the text string. The line will be drawn through the text offset
position - thus there will be overlining for ALIG TBODY. DTUL is ignored for DSTYL

Version 11.5
Dimensioning
DIMLINE unless the text radial position is outside the circumference. The default
setting will be OFF.
See Figure 3-29 for examples of the LEADERLINE style (all shown with DTUL ON).
240
120
DTANG STAN DTANG STAN DTANG HORIZ DTANG HORIZ

DTOFF 0 0 DTOFF 0 0 DTOFF 5 0 DTOFF 5 0
DTFLAG CENTRE DTFLAG CIRCUM DTFLAG CENTRE DTFLAG CIRCUM
DTRAD 0 DTRAD 5 DTRAD 0 DTRAD 10
DFLAG RADI
Figure 3-29 Example RDIMs in LEADERLINE Style

The EXTERNAL style is a variant on the Dimline style. For Diameter dimensions, two
short radial lines are drawn outwards from the circumference with terminators on the
circumference. If the text radial position lies outside the circumference, then one line is
extended to the text offset position (with optional text underlining).
For Radius dimensions with EXTERNAL style the appearance depends on the text
radial position. If it lies inside the circumference, then a single short radial line is
drawn outwards from the circumference with a terminator on the circumference.
If the text radial position lies outside the circumference, then the dimension is drawn
exactly the same as in the DIMLINE style except that the terminator direction is flipped
to be outside the dimension line. See Figure 3-30 for examples of the EXTERNAL style
(all shown with DTUL ON).
240
120
DTANG STAN DTANG STAN DTANG HORIZ DTANG HORIZ

DTOFF 0 0 DTOFF 0 0 DTOFF 5 0 DTOFF 5 0
DTFLAG CENTRE DTFLAG CIRCUM DTFLAG CENTRE DTFLAG CIRCUM
DTRAD 0 DTRAD 5 DTRAD 0 DTRAD 10
DFLAG RADI
Figure 3-30 Example RDIMs in EXTERNAL Style

Version 11.5
Dimensioning
3.5.3 Appearance of Radial Dimensions - General Attributes

In addition to the attributes described in the previous section there are further
attributes which control the appearance of the dimension, which are also used by Linear
and Angular Dimensions (see section 3.7) and Dimension Points. These attributes will
be cascaded down from the owning LAYE. The attribute setting DEFAULT is not
available for Radial Dimensions.
The general attributes are:
The Dimension Terminator attribute DTER - see Section 3.4.4 for details.
The Terminator Size attribute TSIZ - see Section 3.4.4 for details.
The Dimension Line Pen attribute DLPN - line pen used to draw the dimension and
leader lines. The initial value is cascaded from the LAYE. See Section 8, Part 1, Basic
Drawing Creation & Output for details of pens and linestyles.
The Gaps array attribute GAPS - an array of user-defined gaps; no gaps by default. The
gaps defined in this array will be applied to the dimension- and leader lines of the
Radial Dimension. This is in addition to the gap under the dimension text which is
inserted automatically in the dimension line. See Section 3.4.4 for details. The command
GAP TIDY
deletes unused gaps.
Dimension Text will also have the following attributes, similar to those in use for
LDIMs and ADIMs:
Vertical Alignment ALIG - cascaded from the LAYE. See Section 4.2.7 for
further details of ALIG.
Font DFONT - cascaded from FONT on LAYE. See Section 6 for
details of text fonts.
Dimension Text Pen DTPN - cascaded from TPEN on LAYE.
Character Height DTCH - cascaded from CHEI on LAYE - see Section 3.4.4
for details.
Letter height DTLH - attribute derived from DTCH.
3.5.4 Appearance of Radial Dimensions - Ancillary Graphics

Attributes
Additional attributes are provided to control ancillary graphics as follows:
Marker Pen MPEN - settings OFF or integer value; default OFF. This controls the pen
used for the optional marker at the circle centre. See Section 8, Part 1, Basic Drawing
Creation & Output for further details of MPEN.
Crosshairs Line Pen CHPN - settings OFF or integer value; default OFF. This
controls the pen used for the optional horizontal and vertical fixed crosshair markers
which mark the centre of the circle/arc being dimensioned.

Version 11.5
Dimensioning
Crosshairs Overshoot distance CHOSHT - default value 6. This controls the distance
by which the crosshairs overshoot the circle circumference. This value can be negative.
CHOSHT can be set using the cursor, i.e. using the command
CHOSHT @
Angle Subtended ASUB - default 0. This controls the angle subtended by the optional
projection arcs at the circle circumference. For DFLAG DIAMETER two arcs are
drawn, one at each end of the dimension-line; for DFLAG RADIUS only one arc is
drawn. The midpoint of these arcs will intersect the dimension-line. Note that
ASUB=180 generates a circle for a diameter dimension.
Projection Line Pen PLPN. This pen is used to draw the optional projection arcs. The
default value of this will be cascaded from the LAYE.
3.5.5 Creating Radial Dimensions using the Cursor

NOTE: The creation methods given here are applicable to RDIMs and PDIMs (Pitch
Circle Dimensions) - see Section 3.6.
In addition to the basic creation method given in Section 3.5.1, some style attributes
may be defined by cursor interaction. Having created the RDIM/PDIM and defined its
position,
DIM @
will cause both dimension angle DDEG and text radius DTRAD to be defined in one go.
(The dimension text origin will be at the cursor crosshair position.) It will not modify
DTOF.
3.5.6 Modifying Radial Dimensions through Graphical Interaction

A powerful facility for modifying an existing radial dimension is provided by the
command
MODIFY @
Having made the dimension you wish to modify the current element, giving this
command causes the Dimension Modification Form to appear, and the selected
dimension is highlighted with four pickable ‘hot spots’ which allow modification of the
DDEG, DTRA and DTOF attributes of the dimension. In addition, DTANG can be
modified using the Text angle option button.
To modify the dimension, click on the ‘hot spot(s)’ that you wish to move, click on the
new position (a transient image of the dimension will appear, which will move as the
mouse is moved), then click on OK on the form. (Cancel allows the command to be
aborted with no change to the dimension; Reset causes the position of the current ‘hot
spot’ to be reset to its database position; Delete causes the current ‘hot-spot’ to be
deleted or set to a default position.)
The form also contains the point construction Option list button which allows positions
to be defined in terms of end-points, intersection points, etc.

Version 11.5
Dimensioning
3.6 Pitch Circle Dimensions
A Pitch Circle Dimension (PDIM) is a form of radial dimension which may be used to
draw radius and diameter dimensions between two independently definable points. A
PDIM is defined by two Dimension Point elements which are owned by the PDIM. These
in turn are defined by p-points/p-lines (Radial Dimension P-Point, RPPT element) or
3D positions (Radial Dimension Position Point, RPOI element). As with Linear
Dimension Points, it is possible to use a RULE to parameterise 3D positions. It is not
possible to create more than two Radial Dimension Points. A PDIM will be drawn when
two significant dimension points are defined. It is not normally necessary to navigate to
the two individual Dimension Points.
The first dimension point will be at the centre of the dimension, the second will define
the circumference of the dimension. A PDIM contains the same style attributes as
an RDIM (see Section 3.5.2, but does not have DDNM/DDNX and AKEY attributes. As
with RDIMs, the meaning of the ’#DIM’ dimension text is defined by the DFLAG
attribute. The dimension points contain no style attributes. Figure 3-31 shows a simple
example PDIM (bold line - other dimensions are RDIMs).
The dimension radius will be the distance between the two dimension points as
projected into the VIEW, not the true 3D distance between these points. This projected
distance defines the value reported in the dimension text. This is consistent with the
functionality for Linear Dimensions (LDIMs) with Direction TRUE (see Section 3.4.3).

Version 11.5
Dimensioning
Figure 3-31 Pitch Circle Dimension - example
3.6.1 Creating Pitch Circle Dimensions

The PDIM position is defined by two p-points, p-lines or positions, for example:
NEW PDIM Create PDIM
PCEN IDP @ Define centre point as p-point position
PCIRC IDP @ Define circumference point as p-point position
NEW PDIM
PCEN POS @ Define centre point as 3D position

Version 11.5
Dimensioning
PCIRC IDP @
The PCENTRE command defines or redefines the centre point of a PDIM. For example:
PCEN IDP @
Position centre point on p-point - creates an RPPT
PCEN IDPL @
Position centre point on p-line (start) - creates an RPPT
PCEN IDPD @
Position centre point at a distance along a p-line - creates an RPPT
PCEN POS @
Position centre point at a 3D position - creates an RPOI
PCEN POS IDP @
Position centre point on p-point position - creates an RPOI
PCEN POS IDPL @
Position centre point on p-line (start) position - creates an RPOI
PCEN POS IDPD @
Position centre point at a distance along a p-line - creates an RPOI
PCEN @
Position centre point on a p-point (and set DDEG if possible)
If the existing centre point is the wrong database type, then this command will delete it
and create a point of the correct type.
The PCIRCUMFERENCE command defines or redefines the Circumference point of a
PDIM:
PCIRC IDP @
Position circumference point on p-point - creates an RPPT
PCIRC IDPL @
Position circumference point on p-line (start) - creates an RPPT
PCIRC IDPD @
Position circumference point at a distance along a p-line - creates an
RPPT
PCIRC POS @
Position circumference point at a 3D position - creates an RPOI
:
etc (as for PCEN)
This creates or redefines the circumference point of the PDIM. As with the PCEN
command, an RPPT or RPOI element is created as appropriate. If necessary the existing
circumference point is deleted. DDEG normally remains unchanged. However, the
command
DDEG TRUE
will change DDEG so that the dimension line passes through the circumference point.
A PDIM may be defined using two cursor hits. These define the Dimension Points and
set DDEG for a PDIM but do not set DTRAD. For example:

Version 11.5
Dimensioning
NEW PDIM PCEN IDP @ PCIRC @

Individual RPPT Dimension Points may be redefined using the ON command. Individual
RPOI Dimension Points may be modified by the POS command. If a RULE is required to
parameterise the 3D position, then this must be set or deleted explicitly at the RPOI.
3.7 Angular Dimensions
3.7.1 Angular Dimensions and How to Create Them

This section concentrates on those features which are unique to angular dimensions.
Figure 3-32 shows a simple angular dimension.
The simplest type of Angular Dimension consists of a pair of directions in the Design
model (the dimension directions) which radiate out from the dimension origin.
These directions are projected onto the drawing and are represented by projection
lines. Between these lines a dimension arc is drawn centred upon the dimension
origin. Each dimension arc and projection line may have a piece of text associated with
it.
Angular Dimensions share many of the properties of Linear Dimensions; they may be
single or multi-valued, chained or parallel, and if parallel the dimension arcs may be
truncated. In the case of parallel dimensions the projection lines will be automatically
‘gapped’ if their overshoot is sufficiently large (for instance where there is projection line
text) to cause them to cross dimension arcs.
Figure 3-32 Single Value Angular Dimension

An Angular Dimension cannot be drawn until its origin and dimension have been
properly defined. This could be done by typing the following commands, starting at
Layer level:

Version 11.5
Dimensioning
NEW ADIM - Create new Angular Dimension element

ON ID @ - Use cursor to nominate Dimension origin
FROM @ TO ID @ - Use cursor to nominate items defining first and
second Dimension Directions
Having pressed Enter when the confirmation command line appears, the Dimension will
appear on the display. A pair of Dimension Direction elements will have been
automatically created, with the last direction becoming the current element.
The ON command sets the DDNM attribute of the ADIM to the name of the element at
the Dimension origin. The NPPT attribute of the ADIM is set to the p-point which is the
origin position. In the example above, NPPT will be set to a default value which equates
to the origin of the element named by the DDNM.
In this example the Dimension Directions will be DPPT elements - the directions are
defined by lines drawn from the origin of the ADIM to the specified p-points (in this case
the origins of the specified nozzles). The DPPT also has DDNM and NPPT attributes. In
this case DDNM is set by the FROM or TO keyword to the name of the Design element
which defines the Direction, NPPT being the specific p-point within the Design element
(the origin by default).
Any p-point can be nominated to define a Dimension Direction by replacing the FROM
@ command above by FROM IDP @.
The other types of Dimension Direction that may be owned by an ADIM element are:
• DPOI - allows the direction to be defined by any given 3D position
• ADIR - allows the direction to be defined by any given 3D direction
• APPT - allows the direction to be defined by any given p-point direction
DPOI elements would be created by a sequence such as:

NEW ADIM
ON ID @
FR POS @ TO POS @
Here the FROM and TO commands set the POS attribute of each DPOI to the position
defined by the cursor.
ADIR elements would be created by a sequence such as:
NEW ADIM
ON ID @
FR DIR N30E TO DIR S20W
The DIR attribute of each ADIR will be set to the specified direction. If the PLTX
attribute is set to ’#DIR’, the projection line direction (as specified by DIR) will appear as
projection line text. #DIR is an example of intelligent text - see Section 5.
APPT elements would be created by a sequence such as:
NEW ADIM
ON ID @
FR DIR IDP @ TO DIR IDP @

Version 11.5
Dimensioning
Here the PPDI attribute of each APPT will be set to the number of the p-point of the
nominated element which defines the Dimension Direction.
In each example above, the FROM keyword defines the Direction at the start of the
Dimension’s member list, TO defines a Direction after the last item in the list. The
Directions will be drawn in the order in which they appear in the list, and the rotational
direction between the Directions is determined by the minor arc between the first two
Directions.
The above examples show the easiest way of creating ADIM elements, but many other
methods are available. The dimension origin can be defined explicitly as a 3D point, as a
p-point, as a Branch Head or Tail or as (the origin of) any Design element; similar
considerations also apply when defining the Direction elements.
An example of a chained Angular Dimension is shown in Figure 3-33.
Figure 3-33 Chained Angular Dimension

Such a dimension is created in a similar way to a chained Linear Dimension. Notice how
the Dimension Arc text is (automatically) oriented and positioned relative to the
Dimension Arc so as to make it easiest to read.
Additional ‘links’ can be inserted in or added to a chained Dimension (or a single-valued
Dimension can be ‘converted’ to a chained Dimension) by using the INSERT command in
a similar way to with Linear Dimensions.
The SORT DIM command can also be used with Angular Dimensions to reorder any
incorrectly ordered Directions.
An example of a parallel Angular Dimension is shown in Figure 3-34.

Version 11.5
Dimensioning
Figure 3-34 Parallel Angular Dimension

A parallel Dimension can be produced simply by setting the LCHA attribute of an ADIM
to PARA (a chained dimension has LCHA CHAI).
3.7.2 Principal Attributes of Angular Dimensions

Those attributes of a linear Dimension which most affect its general appearance -
namely DOFF, DPOS, LCHA, OSHT and PLCL - are all the same as or similar to those
for Linear Dimensions, and are set in the same way. Those attributes which relate to
the dimension line of a Linear Dimension relate to the dimension arc of an angular
dimension, and those attributes which relate to the projection line of a linear dimension
relate to the dimension radius of an Angular Dimension.
DOFF for an Angular Dimension is the radius of the dimension arc and is set by the DIM
RAD command (cf DIM OFFS). Clearly, the PLDI (projection line direction), DIR
(projection line direction) and TLIN (true length) attributes do not apply to Angular
Dimensions.
The SENSE attribute enables the rotational direction of the Dimension to be changed.
The standard value is that given by the minor arc from the first to the second dimension
point. The rotational sense may be altered by using:
SENSe REVerse
The standard sense may be restored using:
SENSe STANdard

Version 11.5
Dimensioning
WARNING: This attribute should be used with caution. It is primarily intended for
use with parallel Dimensions or those containing two points only.
Chained or truncated Dimensions with more than two points will
contain overlapping arcs.
It is also possible to specify an explicit rotational sense:
SENSe CLOCkwise or SENSe ANTIclockwise
However, standard or reverse sense should be used with parallel dimensions.
3.7.3 Detail Attributes of Angular Dimensions

Angular Dimensions have the same TRUN and DMSP attributes as Linear Dimensions.
Dimension arc and projection line (dimension radius line) text is set and positioned in
the same way as for linear dimensions. Projection line gaps are also handled in the same
way.
At ADIMs the default setting of attribute DMTX is ’#DIM~0’. This produces a degree
symbol after the angle value, which is output to one decimal place. (See Section 5 for
details of ‘hash codes’, e.g. #DIM.)
The DTANGLE (Dimension text angle) attribute is available for Angular Dimensions
and their Dimension Points. However, the settings are restricted to the following:
DTANG HORIZ
DTANG VERT
DTANG STAN
DTANG DEF
The meanings of these settings are similar to those for Linear Dimensions (see Section
3.4.4).
3.8 Identifying Dimensions

The cursor may be used to identify Dimensions and Dimension Points/Directions as
follows:
ID LDIM @
ID ADIM @ - identify Dimension nominated by cursor
ID @ - identify Dimension Point/Direction nominated by cursor
Dimensions can also be highlighted - see Section 6.6, Part 1, Basic Drawing Creation &
Output.
3.9 Suppressing the Display of Dimension and Projection

Lines
The display of either the dimension- or projection lines of a Linear or Angular

Dimension may be suppressed using the DLFG attribute of the LDIM:

Version 11.5
Dimensioning
DLFG PROJ
causes only the projection lines of a Dimension to be drawn. The setting of the LCHAIN
attribute is ignored in this case - all dimensions are treated as chained. This enables
coordinate dimensions to be output - with the coordinate reported in the projection-line
text.
DLFG DIM
causes only the dimension lines of a Dimension to be drawn. The default setting, causes
both dimension- and projection lines to be drawn:
DLFG ALL
3.10 Dimensioning Skewed Pipe in Isometric Views

Dimensions on skewed Pipe in isometric views can have misleading graphics. This can
be avoided by using a constructed Dimension Point, whose position is defined by a
RULE set which gets one coordinate of position from one Component and the remainder
from another. This constructed Dimension Point can then be used with either
Component to draw Dimensions with sensible graphics.
For example, an elevation Dimension is required between a Valve and an Elbow in
skewed pipe. Sensible graphics can be achieved by the following:
NEW LDIM
FROM valve_id
NEW DPOI
RULE SET POS (E (POS(1) OF <valve_id> WRT /* ) $
(N (POS(2) OF <valve_id> WRT /* ) $
(U (POS(3) OF <elbow_id> WRT /* )
RULE EXEC POS
A copy of this Dimension Point can be used in other Dimensions to dimension between
the Elbow and the Easting/Northing of the Valve.
See the manual VANTAGE PDMS DRAFT Administrator Application User Guide for
more details about rule sets.
3.11 Updating Dimensions
If the VIEW XYPS is changed, or if the positions of Design elements are changed, the
positions of Dimensions on the Sheet will not change automatically. For the necessary
repositioning to occur the command:
UPDATE ANNO
must be given. The above command will affect the current element (and elements below
it). Commands of the form:
UPDATE element_identifier ANNO

Version 11.5
Dimensioning
(where element_identifier would typically be a DRWG, SHEE, VIEW, LAYE etc) are also
valid. Such a command can, of course, be given from any position in the hierarchy; only
annotation relating to the named element will be updated.
The ANNO keyword can be omitted if element_identifier defines a piece of annotation
only, for example, LDIM.

Version 11.5
Dimensioning
Summary of Commands
Creating Linear Dimensions . . .

FROM ID @ - create a Dimension start point
TO ID @ - create subsequent Dimension Points
INSERT ID @ - create a Dimension Point in order
TO AFT ID @ - create a Dimension Point ‘after’ (with respect to dimension

direction) nominated Design item
TO BEF ID @ - create a Dimension Point ‘before’ (with respect to dimension

direction) nominated Design item
TO POS @ - create a dimension Point at a 3D Design World coordinate
TO IDP @ - create a dimension Point at a p-point
TO IDPL @ - create a dimension Point at a p-line
Autoblanking . . .
AUTOBLANKING ON/OFF
- switches autoblanking ON or OFF for a DRAFT session
BLNK TRUE/FALSE
- sets autoblanking for the current element, which can be
LDIM, ADIM, RDIM, PDIM, GLAB, SLAB, VNOT, or NOTE.
BMAR value - specifies the blanking margin, where <value> is a real value
which is greater than or equal to 0.0.

Version 11.5
Dimensioning
Positioning the dimension line . . .

DPOS @ - set Dimension line position through a paper position (DPOS)
DOFF value - set a Dimension line position as an offset from the first
Dimension Point explicitly
DIM OFFS - convert a DPOS attribute to DOFF (offset distance from the
first dimension point)
DIM ABS - convert a DOFF attribute to DPOS (absolute paper coordinate)
Setting dimension directions . . .

SORT DIM- rearrange Dimension Points into a logical sequence
DIR value - sets Dimension direction & uses standard PDMS direction
syntax, or you can use a design p-point direction - sets DIR
PLDI value - set projection line direction via a direction or angle - sets
PLDI
DIR TRUE - set dimension line direction to be that calculated from the
first & second p-points - sets TLIN true
Creating and modifying radial dimensions . . .

NEW RDIM - creates RDIM element
ON ID @ - use cursor to define dimension centre
AKEY word - sets AKEY to give a diameter or radius dimension as required

(default DIAM)
DIM @ - defines both dimension angle DDEG and text radius DTRAD
in one go. (Dimension text origin will be at cursor crosshair
position.)
MODIFY @ - modifies DDEG, DTRA or DTOF attributes by cursor
interaction
Creating pitch circle dimensions . . .

NEW PDIM - creates PDIM
PCEN IDP @ - defines centre point as p-point position
PCIRC IDP @ - defines circumference point as p-point position

Version 11.5
Dimensioning
NEW PDIM
PCEN POS @ - defines centre point as 3D position
PCIRC IDP @
PCEN IDP @ - positions centre point on p-point - creates an RPPT
PCEN IDPL @ - positions centre point on p-line (start) - creates an RPPT

PCEN IDPD @ - positions centre point at a distance along a p-line - creates an
RPPT
PCEN POS @ - positions centre point at a 3D position - creates an RPOI
PCEN POS IDP @ - positions centre point on p-point position - creates an RPOI
PCEN POS IDPL @ - positions centre point on p-line (start) position - creates an
RPOI
PCEN POS IDPD @ - positions centre point at a distance along a p-line - creates an
RPOI
PCIRC IDP @ - position centre point on p-point - creates an RPPT
PCIRC IDPL @ - position centre point on p-line (start) - creates an RPPT

PCIRC IDPD @ - position centre point at a distance along a p-line - creates an
RPPT
PCIRC POS @ - position centre point at a 3D position - creates an RPOI

:
:
etc
NEW PDIM PCEN IDP @ PCIRC IDP @

defines Dimension Points and sets DDEG
Creating angular dimensions . . .

ON ID @ - specify the Design item which will be referenced for an
Angular Dimension - sets DDNM
FROM DIR option - creates a Dimension start point with the direction set as the
p-point specified - sets DDNM & PPDI, or if direction
specified - sets DIR. options: PA, PL, PH, PT, PPoint, IDP, N,
S, D, E, W, X, Y, X, HH, HT
TO DIR option - creates subsequent dimension Point with direction set as
p-point specified - sets DDNM & PPDI, or if direction specified
- sets DIR
DIM RAD value - sets the dimension line position as an offset radius from the
first Dimension Point - sets DOFF
SENSE REV
SENSE STAN changes rotational sense of angular dimensions

Version 11.5
Dimensioning
Setting dimension line text . . .

DTOF option - set dimension text offset distance from origin. Options:
STAN - sets to 0 0
DEF - sets to Dimension default value
@ - set via cursor-constructed point,
e.g. DTOF ENDP OF /LINE1 QUAL X500 Y500
DTOF N 1 @ - move x coordinate of dimension text origin to cursor position (y
coordinate not changed)
DTOF N 2 5 - change y coordinate of dimension text origin by 5mm (x
DMTX ’text’ - set dimension text as text string. Unsets from #DEF (i.e. #DIM)
DTCH value - sets text character height in mm
DTLH value - sets text letter height in mm (=0.8 * character height)
DLPN value - sets dimension line pen number
DLPN DEF - sets dimension line pen number to Dimension default value
DTPN value - sets dimension text pen number
DTPN DEF - sets dimension text pen number to Dimension default value
DTANGLE STAN - sets dimension text angle to STANDARD
DTANG HORIZ - sets dimension text angle to HORIZONTAL
DTANG VERT - sets dimension text angle to VERTICAL
DTANG EXTERN - sets dimension text angle to EXTERNAL
DTANG PARA - sets dimension text angle to PARALLEL
PTANG DEF - sets dimension text angle to DEFAULT
Setting projection line text . . .

PTOF option - set projection text offset distance from origin. Options:
STAN - sets to 0 0
DEF - sets to Dimension default value
@ - sets via cursor-constructed point,
e.g. CENTRE OF /CIRCLE1
PTOF N 1 @ - move x coordinate of projection line text origin to cursor position

Version 11.5
Dimensioning
(y coordinate not changed)
PTOF N 2 5 - change y coordinate of projection line text origin by 5mm (x

PLTX ’text’ - set projection text as text string. Unsets from #DEF (i.e. #DIM)
PTCH value - sets text character height in mm
PTCH DEF - sets projection text character height to Dimension default value
PTLH value - sets text letter height in mm (=0.8 * character height)
PJUS option - sets projection text justification . Options:

TOW
AW
C
DEF (default)
PTPN value - sets projection text pen number
PTPN DEF - sets projection text pen number to Dimension default value
PLPN value - sets projection line pen number
DPEN value - sets both dimension and projection line pen numbers
DTXPEN value - sets both dimension and projection text pen numbers
PTANGLE HORIZ - sets projection text angle to HORIZONTAL
PTANG VERT - sets projection text angle to VERTICAL
PTANG STAN - sets projection text angle to STANDARD
PTANG DEF - sets projection text angle to DEFAULT
Setting gaps . . .
GAP @ - specifies a gap in a projection line by giving start & finish points
GAP AT @ - specifies a default length gap of 2mm in a projection line by a

single point
SETDEF GAP value - sets default gap length
GAP AT @ L value - specifies a gap by giving a single point
GAP DELETE @ - deletes a gap identified by cursor
GAP DELETE ALL - deletes all gaps on the current projection line or dimension line

Version 11.5
Dimensioning
GAP TIDY - deletes all unused gaps (Radial Dimensions only)
Miscellaneous operations on dimensions . . .
LCHA PARA - sets dimension type to Parallel
LCHA CHAI - sets dimension type to Chained
DMSP value - for Parallel Dimensions, sets separation spacing explicitly
DMSP @ - for Parallel Dimensions, sets separation spacing using cursor
TRUN BY value - for Parallel Dimensions truncates dimension lines by a

percentage specified
TRUN TO value - for Parallel Dimensions truncates dimension lines to a
specified value in mm
DTER option - set dimension line terminator. Options: ARR, OBL, DOT, OFF
FTER option - set first dimension line terminator. Options: ARR, OBL, DOT,
OFF, DEFAULT
TSIZ 4 - set terminator size to 4mm (default 3mm)
OSHT value - sets projection line overshoot explicitly
OSHT @ - sets projection line overshoot using cursor
OSHT TOP /CIRC1 - projection line overshoot defined by a constructed point
PLCL value - sets projection line clearance explicitly
PLCL @ - sets projection line clearance using cursor
DLFG PROJ - draw projection lines only
DLFG DIM - draw dimension lines only
DLFG ALL - draw projection and dimension lines (default)
Radial Dimensions:
AKEY option - stores the code of a dimensional attribute of the Design
element type which is to be dimensioned. Option dependent
on Design element type. Default DIAM.
DFLA option - controls whether the dimension line is drawn from the centre
(Radius) or across the diameter (Diameter).
option = DIAMETER or RADIUS, default RADIUS.
DDEG value - controls angle at which dimension line is shown, relative to

Version 11.5
Dimensioning
the 2D
DDEG @ - coordinate system of the VIEW. Default 0 (horizontal in the
VIEW).
DTFL option - controls whether the text radius DTRAD is measured from the
CENTRE, MIDPOINT or CIRCUMFERENCE of the radial
dimension. Default CENTRE.
DTRA value - radial position of the dimension text origin from the centre or
circumference DTRA @ (according to the DTFL setting) of the
dimensioned object.
DTRA FLAG option - modifies DTFL and recalculates DTRA to keep same visual
appearance. option = CENTRE, MIDPOINT or
CIRCUMFERENCE.
DTAN option - controls the Dimension text angle. option = STANDARD,
HORIZ, VERT, default STANDARD.
DSTY option - ombined with DTAN, controls the overall dimension style. Option
= DIMLINE, LEADERLINE, EXTERNAL, default DIMLINE.
CHPN option - controls the pen used for the optional horizontal and vertical fixed
crosshair markers which mark the centre of the circle/arc being
dimensioned. option = OFF or integer, default OFF.
CHOS value
CHOS @ - controls the distance by which the crosshairs overshoot the
circle/arc circumference. value can be negative, default 6.
ASUB value - controls the angle subtended by the optional projection arcs
at the circle/arc circumference. For DFLAG DIAMETER two
arcs are drawn, one at each end of the dimension line; for
DFLAG RADIUS only one arc is drawn. The midpoint of these
arcs will intersect the dimension line. ASUB 180 generates a
circle for a diameter dimension.
MODIFY @ - allows interactive modification of Dimension, with graphical
feedback.
Querying . . .
Q DESC - (at Dimension or Dimension Point)
- gives dimension direction and Dimension Points (Linear
Dimensions)
- gives dimension origin and Dimension Points (Angular
Dimensions)
- reports whether a Radius or Diameter dimension is required
(Radial Dimensions)
- names the Design element and attribute dimensioned (RDIMs)
- gives the Radial Dimension Points (PDIMs)
Q SETDEF - (at Dimension or Dimension Point) - gives default gap length

Version 11.5
Dimensioning
and PKDI setting
Q DDNM X coord
Q DDNM Y coord
Q DDNM X coord Y coord - gives the X and/or Y Sheet coordinate(s) of the 3D
position of either the p-point specified by the NPPT
attribute or the position specified by the PKEY and
PKDI attributes. These values may be useful when
attempting to position GLABs and SLABs neatly.
Q EXTENT DMTX
Q EXTENT PLTX - (at Dimension Point) - gives Sheet area occupied by
Dimension - Text/Projection Line Text
Q PCENTRE - (at a PDIM) - gives centre point of dimension
Q PCIRC - (at a PDIM) - gives circumference point of dimension
Q AKEYLIST - (at a Design element) - lists possible AKEY settings for element
type
Deleting unwanted dimension points . . .

DELETE NULL ANNO - deletes all RDIM, DPPT, DPBA and APPT elements with
DDNM set to NULREF. For PDIMs, if the first
dimension point (RPPT element) is inaccessible, then
the entire PDIM will be deleted; if only the second
dimension point (RPOI element) is inaccessible, then
only that dimension point will be deleted, leaving the
PDIM and its centre point still defined.

Version 11.5
4 Labelling
4.1 Introduction
Labels are a form of drawing annotation, comprising text and/or graphics, associated
with Design items or Views. The Label elements are the General Label (GLAB), and
the Special Label (SLAB). SLABs are similar to GLABs except that they are generated
from templates rather than individually.
Label elements are owned by Layers or Views; SLAB templates (Text Label
Templates, (TXTMs)) exist as members of Label Libraries (LALBs). The relevant part
of the DRAFT database hierarchy is shown below.
LIBY
LAYE
LALB
GLAB SLAB
TXTM SYTM
DDNM
DDNM TMRF
Design database
element or VIEW
Figure 4-1 DRAFT Database Hierarchy - Label Elements

Labels may be created individually, or automatically following the definition of a set of
rules controlling the elements to which the Labels are to be applied (see Section 4.4).
Figure 4-2 illustrates a typical Label, showing its principal features and attributes.

Version 11.5
Labelling
Figure 4-2 A typical Label element
The main features of a Label are:

• Label Attachment Point. The 2D VIEW position equivalent to a user-specified p-
point or distance along a p-line or (by default) the origin of the Design item with
which the Label is associated.
• Label Origin. A position within the body of the Label which is used to position it.
• Label Position. A 2D position within the VIEW at which the Label’s origin is
placed; this may be an absolute VIEW position or a position relative to the Label’s
attachment point.
• Leader Line. A line from the connection point to the Label attachment point.
• Leader Line Connection Point. A position, defined relative to the Label origin, to
which the leader line is drawn.
• Leader Line Connection Point. A position, defined relative to the Label origin, to
which the leader line is drawn.

Version 11.5
Labelling
4.2 Creating and Manipulating Labels
4.2.1 Creating Labels and Label Text

The example Label shown in Figure 4-2 could be created simply by typing the following
(starting at LAYE) level:
NEW GLAB - create new General Label (or NEW SLAB to create a
Special Label)
DDNM ID @ - position Label attachment point using cursor
The above two commands are all that is needed to create a Label with the features
shown in Figure 4-2; the text which appears in the Label frame is by default the name
of the Design element at the Label attachment point, all other attributes having default
settings cascaded down from the owning Layer.
The Label attachment point will be at the origin of the element specified by the Label’s
Design Data Name (DDNM) attribute.
For elements that have p-points or p-lines the attachment point can be varied by setting
the NPPT or PKEY attributes to the specified p-point number/p-line name respectively.
For example:
NPPT 2 - set NPPT to (p-point) 2
PKEY TOS - set PKEY to p-line TOS (top of steel)
PKEY MEML - set PKEY to member line
For elements with p-lines the attachment can be further varied by setting the PKDI (p-
line distance) attribute. See Section 7.5.3 for details.
The ON command allows the DDNM and NPPT or PKEY/PKDI attributes to be set
simultaneously. For example:
ON ID@
ON /PUMP1-1/NOZZ1
ON IDP @
ON P2 OF NOZZ4 OF EQUI /1101
ON PHEAD OF /BRAN2-1
ON PLEAVE OF /VALVE3
ON IDPLINE @
ON PPLINE BOS OF /SCTN.PN1_PN5
ON IDPDISTANCE @
ON PPLIN TOS OF /SCTN5 PROP 0.8
With the ON command it is also possible to specify an absolute distance along a p-line,
although the value given will be converted to a proportional value for storage in the
database:
ON PPLIN TOS OF /SCTN4 2500 FROM START
ON PPLIN BOS OF /SCTN5 1000 FROM END

Version 11.5
Labelling
If the FROM keyword is omitted then FROM START is assumed.

When using the ON command if values for NPPT, PKEY and PKDI are not specified
then the defaults will be used - any existing values may be overwritten.
The Label attachment point can be offset from the DDNM using the APOF
(Attachment Point Offset) attribute. This defines an offset position (in VIEW
coordinates) measured from the p-point/p-line distance referenced by the Label. The
leader line will be attached to this point (although if the clearance attribute (LLCL) is
set the leader line will overshoot or stop short of it). This means that the leader line and
its terminator can be moved away from the p-point to any desired position. By default
APOF will be (0,0) - i.e. no offset. APOF may be set directly, for example:
APOF 15 0
or in terms of Sheet coordinates by:
LEAD ATTA X455 Y677
LEAD ATTA @
The offset may be removed by:
LEAD ATTA DELETE (or APOF 0 0 or APOF UNSET)
The Body Text (BTEX) attribute is by default set to the ‘intelligent text’ string
#NAME, which translates to the name of the Design element at the attachment point
when the Label is created. If the Design element at the attachment point is unnamed,
‘#NAME’ will appear in the Label frame. BTEX can be set explicitly by commands such
as
BTEX ’NOZZLE 2’
or can be set using a combination of explicit and intelligent text. For example, the
commands
BTEX ’NOZZLE 2
Text*#NAME’
would produce the Label shown in Figure 4-3. Note how the size of the Label frame
automatically adjusts to accommodate the specified text.
Figure 4-3 Label Text

See Section 5 for a full description of intelligent text.

Version 11.5
Labelling
The extent of the text defined by the BTEX setting can be queried by
Q EXTENT BTEX
See Section 9.5 for details.
Label text can be edited through use of the EDTEXT command. For example, if the
target string is ‘NOZZLE 2’:
EDTEXT ’NOZZLE 2’ ’NOZZ 1-2’ - change Label text to ‘NOZZ 1-2’
not the resultant text. See Section 6.4 for full details of the EDTEXT command.
4.2.2 Labelling Views

Labels (GLABs and SLABs) can be applied to Views, allowing View names, scales, etc to
be applied easily. The Label is associated with the View by setting its DDNM attribute
to the View, either directly or using the ON syntax. For example:
DDNM View
ON /View99
4.2.3 Positioning and Orienting Labels

When a Label is created, its origin (held as the XYPS attribute) is placed at a fixed offset
(default x 25mm, y 25mm) from its attachment point. The Label origin (and hence the
Label) may be moved by the AT @ command, which resets XYPS to the position
specified by the cursor. This command calls up the Point Construction Option Form, which
contains the point construction Option list button which allows positions to be defined
in terms of end-points, intersection points, etc.
If the Label’s OSET attribute is TRUE then the origin is held as an offset from the
attachment point; if OSET is FALSE then the Label origin is held as an absolute Sheet
coordinate.
Note that the coordinates specified with the AT command (whether explicit or from
cursor input) are always taken to be absolute coordinates, irrespective of the OSET
setting. To avoid any potential confusion when positioning labels explicitly, several
alternatives are available. For example:
OFFS X45 Y45
Set Label origin to given offset coordinates. XYPS set to offset
coordinates (from Label attachment point)
OFFSET
Convert XYPS (absolute coordinates) to offset coordinates (Label will
not move). Equivalent to OSET TRUE.
ABSOLUTE
Convert XYPS (offset coordinates) to absolute coordinates (Label will
not move). Equivalent to OSET FALSE.

Version 11.5
Labelling
AT X300 Y200 ABS

Set Label origin to given absolute coordinates. XYPS set to absolute
coordinates.
AT X300 Y200
Set Label origin to given absolute coordinates. XYPS set to offset
coordinates (from Label attachment point)
XYPS 20 20
Set Label origin as given coordinates, taken as offset if OSET TRUE,
absolute if OSET false. (XYPS @ also available).
Note: When a Pipe element is labelled directly, the Pipe origin is assumed to be the
position of the HEAD of the first Branch visible in the VIEW region, if any. If no
Branch HEADs are visible in the VIEW region, then the position of the HEAD
of the first Branch is used.
Constructed points (see Section 11) may also be used for Label positioning operations.
See Summary of Commands section at the end of this Section for examples.
Labels may be oriented by the ANGLE command, which sets the Label’s ADEG attribute
if an angle is specified explicitly, or the PPDI attribute if the orientation is specified as a
p-point direction. (The p-point must belong to the associated Design item DDNM but
need not be the same as the Label’s attachment point). For example:
ANGLE 30
Set angle of turn to 30 degrees (see Figure 4-4)
ANGLE IDP @
Specify orientation as p-point direction using cursor
ANGLE P2 OF BOX 1 OF /1502B
Specify p-point direction explicitly
ANGLE PPLIN NA OF /SJ1-1
Specify orientation as p-line direction (of secondary joint)
Figure 4-4 Label Orientation

Version 11.5
Labelling
4.2.4 Label Frame Manipulation

The Label frame may be hidden or shown simply by typing
FRAME ON or
FRAME OFF
as appropriate. The frame clearance (the distance between the edge of the Label text
and the edge of the frame is set by typing (for example):
FRAME CLEARANCE 4 - set frame clearance to 4mm (see Figure 4-5)
The FRAME CLEARANCE command sets the Label’s GBOX attribute (default setting
1mm).
Figure 4-5 Frame Clearance
The frame may be drawn in any desired pen, specified by a command such as
FRA PEN 6 (sets the LFPN attribute)
Similarly, the leader line pen may be set using the LEAD PEN command. The frame and
leader line pens may be set simultaneously by setting the Label’s LPEN attribute to the
desired pen number. See Section 8, Part 1, Basic Drawing Creation & Output, for pen
options.
4.2.5 Hiding Labels

A Label’s visibility is controlled by its LVIS attribute:
LVIS TRUE - the label is visible (the default)
LVIS FALSE - the label is invisible
This facility could be used to hide labels attached to obscured Design elements.

Version 11.5
Labelling
4.2.6 Autoblanking
Autoblanking can be used to hide design graphics in areas close to annotation. For
details, see Section 2.2.
4.2.7 Label Text Manipulation

Character height and spacing, and line spacing are all definable, as is the text
justification.
The set of attributes which control the appearance of a Label text is:
CHEI - character height (default 4mm)
LHEI - letter height (0.8* character height)
CSPA - character spacing factor (default 0)
LSPA - text line spacing factor (default 0)
Initial (default) values of all these attributes are cascaded to GLABs from their owning
LAYE. All the above attributes are set directly, for example:
CHEI 6 (LHEI automatically set to 4.8)
CSPA 1
LSPA 1
The character height and letter height attributes are discussed further in Section 6.
CSPA and LSPA may be given negative values. For CSPA, small negative values (of the
order of -.1) will cause text to become compressed (values much smaller than this are not
useful). For LSPA, values of the order -.1 will compress lines, values of the order -3 will
reverse the order of lines. (Limits are -10 to +10 for LSPA, -0.5 to +10 for CSPA.)
Figure 4-6 illustrates the effects of varying the character spacing and line spacing.
Figure 4-6 Label Text - Character Spacing and Line Spacing

Text justification and vertical alignment are controlled by the settings of the JUST and
ALIG attributes, which may have the following alternative settings:

Version 11.5
Labelling
JUST L - Text left justified (default)

JUST C - Text centre justified
JUST R - Text right justified right
ALIG BB - Text aligned with bottom of body (default)
ALIG HB - Text aligned halfway up body
ALIG TB - Text aligned with top of body
ALIG BASE - Text aligned with base of first character (on first line
of text)
Here, horizontal justification is relative to the Label origin, vertical alignment is relative
to the text body - the area occupied by the text. The text base ignores text descenders
(for example, the tail of a ‘p’ or a ‘y’).

Version 11.5
Labelling
Figure 4-7 illustrates the effect of varying these attributes.
Figure 4-7 Horizontal Justification and Vertical Alignment

In Figure 4-8, the symbol shows the text string origins for BBODY and BASE
alignments. For a multi-line text string (as shown), the origin is at the baseline of the
first line of text.
ALIG BBODY ALIG BASE
Figure 4-8 Text Base/Body Alignments

Version 11.5
Labelling
The Label FONT attribute controls the Label text font - see Section 6 for details of text
fonts.
The TPEN attribute controls the text colour - see Section 8, Part 1, Basic Drawing
Creation & Output for details of pen settings.
4.2.8 Leader Lines

For Labels, a leader line may or may not be drawn. If drawn it will join the Label’s
leader line connection point with its attachment point, and may have gaps in it.
The leader line is turned on and off simply by typing
LEADERLINE OFF or
LEAD ON
as appropriate (these commands set the Label’s LLEA attribute).
The leader line may terminate with an arrow, a dot or nothing, at a definable distance
from the attachment point; this distance may be specified by setting either the leader
line clearance attribute (LLCL) or the attachment point offset (APOF)a position.
The terminator is controlled by the LTER attribute:
LTER ARROWS
LTER DOTS
LTER OBLIQUE
LTER OFF
These commands set the Label’s LTER attribute, which is set to ‘no terminators’ by
default.
The size of the terminator is controlled by the TSIZ attribute:
TSIZ 4 - set size to 4mm (default 3mm)
The initial settings of LTER and TSIZ are cascaded down from LAYE level.
The leader line clearance (attribute LLCL, 0mm by default) is set as follows:
LLCL 4 - clearance 4mm
The attachment point offset (APOF), unset by default, is set by commands such as:
APOF 3 0 - sets attachment point offset to be X3 Y0
Labels also have a POS attribute, which by default is unset. If the POS attribute is set,
the 3D World position specified will be used as the leader-line attachment point (rather
than the DDNM and NPPT or DDNM, PKEY, and PKDI attributes). A DDNM attribute
still has to be specified for the label to be properly defined. This allows labels to be
positioned at a calculated position (for example, in the centre of a Panel or half-way
along a GENSEC) without having to determine the most suitable p-point or pline to
reference.

Version 11.5
Labelling
The leader line may be straight or bent, with one or two bend point positions specified
either explicitly (by defining either a specific point within the VIEW or an offset from
the attachment point), or implicitly by specifying that the leader line is to contain a
vertical or horizontal portion.
Examples of commands used to specify the bend point explicitly are shown below, with
the results of the commands being shown in Figure 4-9.
Figure 4-9 Bending the Leader Line

Version 11.5
Labelling
LEAD BENT OFFS X7

Specify bend point as offset from Label attachment point
LEAD BENT OFFS X0 Y-60 X100 Y-60
Specify two bend points
LEAD BENT @
Specify bend point using cursor
LEAD BENT PT 2 @
Specify second of two bend points using the cursor
LEAD BENT PT 2 X722 Y40
Specify second of two bend points explicitly
LEAD BENT PT 1 OFF X15
pecify first of two bend points as offsets from Label attachment point
LEAD BENT PT 1 DEL
Delete first of two bend points
LEAD BENT @ @
Specify two bend points using cursor
LEAD STRAIGHT
Return to straight leader line
The above commands set the Label’s LSHA (Leader Line Shape) and BPOF (Bend-
Point Offset) attributes.
When defining two bend-points using a single command, the first point to be defined
should be the one nearest the 3D item labelled. The BPOF attribute stores one or two
pairs of coordinates defining the positions of the bend-points relative to the paper
position of the p-point to which the label is attached. The LSHA attribute defines how
the values stored in BPOF are to be interpreted. These attributes may be set (and
queried) directly, for example:
LSHA BENT
BPOF -50 0 -75 25
When defining bend point 2 of two individual bend points, bend-point 1 will be set to
Offset X0 Y0 if it does not already exist. When deleting bend point 1 bend-point 2 (if it
exists) will be made the new bend-point 1.
Depending on the position of the bend point, the leader line connection point may
change - see the bottom illustration of Figure 4-9 for an example.
In the case of a bent leader line specified as having a horizontal or bent portion, the
bend point will be at the intersection of the horizontal/vertical part of the line and a
sloping line drawn at a user-specified angle to the attachment point. The first of these
two portions to be specified will be at the end nearest to the attachment point. The
portion of the leader line nearest to the connection point will go to a corner of the Label
box if the horizontal/vertical portion is specified first, or to the middle of a box line if the
horizontal/vertical portion is specified last. See Figure 4-10 for examples of the
commands involved and their results.

Version 11.5
Labelling
Figure 4-10 Bending the Leader Line - Horizontal/Vertical Portions

If a Label’s position relative to its attachment point is changed then on Drawing
regeneration the leader line, if bent, will always be drawn specially - you don’t
necessarily have to redefine the bend point position.
4.2.9 Varying the Leader Line Connection Point

The Leader Line connection point can be offset from its standard position using the
CPOF (Connection Point Offset) attribute. This is STANDARD by default, which causes
DRAFT to determine the actual leaderline connection point. Other settings are ORIGIN,
which puts the connection point at the Label origin, or an explicit 2D value, which
offsets the connection point relative to the Label origin. See Figure 4-11.

Version 11.5
Labelling
ABC ABC ABC
CPOF STAN CPOF ORIG CPOF -3 0

Figure 4-11 Varying the Leader Line Connection Point
4.2.10 Leader Line Gaps

A leader line may have up to 10 gaps in it. These are most easily defined using the
cursor, with either the start and end points or a mid-point and a length being specified.
(In the latter case a default gap length will be assumed if a value is not specified.)
Examples of the relevant commands are:
GAP @
Insert gap by specifying start and finish points with cursor
GAP AT @
Insert gap of default length centred on cursor position
GAP AT @ L 5
Insert 5mm gap centred on cursor position
GAP OVER @
Insert gap by specifying start and finish points with cursor, and delete
all other gaps in line
GAP DELETE @
Delete gap specified by cursor
GAP DEL ALL
Delete all gaps on current Sheet
GAP TIDY
Deletes all unused gaps from Label
The default gap length may be set by using the SETDEFAULT GAP command, for
example
SETDEF GAP 5
Set default gap length to be 5mm
Gaps in Label leader lines can be sketched and erased in the same way as Dimension
projection line gaps - see Section 3.

Version 11.5
Labelling
4.2.11 Modifying Labels through Graphical Interaction

You can modify a label graphically by making it the current element and giving the
command
MODIFY @
The Annotation Modification Form will appear, and the selected Label is highlighted with
six pickable hot spots which enable the APOF, BPOF, CPOF, XYPS, and ADEG
attributes of the Label to be modified interactively.
Note: For this functionality to be available the Annotation Modification Form must be
loaded. The form contains the point construction Option list button which
allows positions to be defined in terms of end-points, intersection points, etc.
To modify the Label, click on the hot spot that you wish to move, and click on the new
position. A transient image of the Label will appear, which will move as the mouse is
moved. You can then do one of the following:
Click on OK on the form, to accept the changes you have made.
Cancel allows the command to be aborted with no change to the Label.
Reset causes the position of the current hot spot to be reset to its database position;
Delete causes the current hot-spot to be deleted or set to a default position:
A bend point will be deleted
The attachment point will be set to the p-point (i.e. APOF 0 0)
The connection point will be set to its default value (i.e. CPOF
STANDARD)
The angle of the label will be set to 0.
The Label position will not be affected.
4.3 Label Templates And Special Labels
4.3.1 Introduction
Label templates are a means of predefining the graphical appearance and text contents
of a Label. Label templates are stored in a Label Library (LALB), which, like a SHEE,
can be displayed in an area view. The templates can be positioned and picked off to be
used on a VIEW. Label Templates may be ‘textual’, having the same general appearance
as a General Label (GLAB) or ‘Special’.
4.3.2 Text Label Templates and Special Labels

The Text Template element (TXTM) has the appearance of a GLAB without the leader
line, and is referred to a VIEW by the drawing element Special Label (SLAB), via the
SLAB attribute TMRF (see Figure 4-1). The other attributes of SLAB are, for this
application, the same as for a GLAB.

Version 11.5
Labelling
The appearance of the SLAB is controlled by a combination of the attributes from both
the SLAB itself and the TXTM it references. The text and frame (i.e. the BTEX, NLPN,
MPEN, LFRA, GBOX, CSPA and LSPA attributes) are designated by the TXTM; the
rest, including the leader line, are controlled by the SLAB.
The following attributes on a Special label (SLAB) (settings cascaded from owning
Layer) may be set to use the TXTM value:
FONT Font
TPEN Text pen
LFPN Label frame pen
CHEI Character height
ALIG Text vertical alignment
JUST Text justification
If the attribute values are set to TEMPLATE, then the attributes on the template
(TXTM or primitives owned by an SYTM) are used for drawing the Label. Example
syntax:
TPEN TEMplate
CHEI TEMplate
If explicit values are set, then the SLAB attributes are used. These will override any
variation in pen colour or style between primitives in the original template for a Special
label.
The initial values for these attributes on a newly created SLAB are cascaded from the
Layer (LAYE). The values ‘Template’ must be explicitly set on the SLAB when required.
All four attributes affect the appearance of a text label. However, only the two pen
attributes will affect the appearance of a Special label. CHEI and FONT values have no
effect on appearance of a Special Label.
The text attribute of a TXTM (i.e. BTEX) can hold explicit and/or intelligent text, but for
the latter the expanded result will not be shown on the library Sheet and will only
appear on a VIEW once used from within a SLAB.
The ETEX (example text) attribute (of the TXTM) exists only as a documentary
attribute, which is useful for recording the results of intelligent text expansions. It is set
in the same way as BTEX.
The ATEX attribute of a SLAB may be set in the same way as BTEX (see below) and
may be used to provide a label identifier. Provided the BTEX attribute of the TXTM (or
of a TEXP element of an SYTM, see next section) is set to ‘#ATEX’, the SLAB label text
will always take the ATEX setting. If BTEX is set otherwise, the ATEX setting (if any)
will be ignored. For example, consider the command sequence:
NEW TXTM /TEMPLATE
BTEX ’Number #ATEX’
NEW SLAB
TMRF /TEMPLATE
ATEX ’99’
This would output a Label containing the text ‘Number 99’.

Version 11.5
Labelling
The following sequence of commands illustrates the use of SLABs and TXTMs (starting
at Library level).
NEW LALB - create new Label Library
NEW TXTM /TP1 - create new Template
BTEX ’#NAME’ - set label text
NEW TXTM /TP2
BTEX ’PUMP
Text*#NAME’
Following these commands, the Label Library could be PUT into an area view as
illustrated in Figure 4-12. Note: when a TXTM is created its XYPS attribute is not set -
this must be set before the Template can be drawn on the Library Sheet. Also, it may be
necessary to window in on the TXTM and/or adjust its CHEI attribute before it becomes
clearly visible.
The extent of the text defined by the BTEX setting can be queried by
Q EXTENT BTEX
See Section 9.5 for details.
Figure 4-12 Displaying Templates

Version 11.5
Labelling
Having created the Templates and displayed them, new SLAB elements can be created
which can be linked to the Templates by the TMRF attribute. The SLABs can then be
used on the Drawing Sheet. For example:
NEW SLAB - create new Special Label
TMRF ID @ - set template reference by using cursor to nominate template
in Library Sheet
Figure 4-13 shows the result of such commands, starting from the elements and the
display set up shown in Figure 4-12.
Figure 4-13 Application of Special Labels and Templates
4.3.3 SLAB Leaderline Connection Points

The leaderline connection point for SLABs is determined by the setting of its CPOF
attribute. This is STANDARD by default, which causes DRAFT to determine the actual
leaderline connection point. Generally, when the SLAB references a SYTM, this will be
at its origin. However if the first member of the SYTM’s list is:

Version 11.5
Labelling
• a CIRC primitive, and the SLAB is drawn undistorted (i.e. its XYSC values are
equal) then the leaderline will terminate at the CIRC
• a MRKP primitive, then the leaderline will terminate at the MRKP.
• a TEXP primitive, then the leader line will terminate at the opposite corner of the
test box, as occurs with GLABS.
The CPOF attribute can be defined in several ways using the LEADERLINE
CONNECTION command:
LEAD CONN @ - allows the point to be defined by cursor

LEAD CONN X30 Y35 - allows an explicit Sheet position to be specified
LEAD CONN OFFS X10 y-10
CPOF 30 30 } - allows a relative position to be specified
LEAD CONN STAN

CPOF STAN } - resets CPOF to its default value
LEAD CONN ORIG

CPOF ORIG } - sets CPOF to 0,0
The values stored in CPOF define the coordinates of the connection point relative to the
template’s origin and they are in the axis system of the template. Hence if the SLAB’s
orientation is changed the connection point will rotate with it.
For SLABs defined by a SYTM having a TEXP as its first member the leader-line will
terminate at the appropriate corner of the text-box (as occurs with GLABs) unless the
SLAB’s CPOF attribute defines a specific leader-line connection point.
NOTE: The CPOF attribute for a SLAB is an offset from the Label origin. For a SLAB
which references a TXTM, this is defined by the JUST and ALIG attributes of
the TXTM. Hence if the JUST or ALIG components of a TXTM are modified the
leaderline will be connected to a different part of the Label.
The selection system makes it possible to do a global change on the CPOF
attribute of all SLABS which use a given TXTM., using a macro such as:
VAR !A COLLECT ALL SLAB WITH (TMRF EQ /template_id ) FOR SHEE
DO !B VALUES !A
$!B
CPOF -5 10
ENDDO
Where the CPOF setting defines an offset from the new Label origin and
template_id is the TXTM name (which must be followed by a space).
4.3.4 Special Label Templates and Special Labels

SLABs may also reference Special Label Templates (SYTMs). SYTMs may be
members of LALBs or SYLBs (Symbol Libraries).

Version 11.5
Labelling
The appearance of SYTMs is completely user-definable, and may consist of any size and
combination of basic geometrical shapes (squares, circles etc), as well as text (which may
be ‘intelligent’). SYTMs are generated using DRAFT’s 2D drafting facilities - see Section
9. (Note also that Point Construction (see Section 11 ) can also be used to create
SYTMs.) SYTMs are used in the same way as TXTMs.
As well as the XYPS (2D Sheet position), SYTMs have other attributes common to other
DRAFT graphical elements, namely, NLPN (note line pen), MPEN (marker pen), TPEN
(text pen), FONT (text font), CHEI, CSPA and LSPA (text character attributes). See
Section 8, Part 1, Basic Drawing Creation & Output for more information on pens. All of
these attributes have default values which are obtained from the owning Library. These
attributes cannot be modified at the SLAB.
4.3.5 Scaling and Mirroring Special Labels

The XYSCALE attribute of a SLAB allows independent scale control in the X and Y
directions. Either or both values assigned to XYSCALE may be negative, which allows
the SLAB to be ‘mirrored’.
Instanced text is only affected by its scale in Y direction. It is not possible to produce
backwards or distorted text. A negative Y value will rotate the entire text to be upside-
down. The Y scale affects the overall size of the text string. It is recommended that
JUSTIFICATION CENTRE is used for text. This will keep the text position unchanged
with respect to the rest of the symbol when the symbol is mirrored.
The SYSZ attribute may be used to change the scale uniformly in both directions, for
example
SYSZ 2 is equivalent to XYSCALE 2 2
Another variation is:

SYSZ @ @ - resize SLAB using the cursor
Figure 4-14 illustrates the effects of varying XYSCALE.
NOTE: Symbols (SYMB), see Section 9, also have the XYSCALE attribute and may be
manipulated in the same way. XYSCALE is also settable at LAYE level.

Version 11.5
Labelling
XYSCALE 1 1
XYSCALE 1 2 XYSCALE 2 1
XYSCALE -1 1 XYSCALE -1 1 XYSCALE -1 -1
Figure 4-14 Varying the SLAB XYSCALE attribute
4.4 Autotagging
4.4.1 Introduction
DRAFT’s ‘autotagging’ facility enables you to generate automatically a series of Labels
in one or more VIEWS of a Drawing, having defined a set of rules to control which
elements are to be labelled and the (common) appearance of the labels.
The automatically generated labels (which may be GLABs or SLABs) can then be
individually edited. For example, it may be necessary to reposition a label or to modify
its leader line. The editing functionality is subject to a few constraints so as to prevent
Labels from becoming out of line with the criteria under which the autotagging process
operated.
The autotagging process is under the control of a Tag Rule (TAGR) element. The
relevant part of the DRAFT database hierarchy is shown overleaf.
A Tag Rule exists as a member of a Layer (LAYE) or of a Tag Ruleset (TRST). Tag
Rulesets are owned by Tag Rule Libraries (TRLB).
The Layer element has a Tag Ruleset Reference attribute (TRSF) which, if set, will refer
to a TRST. All automatically generated Labels will be owned by a Layer. Those Labels

Version 11.5
Labelling
within a given Layer will will have been generated either from TAGRs owned by that
Layer or from TAGRs referenced by the Layer via its TRSF attribute.
Having defined a TAGR element, the Labels are generated by giving the command:
UPDATE TAGGING
The UPDATE TAGGING command should be given whenever the Design changes such
that Labels move (but remain within the VIEW), or if the TAGR itself changes.
LIBY
TRLB
VIEW
TRST
LAYE
TAGR
TRSF
TMRF
GLAB, IDLN
SLAB or
template GLAB/SLAB GLAB/SLAB
element
Id List or SORF SORF
DESIGN TAGR
element
TMRF
GLAB,
SLAB or IDLN
template
element
Id List or
DESIGN
element
Figure 4-15 DRAFT Database Hierarchy - Autotagging Elements

Version 11.5
Labelling
4.4.2 Defining the Autotagging Hierarchy and Rules

A typical sequence of commands for setting up an autotagging hierarchy would be:
NEW TRLB
NEW TRST
NEW TAGR /TR1
TMRF /LAB1-1 - define Label appearance by setting template reference
attribute to point to existing GLAB, SLAB, SYTM or
TXTM
IDLN /ID6 - define elements to be labelled by setting Id List name
attribute to point to existing Id List [or Design] element.
[Set to /* by default.]
NOTE: If the TMRF attribute is set to reference a GLAB or SLAB (as opposed to a
TXTM or SYTM) than that GLAB or SLAB must not have been generated by a
Tag Rule.
Having constructed the hierarchy and set up the necessary references, the items to be
tagged are defined by the TAG command, which applies to those elements defined by the
IDLN setting. Examples of the use of the TAG command are:
TAG ALL NOZZ
TAG ALL BRAN MEM
TAG (ALL VTWA ALL VFWA ALL VALVE) WI (STYP EQ ’GATE’ AND ABORE GE 80)
TAG ALL WI (CREF NE =0)
The TAG command has the same syntax as the USE style_name FOR command. See
Sections 4.2 and 4.2.1 in Part 1, Basic Drawing Creation & Output for more examples.
The CRIT attribute for the current tag rule can be set explicitly. For example:
CRIT ALL BRAN WI (HBOR LE 80 OR TBOR LE 80)
4.4.3 Controlling Label Appearance and Elements to be Tagged
4 Label Appearance
This is defined by the element referenced by the TAGR’s TMRF attribute. If the
referenced element is a GLAB or a SLAB, the generated labels will be identical to it
except for attributes DDNM and LVIS (which will be set TRUE). The GLAB or SLAB
need not be in the current Drawing.
If the referenced element is a TXTM or SYTM, the basic style of the generated SLABs
will be defined by the referenced template, but detail appearance attributes will be
cascaded down from the owning LAYE. Attributes CHEI, FONT, LPEN and TPEN may
be set at LAYE level to ‘TEMPLATE’, which means that these attributes will take their
values from the template referenced by the TAGR. (This applies only to SLABs; other
LAYE members, for which the ‘TEMPLATE’ setting would be meaningless, would be
created with values of 4mm, 1, 1 and 1 (respectively) for these attributes.)

Version 11.5
Labelling
4 Elements to be Tagged
These are defined by the element referenced by the TAGR’s IDLN attribute. By default,
this is set to reference the WORLD, in which case all elements included in the owning
VIEW’s Id List will be considered for tagging. If the IDLN attribute is set to refer to an
Id List, only those elements common to this Id List and the VIEW’s Id List will be
considered for tagging. Similarly, if the IDLN attribute is set to refer to a Design
element, only those elements common to this element and the VIEW’s Id List will be
considered for tagging.
4.4.4 Querying
TMRF and IDLN are queryable in the usual way. With a TAGR as current element, the
query command
Q DESC
will output the tagging rule used.
A description of all tag rules relevant to a Layer (i.e. those owned by it and those owned
by the TRST it references) may be output by:
Q TRSF DESC (at LAYE)
4.4.5 Label Generation

Having set up a TAGR element and its associated autotagging rules, the Labels are
generated by UPDATE TAGGING command. This is of the form:
UPDATE element_identifier TAGG
If element_identifier refers to a TAGR owned by a LAYE, then all Labels defined by the
given Tag Rule will be generated.
If element_identifier refers to a LAYE, then all Labels defined by all the member Tag
Rules of the Layer, plus those owned by the TRST referenced by the Layer’s TRSF
attribute will be generated.
If element_identifier refers to a VIEW, SHEE or DRWG then this is equivalent to giving
an UPDATE TAGG command for each Layer beneath them in the hierarchy.
If element_identifier is omitted then the current element is assumed and one of the
three previous conditions will apply. Tag Rules will also be updated by UPDATE ALL.
When a Tag Rule is updated for the first time a set of Labels will be created and drawn
which can then be edited if required - see section 4.4.7. Each Label will have its SORF
(source reference) attribute set to refer back to the TAGR.
Labels will not be created for any element that is not drawn because
• it is not included in the VIEW’s Id List, or
• it falls outside the VIEW rectangle, or
• it is excluded by the action of a Section Plane.

Version 11.5
Labelling
In the latter two cases, whether or not an element is excluded depends upon the position
of the p-point to which the Label is to be attached. Note that Labels will be created for
elements that are not drawn because they are obscured by others. If these Labels are
not required it is recommended that they are made invisible by setting LVIS FALSE.
Deleting them will only cause replacements to be generated on the next UPDATE TAGG
command.
If a LAYE element is LOCKed then none of its TAGRs will be updated. An UPDATE ALL
command will still cause the annotation of that Layer to be updated. If a GLAB or
SLAB, which needs to be modified or deleted, is LOCKed then it will be UNLOCKed and
the modification or deletion carried out.
When a Tag Rule is updated a second (or subsequent) time, existing Labels will not be
deleted and recreated from scratch unless the OVERWRITE option is used, i.e.
UPDATE TAGG OVERWRITE (or UPDATE element_identifier TAGG OVERWRITE)
Using OVERWRITE will destroy any editing of individual Labels that may have been
done. Not using OVERWRITE will cause existing Labels to be updated so as to reflect
any changes that may have occurred in the Design database; new Labels will only be
created for those Design elements found without Labels with correctly set SORF
attributes. Any existing Label (with a correctly set SORF attribute) on a Design element
which no longer exists or which no longer meets the criteria of the Tag Rule (see above)
will be deleted.
The following example illustrates the effect of updating a Tag Rule a second time
(without OVERWRITE):
VIEW /VIEW1 has an Id List /LIST1 which calls up four Equipments, /VESS1, /VESS2,
/VESS3 and /VESS4. /VIEW1/LAYE1 owns Tag Rule /TR1 which is simply defined as
‘TAG ALL EQUI’. The IDLN attribute of /TR1 is set to /*, i.e. the whole of /LIST1 is to be
scanned and all EQUIs tagged.
When /TR1 is updated for the first time four Labels are created in /VIEW1, one on each
of /VESS1, /VESS2, /VESS3 and /VESS4. For the sake of convenience we shall refer to
these Labels as /LAB1, /LAB2, /LAB3 and /LAB4, although the autotagging process
would not actually give them names.
The following Design and DRAFT database changes are then made:
• /VESS1 - unaltered
• /VESS2 - moved by W2500
• /VESS3 - deleted
• /VESS4 - removed from /LIST1
• /VESS5 - added to /LIST1
When /TR1 is subsequently updated the Labels change as follows:

• /LAB1 - updated, but no changes
• /LAB2 - updated, and moved to reflect new position of /VESS2
• /LAB3 - deleted

Version 11.5
Labelling
• /LAB4 - deleted
• /LAB5 - new Label, created on /VESS5
4.4.6 Tracking the Autotagging Process

The command
TAGGING MESSAGES ON
will result in messages being output during an tagging update operation advising of
Label creation and deletion. Other options are:
TAGG MESS ON FILE /filename
- output messages to file
TAGG MESS ON FILE /filename OVER
- as above, but overwrite existing file
TAGG MESS ON FILE /filename APPE
- as above, but append messages to existing file
TAGG MESS ON FILE EN
- close message file
TAGG MESS OFF
- turn message output off
By default, messages will not be output.
4.4.7 Label Editing and Copying

A GLAB or SLAB generated by the autotagging process will be the same as a
conventionally created Label except that its SORF attribute (set to Nulref in the
‘manual’ case) will be set to refer back to the controlling TAGR. SORF may be set to
Nulref, thus breaking the link between the Label and the TAGR, but it may not be set to
point to another TAGR (or to any other value). Having broken the link, a subsequent
UPDATE TAGGING command will create another Label on the labelled Design element.
GLABs or SLABs generated by the autotagging process can be edited, but the following
safeguards are applied to ensure that the Labels will always comply with the definition
set up by the TAGR:
• the DDNM attribute cannot be changed
• the BTEX attribute cannot be changed (GLABs)
• the TMRF attribute cannot be changed (SLABs)
• the Label cannot be INCLUDED in another Layer
• the Label cannot be deleted.

Version 11.5
Labelling
If a Label with its SORF attribute set is copied, the new Label will have its SORF
attribute set to Nulref.
SORF may be unset by
SORF =0 or
SORF NULREF
4.4.8 Tag Rule Editing

TRLB, TRST and TAGR elements may all be modified in the usual way by changing
their attribute settings (although with TRLB and TRST elements only the standard
attributes, e.g. Name, are settable). Note, however, that editing these elements could
cause existing Labels to no longer represent the TAGR definition.
If a TAGR owned by a LAYE is deleted or included in another LAYE then the SORF
attribute of all labels generated from it will be set to Nulref. It is not feasible to do this
for TAGRs owned by TRSTs (because many labels in several databases may be affected)
or to set to Nulref SORF attributes for any other changes to TAGRs (because a change
may broaden the scope of the TAGR so that existing Labels are still valid). If changes
are made to a TAGR or TRST that potentially cause database inconsistencies then a
warning message will be output.
If a TAGR’s TMRF attribute is changed then, at the next UPDATE TAGG command, an
implicit UPDATE TAGGING OVERWRITE operation will be performed, which will
ensure that the correct appearance of existing labels is maintained. If the TMRF is
changed from one TXTM or SYTM to another TXTM or SYTM then existing label edits
will be kept. If the TMRF is changed in a different way (e.g. GLAB to GLAB or SYTM to
SLAB) then existing Label edits will be lost.
4.4.9 DATAL Transfer

Note that since it is not possible to set the SORF attribute (other than to Nulref) it is not
possible to reproduce the link between a Tag Rule and its GLABs and SLABs by DATAL
output. RECONFIGURER must be used for correct transfer of data between databases.
4.4.10 Schedule Generation

Using Autotagging, tabbing in intelligent text, and the PDMS Programmable Macro
Language (PML) it is possible to generate schedules on drawings easily.
The Tag Rule’s TMRF attribute should reference a GLAB that has been positioned
absolutely (e.g. AT X1000 Y800 ABS) at the top or bottom of the required schedule’s
position. The GLAB’s BTEX attribute should contain a number of code-words separated
by tabbing codes (see Section 5.8.2). For instance for a nozzle schedule the BTEX may be
’#NAME#15#P1BOR#25#CREF’.
This will create a schedule of three fields giving nozzle name, bore, and connection
reference. The second field will start at character column 15 and the third at column 25.

Version 11.5
Labelling
The width of the fields should be made sufficient to accommodate the expanded
codewords. The GLAB’s FONT attribute should point to a font set up with fixed-width
characters (i.e. styles 6 or 7), its CHEI set to an appropriate value, and its leader line
and text frame suppressed.
When the Tag Rule is updated all the GLABs generated will be in the same position. A
macro should be written that will scan round the Layer looking for GLABs with their
SORF attribute referencing the Tag Rule. Each such GLAB found should be moved up or
down (depending upon whether the template GLAB was positioned at the bottom or top
of the schedule). The size of the move should be calculated from the character height of
the GLAB and its number in the scan.
The macro should also create a TABL element to provide the frame of the schedule and
its horizontal lines, a TEXP element to define the field headings, and vertical STRA
elements to separate the fields. To achieve this it will be found necessary to use the Q
EXTENT BTEX feature (see Section 9.5.1) to determine the lengths and positions of text
strings.
4.5 Intelligent Label Placement
A facility is provided to ‘tidy up’ crowded labelling, so as to minimise Label overlap and
leader-line crossing. As well as changing label positions the facility may also change
Label orientations, text justifications and alignments, and the definition of leader-line
shapes and bend-points. The facility uses two versions of the SPREAD command, which
may be used to position Labels locally or remotely.
With local positioning, Labels will be positioned around their significant design
elements in such a way as to minimise Label overlap and leader-line crossing. Labels
will not be moved from their initial positions unless it is necessary. If they are moved
then, as far as possible, leader lines will be straight and at ± 45° to the VIEW axis.
An example of 'local spreading' is shown in Figure 4-16 (a) and (b).

Version 11.5
Labelling
Figure 4-16(a) Poorly positioned Labels
Figure 4-16(b) Result of SPREAD command on Labels shown in Figure 4-16(a)

Version 11.5
Labelling
In the above example, the command

SPREAD LOCAL SELECT INSIDE @ @
was used to define a window within which the labels to be repositioned lie. By default,
the Labels will be offset by 25mm (in the X and Y directions) from the Label attachment
point. The SPREAD LOCAL command can be used with the PDMS general selection
syntax (see the PDMS DESIGN Reference Manual, Part 2). Other variations of the
SPREAD LOCAL command are:
SPREAD LOCAL SELECT ID @ ID @
Use cursor to identify (two) Labels to be spread.
SPREAD LOCAL OFFSET 10
Change Label spread offset to 10mm (X and Y directions)
SPREAD LOCAL XOFFSET 15
Change Label spread offset to 10mm (X direction only)
SPREAD LOCAL RADIUS 20
Specify Label spread offset indirectly by giving a diagonal length
With remote positioning, labels will be positioned around the VIEW border. It is
possible to define a margin outside the VIEW frame which will define the positioning of
the Labels. It is also possible to define a side of the VIEW frame alongside of which
repositioned Labels will not be placed, and the minimum permissible gap between any
two Labels can also be specified.
Labels will be repositioned at the (allowed) VIEW side nearest to their attachment
points. Labels along the top and bottom sides will be rotated through 90° (readable from
the right-hand side) unless otherwise specified. To avoid overlapping, some leader lines
will be doglegged at 45°.
Examples of the SPREAD REMOTE command are:
SPREAD REMOTE SELECT ID @ ID @
Use cursor to identify (two) Labels to be spread.
SPREAD REMOTE SELECT INSIDE @ @
Use cursor to specify corners of window enclosing Labels to be spread.
SPREAD REMOTE REPOSITION @ @
Use cursor to specify corners of rectangle around which Labels are to
be repositioned (could be outside or inside of VIEW border).
SPREAD REMOTE MARGIN 10
Reposition Labels within 10mm of VIEW border
SPREAD REMOTE OMIT TOP
Prevent Labels being placed alongside the top side of the rectangle
around which they are to be repositioned.
SPREAD REMOTE GAP 5
Specify 5mm as minimum gap between any two Labels.
SPREAD REMOTE NOROT
Prevent Labels from being rotated by 90°.

Version 11.5
Labelling
Note: All options must be specified on the same command line; the previous SPREAD
parameter settings will not be remembered.

Version 11.5
Labelling
Summary of Commands
Setting Label Attributes . . .

ON ID @ - specify the Design element for the label attachment - sets DDNM
AT @ - offset the Label from the default using the cursor - sets XYPS,
OSET
AT @ ABS - absolute position for the Label using the cursor - sets XYPS,
OSET
ANG value - turn the Label through an anticlockwise angle - sets ADEG
FRA option - set Label frame visibility - sets LFRA

options: ON
OFF
FRA CLEA value - set Label frame clearance - sets GBOX
Aligning the Label Text . . .

JUST option - justify text
options: L
C
R
ALIG option - set text alignment

options: BB
HB
TB
BA
Setting Label Frame attributes . . .

LFPN integer - set frame pen number
LLPN integer - set leader line pen number

Version 11.5
Labelling
Spreading Label positions . . .

SPREAD LOCAL SELECT selection_option
- select Labels to be spread (locally)
SPREAD LOCAL SELECT INSIDE position_options

- spread Labels inside specified window
SPREAD LOCAL OFFSET distance

- specify Label spread offset (X and Y directions)
SPREAD LOCAL XOFFSET distance

- specify Label spread offset (X direction only)
SPREAD LOCAL YOFFSET distance

- specify Label spread offset (Y direction only)
SPREAD LOCAL RADIUS distance

- specify Label spread offset indirectly by giving a diagonal length
SPREAD REMOTE SELECT selection_option

- select Labels to be spread (remotely)
SPREAD REMOTE SELECT INSIDE position_options

- spread Labels inside specified window
SPREAD REMOTE REPOSITION position_options

- spread Labels around specified rectangle
SPREAD REMOTE MARGIN distance

- spread Labels within given distance of VIEW border
SPREAD REMOTE OMIT (top/bottom/left/right)

- prevent Labels being placed alongside the specified side of
the rectangle around which they are to be repositioned.
SPREAD REMOTE GAP distance
- specify minimum gap distance between any two Labels.
SPREAD REMOTE NOROT

- prevent Labels from being rotated by 90°.

Version 11.5
Labelling
Autoblanking . . .
AUTOBLANKING ON/OFF - switches autoblanking ON or OFF for a DRAFT
session
BLNK TRUE/FALSE - sets autoblanking for the current element, which can be
LDIM, ADIM, RDIM, PDIM, GLAB, SLAB, VNOT, or NOTE.
BMAR value - specifies the blanking margin, where <value> is a real value
which is greater than or equal to 0.0.
Setting Label Text attributes . . .

BTEX ’text’ - specify text string
CHEI value - specify text height
LHEI value - specify letter height (=0.8*character height)
CHEI TEM - (Special Labels only) - set text height to that of Template
(TXTM) element
CSPA value - specify character spacing factor
LSPA value - specify text line spacing

OFFS - set text position as an offset from the p-point - sets OSET
TRUE (default)
ABS - set text position as a specific position on the Sheet – sets
OSET FALSE
Setting Leader Line attributes (GLABs) . . .

LEAD option - set leader line visibility - sets LEAD TRUE/FALSE.
option = ON or OFF.
LTER option - sets leader line terminator. options: OFF, ARR, DOT,
OBLIQUE
LEAD STRA - sets a bent leader line to straight
TSIZ 4 - set terminator size to 4mm (default 3mm)
LEAD BENT @ - bend a leader line at a position set by cursor (@ @ for two
bend points)
LEAD BENT AT @ OFFSET Y50
- bend leader line at an offset from a position set by the cursor
LEAD BENT CENTRE OF /CIRC1

- bend a leader line at the centre of the named circle

Version 11.5
Labelling
LEAD BENT OFFS X value Y value

- bend a leader line at a position explicitly (repeat X
value Y value for two bend points)
LEAD BENT PT 2 @ - specify 2nd of two bend points using cursor
LEAD BENT PT 2 X722 Y40 - specify 2nd of two bend points explicitly
LEAD BENT PT 1 OFF X15 - specify 1st of two bend points as offsets from Label
attachment point
LEAD BENT PT 1 DEL - delete 1st of two bend points

LEAD value option - bend a leader line at an angle then horizontal or
vertical. option = HORI or VERT
LEAD option value - bend a leader line horizontal or vertical then at an

angle option = HORI or VERT
LEAD CLEA ENDP OF /LINE1 QUAL X500 Y500
- sets leader line clearance using a constructed point
APOF value value - offsets attachment point from DDNM (Sheet units)
LEAD ATTA X value Y value

LEAD ATTA @ - specify attachment point offset explicitly
LEAD ATTA DELETE

APOF 0 0
APOF UNSET - remove attachment point offset
CPOF STAN - places leader line connection point at standard

position
CPOF ORIG - places leader line connection point at Label origin
CPOF value value - allows a relative position to be specified
Setting Leader Line attributes (SLABs) . . .

LEAD CON @ - sets leader line connection point by cursor (sets CPOF)
LEAD CONN X value Y value - allows an explicit Sheet position to be specified
}
LEAD CONN OFFS
X value Y value allows a relative position to be specified
CPOF value value
}
LEAD CONN STAN
resets CPOF to its default value
Version 11.5
Labelling
CPOF STAN
}
LEAD CONN ORIG
sets CPOF to 0,0
CPOF ORIG
APOF value value - offsets attachment point from DDNM (Sheet units)
LEAD ATTA X value Y value

LEAD ATTA @ - specify attachment point offset explicitly
LEAD ATTA DELETE

APOF 0 0
APOF UNSET - remove attachment point offset
Setting gaps . . .
GAP @ - specify a gap in a leader line by giving start & finish points
GAP AT @ - specify a default length gap of 2mm in a leader line by a
single point
GAP AT @ L value - specify a gap of a specified length by giving a single point
GAP DELETE @ - delete a gap identified by cursor
GAP DELETE ALL - delete all gaps on the current Sheet
GAP TIDY - deletes all unused gaps from current Label
SETDEF GAP value - set default gap length
Querying . . .
Q LAB option
query specified label attributes
options: LEA - leader line
POS - position, rotation and p-line attributes
(latter only relevant if Structural
element is being labelled)
ORIG - origin
ATTA - point annotated
TEX - text
STY - text style
Q DESC option - (at GLAB) - gives Label attachment point, Sheet
position, offset and angle of turn.

Version 11.5
Labelling
(at SLAB)- gives template type, Sheet position, offset

and angle of turn.
Q TRSF DESC - (at LAYE) - gives description of all relevant tag rules
Deleting unwanted Labels . . .

DELETE NULL ANNO - deletes all GLAB and SLAB elements with DDNM
set to NULREF
Autotagging . . .
TAG selection_option - sets up elements specified by selection_option to be
tagged. Selection rule syntax same as USE . . . FOR
command
CRIT ALL BRAN WI (HBOR LE 80 OR TBOR LE 80)

- sets the CRIT attribute for the current tag rule explicitly
TAGG MESS ON - output tagging messages to screen
TAGG MESS ON /filename - output tagging messages to file

UPDATE TAGG - causes Tag Rules to be evaluated and generates
Labels down from current element
UPDATE TAGG IGNORE - as above, but deleted (and unrecognised) Design
elements referenced in the Idlist are ignored,
without the UPDATE process being aborted
UPDATE element_identifier TAGG
- enerates Labels down from element_identifier
UPDATE element_identifier TAGG IGNORE

- as above, but deleted (and unrecognised) Design
elements referenced in the Idlist are ignored,
without the UPDATE process being aborted
UPDATE TAGG OVERWRITE - as UPDATE TAGG, but all labels recreated from
scratch
UPDATE element_identifier TAGG OVERWRITE - as UPDATE element_identifier
TAGG, but all labels recreated from
scratch

Version 11.5
5 Intelligent Text
5.1 Introduction
Intelligent text allows data to be automatically extracted from the Design, Catalogue or
Drawing databases and entered on a Drawing. Intelligent text uses code words, which
all begin with a # character. For example:
’Standby pump #NAME’
The advantages of intelligent text are:
• If the data in any of the three databases changes then when the Drawing is updated
the correct new values will be automatically obtained and entered upon the
Drawing.
• You do not have to navigate through the relevant database, retrieve the data, return
to the DRAFT database and enter the data manually.
• The same text string with its embedded code words can be used many times to
generate text strings that are similar in format but different in detail.
The text strings where you can use intelligent text are:
DMTX - dimension line text (of Dimension Points and Directions,
PLTX - projection line text (i.e. ADIR, APPT, DPOI, DPPT, DPBA)
BTEX - general text string of General Labels (GLAB) and Templates
(TXTM). (See also 2D Drafting TEXP element, Section 9.5.)
5.2 Code Words
The code words fall into one of six categories:

Code words that access data associated with the Design or Catalogue element referenced
by the DDNM attribute of the Drawing database element. See Section 5.3.
• Code words that access data associated with the Drawing database element which
owns the text string. See Section 5.4.
• Code words that access dimensioning data. See Section 5.5.
• Code words that access UDA data. See Section 5.6.
• Code words that access administrative data. See Section 5.7.

Version 11.5
Intelligent Text
• Code words with special functions. See Section 5.8.
5.3 Accessing Data from the Design or Catalogue

Databases
All Design and Catalogue database attributes are accessible. For example, attribute
ABCD would be accessed by code #ABCD (or #abcd). In addition, any Design element
can be accessed. For example:
#SITE - Name of site owning the referenced element
#BRAN - Name of Branch owning the referenced element
PDMS pseudo-attributes may be accessed in the same manner.

The codewords for position attributes can be modified so as to provide only one of the
coordinates. For example:
#POS - full 3D position, e.g. W12250 N7890 U3120
#POSE - Easting coordinate only, e.g. E12250, W9675
#POSN - Northing coordinate only, e.g. N7890, S22150
#POSU - Upping coordinate only, e.g. U3120, D250
All Design database position attributes can be modified in this way. These are POS,
HPOS, TPOS, NPOS, POSS, POSE, DRPS and DELP. Note that the codeword #POSE
can have two meanings, depending on the context: for SCTNs it means the POSE
attribute (Section End Position), in other cases it means the Easting of the POS
attribute.
The position codewords generate values in World coordinates. It is possible to generate
values in the coordinate systems of other elements by the use of transform keywords -
see Section 5.11.
Note: As an alternative to the standard ENU position format, positions can be output
with +/- format by appending ‘+’ to the codeword. For example,
#POS - full 3D position, e.g. W12250 N7890 U3120
#POS+ - would give -12250 +7890 +3120

Version 11.5
Intelligent Text
5.3.1 P-point data

P-point data can be obtained by a codeword of the form:
#Pnxa - Data from p-point n of element
where n = p-point number, or ‘L’ for leave p-point or ‘A’ for arrive
p-point
x = POS, DIR, BOR, BOP, TOP or CON
a = blank, E, N or U (valid for x = POS, BOP or TOP only)
For example:
#P3BOR - bore at p-point 3
#PLBOPU - Upping of leave p-point BOP position
#P1POS - position of p-point 1
Ppoint codewords can have an optional ^ delimiter between the p-point number and the
attribute. For example:
#P2^POS
The delimiter is optional, but it must be used when the number is omitted, for example:
#P^POS
in which case the value from the NPPT attribute of the relevant piece of annotation will
be used.
5.3.2 P-line Data

The P-line syntax may refer to the p-line used for annotation (i.e. that defined by the
PKEY attribute) or to a specified p-line. A specific codeword defining the p-line precedes
strings requesting position, direction and offset.
The syntax for p-lines is
#PK
(for PKEY). This syntax on its own is a request for the p-line name (e.g. NA or TOS,
stored as the PKEY attribute). #PK may optionally be followed by the p-line name, for
example #PKNA for p-line neutral axis. The p-line name (if present) may be 1-4
characters long. #PK may also be followed by MEML (i.e. #PKMEML) if data for the
Section’s member-line is required. (This is only valid if the SCTN has its MEML
attribute set.)
The p-line name may optionally be followed by a p-line attribute name, for direction or
position, for example:
#PK^DIR or #PKNA^POSSU
The last format would mean ‘Upping of Start position of Neutral axis p-line’.
The internal delimiter ^ is necessary to separate the p-line attribute from the p-line
name. There is nothing to stop you from having p-line names such as NAPO or even
DIR. Names such as these would be impossible to separate from the p-line sub-codeword

Version 11.5
Intelligent Text
without this delimiter. Spaces are not permitted between the codeword and sub-
codeword.
The following sub-codewords may follow the p-line codeword #PK or #PKname:
^DIR - p-line direction
^POSS - p-line start position
^POSSE - Easting of p-line start position
^POSSN - Northing of p-line start position
^POSSU - Upping of p-line start position
^POSE - p-line end position
^POSEE - Easting of p-line end position
^POSEN - Northing of p-line end position
^POSEU - Upping of p-line end position
^PKDI - position of point along p-line defined by PKDI attribute
^PKDIE - Easting of point along p-line defined by PKDI attribute
^PKDIN - Northing of point along p-line defined by PKDI attribute
^PKDIU - Upping of point along p-line defined by PKDI attribute
For example
#PKNA^POSS
- gives the start position of the NA p-line
#PK^DIR
- gives the direction of the p-line given by the PKEY attribute
The #PK^PKDI keyword will extract the position along a p-line at which a Label is
attached. This will generate the position defined by the PKDI attribute of the label.
Thus if PKDI = 0 the Label will be positioned at the start of the p-line (defined by the
PKEY attribute) and the start position will be generated. If PKDI = 0.5 it will be at the
p-line’s mid-point and its mid-point position generated.
Besides GLABs and SLABs, the VNOT, ADIM, DPPT, RPPT and PPPT elements also
possess the PKDI attribute.
NOTE: In DRAFT p-lines are always cut back by SCTN end-preparations and member-
lines are always extended to the ‘working point’. The positions generated by
these codewords reflect this functionality.
The transform qualifier (see Section 5.11) may be used with any of these sub-codewords,
but not for p-line name. For example
#PKTOS^POSEU<WRT /DATUM>
Gives the upping with respect to /DATUM of the end position of the
TOS p-line
#PKTOS^POSEU+<WRT /DATUM>
As above, but gives upping in ‘+/-’ format
#DERPOS[a]
Derived position of a Joint, Fitting or Secondary Node, where a = N for
Northing, E for Easting, U for Upping (optional)

Version 11.5
Intelligent Text
5.3.3 Accessing Data in Catalogue Datasets

Data in a Catalogue Dataset is obtained by a two-part codeword of the general form:
#attribute^qualifier
For example:
#PROPERTY^WIDTH - obtain Property value of WIDTH dataset entry
#PRTITLE^WIDTH - obtain Property Title of WIDTH dataset entry
The Property Default (PRDEFAULT) and Property Purpose (PRPURPOSE) settings can
be obtained in a similar manner. In each case the first part of the codeword (ie
PROPERTY etc) can be abbreviated to four characters.
PROPERTY values are evaluated as distances or bores if the PTYPE attribute of the
relevant DDTA (or DDAT) element is set to DIST or BORE respectively.
5.4 Accessing Data from the DRAFT Database
All DRAFT (PADD) attributes are accessible. For example, attribute ABCD of the
current annotation element would be accessed by code #ABCD. In addition the name of
any DRAFT element can be accessed. For example:
#VIEW - The name of the View owning the annotation element
#DRWG - The name of the Drawing owning the annotation element
Attributes of other DRAFT elements can be accessed using the FROM qualifier. For
example:
#AUTH<FROM DRWG>
Generates the Author of the Drawing owning the annotation elements.
See Section 5.12 for full details of the FROM qualifier.
The following special codewords are also available:
#DTITL - Drawing title, equivalent to #TITL<FR DRWG>
#STITL - Sheet title, equivalent to #TITL<FR SHEE>
#VTITL - VIEW title, equivalent to #TITL<FR VIEW>
Special functionality is provided for the following codewords that extract revision data:
#APPR - Approver
#APDT - Approval date
#RVSN - Revision
#RVDT - Revision date
#RVAU - Revision author
These codewords extract their data from the first REVI element in the Sheet’s list. If the
qualifier <FR DRWG> is appended then data will be extracted from the first REVI

Version 11.5
Intelligent Text
element in the Drawing’s list. To extract data from a specific REVI element a qualifier
should be used. The REVI element can be specified by name, for example:
#RVAU<FR/REV3>
or the pseudo-reference array attributes SREVAY and DREVAY can be used. For
example:
#RVDT<FR SREVAY[2]>
Generates the revision date from the sheet's second revision
#APPR<FR DREVAY[3]>
Generates the approver from the drawing's third revision
For details of the SREVAY and DREVAY attributes see Section Section 9.3, Part 1,
Basic Drawing Creation & Output.
For details of the FROM qualifier see Section 5.12.
5.5 Accessing Dimensioning Data
Code words that are allowed values for the Dimension Line Text (DMTX) and Projection
Line Text (PLTX) of Angular and Linear Dimensions (ADIM and LDIM) and Dimension
Points/Directions (ADIR, APPT, DPOI, DPPT, DPBA) and have special meanings:
#DIM - Calculated dimension value (DMTX or PLTX)
#DEF - Use default text string supplied by owning ADIM or LDIM
(Must appear alone in a text attribute, e.g BTEX ’#DEF’ is
valid, ’name #DEF’ is not.)
#DIR - Projection line direction (of ADIR)
The following codewords are valid in the PLTX of LDIMs and their members, and cause
the 3D Dimension Point position to be generated in World coordinates.
#DIMPOS
3D position
#DIMPOSE, #DIMPOSN, #DIMPOSU
Easting, Northing, Upping, respectively
#DIMPOSDD
Coordinate in the Dimension Direction of the 3D Dimension Point
position
For example, if the Dimension Direction is North, the Northing of the Dimension
Position will be output- ie exactly the same result as #DIMPOSN. If the Dimension
Direction is not orthogonal, the full 3D position will be output (ie as would be generated
by #DIMPOS) together with error message
64,399: /ldim-name: Dimension direction not orthogonal, so unable to
calculate single coordinate for codeword #DIMPOSDD
These codewords may be used in conjunction with the WRT qualifier (see Section 5.11)
to generate relative positions.

Version 11.5
Intelligent Text
At a DPOI which has POS and optionally DDNM attributes set, #POS will always obtain
data from the element referenced by DDNM. #POS will only obtain data from the POS
attribute setting if DDNM = 0/0. Hence you should always use #DIMPOS to generate the
coordinates of DPOI elements.
5.6 Accessing UDA Data
Those that extract (UDA) data from the database. The codewords which access User-
defined attribute (UDA) data have the format
#:uda_name
For example:
#:UDA1
All relevant qualifiers (see Sections 5.9 - 5.12) which apply to ordinary codewords may
also be applied to UDAs. The output of data follows a format similar to that used by
existing UDA queries. Real UDA may have distance or bore units and will be reported
as such. Other uses of UDA reporting are described in Section 5.11.
5.7 Accessing Administrative Data
Codewords relating to administrative data are:

#ADATE - Date: format mm/dd/yyyy, e.g. 09/30/1998
#BDATE - Date: format dd/mm/yyyy, e.g. 30/09/1998
#CDATE - Date: format dd mon yyyy, e.g. 30 Sep 1998
#ADATEX - Date: format mm/dd/yy, e.g. 09/30/98

#BDATEX - Date: format dd/mm/yy, e.g. 30/09/98
#CDATEX - Date: format dd mon yy, e.g. 30 Sep 98
#DFDATE - Date: format specified by the DATEFOrmat attribute of the

DEPT above the current element.
#TIME - System time: format hh:mm:ss, e.g. 09:07:57
#SYSUSE - current user’s System Name
#PROJECT^NUMBER - Project number

#PROJECT^NAME - Project name
#PROJECT^DESCRIPTION - Project description
#PROJECT^MESSAGE - Project message
#PROJECT^CODE - Project code

Version 11.5
Intelligent Text
DEPT and LIBY elements have a DATEFOrmat attribute. It controls the format of the
values of DATE (of DRWGs) and RVDT (of REVIs) attributes which are automatically
generated. DATEFOrmat may be set to:
DDMMYYYY which gives a format equivalent to #ADATE
DDMMYY which gives a format equivalent to #ADATEX
MMDDYYYY which gives a format equivalent to #BDATE
MMDDYY which gives a format equivalent to #BDATEX
DDMONYYYY which gives a format equivalent to #CDATE
DDMONYY which gives a format equivalent to #CDATEX
5.8 Codewords with Special Functions
5.8.1 The Template Codeword

#Tname is the Template codeword, which enables complex text strings to be defined
once in a Text Template (TXTM element). This template may then be referenced from
other elements.
name refers to a text template TXTM. For example:
#T/TEM24
#T may be used in PLTX or DMTX attributes of Dimensions or Dimension Points, or in
the BTEX attribute of Labels (GLAB or SLAB) or text primitives (TEXP).
The codeword #T/name must be the only content of the text string. The referenced text
string may contain intelligent text codeword strings. However the BTEX attribute of a
TXTM cannot itself contain a #T codeword since this could lead to recursion.
5.8.2 The Tab Generator Codeword

#n is the tab generator codeword, where n is the number of the column where the next
character is to be output.
The tabbing codeword controls tabbing, taking the form #n, where n is the number of the
column where the next character is to be output. For example
#NAME#24#CATR
- output NAME, then output Catalogue Reference starting in column 24
The blanks in the output character string will be padded with spaces. For example
’ABC#10DEF’
would appear on a drawing as
ABCvvvvvvDEF
(where v is used here to denote a space). The string
’#NAME#15#CATR#25#CREF’

Version 11.5
Intelligent Text
would expand (typically) to

/PUMP1/NSvvvvv/NFJJvvvvv/PIPE1-1
If the number specified is already exceeded by the length of the output character string
then a single space will be inserted. For example
’#NAME#5#CATR#10#CREF’
would expand to
/PUMP1/NSv/NFJJv/PIPE1-1
Tabbing will take account of linefeeds within the text string, whether specified explicitly
or by the new line generator code ’#/’. Hence
’#5#NAME#/#8#CATR#/#8#CREF’
would expand to
vvvv/PUMP1/NS
vvvvvvv/NFJJ
vvvvvvv/PIPE1-1
The use of this feature in combination with a fixed-width font (e.g. style 6 or 7) allows
you to arrange text neatly in a tabular form. Used in combination with Autotagging and
the PDMS Programmable Macro Language (PML), it is possible to generate schedules
on drawings easily. See Section 4.4.10.
5.8.3 New Line Generator

The codeword #/ generates a new line.
5.8.4 # Character
The codeword ##outputs a single # character.
5.8.5 Underlining
#< start underline
#> finish underline
When a GLAB text string has been underlined, GBOX should be set to zero in order for
the leaderline to meet the underline.

Version 11.5
Intelligent Text
5.9 Substrings
There are two methods of specifying that a substring of the data associated with a code
word is required for output.
5.9.1 String Definition by Characters

Substrings can be extracted from text by following the code word with a substring
descriptor of the form:
(Cn1:n2)
where C indicates that n1 and n2 refer to character positions and n1 and n2 are integers
which indicate the leftmost and rightmost character positions of the substring
respectively; if n1 is omitted then 1 is assumed by default, and if n2 is omitted then the
last character of the string is assumed. For example:
If #PIPE expands to ‘/ZONE-4/PIPE-6’ then #PIPE(C2:6) expands to
‘ZONE-’
By default all PDMS names will be output with the initial slash. If you do not want the
slash to appear on the drawing use the substring descriptor (C2:). For example:
#PIPE(C2:) expands to ‘ZONE-4/PIPE-6’
5.9.2 Substring Definition by Parts

You can define a substring by reference to the constituent parts of the original string. A
part of a string is defined by delimiters, which are user-definable.
The substring required is specified by following the code word with a substring
descriptor of the form:
(P-n1:n2)
Here P indicates that n1 and n2 refer to delimiter numbers and ‘-‘ indicates the
character used as the delimiter. If omitted, ‘/’ is assumed. The delimiter must not be
numeric.
n1 and n2 are integers which indicate respectively the delimiter numbers at which the
substring is to start and finish; the delimiter before n1 is always included in the output
substring but the delimiter after n2 is always excluded. If n1 is omitted then the
substring will start at the beginning of the ‘parent’ string, and if n2 is omitted then the
substring will end at the end of the ‘parent’ string. The start and end of the ‘parent’
string are always assumed to be delimiters. For example:
If #PIPE expands to the parent string ‘/ZONE-4/PIPE-6’ then
#PIPE(P/2:) expands to ‘/PIPE-6’ and

#PIPE(P-:2) expands to ‘/ZONE-4/PIPE’

Version 11.5
Intelligent Text
It is possible to append a number of substring definitions (both character type and part
type) to a code word. These are processed sequentially, left to right. Any number of
substring definitions is allowed. For example:
#PIPE(P2:)(C2:) expands to ‘PIPE-6’
There is a special form of the substring descriptor,
()
which is shorthand for (C1:)
This form can be used for putting codewords back to back in a text string where the
other codeword delimiters are not suitable, for example, when a space is not required
between codeword data. For example:
#POS #NAME would, when expanded, have a space between the two data
items:
#POS()#NAME would not.
5.10 Array Indexing
The format used for the array indices is:

[n] or [n,m]
where n and m are integers and m is greater than n. The first format generates a single
array element, the second generates a range of array elements. For example:
#CRFA[2]
#:ARRAY[4,6]
Embedded spaces are allowed within an array index but are not mandatory. In the
second format, one of the integers may be omitted. Omission of the first integer implies
n=1, and omission of the second implies m=K, where K is the significant length of the
array.
Array indices my be used (where appropriate) with both basic codewords and UDA
names.
Array indices cannot be used with text, position, displacement or direction attributes.
Components of position attributes (Eastings, Northings and Uppings) should be
extracted using the special codewords for that purpose (e.g. #POSU).
The length of an array attribute can be extracted and applied to a sheet using:
‘#codeword[SIZE]’
SIZE may be abbreviated down to S and may be lower-case. The [SIZE] suffix may be
used with any hash code-word for which array indices are valid.

Version 11.5
Intelligent Text
5.11 Transforming Position/Direction Data
If qualified by a transform keyword, position and direction attributes will be reported in

the coordinate system of the specified element. The qualifier may be used with any
position or direction codeword, including those for p-points, P-lines and Structural
derived attributes.
The qualifier uses the keyword WRT (‘with respect to’) to denote the coordinate system
to be used. Lower case wrt is also allowed; minimum abbreviation is W (or w).
WRT must be followed by a single parameter to define the coordinate system required.
This parameter may be a word or name which specifies a Design element.
If a name is used, it must not contain the comma (,) or closed angle-bracket (>)
characters. For example:
#P1POS<WRT /1201A>
This will output the position of p-point 1 of the DDNM element with respect to element
/1201A. The word parameter may either define an element type or a reference attribute,
for example:
#POS<WRT ZONE>
#POSU<WRT OWNE>
If an element type is specified, it must refer to an owner of the Design element specified
in the DDNM attribute. This may be the immediate owner or an element in the
database hierarchy above the DDNM element.
If a reference attribute is specified, it should refer to a reference attribute of the DDNM
element, for example OWNE or CREF. The reference attribute may also be a UDA:
<WRT OWNE>
<WRT HREF>
<WRT :uda>
Individual components of reference array attributes may also be used:
<WRT CRFA[3]>
<WRT :UDARR[2]>
The default coordinate system is the Design World - i.e. the implied syntax is:
<WRT WORL>
The qualifier ‘CE’ must be used to refer to the coordinate system of the current element.
For example, to report the position of P3 of a Box with respect to the Box origin:
#P3POS<WRT CE>
Only position, direction, displacement and orientation codewords may have transform
qualifiers. This includes some P-line and p-point attributes.
When outputting a qualified position in +/- format, the ‘+’ must appear before the
qualifier, for example
#P1POSU+<WRT /DATUM>

Version 11.5
Intelligent Text
5.12 Extracting Attribute Data from any Specified

Element
Attribute data may be extracted from any element rather than the element defined by
the DDNM attribute. This element may be specified by name, element type or reference
attribute.
The keyword for this navigation qualifier is FROM (or from), which may be abbreviated
to F (or f). This keyword may be followed by one or more parameters separated by
spaces:
<FROM parameter>
<FROM parameter parameter parameter>
The format for each parameter is the same as that for the transform qualifier (WRT), i.e.
element name, element type or reference attribute. For example:
#POS<FROM /VESS1>
Outputs the position of /VESS1 (in World coordinates)
#POSE<FROM SITE>
Outputs the Easting of the Site above the DDNMelement
#DTXR<FROM TUBE>
Outputs detailing RTEXT for the implied Tube associated with the
DDNM element.
#HBOR<FROM CREF>
Outputs the HBOR of the Branch referred to by the CREF of the
DDNM element
#SPRE<FROM :fred>
Outputs the SPRE of the element referred to by the :fred attribute of
the DDNM
#PARA[3]<FROM SPRE CATR>
Outputs value of third array element of relevant PARA attribute from
referenced catalogue Component.
#PARA[3]<FROM /VCHJJ>
Outputs value of third array element of relevant PARA attribute from
referenced catalogue Component.
#DUTY<FROM CRFA[2]>
Outputs the DUTY of the Branch referred to by CRFA[2]
The first three examples refer explicitly to elements by name or type. The next three
contain reference attributes of the current element, the referenced element being
accessed. The last is a reference array attribute and must be followed by an array index.
More than one navigation parameter may be used to enable compound navigation to
access the required Design element. Parameters are applied in order from left to right.
Thus:
<FROM CRFA[2] OWNE>
means data from the owner of the element referred to by CRFA[2].

Version 11.5
Intelligent Text
#MTXZ<FROM /VALVE1 TUBE>

Outputs the ZTEXT relevant to the implied tubing of /VALVE1.
The order of parameters is important:
<FROM CREF OWNE>
<FROM OWNE CREF>
These two FROM keyword formats do not have the same meaning. The first means the
owner of the element specified by the CREF attribute and the second means the element
specified by the CREF attribute of the owner.
Up to five parameters may be used. A complicated case might be:
<FROM OWNE CREF OWNE :UDARR[3]>
This means that data is to be extracted from the third element referred to in the UDA
reference attribute ‘:UDARR’ of the owner of the CREF element of the owner of the
current Design element.
The starting point for navigation is the current element. This is normally the current
Design element, as referred to by the DDNM attribute of the annotation element.
However where the codeword obviously refers to annotation data (for example #AUTH,
#TITL refer to AUTH and TITL attributes in the DRAFT database), navigation is from
the annotation element.
It is possible to apply both navigation and transform qualifiers. For example:
#POS<FROM OWNE, WRT /DATUM>
Note that the navigation qualifier is always applied before the transform qualifier,
whatever the order of syntax. For example:
#POS<FROM /EQUIP, WRT ZONE>
Here, the position of /EQUIP will be output in the coordinate system of the ZONE which
owns /EQUIP, rather than the Zone of the DDNM element.
If the navigation qualifier is omitted, the appropriate current element is usually used for
data extraction. However certain codewords extract data from a specific element type
rather than from the current element. An example of this is #PRFL. Data is extracted
from the PRFL attribute of the SUBS element which owns the current element.
Standard Codewords such as #BRAN and #DRWG are equivalent to #NAME<FROM
BRAN> etc.
Pseudo- reference attributes can be used within codeword navigation qualifiers. For
example #XXXX<FR SPREF> will extract the data for attribute XXXX of the element
referenced by attribute SPREF of the current Design element. (Note that SPREF is a
pseudo-attribute of NOZZ as well as being a standard attribute for all Piping
Components.)

Version 11.5
Intelligent Text
5.13 Distance, Position and Bore Data Output
5.13.1 General
The format of distance, position and bore data generated by codewords is controlled by
the UCOD attribute of the Layer element.
All intelligent text codewords generate the same format for ‘FINCH’ and ‘FINCH US’
units (as set in the UCOD attribute of the Layer):
UCOD FINCH DIST
- set distance units to ‘PDMS style’ feet and inches, e.g. 5’5.13/16
UCOD FINCH US DIST
- set distance units to ‘USA style’ feet and inches, e.g 5’-5 13/16”
UCOD INCH BORE
- set bores in inches
UCOD CM DIST
- set distances in centimetres
UCOD CM BORE
- set bores in centimetres
FINCH (PDMS): 25’3.1/2
FINCH US: 25’-3 1/2”
The INCH option may be qualified to allow different formats for distance, position, and
bore values generated by intelligent text codewords. These are:
INCH USA - output of the form: 1/2” or 1 1/2” or 24”
INCH PDMS - output of the form: 0.1/2 or 1.1/2 or 24
INCH DECIMAL - output of the form: 0.5 or 1.5 or 24.0
If the qualifier is omitted then DECIMAL is assumed.
A nominal/actual qualifier is available for bores. For example
UCOD FINCH PDMS BORES ACT
UCOD FI US BO NOM
The setting is NOMINAL by default. The UCOD setting controls the bore sizes output to
a drawing by DRAFT’s intelligent text system. The two qualifiers have exactly the same
effect as the general PDMS PRECI BORE NOM (or PRECI BORE ACT) commands.
UCOD settings can be queried by using the pseudo-attributes:
Q UCODD and Q UCODB
5.13.2 Mixed Units within Intelligent Text Strings

The units used in intelligent text strings are determined by the UCOD attribute of the
owning LAYE. However, it is possible to insert a ‘switch units’ code in the text string,

Version 11.5
Intelligent Text
which will cause all distances and bores which follow to be output in ‘alternate’ units, as
defined below.
Layer Units Alternate Units
UCOD INCH DECI MM
UCOD INCH PDMS MM
UCOD INCH US MM
UCOD FINCH PDMS MM
UCOD FINCH US MM
UCOD MM INCH DECI
UCOD CM INCH DECI
UCOD METRE INCH DECI
The ‘switch units’ code is %U so, for example, to generate a dimension in both Imperial
and metric units, with the second value in brackets, the intelligent text string:
’#DIM() %U(#DIM())’
should be used. The units may be switched back to the standard units by a subsequent
use of a %U code.
5.13.3 Controlling the Precision of the Generated Output

The precision of both linear and angular data is controlled by the Precision Code
(PCODE) attribute. PCODE is an attribute of the DEPT, REGI, DRWG, LIBY, SHLB,
OVER and LAYE elements, with its value being cascaded down the database hierarchy.
PCODE stores four values of precision for metric (decimal) values, Imperial decimal
values, imperial fractional values, and angles. By default, these four values are 0 (dp), 1
(dp), 32nds and 1 (dp) respectively. (dp = decimal places.)
The following are examples of setting PCODE:
PCODE LIN MM TO 2 DPLS
Set linear (metric) precision to two decimal places
PCODE LIN IN TO 2 DPLS
Set linear (Imperial) precision to two decimal places
PCODE LIN FRA TO 32 NDS
Set linear (Imperial, fractional) precision to 32nds
PCODE ANG DEG
Set angular precision to nearest whole number of degrees
PCODE ANG TO 2 DPLS
Set linear angular precision to two decimal places
Angles output in degrees, minutes or seconds will be in the standard format (ie using °,
’ or ”). Angles output in the decimal format will have no symbols. If required a °
symbol can be accessed from DRAFT’s alternative character set by using the code ~0.

Version 11.5
Intelligent Text
Data output in metre or centimetre format will be to the precision specified by the
PCODE MM option. Thus if this is to 1 dp then the output will be to 4 dps for metre
output and 2 dp for centimetre output.
Four pseudo-attributes exist to allow the querying of the individual parts of the PCODE
attribute:
Q PCODMms - query metric (mm) precision
Q PCODInches - query Imperial (inch) precision
Q PCODFractions - query fraction precision
Q PCODAngles - query angle precision
5.14 Customising Error Text
When it is not possible to extract data from an attribute, the intelligent text system
returns an error and (by default) substitutes the text ‘---’ for the missing data. The
NTEXT attribute allows you to substitute your own ‘null text’. For example
NTEXT ’No data’
NTEXT may consist of up to 12 characters. It is an attribute of DEPT, REGI, DRWG.
LIBY, SHLB, OVER and LAYE elements, and its setting will be cascaded down the
hierarchy.
5.15 Intelligent Text Syntax - Summary
The combined format for a codeword string may be summarised as follows:

#word + ^word + [n,m] + <qualifiers> + (Cn1:n2) (P/n1:n2)
substring editing by
parts
substring editing by
characters
data qualifier
array index
sub-codeword (after #PK only)
basic codeword or UDA name

(The + signs are not literal.) All components except the first are optional. The substring
editing qualifiers may appear more than once in any order. Some combinations have no
meaning. All qualifiers may contain embedded spaces, therefore the closing delimiters
cannot be omitted.
The combined format for the data qualifier list is:

Version 11.5
Intelligent Text
<FROM parameter [parameter], WRT parameter>

Examples of Codeword Strings
#POS<FROM OWNE, WRT SITE>
- position of owner in Site coordinates
#CRFA[2]<FROM /VFWA1>
- name of second element of CRFA attribute of /VFWA1
#HREF<FROM OWNE>(P/2:3)
- parts 2 and 3, delimited by ‘/’, of the HREF of the owner
#PKNA^POSE<WRT FRMW>
- end position of P-line NA in framework coordinates
#PK^POSSE
- Easting of P-line start position in world coordinates. The P-line
name has been omitted, meaning the P-line used to position
annotation.
#POSE
- At a SCTN this means the POSE attribute, otherwise it means
the Easting of the POS attribute.
#OWNE<FROM CRFA[2]>
- owner of element 2 of CRFA attribute
#NAME<FROM CREF :udarr[2]>
- name of element specified in :udarr[2] of element specified in
CREF
#:FRED[3]<FROM EQUI>
- array element 3 of UDA attribute :FRED of the owning
Equipment.
#T/T24
- use the value of the BTEX attribute of text template /T24
#DTXR<FROM ROD>
- detailing RTEXT from the implied rod of the current element
#VRAT[1]<FR VIEW> to #VRAT[1]<FR VIEW>
- outputs VIEW scale as a ratio, as specified by the VRATIO
attribute.

Version 11.5
Intelligent Text
5.16 Notes
In the code word descriptions given in this section, the words ‘owner’ or ‘owning’
(enclosed in quotes) refer to the element of the type described equal to or above the
referenced element in the database hierarchy - not necessarily the true owner. Where
the word owner appears (unenclosed by quotes) then this means the true owner.
General points:
• All text strings have a maximum length of 120 characters in unexpanded form, 180
characters in their expanded form.
• Lower case and upper case (but not mixed case) forms of all code words are valid.
• When a piece of text generated from a # code word itself contains a # code (or a ~
code or % code, see Section 6) then this code is not expanded unless the original
piece of text comes from either a DRAFT or DESIGN database text attribute or a
text user-defined attribute (UDA) from any database.

Version 11.5
Intelligent Text
Summary of Commands
Design World Hash Codes (examples)...

#NAME #TREF #TDIR #OWNER #SPREF #ABOR
#EQUI #CATR #LBOR #PIPE #POS #POSa
#HPOSa #TPOSa #BRAN #HPOS #CREF #TPOS
#HREF #HDIR #PRFL #FUNC #PTSP #DUTY
#DSCO #INSC #STEX #LENG #BORE #TEMP
#PRES #LNTP #HBOR #TBOR #FLOW #HCON
#TCON
a = N, E or U
Pnxu, where n = integer 0-99 or L or A
x = POS, DIR, BOR, BOP, TOP or CON
u = blank, E, N or U (for x = POS, BOP, TOP only)
e.g P3BOR
#CRFA #JOIS #JOIE #LSTU #HSTU #HSRO

#LSRO #STSP #MATR #ISPE #INRE
#GRA #FIRE #ZDIS #CUTB
#ANTY #DESC #FIXT
#NPOS #NPOSE #NPOSN #NPOSU
#POSS #POSSE #POSSN #POSSU
#POSE #POSEE #POSEN #POSEU
#DERCUT #DERLEN #DRPS #DRPSE #DRPSN #DRPSU

Version 11.5
Intelligent Text
DRAFT Drawing World hash codes...

#DTITL - Drawing title
#STITL - Sheet title
#VTITL - VIEW title
#DRWG - Drawing name
#DIMPOSa - 3D Dimension Point position, where a = N, E or U
#AUTH - Author (of DRWG or SHEE)
#ADATE, #BDATE, #CDATE - date of creation (of DRWG)
#APPR - approver
#APDT - date of approval
#RVSN - revision
#RVDT - date of revision
#RVAU - revision author
Special characters...
#Tname - template codeword
#/ - new line
## - single #
#< - start underline
#> - finish underline
#n - tabbing codeword. Next character to be output in column n.
+ - when appended to position codeword, gives position in ‘+/-’ format

instead of ENU. Only available for position-generating codewords.
Hash code delimiters...

( , SPACE or RETURN

Version 11.5
Intelligent Text
Sub-Strings...
(Cn1:n2) Substring by characters
(P/n1:n2) Substring by parts
() remove gap between subsequent hash codes
Array Indexing...
#codeword[n] or #codeword[n,m]
where n and m are integers and m is greater than n. The first format generates a single
array element, the second generates a range of array elements.
Transforming Position/Direction Data...

<WRT qualifier>
where qualifier is a word or a name which specifies a Design element.
Attribute Navigation...
<FROM parameter>
<FROM parameter parameter parameter>
The format for each parameter is the same as that for the transform qualifier (WRT), i.e.
element name, element type or reference attribute.
Extraction of P-line Data...

#PK[p-line name][p-line sub-codeword]
The available sub-codewords are:
^DIR - p-line direction
^POSS - p-line start position
^POSSE - Easting of p-line start position
^POSSN - Northing of p-line start position
^POSSU - Upping of p-line start position
^POSE - p-line end position
^POSEE - Easting of p-line end position
^POSEN - Northing of p-line end position
^POSEU - Upping of p-line end position
^PKDI - position of point along p-line defined by PKDI attribute
^PKDIE - Easting of point along p-line defined by PKDI attribute
^PKDIN - Northing of point along p-line defined by PKDI attribute
^PKDIU - Upping of point along p-line defined by PKDI attribute

Version 11.5
Intelligent Text
Querying...
Q EXBTEX - Query expanded form of BTEX attribute
Q EXPLTX - Query expanded form of PLTX attribute
Q EXDMTX - Query expanded form of DMTX attribute
Updating...
UPDATE option ANNO - update attributes holding hash codes options:
DRAW, SHEE, VIEW, LAYE
Setting units (at LAYE)...

UCODE FINCH US DIST - set distance units in feet & inches, USA style
UCODE FINCH DIST - set distance units in feet & inches, PDMS style
UCODE METRE DIST - set distance units in metres
UCODE INCH BORE - set bores in inches
UCODE INCH USA

UCODE INCH PDMS
UCODE INCH DECIMAL - set inch output to appropriate format
UCODE MM BORE - set bores in mm
UCODE METRE BORE - set bores in metres
Q UCODD - query distance units
Q UCODB - query bore units
Controlling the Precision of the Generated Output...

PCODE LINEAR MM TO integer DPLS - set linear (metric) precision to integer
decimal places
PCODE LINEAR INCHES TO integer DPLS - set linear (Imperial) precision to
integer decimal places
PCODE LINEAR FRACTIONS TO integer [THS | NDS]
- set linear (fractional, Imperial) precision to integer 32ths (or
32nds).

Version 11.5
Intelligent Text
PCODE ANGLES TO integer [DPLS | DEGREES | MINUTES | SECONDS]

- set angular precision to integer decimal places (or degrees, or
minutes, or seconds).
Q PCODMms - query metric (mm) precision
Q PCODInches - query Imperial (inch) precision
Q PCODFractions - query fraction precision
Q PCODAngles - query angle precision

Version 11.5
6 Miscellaneous Text Facilities
Within DRAFT, text is used by Dimensions (dimension line and projection line text),
Labels, and as part of the 2D-drafting facilities (TEXP elements). The text is set using
the BTEX, DMTX or PLTX attribute of those elements, as appropriate. (See Section
4.3.2 for other uses of BTEX, also the ATEX, DMTX, PLTX and ETEX text attributes.)
There is a choice of fonts, a set of non-alphabetic characters is available and the text
may be edited. The text ‘quality’ is selectable to allow for rapid drawing. These facilities
are described below.
6.1 Text Fonts
DRAFT makes use of the four font families, which can include user-defined fonts, that
can be set up in ADMIN. (See the VANTAGE PDMS ADMIN Command Reference
Manual for details.) Details of these font families can be obtained by the command:
Q FONTS
There are three text font attributes - FONT, DFON, and PFON. These are used to define
the appearance of the various text strings that can appear on Drawings. These font
attributes can be set to 1, 2, 3, or 4 in which case the normal version of the relevant font
family will be obtained. Variations on these normal versions can be obtained by setting
the font attributes to a value obtained from the table below.
Normal Bold
Upward Forward Reverse Upward Forward Reverse
1 11 12 13 14 15 16
2 21 22 23 24 25 26
3 31 32 33 34 35 36
4 41 42 43 44 45 46
For example, font 35 is variation 5 of font family 3. Variation 5 is always bold and
forward-sloping. From the table it will be seen that fonts 11, 21, 31, and 41 are
equivalent to 1, 2, 3, and 4. (For completeness the font attributes can also be set to 10,
20, 30, and 40 which are also equivalent to 1, 2, 3, and 4). Bold fonts are not provided for
all font families. In such cases the selection of a bold option will result in the use of the
appropriate normal font.

Version 11.5
Miscellaneous Text Facilities
6.2 Multiple Fonts within Text Strings
It is possible to switch from one font to another within a single text string, subject to a
maximum of four fonts per string. This will allow sub-strings, individual words, or even
parts of words to be emphasised. Note that the extension character set, which provides
the special symbols, counts as a font.
The string will start to be output using the principal font; this is the one specified by the
relevant FONT, DFON, or PFON attribute. Font switching is controlled by a set of
special characters embedded in the string. This set will be composed of an escape
character (%) followed by either two numeric digits or one alpha character. These sets
are best demonstrated by examples:
%24 - switch to font 24 (ie variation 4 of font family 2)
%46 - switch to font 46
%02 - switch to variation 2 of the current font family
%30 - switch to font family 3 maintaining the current variation
%37 - invalid, variation 7 is not defined (only variations 1 - 6)
%51 - invalid, font family 5 is not defined (only families 1 - 4)
%2 - invalid, two numeric digits are required
%P - switch to principal font (ie that defined by the font attribute)
%T - switch back to previous font (i.e. toggle)
%C - invalid, only %P, %p, %T, and %t are currently allowed
Font switching can be prevented and the escape character output by doubling it (i.e.
%%). Invalid codes (e.g. %51) will be output literally. The font switching character
sequence does not have to be preceded or followed by blank characters. For example
‘ABC%04DEF%pGHI’ will be output as the 9-character string ‘ABCDEFGHI’ with the
two sub-strings ‘ABC’ and ‘GHI’ in the principal font, and the middle three characters
(i.e. ‘DEF’) in variation 4 (i.e. upright bold) of the principal font.
6.3 Alternative Character Set
DRAFT incorporates an alternative character set which provides useful symbols. An

‘alternative’ character is specified by preceding one of a set of normal alphanumeric
characters by the tilde (~) sign. For example, the steelwork I-beam symbol could be
defined as a TEXP by setting the BTEX attribute as:
BTEX ’~I’
The tilde may be input as normal text by doubling it (i.e. ’~~’ produces a single tilde).
Normal text, intelligent text and ‘alternative’ characters may be input in any
combination.
See Figure 6-1 for the full list of available symbols.

Version 11.5
Symbol Code Meaning Symbol Code Meaning
B Footnote symbol W Omega
C Centreline symbol X Superscript `1'
D Diameter symbol Y Superscript `2'
E Z Superscript `3'
F Steelwork Channel 0 Degrees symbol or

superscript 0
G Steelwork Angle 1
H Steelwork H-Section 2
I Steelwork I-Section 3
J Steelwork T-Section 4
K Steelwork Double Angle 5
L Steelwork L-Section 6
M Mu 7
N Yen sign *
O Steelwork hollow circular Section +
P Plate symbol - Line
Q Copyright symbol /
R Registered trademark symbol < Left arrow
S Steelwork hollow rectangular Section = Hash
T Trademark symbol > Right arrow
U [ Much less than
] Much greater than

V Down arrow
^ Up arrow
Figure 6-1 Alternative Character Set

Version 11.5
6.4 Editing Text
Editing a text attribute is achieved through use of the EDTEXT command, which gives a
simple case-sensitive, string exchange facility operating on the attribute in question (see
below).
The EDTEXT command takes the general forms:
EDT text_type number string_1 string_2
text_type is the text attribute in question, which can be any DRAFT text attribute,
including the name attributes OSFN and BSFN. If text_type is not
specified, BTEX is assumed.
number is the order of occurrence of string_1 within the target string. If this is
omitted then the first occurrence, is assumed, if a value of 0 is specified
then all occurrences of string_1 are processed (i.e. replaced by string_2).
Several editing instructions may be given in the same command line. The command
EDT text_type APP string
will append the given string to the specified text attribute.
The different syntax options of the EDTEXT command are illustrated by the examples
given below.
Target string: ‘The dog, the cat and the rabbit were in the garden’
EDT ’the’ ’that’ (change first occurrence of ‘the’ to ‘that’)
gives: ’The dog, that cat and the rabbit were in the garden’
EDT ’the rabbit’ ’Dolores’
gives: ’The dog, the cat and Dolores were in the garden’
EDT 2 ’the’ ’that’ (change second occurrence of ‘the’ to ‘that’)
gives: ’The dog, the cat and that rabbit were in the garden’
EDT 0 ’the’ ’that’ (change all occurrences of ‘the’ to ‘that’)
gives: ’The dog, that cat and that rabbit were in that garden’
EDT ’dog’ ’horse’ ’at’ ’ow’ 3 ’the’ my’
gives: ’The horse, the cow and the rabbit were in my garden’
EDT ’fox’ ’fish’ - no change, ‘fox’ is not found
EDT PLTX 3 ’we’ ’a’ - attribute PLTX would be altered, if found
EDT OSFN ’A3’ ’A4’ - OSFN would be altered, if found
EDT DATE ’1990’ ’1991’ - DATE would be altered, if found
not the ‘resultant’ text.

Version 11.5
6.5 Text Quality
Two standards of text ‘quality’ are available. EXACT quality is standard, BASIC quality
gives a ‘font’, whose exact appearance and size depends on the device type in use.
BASIC text would be used when drawing time is considered to be more important than
quality of textual output. When BASIC text is used, the space occupied by the
equivalent EXACT text is bordered by a rectangle. Plotted text is always drawn in
EXACT mode so there is no need to ‘convert’ from BASIC prior to plotting a Sheet.
Text quality is set by the TQUALITY command, which has the alternative forms:
TQUA EXACT or TQUA BASIC
The current text quality setting can be queried by:
Q TQUA
6.6 Character Height
DRAFT measures character height from the character base line to the top of the
character body. See Figure 6-2.
Top of body
Capitals line
ÁËôý
Character
Letter Height
Height
Base line
Bottom of body
Figure 6-2 Character Height

The gap between the capitals line and the top of the character body is 20% of the
character height, so the letter height = 0.8* character height. The gap for descenders
between the base line and the bottom of body is one third of the character height. (These
proportions do not apply to the SCRIPT font.)
Letter Height = LHEI (Label Text)
DTLH (Dimension Line Text)
PTLH(Projection Line Text)
Character Height = CHEI (Label Text)

DTCH(Dim Line Text)
PTCH (Proj Line Text)

Version 11.5
7 Annotating Structural Elements in
DRAFT
7.1 Basic Annotation
Structural elements, like other Design elements, may be labelled, dimensioned and used
in 2D drafting. This means that positions and directions in the Design World must
be obtained for these elements.
Annotation elements which (may) require a 3D position include labels (GLAB, SLAB);
View Notes (VNOT), drafting primitives whose drafting point references (PTRF or
PTFA) use a PPPT (drafting point with design data); Angular Dimension elements
(ADIM) and two types of dimension points: DPPT and DPBA. Dimension points of type
DPBA do not require p-line data since they are concerned with the limits of a Design
element.
Annotation elements which require a 3D direction include Linear dimension elements
(LDIM) and Dimension Points of type APPT. In addition, where the direction of a p-line
is used for position on a Label or View Note, it may also be used to define the angle of
the Label or View Note to the horizontal in the view region.
Fittings, Nodes and Joints with p-points are treated in the same way as other elements.
There is no change in the functionality for annotating these.
7.2 3D Position from a P-line
Wherever a Design element or p-point may be used for position, a p-line may also be
used. However, a p-line is a line in a given direction between two points, and does not
define a single position.
In order to use p-line for position, it is necessary to specify a distance along that p-line.
This may be done using syntax based on that in DESIGN, as follows:
PPLINe word OF element_identifier STart
PPLINe word OF element_identifier ENd
The start and end of a p-line are the points at which the p-line crosses the two end-
cutting planes of a Section. These are proportional distances 0.0 and 1.0 respectively.
The start and end of the neutral axis are coincident with the points defined by the POSS
and POSE attributes of the Section.
PPLINe word OF element_identifier units_value
This syntax defines an absolute distance from the start of the p-line.

Version 11.5
Annotating Structural Elements in DRAFT
PPLINe word OF element_identifier PROPortion value
This syntax defines a proportional distance along the p-line from its start.
PPLINe word OF element_identifier
When no p-line position is stated explicitly the default value for proportional distance is
used. This default may be altered by using the PKDI SETD command (see Section 7.5.3).
The initial value is 0.5, meaning the mid-point of the p-line.
7.3 3D Direction from a P-line
Wherever a Design element or p-point is used for a direction, a p-line may also be used.
The p-line itself may be used for direction, or an axis of the p-line may be used.
The syntax for p-line direction is based on that in DESIGN, as follows:
PPLINe word OF element_identifier
This defines the direction along the p-line in the Design. This syntax must be used if
you wish to store the p-line in the annotation element.
PPLINe word OF element_identifier NEGative
This syntax specifies the negative or reverse direction along the p-line in the Design.
This is equivalent to specifying the p-line -Y direction.
A direction parallel to an axis of the p-line itself may also be selected:
PPLINe word [OF element_identifier] [+] plxyz
PPLINe word [OF element_identifier] - plxyz
where plxyz is any one of:

X [DIRection]
Y [DIRection]
Z [DIRection]
LEAve [DIRection]
The axis of the p-line along the length of the Section is its Y direction. The Z or Leave
direction and the X direction both lie in the plane of the perpendicular cross-section of
the Section. The reverse of these directions may be obtained by the use of the minus
sign.
Syntax for p-line direction qualified by <plxyz> cannot be used to set p-line attributes in
the annotation. DIRECTION syntax of this form will be used to set the DIR attribute
rather than p-line attributes. The following commands are examples of this:
NEW LDIM DIRection PPLINe word OF element_identifier LEAVE [DIRection]
NEW ADIM ON ...
FROM DIRection PPLINe word OF element_identifier -Z [DIRection]
TO DIRection PPLINe word OF element_identifier NEGative

Version 11.5
However, the following command would actually store p-line data in the annotation
element:
TO DIRection PPLINe word OF element_identifier
In this case the p-line direction has not been qualified by specifying an axis. Therefore
the axis along the length of the Section is what is required and will be stored directly in
the database as such.
7.4 Angle from a P-line
The p-line direction as defined above may be used to set an angle. This is true of any
element with an ADEG attribute, such as a drafting primitive.
However, for Labels (GLAB, SLAB) and View Notes (VNOT), there is an additional
possibility. If the p-line is used for position, then the same p-line may also be used
instead of the ADEG attribute to store angle.
The syntax for p-line angle is as follows. This is normally used to set the ADEG
attribute:
ANGle PPLINe word OF element_identifier [+] plxyz
ANGle PPLINe word OF element_identifier - plxyz
ADEGrees PPLINe word OF element_identifier [+] plxyz
If p-line is required for angle on a Label or View Note, there is a simple way of setting it.
This is done using the following syntax:
ANGle PKEY or
ADEGrees PKEY
This command first checks that a p-line is in use for position, and uses it to define the
angle of the Label or View Note.
The ANGle PPLINe syntax may also be used to store p-line for angle in the database.
However this will only be done if both of the following criteria are satisfied:
• The p-line identified must be that used for p-line position
• The p-line direction syntax must not be qualified by a p-line axis
7.5 P-line Attributes
The syntax for position, direction and angle described above is stored in the database
using the following attributes:
• DDNM for the Design element name
• PKEY for p-line name
• PKDI for proportional distance along a p-line

Version 11.5
• under special circumstances, PPDI will be used to specify p-line for angle.
These attributes and associated syntax are described further below.
7.5.1 P-line Design Element

The name of the Design element to which the p-line applies is stored in the DDNM
attribute of the annotation element. When a p-line is in use, the p-point attributes
(NPPT or PPDI) are normally unset (value -1). The exception to this is where p-line is
used for angle. This case is described further in the section on p-line angle (see below).
If p-line data for an annotation element is replaced by a direct reference to a Design
element or p-point, then the p-line attributes (PKEY and PKDI) are set back to the
default values.
7.5.2 P-line Name

The p-line name is identified by the PKEY attribute of the annotation element. Where
no p-line name is specified, the value 0 is taken to mean the neutral axis of the specified
Design element. This may be NA, NAXI or ZAXI as set up in the Catalogue data. The
value 0 is the default value for the PKEY attribute.
The PKEY attribute may be set directly using the following syntax:
PKEY word
The word given should refer to an existing p-line of the Design element, if that is set.
PKEY PPLINe word OF element_identifier
The specified p-line must exist. The specified element should be that given in the
DDNM, if set.
7.5.3 P-line Distance

P-line distance is stored in the PKDI attribute of the appropriate annotation elements
(GLAB, SLAB, VNOT, ADIM, DPPT and PPPT). This stores the proportional distance
along the p-line from its start. The default value for this attribute may be altered by the
user. Its initial value is 0.5, meaning the midpoint of the p-line.
The PKDI attribute may be set directly using the syntax:
PKDIstance STart
PKDIstance ENd
These commands set the values 0.0 and 1.0 respectively.
PKDIstance [PROPortion] value
This value may also be obtained by cursor using the PKEY and DDNM attributes of the
current element (if suitable):

Version 11.5
PKDIstance @
The point input is converted to a proportional distance.
PKDIstance DEFault
This command resets the PKDI attribute to the default value. The default value may be
altered using the syntax:
SETDefault PKDIstance value
The current value of the PKDI default setting may be queried:
Query SETDefault PKDIstance
7.5.4 P-line Direction

No additional attributes are required to define this. The p-line is defined by the PKEY
and DDNM attributes. The p-line direction is along the length of the p-line.
P-line direction is used on LDIM and APPT elements.
7.5.5 P-line Position

P-line position is defined by the p-line attributes PKEY and DDNM, with the addition of
the distance attribute PKDI to define a position on that p-line.
P-line position is used on the following elements: GLAB, SLAB, VNOT, ADIM, DPPT
and PPPT.
7.5.6 P-line Angle

A p-line may be used for angle on the following elements: GLAB, SLAB and VNOT.
It is defined by the p-line attributes (PKEY and DDNM) together with a special value of
the PPDI attribute. The value
PPDI -2
means that the p-line used to position the annotation is also used for angle.
7.6 Representation of SCTN Ends
Warning: The functionality described in this section will be removed at a future release
of PDMS.
The DRGP (Drawing Priority) SCTN attribute is used by DRAFT to determine how to
draw SCTN ends in hidden-lines-removed views. DRGP may be set (in the Design
Database) to any integer value between 0 (highest priority) and 50.

Version 11.5
The effect is demonstrated in the diagrams below, which show plan views of four SCTNs
meeting at a node point. The top flanges of the SCTNs are coplanar and none of the
SCTN ends have been cut back. In Figure 7-1(a) the DRGP attributes of all four SCTNs
have been left at 0; as a result DRAFT is unable to determine how to draw the
intersection lines between the SCTNs and so draws the full outlines of all SCTNs. In
Figure 7-1(b) the DRGP attributes of the four SCTNs have been set as indicated, which
confers a priority order on them. As a result, DRAFT is able to determine the
representation that is intended.
DRGP=2 DRGP=0
DRGP=1
DRGP=0
(a) (b)
Figure 7-1 Effect of SCTN DRGP Attribute

Version 11.5
8 Underlays and Overlays
8.1 Introduction
DRAFT gives you the ability to use underlays and overlays on a Sheet. These may take
the form of plotfiles held in the system database, or may be DRAFT database elements.
They can be used as backing sheets for a title block and border, or as overlay sheets for
placing such items as keyplans or standard notation.
A backing sheet has its origin coincident with, and must be the same size as, the Sheet
being underlayed. An overlay sheet can be placed anywhere on the Sheet, and can be of
any size. Any number of Overlay Sheets may be used on the one SHEE, but it is only
possible to have one backing sheet on a SHEE.
8.2 Using Plotfiles
The command syntax for underlaying and overlaying a plotfile is as follows:

BSHEE FILE /plotfile name
Sets Sheet’s BSFN attribute
OSHEE FILE /plotfile name
Sets Overlay’s OSFN attribute, see next section
To remove an underlay or overlay from a Sheet, the following commands can be used:
BSHEE UNSET
OSHEE UNSET
Note that BSHEE is valid at LAYE or below, whereas OSHEE is only valid at OLAYs.
An overlay is positioned on the current Sheet by changing the OPOS and OANG
attributes of the Overlay element (see next section), which determine the position and
angle respectively. For example:
OPOS @
Set overlay origin using cursor
OPOS X250 Y300
Set overlay origin explicitly (relative to the Sheet origin
OPOS ENDP OF /LINE1
Set overlay origin to a constructed position
OANG 30
Rotate the overlay 30 degrees anticlockwise about its origin

Version 11.5
Underlays and Overlays
Alternatively, file specification and positioning may be combined into a single OSHEE
command, for example:
OSHEE FILE /OS1 ANGLE 90 @
Define, position and orientate overlay sheet
OSHEE ANGLE 60 @
Reposition and reorientate currently defined overlay sheet
OSHEE @
Position Overlay absolutely
OSHEE BY @
Position relative to old position
These commands may also be used to position Overlay Sheet templates.
Note that you can query the size of a plotfile using the command:
Query PLOTFile name SIZE
The response will be the size rectangle of the plot.

Version 11.5
8.3 Database Elements for Underlays and Overlays
DRWG
LIBY
BSRF
SHLB SHEE
BSRF
OLAY
BACK OVER
OSRF
NOTE
VIEW NOTE
Figure 8-1 DRAFT Database Hierarchy - Overlay/Underlay Elements

Elements for use as backing and overlay sheets may be created in DRAFT and stored in
the DRAFT database. The relevant part of the database hierarchy is shown Figure 8-1.
The SHLB (Sheet Library) exists as a member of a LIBY and is used as an
administrative element to group together BACK (Backing Sheet template) and OVER
(Overlay Sheet template) elements.
A BACK would probably be used as a frame sheet and would contain frame lines,
authorisation boxes etc. These would exist as (member) NOTE elements created via
DRAFT’s geometric 2D drafting facilities. Any hash codewords defined by TEXP
elements will be expanded when the BACK is referenced. These codewords will typically
exctract data from the DRAFT database. See Section 5.4.

Version 11.5
OVER elements may also own NOTEs as well as VIEW elements, and would probably be
used to overlay graphic details such as keyplans on drawing sheets. An OVER shares
many of the attributes of a SHEE. Note that Point Construction (see Section 11) can be
used to create BACK and SHEE elements.
Most Overlay Sheet attributes are held by the Overlay (OLAY) element.
BACKs and OVERs are referred to by the relevant drawing Sheet’s BSRF and the
relevant Overlay’s OSRF attributes (respectively). (BSRF may also be set at Drawing
level.) The BACK/OVER to be used may be specified by using commands such as:
BSHEE /BS1 Underlay specified backing sheet element
OSHEE /OS1 Overlay specified overlay sheet element
The Overlay’s OSLV (‘overlay sheet view layers visible’) attribute defines those Layers
of the overlay sheet (i.e. the LAYE element(s) owned by the VIEW(s) owned by the
OVER referenced by the drawing Sheet) which are to be visible.
The Overlay’s XYSCALE attribute allows independent scaling in the X and Y directions
of the instanced overlay sheet or plotfile. For example:
XYSCALE 2 1
Either or both values may be negative, but zero is not allowed.
Note that when an Overlay Sheet is instanced (i.e. attribute OSRF is set), text is only
affected by the scale in the Y direction. It is not possible to generate backwards or
distorted text. However, when a plotfile is used (i.e. attribute OSFN is set), then there is
no such safeguard and text could be distorted if differing X and Y scales are specified.
See also Section 4.3.5.
Control of complex overlays may be achieved by using multiple OLAY elements.
The Layers which are to be visible may be referred to either by Layer purpose (i.e. the
PURP attribute) or by their member list position under the VIEW(s) owned by the
OVER. Up to 12 Layers may be made visible at once. The Layers which are to be visible
are specified by a further option of the OSHEET command. For example:
OSHEE LAYERS 1 LABS
Make all Layers at list position 1 and all Layers with PURP ‘LABS’
visible
OSHEE ALL
Make all Layers visible (default)
OSHEE ALL OFF
Make all Layers invisible
The Design graphics may be made visible by including Layer DESI. If the overlay sheet
has more than one VIEW then the Layer visibility statement will apply across all
VIEWs. (It is not possible to specify, for example, a Layer with PURP DIMS to be visible
for /VIEW1 but not for /VIEW2, assuming both VIEWs own such Layers.) The setting of
a Layer’s LVIS attribute has no bearing on the visibility questions discussed in this
section.

Version 11.5
The above functionality is only available when an overlay sheet template reference is
used. No distinction between Layers can be made when using overlay sheet graphics
from a file.

Version 11.5
Summary of Commands
Underlays...
BSHEE FILE /plotfile name
- underlay a specified plotfile on the current SHEE.
Must be at SHEE level or below. Sets SHEE BSFN attribute
BSHEE UNSET - delete SHEE underlay
UPDATE BSHEETS - (valid at SHEET and above) Updates Backing Sheets. Will
ensure that the latest version of the referenced BACK is used
and will re-evaluate hash codewords.
Overlays...
OSHEE FILE /plotfile name
- overlay a specified plotfile on the current SHEE.
Must be at OLAY level. Sets OLAY’s OSFN attribute.
OSHEE UNSET - delete OLAY overlay
Differences...
BSHEE - same size as SHEE origin in same position as SHEE
OSHEE - any size origin can be placed anywhere on SHEE
NOTES: It is only possible to have BSRF or BSFN set, not both

It is only possible to have OSRF or OSFN set, not both
Manipulating overlays...
OPOS @ - set overlay origin using cursor
OPOS xpos ypos - set overlay origin explicitly (relative to the Sheet origin)
OANG value - rotate the overlay anticlockwise about its origin
XYSCALE value value - rescale overlay sheet
OSHEE FILE name ANGLE value @ - define, position and orient overlay sheet
OSHEE ANGLE value @ - reposition and reorient currently defined overlay

sheet

Version 11.5
OSHEE @ - position Overlay absolutely
OSHEE BY @ - position relative to old position

Version 11.5
9 2D Drafting
9.1 Introduction
DRAFT’s 2D drafting facilities are designed to be complementary to its main drawing

production facilities. 2D drafting allows you to add to drawings such features as notes,
plane and boundary lines, keyplans, tables of symbols etc. In addition, backing
sheets, overlay sheets and symbol templates may be created.
2D drafting shapes (or primitives) may be positioned explicitly, with a cursor hit or by a
construction. Because the principle of point construction can be applied to all DRAFT
primitives which have a position attribute, point construction is described in Section 11.
2D positions generated by a cursor hit will be snapped to a grid position if snapping is
ON. See Section 6.5, Part 1, Basic Drawing Creation & Output.
Note: For 2D drafting purposes, it is possible to enter DRAFT having specified a
multiple database (MDB) which does not contain a Design database. Clearly, in
this ‘drafting-only’ mode, intelligent text which extracts data from a Design
database cannot be used.
9.2 Where 2D Drafting is Used
The 2D drafting application can be used for creating:

• Backing and overlay Sheets. See Section 9.2.1.
• Symbol templates. See Section 9.2.2.
• ISODRAFT symbol templates. See Section 10.
9.2.1 Backing and Overlay Sheets

2D drafting may be used to create backing and overlay sheets, or may be used to
annotate overlay sheets which exist as VIEW elements. The relevant part of the DRAFT
database hierarchy is shown in Figure 9-1.

Version 11.5
2D Drafting
SHEE
SHLB
N O TE VIEW
BACK OVER LA YE
VN O T
VIEW
LAYE
NOTE NOTE VNOT
CIRC
TEXP SYMB
ELLI
RECT
TABL
ETRI
DMND
HEXA
MRKP
STRA
ARC
OUTL
Figure 9-1 DRAFT Database Hierarchy - Sheet Library/2D Drafting Elements

Version 11.5
2D Drafting
A BACK (backing sheet template) element would probably be used as a frame sheet and
would contain frame lines, authorisation boxes etc. These would exist as (member)
NOTE elements (see below).
OVER (overlay sheet template) elements may also own NOTEs as well as VIEW
elements, and would probably be used to overlay graphic details such as keyplans on
drawing sheets. An OVER shares many of the attributes of a SHEE.
Sheet Note (NOTE) elements exist to own the 2D drafting elements themselves (see
section 9.3). This means that NOTEs can be used to ‘group’ drafting elements together -
changes to the NOTE’s position and orientation will affect all of its member drafting
elements. As well as the basic attributes of XYPS (2D Sheet position), ADEG
(orientation) and LVIS (visibility), NOTEs/VNOTs have a set of attributes which are
used to store defaults values that are cascaded down to their members. These are NLPN
(note line pen), FPEN (fill pen), TPEN (text pen), JUST (horizontal justification), ALIG
(vertical alignment), FONT (text font), CHEI (character height) and CSPA and LSPA
(character spacing factors). NLPN and FPEN are cascaded to geometric primitives and
the others to text primitives.
View Note (VNOT) elements are similar to NOTEs, the only difference being that
VNOTs may be positioned using 3D Design World coordinates or on a Design item, p-
point or p-line (or using 2D Sheet coordinates).
Having created a NOTE or VNOT in accordance with the hierarchy shown in Figure 9-1,
drafting elements may be created and manipulated as desired - see Section 9.3.
9.2.2 Symbol Templates

User-defined symbols (consisting only of 2D drafting elements) may be created as
Symbol Templates (SYTMs). These can then be picked from a Library sheet element,
with position, size and orientation attributes being altered to suit. The relevant part of
the DRAFT database hierarchy is shown overleaf.
Symbol Library (SYLB) and Label Library (LALB) elements can be regarded as ‘Sheets’
that can be displayed in an area view. Symbol Templates can then be created on the
Library sheet using the 2D drafting elements.
Setting the TMRF (Template Reference) attribute of a SYMB (Symbol Instance) element
or SLAB (Special Label) will cause the referenced SYTM to appear on the relevant
Sheet. The Symbol can then be positioned, sized and orientated to suit - see the
description of scaling and mirroring SLAB elements in Section 9.3.5 for details of how to
do this.

Version 11.5
2D Drafting
SYLB LAYE
SYTM SLAB
TMRF
NOTE
LALB
SYMB
SYTM
TMRF
CIRC
TEXP SYMB
ELLI
RECT
TABL
ETRI
DMND
HEXA
MRKP
STRA
ARC
OUTL
Figure 9-2 DRAFT Database Hierarchy - Symbol Template and Related Elements
9.3 The Drafting Elements
The 2D drafting elements are primitives, Text Strings (TEXP) and Symbol Instances
(SYMB).
Primitives are basic geometric shapes (rectangle, circle, straight, arc etc).
Text Strings may be up to 120 characters in length, may be multi-line and may
incorporate intelligent text codes. Four fonts are available, and character height,
spacing and alignment may be varied in the same way as for Label text.
Symbol Instances (SYMB) are particular instances of Symbol Templates (SYTM). The
SYTM defines the composition of the symbol, the SYMB defines its size, position, and
orientation.
Symbol instances can be nested - the instanced SYTM may itself own SYMBs which
reference other SYTMs. However, second-level and higher SYTMs must be owned by
SYLBs, not LALBs. Any intelligent text codes in TEXPs owned by such SYTMs will not
be expanded.

Version 11.5
2D Drafting
9.4 2D Drafting Primitives
These are basic geometric shapes which can be ‘drawn’ on a Sheet or a VIEW Layer. The
primitives exist in the hierarchy as members of NOTEs, VNOTEs or SYTMs.
Primitives which exist as members of VNOTs may have their dimensions and positions
defined in terms of 3D Design values
There are eleven types of geometric primitive element corresponding to the shapes
shown in Figure 9-3.
Note: The ‘°’denotes the shape’s (default) origin and is not part of the shape itself.
Figure 9-3 Drafting Primitives

(Note: The Outline (OUTL) primitive consists of a number of connected straight lines
and circular arcs, as defined by the user. The shape shown above is an example
only.)
As a primitive element is created, its position is stored separately, with a reference to
the position being stored as the primitive’s PTRF (or PTFA) attribute. An important
feature of this system is that if a series of primitives is created, each primitive’s position

Version 11.5
2D Drafting
reference (or drafting point) will (initially) be the same, enabling a series of ‘connected’
shapes to be quickly and easily created. For example, the command sequence
NEW CIRCLE DIAM 100 AT @
NEW CIRCLE DIAM 150
NEW CIRCLE DIAM 200
would create a series of concentric circles. In a similar way, a series of connected
straight lines could be created. (A line may have two position references, one at either
end; the start position reference of one line would be set equal to the end position
reference of the previous line - see description of STRA primitive below.) A set of
primitives connected in this way may be moved as a ‘group’ by using the DRAG
command - see below.
DRAFT offers you a variety of methods of defining, identifying, sizing, positioning,
orienting, moving and querying drafting primitives. Many methods of carrying out these
operations are common to all (or most) of the drafting primitives. These methods are
described in the next section; methods which apply to particular primitives (and to
Symbols) are described in Section 9.4.5.
9.4.1 Creating and Manipulating Drafting Primitives - Common

Operations
NOTE: See the Graphical Feedback later in this Section for details of the easiest way of
creating drafting primitives.
4Creating Primitives and Varying Basic Attributes

At NOTE (or VNOT) level, and with a Sheet (or VIEW Layer) in a SHOWn form, the
simplest way of creating a circle (for example) would be by giving the commands:
NEW CIRCLE DEF @
(The cursor would then be used to mark the centre and a circumference point of the
circle, which would then be drawn. Hitting a key produces a command line giving the
(Sheet) coordinates of the cursor position; such a command line could, of course, be typed
in directly.) All the different shapes can be created in a similar way, with a self-
explanatory prompt being output in each case. Note that macros driven from forms
and menus are particularly useful for 2D drafting.
Attributes common to all primitives (except Markers, Lines, Arcs and Outlines) are
orientation (ADEG, relative to a line drawn through the shape’s origin parallel to the
x-axis) and origin code (OCOD). The origin code determines the position of a
primitive’s origin relative to the primitive itself - for example, a circle’s origin may be
placed at its centre or on its circumference. Arcs and Straight Lines have a TCOD (Type
Code) attribute instead of OCOD. TCOD can be set to the endpoint or midpoint of a line,
and to the endpoint or centre of an arc. The TCOD setting defines how to interpret the
other attributes of the primitive. Straight lines also have an ADEG attribute. See below
(STRA and ARC elements).
Clearly, attributes such as orientation cannot be set using the cursor, so if these require
settings other than their defaults they must be set afterwards. (Default orientation is 0,

Version 11.5
2D Drafting
default origin code is CENTRE. For straights and arcs the default TCODE is
ENDPOINT.)
Alternatively, primitives may be created using one-line commands such as:
NEW CIRC RAD 50 ORIG CIRCUM ADEG 45 AT X900 Y750
NEW RECT XLEN 40 YLEN 20 ANG 45 ORIG CORNER AT @
NEW TABL XLEN 60 YLEN 60 NROW 10 NCOL 5 RPEN 2 CPEN 3 ORIG TS ADEG 45 AT @
The effects of varying the attributes of the different primitives are illustrated in Figure
9-4 and Figure 9-5.
Figure 9-4 Drafting Primitives - Varying Attributes

Version 11.5
2D Drafting
Figure 9-5 Drafting Primitives - Varying Attributes (contd.)

Version 11.5
2D Drafting
4Shifting the Origin

The origin code may be set in two ways. If the ORIG keyword is used (for example, ORIG
@ to set by cursor), the Sheet coordinates of the origin change such that the origin moves
to the specified part of the primitive - the primitive itself does not move. The origin code
may also be changed by the OCOD keyword, for example
OCOD CEN
OCOD @
In this case the Sheet coordinates of the origin remain unchanged and the primitive
moves so as to place itself correctly according to the new origin code.
In either case the origin position may be changed at the same time by using commands
such as
ORIG X300 Y250
OCOD TRIGHT @
OCOD BLEFT @
The origin is normally invisible, but may be made visible by the SKETCH command:
SKETCH ORIGIN At primitive level, displays primitive origin
SKETCH ORIGIN ALL At NOTE level, displays origins of all member
primitives
The command
ERASE ORIG
erases the display of the origin(s).
4Moving Individual Primitives

Primitives may be moved using commands such as
AT @ Move to new 2D position
AT X300 Y250
POS ID @ Move to new 3D position (VNOT
POS W5500 N12345 D1200 members only)
ON ID @ Move to specified element origin or
ON IDP @ p-point (VNOT members only)
ON /PUMP1
ON P1 OF /PUMP2/NS
BY @ Move relative to current 2D position
BY X10.5
BY N500 W1200 Move relative to current 3D position
(VNOT members only)
4Moving Groups of Primitives

The DRAG command is used to move a group of primitives which share a common
drafting point. The concentric circles described in the introduction to Section 9.4 are an

Version 11.5
2D Drafting
example of a group of primitives which use the default drafting point - the drafting
point’s position is not specified explicitly, so it is taken as at that of the last-created
primitive.
ORIGIN node_identifier or FPT node_identifier
Examples of the DRAG command (showing examples of node_identifier) are:
DRAG BY @
DRAG BY X120 Y-45
DRAG BY S3500 D500NO TAGNO TAG
DRAG TO @
DRAG TO POS @
DRAG TO IDP @
DRAG TO X120 Y-45
DRAG TO S3500 D500
DRAG TO P1 OF /VESS2/N6
FPT DRAG TO @
(The above DRAG operations have similar interpretations to the AT/ON/BY/POS
commands listed previously.)
4Querying Primitives
The primitives with drafting points in common with the current element may be queried
by giving the command
Q COMMON
This lists the primitives that will be dragged with the current element. The primitives
that may be dragged with any named drafting node of a STRAIGHT or an ARC may be
queried by
Q node_id COMMON
where node-id is the FPT or TPT (etc) of a STRAIGHT or ARC.
The origin and position of a primitive may be queried by
Q ORIG
The offset of a drafting node or primitive origin from the note origin may be set and
queried:
Q node_id OFFSET
Q OFFSET
node_id OFFSET X value Y value
ORIGIN OFFSET X value Y value
where node_id is the node of a straight or arc primitive, i.e. FPT, TPT, MPT, THPT or
CPT. (See list of DRAG commands above for examples of node_id.)
The principal dimensional and positional attributes of a primitive may be listed by
using the
Q DESC
command at the primitive concerned (or at the owning View Note (position and angle)).

Version 11.5
2D Drafting
A drafting point on a STRAIGHT, ARC or span of an OUTLINE may be queried using

Q IDNN @
This allows you to pick one of these points by picking an appropriate position on the
primitive. The query reports the appropriate point, the identity of the primitive picked
and the position of the picked point. For example:
FPT OF /STRAIGHT3 X 123 Y 456
TPT OF /ARC1 E 3000 N 4000 U 0
VPT /VERT1 NEAR /VERT2 X 495 Y200
In the last case where a span of an OUTLINE was picked, the first vertex identified is
the endpoint of the span, and the second is the Vertex (VRTX element) which owns the
span. The two Vertex identifiers may be the same.
For STRAIGHTS and ARCS, the point identified will be the same as that returned by
the Q IDN @ command where the current element is a STRA or ARC. Q IDNN @ allows
both the point and the primitive to be picked by one cursor hit.
The database reference ID and the cursor-hit position of any linear element on the Sheet
(for example a STRA, side of a RECT, part of Design item, etc) may be queried using:
Q IDLINE @
The query returns the database of the picked element (DRAFT or DESIGN), the identity
of the element, the pair of 2D coordinates which define the linear element, and the 2D
position of the cursor hit.
For example, if the query were applied to a STRA element with FPT X100 Y100 and
TPT X200 Y200, the following could be returned:
DRA =151/4636 LINE X 100mm Y 100mm X 200mm Y 200mm QUAL X 167mm Y 166mm
If the query were applied to a part of a Design element, the following could be returned:
DES =35/222 LINE X 6.5/16 Y 7.19/32 X 5.3/32 Y 7.19/32 QUAL X 6.1/32 Y
7.19/32
4Handling Common Drafting Primitives

When the DRAG command is used on a specified drafting primitive, this causes its
drafting points to move. Other primitives which use the same drafting points will also
change position. (Straights and Arcs may also change in shape.) These primitives are
the common drafting primitives for specified primitive.
In order to help predict the effect that a DRAG command will have, the common drafting
primitives may be highlighted or queried. The basic syntax is as follows:
HIGhlight [prim_id] COMmon
Query COMmon- at a primitive
where prim_id identifies a drafting primitive. If prim_id is omitted, the common
primitives for the current element are highlighted/queried.
The DRAG command may also be used on an individual node of a Straight or Arc. The
common primitives of a node may be highlighted or queried, using the following syntax:

Version 11.5
2D Drafting
HIGhlight prim_id COMmon prim_id
Query node_id COMmon
Query COMmon node_id

} At a primitive
For a Straight these are FPT (‘from’ point), TPT (‘to’ point) or MPT (midpoint); and for
an Arc these are FPT, TPT, CPT (centre point) or THPT (‘through’ point).
The node must be currently used by the Straight or Arc: a Straight has either a single
node, MPT or two nodes, FPT and TPT; an Arc has an FPT, TPT and either a CPT or a
THPT. If an unset node or an illegal node is specified, then an error is output.
4Moving all Primitives in a NOTE or VNOT

Moving all of the member primitives of a NOTE or VNOT is done simply by changing
the NOTE/VNOT’s origin position (XYPO attribute). This is the offset of the origin from
the origin of the NOTE/VNOT’s owner (i.e. SHEE/VIEW respectively). The origin of a
SHEE is at its bottom left-hand corner and that of a VIEW at the centre of the VIEW
rectangle. XYPO may be changed directly or by the OFFSET command, for example
OFFSET X50 Y50
- position NOTE/VNOT’s origin at given offset owner’s origin
AT @
AT X400 Y400
- position NOTE/VNOT’s origin at given position on SHEE
BY @
BY X60 Y-20
- shift NOTE/VNOT’s origin by given amount
ADEG 30
- rotate NOTE to 30 from horizontal
NOTE: If a VNOT is moved or rotated, only primitives positioned in 2D will move with
it. The positions of primitives positioned in 3D or on Design elements will
remain unchanged.
4Rotating a Primitive
A primitive of type ARC, CIRC, STRA, ELLI, RECT, HEXA, TABL, DMND, ETRI,
OUTL or MRKP can be rotated using the ROTATE command to specify an angle of
rotation and a point to rotate about. Any position reference may be used to specify the
rotation point. For example:
ROTATE 45 @
Use cursor to specify 2D point to rotate about
ROTATE 45 IDP@
Use cursor to specify Design p-point to rotate about
4Mirroring a Primitive
A primitive of type ARC, CIRC, STRA, ELLI, RECT, HEXA, TABL, DMND, ETRI,
OUTL or MRKP can be mirrored using the MIRROR command to specify a mirror axis.

Version 11.5
2D Drafting
The current element may be mirrored in an existing linear element or two independent
points may be specified to define the mirror axis. In the latter case, any position
reference may be used to specify the axis points. For example:
MIRROR IN @
Use cursor to specify existing linear element to mirror in
MIRROR ABOUT @ @
Use cursor to specify two points to define mirror axis
4Copying a Primitive
Copying a primitive to another position or series of positions is done by using the
REPEAT command with the primitive you wish to copy as current element. The REPEAT
command has three syntax variations, illustrated by the following examples:
REPEAT 5 BY X20 Y20
Produce five copies of the current primitive, each displaced (X20, Y20)
from the last
REPEAT 5 BY @
Produce five copies of the current primitive, using the cursor to define
displacement
REPEAT 5 @
Produce five copies of the current primitive, but with first copy at
cursor position, displacement of second and subsequent copies equal to
that of first copy from original
REPEAT @
Produce five copies of the current primitive, but just one repetition
Figure 9-6 illustrates the use of the REPEAT command.

Version 11.5
2D Drafting
25
REPE 10 BY Y -25
Figure 9-6 Drafting Primitives - Use of the REPEAT Command
4Graphical Feedback
Many cursor commands generate graphical feedback (rubber banding) which makes
the interaction process easy - holding down the left-hand mouse button and moving the
mouse enables the primitive being created to be dragged out to the required
size/orientation. Use of the commands listed below gives the Point Construction Option
Form, from which you can choose to define point(s) not only as simple 2D cursor hits but
also as line end-points, circle centre-points, intersection points etc. The relevant
commands are:
Command Valid Elements
REGN @ VIEW
DEF @ All 2D drafting primitives
ADEF @ ARC
DIAMETER @ CIRC, HEXA
SPAN @ VRTX
RADIUS @ CIRC, HEXA, ARC
ASUB @ ARC
TPT @ STRA, ARC
FPT @ STRA, ARC
MPT @ STRA
CPT @ ARC
THPT @ ARC

Version 11.5
2D Drafting
9.4.2 Re-use of Drafting Points

In order for a DRAG command to drag a group of primitives which have the same initial
position they must share a drafting point. The primitives that do so may be listed using
the Q COMMON command or flashed by the HIGHLIGHT COMMON command. The use of
a shared drafting point may be achieved in one of the following ways:
• When a drafting point is created without specifying its position it will be positioned
using the default drafting point. This is normally the last point used. (This applies
to the initial node for a Straight or an Arc.) For example the series of commands:
NEW CIRC RAD 50 AT @

NEW CIRC RAD 25
NEW ARC TCODE CENTRE RAD 75 ASUB 90
would create two concentric circles and a concentric arc. If the arc were moved using
the DRAG command then the two circles would also move.
• When a primitive is positioned very close to an existing drafting point in the same
NOTE, VNOT or SYTM then the point will be re-used to position the new primitive.
The default tolerance for re-use of points is 1 mm on the Sheet, although some
commands (e.g. BY) work to a tolerance of 0.001 mm.
The tolerance used may be controlled by the TOLERANCE command, for example:
TOLERANCE 0.5 Set tolerance to .5 mm
TOLERANCE may be reset to its default value by the command
TOL DEF
Control over the TOLERANCE setting is particularly important for the re-input of
DATAL macros. The re-use of drafting points within the TOLERANCE limit can
lead to unsatisfactory performance when a NOTE contains a large number of points.
This may happen, for example, when Symbol definitions or Backing Sheets are
input from macros.
The current TOLERANCE status and value may be queried by
Q TOL
The current tolerance will also be output to file by the RECREATE DISPLAY
macro.
If neither of these methods are appropriate, the current primitive must be explicitly
positioned on the required drafting point. The drafting points used by a specified
primitive may be identified by querying its PTRF attribute (PTFA attribute for a
Straight or Arc) or by using the IDDP @ command.
The current primitive may then be positioned on the required drafting point by
commands such as:

Version 11.5
2D Drafting
ORIGIN point_identifier, e.g. ORIG IDDP@

ORIGIN IDDP @
FPT point_identifier e.g. FPT IDP@
DRAG TO IDDP @
(The Q IDN @ command may be used to identify the FPT or TPT of a STRAIGHT.)
9.4.3 Visibility of Drafting Primitives

The derived visibility of a drafting primitive may be extracted into expressions. The
attribute name is PRMVISIBILITY. This is TRUE if all owners of a primitive are
visible. For a primitive or Vertex below a VNOT, this means that PRMVIS is TRUE if
the VNOT, LAYER and VIEW are all visible (i.e. if their LVIS attributes are all TRUE).
PRMVIS is true below a NOTE if the NOTE is visible, and PRMVIS is always true below
SYTMs. For example
(ALL NOTE MEMBERS WITH PRMVIS TRUE)
9.4.4 Enhancing Drafting Primitives

Drafting primitives may be emphasised in a more permanent fashion than the flashing
provided by the HIGHLIGHT command, see Section 6.6, Part 1, Basic Drawing Creation
& Output. This is controlled by the ENHANCE command, which has the general form:
ENHANce [SOLEly] selection_criterion selection_criterion . . .
For example:
ENHANCE SOLELY CE
ENHANCE SOLELY ALL CIRC FOR LAYER
ENHANCE ALL STRA WI ( ATTRIB LENG GT 400 ) FOR /SHEET12
ENHANCE ALL WI ( NLPN GE 11 AND NLPN LE 20 ) FOR NOTE
If the SOLELY option is used then all existing enhancing will be removed, otherwise
existing enhanced elements will be unaffected by this command.
The FOR element_identifier command option is important, since without it the selection
system will scan around the entire MDB.
Enhancing may be removed by the UNENHance command, which may optionally specify
a selection criterion. The brief command
UNENHANCE
removes all enhancing and should always be used for that purpose.
The command
UNENHANCE ALL
should NOT be used as it causes the entire MDB to be scanned.
The list of currently enhanced elements may be queried by:
Q ENHAnce [LIst]

Version 11.5
2D Drafting
The colour in which elements are enhanced may be changed and reset by:
SETENHAnce COLour integer
SETENHA COL BRIGHTORANGE
SETENHA COL DEFAULT (sets enhance colour back to default of
aquamarine)
Overlay (OLAY) elements can also be enhanced.
Entering MDB mode causes all chosen elements to be unenhanced and the enhanced
element list cleared out. When doing a SAVEWORK or a module change the enhancing
will not be permanently written to the picture file. However after a SAVEWORK
command the enhanced element list will still exist and the elements will remain
enhanced on the screen.
When creating plotfiles, enhancing will be ignored. Enhanced elements may also be
HIGHLIGHTed.
9.4.5 Creating and Manipulating Drafting Primitives - Specific

Operations
This section describes primitive-specific operations. If an operation is not specified then
it is ‘universal’ (i.e. applies to all primitives and as such is described in the previous
section) or it is similar to the same operation as described for the CIRCLE primitive.
ARC (ARC)
Attributes
PTFA - Point references (3)
NLPN - Note line pen
RADI - Radius
ASUB - Angle subtended
TCOD - Type code (defines how to interpret attributes). Either set to
ENDPOINT or CENTRE.
Basic Creation Method
An ARC can be defined in three ways:
• by defining the positions of the end-points and a ‘through’ point (from which the
values of Radius (RADI) and Angle Subtended (ASUB) can be derived if required).
• by defining the position of the centre point, ‘from’ point and Angle Subtended (from
which the position of the ‘to’ points and the value of RADI can be derived if
required).
• by defining the position of the centre point and two end points.
The method:

Version 11.5
2D Drafting
NEW ARC
DEF @
results in three points being prompted for (the ‘start’, ‘end’ and ‘through’ points). A line
is drawn through the points and TCOD is set to ENDPOINT. See Positioning
(absolute) overleaf for the second method. If used with an existing ARC any existing
values of RADI and ASUB are altered accordingly.
Defining or redefining an Arc with a centre- and two endpoints is achieved using the
command:
ADEFine <dfnpt> <dfnpt> <dfnpt>
where <dfnpt> defines a position (2D, 3D, p-point etc).
The first two points are the centre - (CPT) and ‘from’ point (FPT) of the Arc. These two
points define the radius. The third point defines the angle subtended by the arc. The
TO-point (TPT) lies in this direction from the Centre (CPT) at the same distance as the
FPT from the CPT. The TCOD attribute is set to CENTRE.
This command may also be used with the cursor:
ADEFine @
A prompt requests three 2D points to be input for CPT, FPT and angle subtended. 3D
points may also be input using the cursor:
ADEFine ID@ ID@ ID@
DEFine IDP@ IDP@ IDP@
Changing Radius and Angle Subtended
RADIUS value [DESIGN]
Sets RADI. For TCOD CENT this moves the ‘from’ and ‘to’ points radially (by the change
in the value of the radius). Centre point position and ASUB are not altered. For TCOD
ENDP this moves the ‘through’ point and changes ASUB; the positions of ‘from’ and ‘to’
points are unchanged.
RADIUS X value Y value
RADIUS E value N value U value
RADIUS IDP @
etc.
For TCOD ENDP this is like THPT @.
ASUBTENDED value [ANTICLOCKWISE]
ASUBTENDED value CLOCKWISE
Sets ASUB. (A positive angle is anticlockwise, a negative one clockwise.)
For TCOD ENDP this repositions the ‘through’ point (mid-way along the Arc) and
changes RADI; ‘from’ and ‘to’ point positions are unaltered. For TCOD CENT this
moves the ‘to’ point of the arc. Centre and ‘from’ points and radius are unchanged.
ASUBTENDED CLOCKWISE
ASUBTENDED ANTICLOCKWISE
Sets the value of ASUB to be negative or positive, respectively.

Version 11.5
2D Drafting
ASUBTENDED @
For TCOD ENDP this is like THPT @; For TCOD CENT this alters the angle subtended
and hence moves the ‘to’ point of the Arc. The new position of the ‘to’ point lies on the
line joining the centre-point and the cursor position; centre and ‘from’ points and radius
are unaltered.
Positioning (absolute) (of an arc point)
The syntax is similar to that for FPTs of STRAs. Possible points are CPT (centre point),
FPT (‘from’ point), TPT (‘to’ point) and THPT (‘through’ point).
CPT @
etc
This changes the arc to be one with TCOD CENT (if not already so). The Centre is
moved whilst keeping the ‘from’ point and ASUB unaltered. The ‘to’-point and radius are
recalculated.
THPT @
etc
This changes the Arc to be one with TCOD ENDP (if not already so). The position of the
‘through’ point is moved whilst keeping the ‘from’ and ‘to’ points fixed - i.e. both radius
and angle subtended are altered.
FPT @
TPT @
etc
For arcs with TCOD ENDP, the ‘from’ or ‘to’ point of the Arc (as appropriate) is moved
whilst maintaining the positions of the other end point and the ‘through’ point.
For Arcs with TCOD CENTRE, the ‘from’ or ‘to’ point of the Arc (as appropriate) is
moved whilst maintaining the position of the centre and the angle subtended. Thus the
radius may change and the position of the other end point will be moved to preserve the
angle subtended.
Repeated Copying
See Circles.
Querying
Similar to Straights, but referring to RADIUS, ASUBTENDED, CPT, FPT, TPT and
THPT as appropriate. The Q IDN @ command may also be used
Dragging another primitive to which the Arc is connected
During the course of a DRAG operation on another primitive, the points of the Arc may
move. The effect on the Arc is as follows.
• for arcs with TCOD ENDP, Radius and Angle subtended are changed.
• for Arcs with TCOD CENT, if the centre point is dragged, then the positions of the
‘from’ and ‘to’ points are also moved to preserve the Arc’s appearance.

Version 11.5
2D Drafting
• For Arcs with TCOD CENT, if an end point is dragged, then a rotation about the
other endpoint takes place, i.e. the centre point is moved and the radius changed.
CIRCLE (CIRC)
Attributes
PTRF - Point Reference for origin
NLPN - Note Line pen
FPEN - Fill pen
OCOD - Origin Code (CENTRE, CIRCUMFERENCE)
ADEG - Angle in owner (useful for OCOD = CIRCU)
DIAM - Circle diameter
Basic Creation Method
NEW CIRCLE DEF X value Y value X value Y value
(‘manual’ method of NEW CIRCLE DEF @ command described in
section 14.4.1. This method applies to all primitives described
below, except where otherwise specified.)
Note: If used with an existing Circle the DEF command always sets ADEG=0 and
ORIG=CENTRE
Identification
ID CIRC @
This method applies to all primitives described described below, for
example ID ELLI @ (ellipse), ID RECT @ (rectangle) etc.
Resizing
DIAMETER value [DESIGN]
RADIUS value [DESIGN]
If DESIGN specified and if underneath a VIEW from which a scale
can be obtained, then a scaled circle will be drawn and the
diameter stored in the database as a Design value.
DIAM @
Sets DIAM equal to the distance between the two points, ADEG
equal to the angle to this line from X axis; if ORIG is
CIRCUMFERENCE, origin is positioned at the first hit.
DIAM X value Y value X value Y value

Manual method
Redefining the Origin

ORIGIN @
Prompts:
Select a possible origin of the CIRC

Version 11.5
2D Drafting
ORIG CENTRE
Sets ORIG as required and changes position of origin to point
specified . The Circle itself does not move.
ORIG CIRCUMFERENCE
Positioning (absolute)
ORIG X value Y value
ORIG CENTRE @
ORIG CIRCUMFERENCE @
ORIG IDP @
ORIG POS @
ORIG ID @
ORIG IDDP @
The last option (ORIG IDDP @) places the primitive on the drafting point used by
another primitive and hence ensures connectivity for the DRAG command.
Moving about the origin
OCOD CIRCUMFERENCE
Moves origin to circumference of Circle. See Figure 9-7.

Version 11.5
2D Drafting
Figure 9-7 Moving about the Origin - Use of the ORIG Command
Rotating about the origin

ADEGREE value
Sets ADEG as specified, causing the circle to rotate about its
origin. (If this is at the centre then no visible change results.)
Querying
In addition to the standard attribute queries the following are provided:
Q DESC
Queries the origin, position and diameter

Version 11.5
2D Drafting
Q DIAM
Queries the diameter in Annotation or Design coordinates as
appropriate
Q ORIG
Queries the origin and its position
Q OFFS
Queries the position relative to the NOTE origin
DIAMOND (DMND)
Attributes
PTRF - Point reference for origin
FPEN - Fill pen
OCOD - Origin code (CENTRE, TSIDE, BSIDE, LSIDE, RSIDE)
ADEG - Angle in owner
XLEN - X axis length
YLEN - Y axis length
Resizing
As for Ellipses.
All other operations are as for Circles.
ELLIPSE (ELLI)
Attributes
FPEN - Fill Pen
OCOD - Origin code (CENTRE, FOCUS TSIDE, BSIDE, LSIDE, RSIDE)
Resizing
XLEN value [DESIGN] DESIGN option applies to VNOT members only
YLEN value [DESIGN]

Version 11.5
2D Drafting
XLEN @ Changes the XLEN by distance along the X axis of the

XLEN IDDP @ primitive from the origin. Note that this is not necessarily the
XLEN IDG @ Sheet or Note axis. If the origin is at the midpoint of the X axis
XLEN IDP @ (i.e. ORIG CENTRE) then XLEN will be twice this distance. If
XLEN ID @ appropriate a Design distance will be used
YLEN @ Changes the YLEN by distance along the Y axis of the
YLEN IDDP @ primitive from the origin. Note that this is not necessarily the
YLEN IDG @ Sheet or Note axis. If the origin is at the midpoint of the Y axis
YLEN IDP @ (i.e. ORIG CENTRE) then YLEN will be twice this distance. If
YLEN ID @ appropriate a Design distance will be used

ORIGIN @
Sets ORIG as required and changes position of origin to point
specified. The ellipse itself does not move
ORIG CENTRE
ORIG RSIDE
ORIG LSIDE
ORIG TSIDE
ORIG BSIDE
EQUILATERAL TRIANGLE (ETRI)
Attributes
FPEN - Fill pen
OCOD - Origin code (CENTRE, LSID, APEX, BRIGHT, BLEFT, RSIDE,
BASE)
FRAD - Fillet radius
LENG - Side length
Resizing
LENGTH value [DESIGN]
Sets side length

Version 11.5
2D Drafting
THROUGH @
THRU @
Prompts:
Input a point on the current sheet
Sets LENG so that the triangle passes through the point specified.
This may not necessarily be a corner - ADEG will not be altered.
THR X value Y value

Manual method
FRADIUS value [DESIGN]

Sets FRAD to value specified. If this is too big for the existing
value of LENG then a warning is output, the triangle is drawn
sharp-cornered, but the FRAD attribute is set as specified and will
be used when the LENG value is made large enough.

ORIG @ prompts: Select a possible origin for the ETRI
ORIG APEX
ORIG BASE
ORIG LSIDE
ORIG RSIDE
ORIG BLEFT
ORIG BRIGHT
HEXAGON (HEXA)
Attributes
FPEN - Fill pen
OCOD - Origin code (CENTRE, CIRCUMFERENCE)
DIAM - Diameter of the enclosing circle
As for Circles. ORIG CIRCUM refers to a vertex of the Hexagon
MARKER PRIMITIVE (MRKP)
Attributes

Version 11.5
2D Drafting
Note that the NLPN attribute must be set in conjunction with the SETPEN command.
For example, to display a ‘cross’ marker the command sequence:
SETPEN 2 CROSS
NLPN 2
would be required. Section 8.6.2, Part 1, Basic Drawing Creation & Output for details of
the SETPEN command.
All other operations on Markers are similar to those for Circles (where relevant).
OUTLINE (OUTL) and VERTEX (VRTX)
An Outline consists of a user-defined series of connected straight lines and circular arcs
(collectively known as spans). OUTL elements do not have any geometry or positional
data themselves, because they are of indeterminate complexity. This is provided by a list
of owned Vertex (VRTX) elements. The origin of an OUTL is considered to be at the
position of its first VRTX. As an alternative to straight lines and circular arcs, a smooth
quadratic curve may be drawn through the vertex points of the OUTL (see CURFIT
below).
Attributes
(OUTL)
FPEN - Fill pen (used to hatch the area enclosed by the OUTL)
MPEN - Marker pen
CURFIT - Curve fitting control
Setting CURFIT to CUBICFIT will cause a smooth quadratic curve (which approximates a
series of cubic curves) to be drawn through the vertex points of the OUTL. CURFIT
DEFAULT turns off the curve-fit function.
(VRTX)
PTRF - Point reference
BULG - Bulge factor
NLPN
MPEN
- Note line pen
- Marker pen } (Can override settings at OUTL)
CHAM - Chamfer distances

Bulge Factor
The BULG attribute is unique to the VRTX element, and is the ratio of the maximum
departure of the arc from the chord joining two VRTXs to the chord half-length. It is
positive when the span lies to the right of the chord when viewed in the direction VRTX1
to VRTX2, negative when it lies to the left. A straight span has a BULG of 0, a counter-
clockwise semicircle a BULG of 1.0, and a clockwise semicircle a BULG of -1.0. BULG
would not normally be set explicitly, but indirectly by the SPAN command (see below).
Chamfering
A chamfer may be applied between two VRTXs using

Version 11.5
2D Drafting
CHAMFER value [value]

The value(s) supplied in the above syntax must be greater than or equal to 0. If two
values are supplied then the first chamfer distance will correspond to the chamfer
joining the current VRTX to the previous one, and the second will correspond to the
chamfer joining the current VRTX to the next. If only one chamfer distance is supplied,
then both chamfer distances will be set equal. Setting the chamfer distance to 0 is
equivalent to setting it to OFF. If the chamfer distance is set on a VRTX then the spans
on either side of it will be drawn straight, i.e. the BULG attribute of the current and
next VRTX will be ignored. CHAMFER OFF will remove the chamfer.
Filleting
A fillet may be applied to a VRTX using
FRADIUS value
Any value may be supplied in the above syntax. A positive value will correspond to a
convex fillet radius at the VRTX, a negative value to a concave fillet. Setting FRAD to 0
is equivalent to setting it to OFF. If the fillet radius is set on a VRTX then the spans on
either side of it will be drawn straight, i.e. the BULG attribute of the current and next
VRTX will be ignored.
VRTX Basic Creation Method
The OUTL and VRTX elements may be created and deleted in the usual manner, e.g.
NEW OUTLine
NEW VRTX AT @
DELETE VRTX
The position of a VRTX and the shape of the span drawn to it from the previous VRTX
are defined by the SPAN command. This command is valid at any VRTX except the first
in list order. Variations of the SPAN command are:
SPAN TO position Vertex point defined by <position>
SPAN THROUGH position Span defined as a circular arc passing
through position. Defines BULG.
SPAN TO positionTHROUGH position
SPAN THROUGH position TO position

} Above two commands combined.
Also SPAN @
SPAN TO CLOSE Vertex point coincident with starting

vertex.
SPAN STRAIGHT TO position Straight line span with vertex at <position>
SPAN RADIUS value Set radius of circle of which (arc) span
forms a part. Converts straight line span to
an arc.
SPAN ASUB value Sets angle subtended by (arc) span.
Converts straight line span to an arc.

Version 11.5
2D Drafting
SPAN BY xypos Move the two VRTXS of the current span by

the given displacements.
SPAN DRAG BY xypos Move the two VRTXS and all connected
drafting primitives of the current span by
the given displacements.
position can be a Design p-point, a 3D point or an explicit Sheet coordinate. A cursor hit
can be used with all except the CLOSE, RADIUS, ASUB and STRAIGHT options. The
position of a VRTX can also be constructed - see Section 11. If a VRTX is made
coincident with the drafting point of another 2D primitive then a logical connection will
be established and the DRAG command will affect the VRTX and the other 2D primitive.
The TO option defines the position of the VRTX without affecting the bulge factor and is
thus similar to the standard DEF command. The CLOSE option positions the current
VRTX to be coincident with the first VRTX of the OUTL and thus closes the Outline.
This does not have to be the last VRTX though - subsequent VRTXs can be created.
The BY and DRAG BY options move the VRTXs at the start and finish of the span by the
specified amount - bulge factor and curvature are unaffected. The THROUGH, RADIUS
and ASUB options only define the bulge factor - knowledge of the through point, radius
and angle subtended are lost. They do not change the position of VRTXs, only the
curvature of the span.
The RADIUS option can have a negative value - this will result in a negative BULG and
hence a span drawn in a clockwise direction. If the radius specified is not large enough
to define the curvature of the span between two VRTXs then the command will be
ignored and a warning message output, giving the minimum possible radius. By default
the command gives the minor arc, the major arc being given by
SPAN RADius value MAJor
The command SPAN @ (or NEW VRTX SPAN @) gives a simplified way of defining the
span. By default, you must define the TO position by a cursor hit, a straight-line span
being assumed. The Outline Span Construction form will appear, giving you various span
definition options. See the on-line help for details.
Querying
Q DESCription is valid at OUTLs and VRTXs, giving details of origin coordinates and
span radius and angle subtended (if appropriate). Q SPAN RADius and Q SPAN
ASUBtended are valid at VRTXs only (but not at the first VRTX in an OUTL).
Miscellaneous Commands
The Q COMmon, HIGhlight, SKEtch POInts, SKEtch ORIgins and ID @ commands are all
valid at OUTLs and/or VRTXs. Note that SKETCH ORIG ALL does not sketch all VRTX
origins - only the origins of the owning OUTLs - i.e. the first VRTX below each OUTL.

Version 11.5
2D Drafting
RECTANGLE (RECT)
Attributes
FPEN - Fill pen
OCOD - Origin code (CENTRE, LSID, TLEFT, TSIDE, BSIDE, RSIDE,
TRIGHT, BLEFT, BRIGHT)
Resizing
XLEN value [DESIGN] DESIGN option applies to VNOT members
YLEN value [DESIGN] only
SQUARE value [DESIGN] Sets XLEN and YLEN to value specified.
XLEN @ Uses relevant offset from origin of primitive to
YLEN @ define XLEN or YLEN as required.
XLEN X value Y value Manual method
YLEN X value Y value
THROUGH @ Prompts:
THRU @ Input a point on the current Sheet
Sets XLEN and YLEN so that a corner of the
rectangle is positioned at the point specified.
THR X value Y value Manual method
FRADIUS value [DESIGN] Sets FRAD to value specified. If this is too big
for the existing XLEN or YLEN values then a
warning is output and the rectangle is drawn
square-cornered. FRAD will be set as specified
and will be used when XLEN and YLEN are
made large enough.

As for ELLIPSE, but also:
ORIG TLEFT
ORIG TRIGHT
ORIG BLEFT
ORIG BRIGHT

Version 11.5
2D Drafting
Creating Rectangles and Squares

Rectangles can be created using the commands:
ADEFine dfnpt1 dfnpt2 Defines a rectangle where dfnpt1 defines a
position (2D, 3D, p-point etc) which is the
centre of the rectangle, and dfnpt2 defines
the position of a corner.
ASDEFine dfnpt1 dfnpt2 Defines a square where dfnpt1 defines the
centre of the rectangle, and dfnpt2 defines
the position of a corner.
SDEFine dfnpt1 dfnpt2 Defines a square where dfnpt1 and dfnpt2
define the positions of the corners
For example:
ADEF X400 Y400 X500 Y450 Defines a RECT 200 by 100 with its centre
at X400 Y400 and a corner at X500 Y450.
SDEF X400 Y400 X500 Y450 Defines a RECT 100 square with one
corner at X400 Y400 and the other at
X500 Y500.
ASDEF X400 Y400 X500 Y450 Defines a RECT 200 square with its centre
at X400 Y400 and a corner at X500 Y500.
These commands may also be used with the cursor, for example:
ADEFine @
A prompt requests two 2D points to be input.
STRAIGHT (STRA)
Attributes
PTFA - Point references (2)
LENG - Length
TCOD - Type code (defines how to interpret attributes). Set either
to ENDPOINT or MIDPOINT.
Basic Creation Methods
A STRA can be defined in two ways:
• By defining the positions of the end-points (from which the values of length and
angle can be derived if required).

Version 11.5
2D Drafting
• By defining the position of the mid-point and values of LENG and ADEG (from
which the positions of the end-points can be derived if required).
The commands:
NEW STRA
DEF @
results in two points being prompted for; a line is drawn between the two points and
TCOD is set to ENDPOINT. See the section on Positioning (absolute) below for the
second method.
The command:
ODEF @
prompts for two points. The straight will be vertical or horizontal depending on the
relative sizes of the horizontal and vertical offsets between the two points given.
Changing length or slope
LENGTH value [DESIGN] Changing LENG or ADEG for a two-point
STRA will move the ‘to’ point.
ADEG value
LENGTH @ Moves the From point of the STRA,
changing its LENG and ADEG attributes.
ALENGTH @ Moves the To point of the STRA, changing

its LENG and ADEG attributes.
Positioning (absolute)
A STRA may have its ‘from’ point, ‘mid’ point or ‘to’ point positioned or moved. Apart
from the initial keyword (FPT, MPT, TPT) specifying which point you are setting the
syntax is similar throughout, as the following examples show:
To position at a 2D (i.e. X,Y) position:
FPT @ prompts: Enter a 2-d position
FPT X 50 Y -250
To position at a 3D (i.e. ENU position):
FPT POS @ prompts: Input a point in a View
FPT E12500 S5000 U0
To position on a p-point:
FPT ID @ prompts: Identify element
FPT IDP @ prompts: Identify design ppoint
FPT /PUMP2/N1
FPT P1 OF /PUMP2/N1
If the MPT command is used, the TCOD will be set to MIDPOINT. This is a single point
STRAIGHT and must have its LENGTH set.

Version 11.5
2D Drafting
A straight can also be created by giving an an orthogonal To point:

OPPT x 50 y 97
OTPT @
The straight will be vertical or horizontal depending on the relative sizes of the
horizontal and vertical offsets between the From point and the To point.
Points on a STRA (FPT, TPT etc) may be identified using the command:
Q IDN @
Positioning (relative)
It is possible to move a STRA or one of its points by a given amount. For a single point
STRA (i.e. one with a mid-point) there will be no difference between moving the STRA
itself or its mid-point, but for a two point STRA moving its ‘from’ or ‘to’ point will cause
its length and/or its slope to change; the position of the other point will remain
unchanged.
BY @ prompts: Input two points on a sheet
or: Input two points in the same View
depending upon whether the STRA is currently positioned on a 2D point or a 3D/p-
point.
BY X55 Y-678 STRAs positioned at a 3D point cannot be shifted by
BY N500 W1200 an X,Y amount, and vice versa.
DRAG BY @
DRAG BY X120 Y-45 - see comments for BY command
DRAG BY S3500 D500
FPT BY @ prompts: Input two points on a sheet
or: Input two points in the same View
depending upon whether the point is currently positioned on a 2D point or 3D/p-
point.
FPT BY X55 Y-678 Points positioned at a 3d point cannot be shifted
FPT BY N500 W1200 by an XY amount, and vice versa.
FPT DRAG [BY] @ These commands change the position of the
drafting point FPT DRAG TO @ to which the FPT is
attached and hence will change the position of
other primitives attached to the same point.
Repeated Copying
See Circles.
Querying
Q DESC queries the Length and point attributes, i.e.

Version 11.5
2D Drafting
LENGTH value
ADEG value
FPT X value Y value
TPT X value Y value
Q FPT Queries the position of the ‘from’ point if
set. Similarly for TPT, MPT
Q OFFS Queries the offset positions of the points set
(relative to the Note origin)
Q FPT OFFS Queries the offset of the ‘from’ point
relative to the Note origin (similarly for
TPT, MPT)
SKETCH POINTS Sketches all points currently in use for the
STRA
SKETCH FPT Sketches the ‘from’ point (if set) - similarly
for the TPT and MPT
SKETCH ORIG Sketches first node
SKETCH POINTS ALL At NOTE level, displays all the points
currently in use for all member primitives
SYMBOL INSTANCE (SYMB)
Attributes
TMRF - Template reference
XYSCALE - Scale in X, Y directions
When instancing a symbol (SYMB), the TMRF attribute should reference a symbol
template (SYTM) in the symbol library (SYLB). If this attribute is not set, nothing will
be drawn.
Changing size and orientation
XYSCALE value value Negative values give a ‘mirroring’ effect
SYSIZE value Sets X and Y scales equally
SYSZ @ @
SYSIZE @ @
ALENGTH value Changes the length of a straight by moving
its From Point
ALENGTH @ Changes the length of a straight by moving
the end nearest to the cursor
You are requested to input two points; the first point selects a position on the symbol,
the second point sets a new position for the selected point. The new symbol size is
calculated from the ratio of the distances of those two points from the symbol origin.

Version 11.5
2D Drafting
SHIFT @ @ as above, but alters ADEG as well as the

symbol size.
Updating Symbol Instances
The command
UPDATE INSTANCES
valid at SHEE, BACK, OVER, SYLB, LALB or above, scans the database hierarchy and
updates all those parts of picture files which use the graphics instancing mechanism.
For example, a SYMB is an ‘instance’ of a SYTM. OLAY and BACK elements are in the
same category.
TABLE (TABL)
Attributes
OCOD - Origin code (CENTRE, LSID, TLEFT, RSIDE, TSIDE,
BSIDE, TRIGHT, BLEFT, BRIGHT)
NROW - No. of rows
NCOL - No. of columns
RPEN - Pen for Internal Rows (if set)
CPEN - Pen for Internal Columns (if set)
All operations, including definition using the ADEFine, ASDEFine and SDEFine
commands, are similar to those for Rectangles, except that FRAD does not apply.
Internal rows and columns are drawn using NLPN by default. If RPEN or CPEN are set,
internal rows and columns may be drawn in a different pen to the outline rectangle.
TEXT PRIMITIVE (TEXP)
Attributes
BTEX - Text string (may include # codes)
FONT - Text font
TPEN - Text pen (defines colour)
CHEI - Character height
LHEI - Letter height
CSPA - Character spacing factor
LSPA - Text line spacing factor
JUST - Justification
ALIG - Vertical alignment
Resizing
Set the CHEI, LHEI, CSPA or LSPA attributes.

Version 11.5
2D Drafting

Set JUST (justification) or ALIG (alignment).
All other positioning operations are as for Circles.
9.5 Text Strings
9.5.1 Entering Text from DRAFT

Text for use with the DRAFT 2D drafting facilities takes the form of TEXP elements
which must be created (as NOTE, VNOT or SYTM members) before the text itself can be
input. The text itself is input as the BTEX attribute of the TEXP, being positioned (by
default) at the default drafting point. The text can be repositioned by an AT @
command. The text size will probably need to be increased, which is done by setting the
CHEI (character height) or LHEI (letter height) attribute to a suitable value.
A TEXP has attributes governing its orientation (ADEG), text pen (TPEN), font (FONT),
horizontal justification (JUST), character/letter height and spacing (CHEI/LHEI, CSPA)
and line spacing and alignment (LSPA, ALIG). All these attributes are the same as
those for Label Text - see Section 4 for details.
In addition to the facilities outlined above, TEXP elements which are NOTE/VNOT
members may incorporate intelligent text codes - see Section 5. TEXP elements which
are SYTM members may also incorporate intelligent text codes, but these will only be
expanded when the SYTM is referenced by a SLAB.
The command
Q EXTENT BTEX
may be used to give the extent of the BTEX text string. Four pairs of coordinates are
output, giving the coordinates of the corners of the rectangular area occupied by the text
in Top-left, Top-right, Bottom-right, Bottom left order with respect to the direction of the
drawn text string.
These coordinate pairs may be used to align another string of text with the queried text
string. The pair of coordinates to be used depends on the Justification and Alignment
attributes of the text to be aligned. Thus if JUSTIFICATION LEFT, ALIGNMENT TBODY
is being used, then the position of the next line of text is given by the fourth pair of
coordinates. This is true whatever the text orientation.
9.5.2 Displaying Text from a File on the Drawing

The contents of a text file may be read in and placed on a drawing using PML file
handling facilities. For example (when at a NOTE):

Version 11.5
2D Drafting
ALIG TB JUST L
OPENFILE /filename READ !TOKEN
READFILE $!TOKEN !RECORD
NEW TEXP AT @ BTEX ’$!RECORD’
VAR !EXTENT EXTENT BTEX
The EXTENT query (together with PML array and string-handling commands) may be
used to calculate the position of the next line of text.
Successive READFILE and TEXP commands may be used until the file is exhausted. The
file may then be closed using:
CLOSEFILE $!TOKEN
Note that any ‘$’ characters in the file should be doubled.
The PDMS Programmable Macro Language (PML) is detailed in the VANTAGE Plant
Design Software Customisation Guide.

Version 11.5
2D Drafting
Summary of Commands
Creating Primitives . . .
NEW CIRCLE DEF @ - use cursor to mark (in this case) circle centre and point on
circumference
NEW CIRC RAD 50 ORIG CIRCUM ADEG 45 AT X900 Y750

- define circle size and position explicitly
Shifting the Origin . . .

ORIG @ - origin Sheet coordinates change; primitive does not move
OCOD @
OCOD CEN - origin Sheet coordinates remain unchanged; primitive moves
to place itself according to new origin code
ORIG X300 Y250
OCOD TRIGHT @ - origin Sheet coordinates and origin code change; primitive
moves
SKETCH ORIG - display primitive origin
Moving Individual Primitives . . .

AT @
AT X300 Y250 - move to new 2D position
POS ID @
POS W5500 N12345 D120
- move to new 3D position (VNOT members only)
ON ID @
ON IDP @
ON /PUMP1
ON P1 OF /PUMP2/NS
- move to specified element origin or p-point (VNOT members
only)
BY @
BY X10.5 - move relative to current 2D position
BY N500 W1200 - move relative to current 3D position (VNOT members only)

Version 11.5
2D Drafting
Rotating Individual Primitives . . .

ROTATE 45 @ - use cursor to specify 2D point to rotate about
ROTATE 45 IDP@ - use cursor to specify Design p-point to rotate about
Mirroring Individual Primitives . . .

MIRROR IN @ - use cursor to specify existing linear element to mirror in
MIRROR ABOUT @ @
- use cursor to specify two points to define mirror axis
Moving Groups of Primitives . . .

DRAG TO @
DRAG TO X120 Y-45 - move to new 2D position
DRAG TO POS @ - move to new 3D position (VNOT members only)
DRAG TO IDP @
DRAG TO S3500 D500
DRAG TO P1 OF /VESS2/N6
DRAG BY @
DRAG BY X120 Y-45 - move relative to current 2D position
DRAG BY S3500 D500 - move relative to current 3D position (VNOT

members only)
Querying Primitives . . .
Q ORIG - queries origin and position of a primitive
Q COMMON - queries primitives with drafting points in common with the

current element
Q OFFSET - queries offset of a primitive origin from the Note origin
Q DESC - queries principal dimensional and positional attributes of a

primitive
Q IDN @ - queries point on the current STRA or ARC

Version 11.5
2D Drafting
Q IDNN @ - queries point on hit primitive
Copying Primitives . . .
REPEAT 5 BY X20 Y20 - produce five copies of the current primitive, each
displaced (X20, Y20) from the last
REPEAT 5 BY @ - as above, but use cursor to define displacement
REPEAT 5 @ - as above, but with first copy at cursor position, displacement

of second and subsequent copies equal to that of first copy
from original
REPEAT @ - as above, but just one repetition
Outlines . . .
NEW OUTL - creates a new Outline element
NEW VRTX AT @ - creates a new Vertex; use the cursor to define its position.
SPAN TO @ - vertex point defined by 2D cursor hit
SPAN TO IDP @ - vertex point defined by 3D Design p-point cursor hit

(similarly
SPAN TO, SPAN THROUGH, SPAN THROUGH . . . TO, SPAN TO
. . . THROUGH)
SPAN TO CLOSE - vertex point coincident with starting vertex; closes Outline.
SPAN STRAIGHT TO X value Y value

- straight line span with vertex at given Sheet coordinates.
SPAN RADIUS value - sets radius of circle of which (arc) span forms a part to given
value.
SPAN ASUB value - sets angle subtended by (arc) span to given value.
SPAN BY X value Y value - moves the two VRTXs of the current span by the
given displacements.
SPAN DRAG BY Y value - moves the two VRTXs and all connected drafting
primitives of the current span by the given
displacement.
CURFIT CUBICFIT - (at OUTL) draws quadratic curve through vertex points
CURFIT DEFAULT - turns off curve fit function

Version 11.5
2D Drafting
CHAMFER value [value] - applies chamfer between two VRTXs
FRAD value - applies fillet to current VRTX
Sketching Drafting Points . . .

SKETCH ORIGIN - at primitive level, displays primitive origin
SKETCH ORIGIN ALL - at NOTE level, displays origins of all member

primitives
SKETCH ORIGIN ALL IN identifier - displays origins of all drafting primitives

at/below the specified element
SKETCH POINTS - sketches all points in use for the current primitive
SKETCH POINTS ALL - at NOTE level, sketches all points currently in use
SKETCH POINTS ALL IN identifier - displays drafting points of all drafting

primitives at/below the specified element
SKETCH FPT - will sketch the ‘from’ point (if set) - similarly for the
TPT and MPT
Enhancing Display of Primitives . . .

ENHANce [SOLEly] selection_criterion . . .
- enhances display of specified primitives
UNENHANce - removes all enhancing
Q ENHAnce [LIst] - lists enhanced elements
SETENHAnce COLour integer

SETENHAnce COLour col-name
- sets enhancement colour

Version 11.5
10 ISODRAFT Symbols
You can create symbols in DRAFT which will be used on the isometrics produced by
ISODRAFT. The symbols are created as ISODRAFT Symbol Templates (ISOTMs),
which are similar to normal symbol templates, except that they can only own STRAs
and MRKPs. They have additional attributes, described in Section 10.1.
ISOTMs are stored in ISODRAFT Symbol Libraries (ISOLBs), which are identical to
SYLBs except that they can only own ISOTMs. The relevant part of the DRAFT
database is shown in Figure 10-1.
ISOLB
ISOTM
MRKP
STRA
Figure 10-1 ISODRAFT Symbol Libraries and Related Elements
10.1 Creating ISODRAFT Symbol Templates
ISODRAFT Symbol templates can only own STRAs, which define the geometry of the
symbol, and MRKP elements, which define the start, end, spindle and tee points on the
symbol. These elements should have their PURP attributes set as follows:
• STRAs owned by ISOTMs should have their PURP attributes set to LINE, INSU or
TRAC (to describe whether the straight represents the pipeline, its insulation or its
tracing).
• MRKPs owned by ISOTMs should have their PURP attributes set to one of ARRI,
LEAV, TEE or SPIN.
The Arrive and Leave points of the symbol will be used as the reference points for
dimensioning.

Version 11.5
ISODRAFT Symbols
10.1.1 Attributes of ISODRAFT Symbol Templates

The attributes of ISODRAFT Symbol Templates which are additional to the attributes of
normal symbol templates are as follows:
SKEY Symbol key: the SKEY of the new Symbol. If this attribute
is set to the SKEY of an existing symbol, the existing
symbol will be redefined. You can use wildcards to define a
symbol for several similar SKEYs, see Section 10.1.2.
BKEY Base symbol key. If a new SKEY is being defined, the
BKEY must be set to a standard SKEY. Wildcards can be
used, see Section 10.1.2
SCALe value Changes the size of the symbol without redefining the
coordinates of the plotted shape (100 = full size).
SPINdle Spindle symbol key. If this attribute is set, the Symbol
Template will include a spindle symbol. For more
information, see the PDMS ISODRAFT Reference Manual.
Default NONE.
ORIN NONE Specifies a symmetrical fitting which the flow direction is
not relevant
ORIN FLOW Specifies a fitting for which the flow direction is important,
such as check valves
ORIN REDUCER Specifies a reducing fitting
ORIN FLANGE Specifies a fitting which begins with a flange; that is, one
which is preceded by a gasket
FLWArrow TRUE Plots flow arrows on the symbol
FLWArrow FALSE Suppresses flow arrows
DIMEnsion TRUE Plots dimensions alongside the symbol. Default
DIMEnsion FALSE Suppresses the plotting of dimensions
INSL TRUE Insulation shown on symbol if specified. Default
INSL FALSE Insulation representation suppressed
TRCG TRUE Tracing shown on symbol if specified. Default
TRCG FALSE Tracing representation suppressed
FILL TRUE Symbol to be filled
FILL FALSE Symbol not filled. Default

Version 11.5
ISODRAFT Symbols
10.1.2 Wildcards in SKEYs

You can use the * character as a wildcard to define a symbol for several similar SKEYs.
For example:
SKEY ’VB**’
This illustrates the use of the ** characters to cover all end conditions, i.e. BW (butt
weld), CP (compression), SW (socket weld), FL (flanged), SC (screwed) and PL (plain),
when defining a new range of SKEYs. This sequence therefore defines the SKEYs
VBBW, VBCP, VBSW, VBFL, VBSC and VBPL in a single operation.
Note: The wildcard option applies only to the definition of SKEYs. You must specify a
particular end condition when you set the SKEY attribute of a DTEX element in
the Catalogue DB; for example, by setting it to VBBW or VBCP but not to VB**.
10.1.3 Example
The following commands are an example of how to create an ISODRAFT Symbol Library
and an ISODRAFT Symbol Template:
NEW ISOLB
NEW ISOTM
XYPS X200 Y200
SKEY ’SSSS’
SPIN ’NONE’
FLWA TRUE
BKEY ’VV**’
SCAL 100
FILL TRUE
NEW MRKP
PURP TEE
ORIG OFFS X0 Y0
NEW STRA
PURP LINE
TPT OFFS X4.0 Y1.0
NEW STRA
PURP LINE
TPT OFFS X8.0 Y1.0
NEW STRA
PURP LINE
TPT OFFS X8.0 Y-1.0
NEW STRA
PURP LINE
TPT OFFS X4.0 Y-1.0
NEW STRA
PURP LINE
TPT OFFS X0 Y0
NEW MRKP
PURP LEAVE
ORIG OFFS X8.0 Y0

Version 11.5
ISODRAFT Symbols
10.2 Outputting ISODRAFT Symbols
When you have defined the symbols you require in the Symbol Library, you must output
the Symbols to an ISODRAFT Symbol File using the ISOSYMBOL command. You can
open a new (or existing) file by giving the command:
ISOSYMBOL filename
The current symbol (ie ISOTM) can be added to the file by:
ISOSYMBOL ADD
A symbol which has been added but is not required can be removed from the file by
giving the command:
ISOSYMBOL DELETE skey
When all the symbols have been added, the file is closed by giving the command:
ISOSYMBOL CLOSE
This will overwrite an existing file.
10.3 Querying ISODRAFT Symbol Templates
The following querying commands are available:

Q ALL ISOTM - lists all ISODRAFT Symbol Templates
Q ALL ISOLB - lists all ISODRAFT Symbol Libraries
Q ISOSYM - list symbol keys and base symbol keys in the library
file
Q ISOSYM NUMBER - gives the number of symbols in the library file
Q ISOSYM n - gives the symbol key and base key for entry number n.

Version 11.5
11 Point and Line Construction
You can define a position in terms of other positions rather than defining it explicitly
using the point construction facilities in DRAFT. Point construction is available for
• Positioning of 2D drafting primitives
• Labelling, where a 2D position is required, e.g. positioning of gaps
• Dimensioning, where a 2D (or, if appropriate, a 3D) position is required, e.g.
positioning of a point through which a dimension line should pass
• Positioning of Overlay Sheets
• VIEW position attributes, e.g. THPO, FRPO, ONPO, VREG command
• SYTM and TXTM positioning.
As well as points, it is also possible to construct lines and arcs.
11.1 Introduction
A drafting point position may be specified explicitly, for example

ORIG X300 Y250
It is also possible to construct a drafting point position, using commands such as:
ORIG MIDP position position
ORIG OFFSET 2D_vector
ORIG position DIST distance
Here, position may be any of:
• A 2D position: ORIG MIDP X100 Y100 X800 Y800
• An existing drafting point: ORIG MIDP ID@ ID@
• A 3D position: ORIG MIDP E150 N7400 U1200 E2150 N4400 U3550
• A Design Item: ORIG MIDP /PUMP1/IN /PUMP1/ON
• A p-point: ORIG MIDP P0 OF /PUMP1/IN P0 OF /PUMP1/ON
• A position on a p-line: ORIG PLIN TOS OF /SECT1 START DIST 150
• The 3D position of a Design item, p-point or p-line position.
2D_vector specifies an offset position from the owner origin of the primitive concerned,
for example
ORIG OFFS X50 Y50

Version 11.5
Point and Line Construction
distance gives a distance and a direction from a point, and may be one of the following in
a NOTE or SYTM:
units_value ANGLE value
HORIZONTAL
VERTICAL
2D_vector
For example:
ORIG X50 Y50 DIST 200MM ANG 30
ORIG X50 Y50 DIST 200 HORI
ORIG X50 Y50 DIST 200 VERT
ORIG X50 Y50 DIST 100 X100 Y100
For a VNOT, distance may be expressed as
units_value DESIGN direction
where direction is a 3D, p-point or p-line direction. The distance specified is a Design
distance in the current View. The above syntax may also be used in most drafting
commands, e.g. FPT, TPT, CPT, DEFINE, DRAG TO, LENGTH, RADIUS etc.
All point constructions are carried out in the context of the current database position. If
the current element is owned by a NOTE or SYTM, a point construction will give a 2D
point. 3D point constructions (for example, positioning the centre of a circle on a Design
element position) are only allowed for drafting below VNOT elements.
In some cases there could be ambiguity about the point to be constructed, for example if
the point were defined using a tangent to a circle, or the intersection of two circles. In
cases such as this the point to be used can be qualified with a cursor hit.
The following sections describe the various types of point construction, with examples.
The symbol @ denotes a cursor hit.
11.2 X, Y Filtering
A 2D position may be defined in terms of the X or Y coordinates of other points. For

example, rather than an explicit point definition such as:
AT X200 Y200
a constructed point could be defined by:
AT X200 Y OF point
The above command would define a position whose Y coordinate would be the Y
coordinate of point, where point could include:
• The endpoint of a line or an arc
• The centre of a circle or an arc
• A tangency point

Version 11.5
• An intersection points
• The point on a line or an arc nearest to a given point
• The point defined by the perpendicular from a given point
The constructed point could also be defined explicitly or by a cursor hit. For example:
AT X200 Y OF @
Y coordinate is Y coordinate of cursor hit
AT X OF @ Y OF @
X coordinate from first cursor hit, Y coordinate from second cursor hit
The process of deriving a coordinate from a coordinate of another point is known as X, Y
filtering. X and Y filters may be used in any command which requires a 2D position on
a Sheet, including edits on various Dimension attributes. For example:
PTOF X OF /VALV1 Y @
DTOF X @ Y250
PLCL X @ Y OF POS E3000 S2000 U0
Y coordinate set to the Y coordinate of 2D projection of given 3D position.
3D positions may also be constructed, but this only applies to 2D drafting primitives
which are members of VNOT elements. X, Y filtering can be used with any 2D element
which has a position attribute, e.g. VIEWs, Labels, Dimension Points etc.
Examples
1. NEW STRA
FPT X100 Y100
TPT X OF @ Y OF @
(or NEW STRA DEF X100 Y100 X OF @ Y OF @)

Here a straight line is created with one of its endpoints defined explicitly and the other
constructed using cursor hits. See Figure 11-1.
Y
500
100
X
100 500
Figure 11-1 X, Y Filtering - General 2D Position

Version 11.5
Here, the ‘to’ point of the line takes its X coordinate from the X coordinate of hit 1 (at
200, 300) and its Y coordinate from the Y coordinate of hit 2 (at 500, 400). The ‘to’ point
is therefore (200, 400).
2. DTOF X @ Y250
With a cursor hit at (400, 900), the above command would move a Dimension text origin
to (400, 250).
3. PLCL X @ Y OF POS E3000 S2000 U0
Here, a projection line clearance X coordinate would be set to the X coordinate of the
cursor hit, the Y coordinate being set to the Y coordinate of the 2D projection of the
given 3D position.
11.3 Construction of 3D Positions
A specified 2D point may be projected into 3D, enabling 3D positions to be constructed

by picks on any line in the Design graphics. This is done using the POSition OF <point>
syntax. For example:
NEW STRA
DEF @
TPT POS OF ENDP OF @
Position TO point at end of 3D line.
A Q DESC command would return a 3D coordinate for the TPT of the line. This facility
is only valid in Plan or Elevation VIEWs.
Note that the Q ENUPOS and Q SHPOS commands (see Section 6.4, Part 1, Basic
Drawing Creation & Output) also calculate conversions between 2D and 3D positions.
11.4 A Midpoint Position
This form of construction derives a position as the midpoint of two other positions, which
may be defined explicitly or by cursor hits.
11.4.1 The Midpoint of Two Defined Points

A drafting point position may be constructed as the midpoint of two other points using
the following command syntax:
MIDPOINT position position
where position is as described in Section 11.1.

Version 11.5
11.4.2 The Midpoint of an Existing Straight Line or Arc

Example
1. NEW STRA
FPT MIDPOINT OF @
TPT MIDPOINT OF @
(or NEW STRA DEF MIDPOINT OF @ MIDPOINT OF @ )

Here, the line would take its endpoints as the midpoints of the two hit items. If the two
hit items were an arc and another straight line then the situation could be as shown in
Figure 11-2.
newly defined STRA
Figure 11-2 Use of the MIDPOINT Construction

The required midpoint could also be that of one side of a closed polyline primitive, e.g. a
rectangle. Line definitions of other elements (such as a line that comprises a piece of a
design item shown in a VIEW) can be extracted by cursor. As well as using a cursor hit,
the STRA or ARC may be identified explicitly.
Note that with this variation of the MIDPOINT syntax, the presence of the OF keyword is
mandatory.
11.5 A Quadrant Point Position
A quadrant point of an existing circle can be used for point construction. This will be the
extreme TOP, BOTTOM, LEFT or RIGHT of the circle. For example
NEW STRA
FPT @
TPT TOP OF ID @
constructed point
2 1
Figure 11-3 Use of the Quadrant Construction (i)

Version 11.5
Quadrant points of an arc or ellipse may also be identified. If an ellipse is rotated, the
nearest extreme of the ellipse will be selected. For example
NEW STRA
FPT @
TPT TOP ELLI /ELLI1
constructed point
2 1
Figure 11-4 Use of the Quadrant Construction (ii)

The syntax will always construct a 2D position.
11.6 An Endpoint Position
This form of construction derives a position as the endpoint of an identified element

(typically a line or an arc). A qualifier may be added if there is any ambiguity about
which endpoint is to be used. If there is any ambiguity, and if the qualifier is omitted,
then a solution will be chosen and returned arbitrarily.
The required endpoint could also be that of one side of a closed polyline primitive, e.g. a
rectangle. Line definitions of other elements (such as one side of an EQUI, or a line that
comprises a piece of a design item shown in a VIEW) may be extracted by cursor.
Examples
1. NEW MRKP DEF ENDPOINT @
Here, a MRKP is positioned on the end of the STRA closest to the cursor hit. Note that
the cursor hit acts as the qualifier.
Note that endpoints of lines and arcs can also be picked directly using the IDPT @
command.
2. NEW STRA
FPT X150 Y250
TPT ENDPOINT OF @
(or NEW STRA DEF X150 Y250 ENDPOINT @)

Here, the line has one of its endpoints defined explicitly, the other as the endpoint of the
hit arc.

Version 11.5
500
(150, 250)
newly defined STRA
100
X
100 500
Figure 11-5 Use of the ENDPOINT Construction

Here, the cursor hit also acts as the qualifier.
3. NEW STRA
FPT X150 Y150
TPT ENDPOINT OF PREV ARC QUAL X400 Y400
Here, the line has its ‘from’ point defined explicitly and its ‘to’ point as the endpoint of
the previous ARC in the list order closest to (X400, Y400).
Y
previous ARC in list order
500
(400, 400)
(150, 250)
newly defined STRA
100
X
100 500
Figure 11-6 Use of the ENDPOINT Construction, with Qualifier
11.7 A Centre or Focus Position
This form of construction derives a position as the centre of a specified circle, arc,
ellipse, rectangle, hexagon, table, diamond or equilateral triangle. A point may also be
constructed using the focus of an ellipse.

Version 11.5
Example
1. NEW STRA
FPT X150 Y250
TPT CEN OF @
(or NEW STRA DEF X150 Y250 CEN OF @)

Here, the line has one of its endpoints defined explicitly, the other as the centre of the
element (in this case a circle) hit by the cursor.
500
(150, 250) newly defined STRA

100
X
100 500
Figure 11-7 Use of the CENTRE Construction

2. NEW TEXP text DEF CENTRE PREV CIRCLE
Here, the text origin is placed at the centre of the previous circle element in list order.
3. NEW STRA
FPT @
TPT FOC OF /ELLI1 QUAL @
Here, the ‘to’ point of the line is placed at the focus of ellipse /ELLI1 qualified by a
cursor hit.
constructed point 2
Figure 11-8 Use of the FOCUS Construction

Version 11.5
11.8 A ‘Nearest To’ Position
This form of construction derives the point on a primitive which is nearest to a specified
qualifying point.
Example
1. NEW MRKP
DEF NEAREST PREV STRA QUAL X150 Y250
In the left-hand case shown below, the MRKP element and the position (X150, Y250) lie
on the perpendicular to the STRA. In the right-hand case, the MRKP lies at the
endpoint of the STRA. In both cases, the MRKP element is the nearest point which lies
on the previous STRA in the list order to the given qualifying point.
Y Y
newly defined MRKP newly defined MRKP
(150, 250) (150, 250)
100 100
X X
100 500 100 500
Figure 11-9 Use of the NEAREST Construction (1)

2. NEW STRA
FPT X150 Y250
TPT NEAREST PREV ARC QUAL @
Here, the STRA has its ‘from’ point defined explicitly, its ‘to’ point being defined as the
nearest point which lies on the previous ARC in list order to the given qualifying point.

Version 11.5
Y
newly defined STRA
(150, 250)
100
X
100 500
Figure 11-10 Use of the NEAREST Construction (2)

3. NEW MRKP
DEF NEAR @
Here, the MRKP element would be snapped to the primitive nearest the cursor hit. Note
that in this case a qualifying point is not needed.
11.9 An Intersection
Here, a point is constructed which is at the intersection of two primitives. The primitives
should be chosen from STRA, ARC, or CIRC, although line-parts of more complex
primitives may be identified by cursor. An ellipse (ELLI) is also an allowable primitive,
but it is only possible to calculate the intersection point between an ellipse and a
straight line. A qualifying point may also be specified when there is more than one point
of intersection (cf. use of qualifier in Section 11.6)
Examples
1. INT @
This variation uses a single cursor hit to pick the intersection point explicitly.
constructed point
2. INT BETW @ @
This constructs a point at the intersection of two hit primitives:
constructed point

Version 11.5
3. INT BETW @ @
In this case the second cursor hit acts as a qualifier:
constructed point
4. INT /CIRC1 AND /STRA1 QUAL X100 Y100

Here, the intersection point is the one closest to (X100, Y100)
constructed point
(100, 100)
5. NEW STRA
FPT INT BETW PREV ARC AND PREV CIRC QUAL X200 Y300
TPT MIDP OF PREV STRA
Here, the STRA has one endpoint defined as that intersection between the specified arc
and the specified circle which is the nearest to the qualifying point, the other endpoint
being the midpoint of a specified line.
Y
newly defined STRA
500
(200, 300)
100
X
100 500
Figure 11-11 Use of the INTERSECTION BETWEEN Construction
11.10 A Tangency Point
This construction generates a point at which a tangent line from a specified reference
point meets a specified arc, circle or ellipse.
Examples

Version 11.5
1. NEW STRA
FPT X100 Y100
TPT X300 Y200 TAN @
Y
500
(300, 200) (reference point)

100
(100, 100) newly defined STRA
X
100 500
Figure 11-12 Use of the TANGENCY Point Construction

This STRA element has an explicit FPT; its TPT is the point on the ARC which, together
with (X300, Y200), forms a tangent to the ARC. Here the cursor hit acts as a qualifying
point. Notice that the STRA produced here is not a tangent line.
2. NEW STRA
FPT X200 Y100
TPT X200 Y100 TAN PREV CIRC QUAL @
Here, the STRA has one endpoint defined explicitly and the other defined as the point
where the tangent line through (X200, Y100) intersects the previous CIRC in list order
which is closest to the cursor-specified qualifying point.
Y
500
100
(200, 100)
newly defined STRA
X
100 500
Figure 11-13 Use of the TANGENT Construction to give a Tangential Line

The qualifier is necessary since in this case there are two possible tangents. (Other
tangent shown dashed.) Other cases would not need a qualifier since only one tangent
would be possible (see below).

Version 11.5
generated point
(200, 100)
3. NEW STRA DEF @ @ TAN @

In this case, the first cursor hit defines one endpoint of the STRA, the second defines one
end of a tangent, and the third picks the circle and also acts as a qualifier. The resulting
STRA intersects the tangent. See below.
2 1
newly defined STRA
Figure 11-14 Use of the TANGENT Construction to give a Line perpendicular to a

Tangent
11.11 Tangent Lines
The TANLINE command can be used to draw a tangent line between any two ARC or
CIRC elements. Provided that the current element is a STRA, the syntax to create
a tangent line would be, for example:
TANLINE @ @
Figure shows various examples of the use of the tangent line facility. Notice how (right-
most illustration) the tangent line may lie on the complement of an ARC.
Figure 11-15 Use of the TANLINE command to give a Tangent Line

Version 11.5
11.12 A Perpendicular Intersection Point
This construction generates a point which is the intersection point between a selected
primitive (a line, arc, or circle) and the perpendicular from a specified point to the
primitive. The perpendicular will always lie in the plane of the paper. If there is more
than one possible constructed point, that nearest the specified point is generated (unless
this is overruled by the presence of a qualifier.)
Examples
1. NEW STRA
FPT X300 Y100
TPT X300 Y100 PERP PREV STRA
Here, the STRA has one endpoint defined explicitly and the other defined as the
intersection of the perpendicular from the specified reference point to the previous STRA
in list order. See Figure 11-16.
Y
500
newly defined STRA

100
(300, 100)
X
100 500
Figure 11-16 Use of the PERPENDICULAR Construction

Where the specified primitive is a line, the constructed point may lie beyond the ends of
the line (as above).
Other variations of the PERPENDICULAR Construction are shown below.
2. NEW STRA
FPT X0 Y0
TPT X0 Y0 PERP PREV CIRC QUAL @
Here (see opposite), two constructed points are possible and so a qualifying cursor hit is
used.

Version 11.5
500
100 newly defined STRA

X
100 500
3. NEW STRA DEF X0 Y0 PERP @ X0 Y0

Here (see below), the cursor hit selects the primitive and acts as a qualifier.
500
100 newly defined STRA

X
100 500
4. NEW STRA DEF @ @ PERP @

In this case, the first cursor hit defines one endpoint of the STRA, the second defines one
end of the line that intersects the circle, and the third picks the circle (and also acts as a
qualifier). See below.
newly defined STRA

1
3

Version 11.5
11.13 Reflected Points
A point may be reflected in another point using the REFLECT syntax. The position of the
reflected point is along the axis of the two specified points. For example:
NEW CIRC DIAM 10 AT @ REFL @
1 newly defined CIRC

2
The first point to be specified must be explicit, i.e. it cannot itself be a constructed point.
A 3D position may be constructed if appropriate.
11.14 Fillet Arcs
The FILLETRADIUS command can be used to draw a fillet arc between any two linear
elements. (A linear element includes a STRA element, or any other element on the
drawing which is composed of straight lines (e.g. 3D design elements, the side of a
RECT, etc). Provided that the current element is an ARC, the syntax to create a
fillet arc would be, for example:
FILLETRAD 10 @ @ FILLETRAD -10 @ @ FILLETRAD -5 @ @
Figure 11-17 Creation of fillet arcs
11.15 Constructed Lines, Ray Lines and Bisector Lines
11.15.1 Constructed Lines

A constructed line in this context is a STRA element whose endpoints lie on the SHEE
boundary. Starting with a STRA as the current element, a constructed line is created
using the CONLINE command to define a Through point (which may be any of the
position options, see Section 11.1) and an angle. For example:
CONLINE @ 30
This would give:

Version 11.5
Sheet boundary
Figure 11-18 A Constructed Line

Note that if the current SHEE size is changed, the FPT (From point) and TPT (To point)
of the STRA will not be updated.
11.15.2 Ray Lines

A ray line in this context is a STRA element whose FPT is user defined, and whose TPT
lies on the SHEE boundary. Starting with a STRA as the current element, a ray line is
created using the RAYLINE command to define a From point (which may be any of the
position options, see Section 11.1) and an angle. For example:
RAYLINE @ 30 RAYLINE @ 210
Figure 11-19 Ray Lines

Note that if the current SHEE size is changed, the TPT of the STRA will not be updated.
11.15.3 Bisector Lines

A bisector line in this context is a STRA element which bisects the angle included
between two existing linear elements. Its FPT is the intersection point of the two
existing linear elements and its TPT lies on a line joining the FPT to the SHEE
boundary. (The two elements need not actually intersect; the intersection point is
derived by projecting the elements if necessary.) Starting with a STRA as the current
element, a bisector line is created using the BISECT command to define the two lines to
be intersected. For example:

Version 11.5
BISECT @ @ BISECT @ @ BISECT @ @ LEN 100
Figure 11-20 Bisector Lines

Note that if the current SHEE size is changed, the TPT of the STRA will not be updated.
11.16 Chamfer Lines
A chamfer line can be drawn between any two linear elements, using the
CHAMFERDIST command to specify the two lines to be chamfered and the chamfer
distances. For example:
2 1
1 2
CHAMFERD 20 @ @ CHAMFERD 20 40 @ @ CHAMFERD 20 40 @ @
Figure 11-21 Chamfer Lines

Note in the above example the effect of changing the order in which the lines to be
chamfered are identified. (The same effect could be achieved by leaving the order of
identification unchanged but switching the chamfer distances values in the command.)
If a single value is specified, this is used for both chamfer distances.
11.17 Non-Drafting Applications of Point Construction
The point construction facilities can be used not only with 2D drafting but also with
other functional areas of DRAFT such as dimensioning and labelling. These uses of
point construction are most useful, and in some cases can only be used, with the cursor;
a linear piece of the design, a dimension line, a label line, for example, can only only be
picked, for use with point construction, directly with the cursor.
11.17.1 Labelling
Point construction is available in all syntax which requires the input of a single 2D
position. For example,

Version 11.5
GAP AT INT @
could be used to introduce a gap in a leader line at the point at which it crosses another
line (which may be part of the design graphics or annotation).
11.17.2 Dimensioning
Point construction is available in all syntax which requires the input of a single 2D (or,
if appropriate, a 3D position). For example,
DIM CENTRE OF @
could be used to position a Dimension line to run through the centre of an existing CIRC
element.
When creating linear and angular Dimensions, it is possible to dimension to a
constructed 2D point using the
TO POS OF @
syntax. (Similarly FROM POS OF @.) This procedure is possible provided the current
VIEW is orthogonal, and the 2D position lies in the current VIEW. For example, the
syntax
FROM POS OF INT @
will create a Dimension point at the intersection of two (valid) elements.
11.17.3 Overlay Sheets

An Overlay Sheet can be positioned at a constructed point using the OPOS and OSHEE
commands.
11.17.4 Drawing the Design

At VIEW level point construction methods can be used to:
• position the VIEW using the AT command
• set the VIEW size and position using the VREGION command
• set the THPO, FRPO and ONPO positions of the VIEW.
The THPO OF @ syntax (similarly FRPO OF @ ) allows input of a 2D constructed point,

provided the current VIEW is orthogonal, and the 2D position lies in the current VIEW.
11.17.5 Other Non-Drafting uses of Point Construction

The XYPOS attribute of SYTMs and TXTMs under Label Libraries (LALBs) and Symbol
Libraries (SYLBs) can be set to a constructed point position (using the XYPS, XYPO or
AT commands).

Version 11.5
11.17.6 The Point Construction Option Form

When the Point Construction Option form is displayed the default option is the 2D Cursor
Hit option. The default can be changed using the PCOPTION command:
PCOPTION TWODhit
PCOPTION ENDOF
PCOPTION CENTReof
PCOPTION MIDOF
PCOPTION MIDBEtween
PCOPTION INTAT
PCOPTION INTBEtween
PCOPTION NEAREST
PCOPTION REPEAT
The first eight commands cause the specified option to be presented as the default.
REPEAT causes the last picked option to be presented.

Version 11.5
Index
ABSOLUTE command............... 4-5, 4-36 Bent leader lines ............................... 4-11
ADEFINE command ................ 9-18, 9-30 BISECT command................................ 17
ADIM (Angular Dimension) element3-41 Blank areas.......................................... 2-2
ADIR angular dimension direction BPOF (Bend Point Offset) attribute........
element........................................... 3-41 ...............................................4-13, 4-16
AKEY attribute ................................. 3-25 BSHEE command.........................8-4, 8-6
ALENGTH command........................ 9-31 BSRF (Backing Sheet Reference)
attribute ....................................8-4, 8-6
ALIG (text alignment) attribute .............
........................................3-30, 4-8, 4-34 BTEX (Body text) attribute .......5-1, 9-35
ANGLE command ............................... 4-6 BTEX (Body Text) attribute ....................
.............................. 4-4, 4-17, 4-28, 4-36
Angle of turn (ADEG) attribute ..............
................ 4-6, 4-16, 4-34, 9-3, 9-6, 9-12 Bulge factor (BULG) attribute ......... 9-26
Angle Subtended (ASUB) attribute ........ BY command ..............................9-9, 9-10
........................................3-3, 3-36, 3-53
CENTRE keyword .................................. 8
Angular Dimension (ADIM) Elements
Chained dimensions...................3-7, 3-42
........................................3-2, 3-40, 3-49
CHAMFERDIST command.................. 18
APPT angular dimension direction
element........................................... 3-41 Character height (CHEI) attribute .........
..................... 3-21, 4-8, 4-17, 4-18, 4-36
ARC element ..................................... 9-17
Character Height (CHEI) attribute.. 3-21
AT command .. 4-5, 4-6, 4-34, 9-9, 9-10, 2
CHECK REFERENCES command .... 3-7
ATEX attribute ................................. 4-17
CIRC (Circle) element................9-6, 9-20
Attachment point
Common draughting primitives
of Labels ........................................... 4-2
handling.......................................... 9-11
Attachment point offset ............. 4-4, 4-16
CONLINE command ............................ 16
Attribute Key (AKEY) attribute .............
............................................... 3-25, 3-52 Connection Point Offset (CPOF)
attribute .......................4-14, 4-16, 4-20
Autoblanking....................................... 2-2
CPT (centre point) command........ 9-19, 2
Autotagging
Crosshairs Line Pen (CHPN) attribute
exclusions from .............................. 4-26
........................................3-2, 3-35, 3-53
BACK (Backing Sheet Template)
Crosshairs Overshoot (CHOS) attribute
element............................................. 8-3
........................................3-3, 3-36, 3-53
BACK (Backing Sheet) element ......... 9-3
CSPA (Character Spacing) attribute.......
Before/After linear dimension............ 3-4 ........................................4-8, 4-17, 4-36
VANTAGE PDMS DRAFT User Guide index-i

Version 11.5
Index
Curve fitting ......................................9-26 Dimension text angle............... 3-16, 3-29

DDNM attribute ..................................3-6 Dimension Text Character Height
(DTCH) attribute.................. 3-21, 3-50
DEFINE command ..... 9-18, 9-20, 9-31, 2
DIMENSION TEXT command......... 3-15
DELETE NULL ANNO command ...3-54
Dimension Text Font (DFONT) attribute
Design Data Name (DDNM) attribute ....
........................................................ 3-35
3-6, 3-14, 3-25, 3-41, 3-49, 3-54, 4-3,
4-25, 4-28, 4-34, 4-39 Dimension Text letter height (DTLH)
attribute ......................................... 3-21
DFLAG attribute......................3-27, 3-52
Dimension Text Letter Height (DTLH)
DIM @ command ......................3-36, 3-48
attribute ......................................... 3-50
Dimension arc....................................3-40
Dimension Text Offset (DTOF) attribute
Dimension attribute key (AKEY) .....3-25 ....................3-16, 3-30, 3-36, 3-48, 3-50
Dimension Line Angle (DDEG) Dimension text underlining
Attribute ............. 3-28, 3-36, 3-48, 3-52
in radial dimensions...................... 3-33
Dimension Line Direction (DIR).......3-11
DIR attribute .................................... 3-11
Dimension Line Position (DPOS)
DLFG attribute........................ 3-45, 3-52
attribute....................... 3-11, 3-43, 3-48
DMND (Diamond) element .............. 9-23
Dimension Line Spacing (DMSP)
attribute....................... 3-15, 3-44, 3-52 DMTX (Dimension Line Text attribute)
............................................... 3-44, 3-50
Dimension line terminators.....3-22, 3-52
DMTX (Dimension Line Text) attribute
Dimension lines..........................3-3, 3-48
................................. 3-15, 3-28, 5-1, 5-6
truncating.......................................3-52
DOFF attribute................................. 3-11
Dimension Offset (DOFF) attribute ........
DPBA (Dimension Point Before/After)
............3-5, 3-10, 3-11, 3-43, 3-48, 3-49
element ................................... 3-4, 3-54
DIMENSION OFFSET command ....3-11
DPOI (Dimension Point) element ............
Dimension origin (of angular dimension) ................................................. 3-4, 3-41
........................................................3-40
DPOS attribute ................................. 3-11
DIMENSION PEN command ...........3-23
DPPT (Dimension Point/P-Point
Dimension points..........................3-3, 3-4 element) ......................... 3-4, 3-41, 3-54
deleting unwanted .........................3-54 DRAG command .... 9-6, 9-9, 9-19, 9-32, 2
DIMENSION RADIUS command ........... Draughting origin
...............................................3-43, 3-49
shifting ............................................. 9-9
DIMENSION SEPARATION command
Draughting points ................. 9-6, 9-15, 1
........................................................3-15
identifying...................................... 9-15
Dimension Style
positioning ...........................................1
of radial dimensions.......................3-33
Draughting primitives
Dimension text ............... 3-16, 3-21, 3-50
index-ii VANTAGE PDMS DRAFT User Guide

Version 11.5
Index
copying .................................. 9-13, 9-14 Frame clearance (GBOX) attribute4-7,

4-17, 4-34
creating ............................................ 9-6
FRAME keyword ................................. 4-7
mirroring........................................ 9-13
FROM command ......................................
moving..................................... 9-9, 9-12
....................... 3-4, 3-6, 3-41, 3-47, 3-49
moving groups of.............................. 9-9
GAP command....... 3-23, 3-51, 4-15, 4-38
querying ......................................... 9-10
Gaps, sketching and erasing............. 3-23
rotating........................................... 9-12
GBOX (frame clearance) attribute ..........
DSTY (Dimension Line Style) attribute ........................................4-7, 4-17, 4-34
............................................... 3-33, 3-53
General Label (GLAB) element .......... 4-1
DTANG attribute .....................................
HEXA (Hexagon) element................. 9-25
.......... 3-16, 3-29, 3-36, 3-44, 3-50, 3-53
HIGHLIGHT command ...........9-11, 9-15
DTER (Dimension Line Terminator)
attribute ................................ 3-22, 3-52 ID ADIM, ID LDIM commands ........ 3-44
DTFL (Text Radius Flag) attribute ........ IDDP command ................................. 9-15
............................................... 3-28, 3-53
INSERT command ............3-7, 3-42, 3-47
DTOF (Dimension Text Offset) attribute
Intelligent text........... 3-15, 3-28, 4-4, 5-1
............................................... 3-16, 3-50
Intelligent text sub-strings ............... 5-10
DTRA (Text Radius) attribute ................
.............................3-28, 3-36, 3-48, 3-53 INTERSECTION keyword................... 11
DTUL (Dimension Text Underline) ISODRAFT symbols .......................... 10-1
attribute ......................................... 3-33 querying.......................................... 10-4
EDTEXT command .............3-21, 4-5, 6-4 ISOLB element.................................. 10-1
ELLI (ellipse) element ............. 9-20, 9-23 ISOTM element ................................. 10-1
ENDPOINT keyword ............................. 7 JUST (text justification) attribute ..........
ENHANCE command ....................... 9-16 ........................................4-8, 4-17, 4-34
ERASE command................................ 9-9 Label attachment point....................... 4-2
ETEX (example text) attribute ........ 4-17 Label attributes
ETRI (Equilateral Triangle) element ..... querying.......................................... 4-38
........................................................ 9-24 Label frame attributes
FILLETRADIUS command ................. 16 setting............................................. 4-34
Filtering Label leader lines ............4-11, 4-36, 4-37
X,Y ....................................................... 3 Label Library (LALB) element ................
FONT attribute .......................... 4-11, 6-1 ................................ 4-1, 4-16, 4-21, 9-3
FPT (From Point) command.................... Label text font ................................... 4-11
..................................9-10, 9-19, 9-31, 2 Labels
FRAD (fillet radius) attribute . 9-24, 9-29 deleting unwanted ......................... 4-39
VANTAGE PDMS DRAFT User Guide index-iii

Version 11.5
Index
for Views...........................................4-5 MIDPOINT keyword ..............................5

modifying........................................4-16 MIRROR command.................. 9-13, 9-38
orienting ...........................................4-6 MODIFY @ command ..... 3-36, 3-48, 4-16
Layer (LAYE) element .................2-2, 9-5 MPT (midpoint) command ............... 9-31
LCHA attribute ................ 3-9, 3-43, 3-52 MRKP (marker) element.................. 9-25
Leader Line Clearance (LLCL) attribute NCOL, NROWS attributes (of Table)
........................................................4-11 ........................................................ 9-34
Leader Line connection point ...........4-13 NEAREST keyword ................................9
Leader Line Spacing (LSPA) attribute NOTE (Sheet Note) element ....................
....................................... 4-8, 4-17, 4-36 ..........................9-3, 9-5, 9-6, 9-12, 9-35
Leader line terminator (LTER) attribute NPPT attribute ................. 3-41, 3-54, 4-3
........................................................4-36
OANG (Overlay Sheet Angle) attribute8-
Leader Line Terminator (LTER) 1, 8-6
attribute..........................................4-11
Obstruction (OBST) level control....... 3-4
Leader Line Visibility (LLEA) attribute
OCOD (origin code) attribute...................
........................................................4-11
.......................................... 9-6, 9-9, 9-20
Leader lines
ODEF command ............................... 9-31
bent .................................................4-11
OFFSET command .................... 4-5, 9-12
LEADERLINE command.........4-11, 4-36
ON command ............................................
Leaderlines ...............3-27, 3-41, 3-49, 4-3, 9-9, 9-10
with Radial Dimensions ................3-33 OSET (offset) attribute..... 4-5, 4-34, 4-36
Legibility OSHEE command........................ 8-4, 8-6
improving .........................................2-2 OSLV attribute ................................... 8-4
LENG (length) attribute ......9-24, 9-30, 2 OSRF (Overlay Sheet Reference)
attribute .................................... 8-4, 8-6
LENGTH command...........................9-31
OTPT command ................................ 9-32
Letter height (CHEI) attribute...........4-8
Outline (OUTL) element ........... 9-5, 9-26
Letter height (LHEI) attribute .........4-36
OVER (Overlay Sheet Template)
LFPN (Label Frame Pen) attribute4-7,
element ............................................ 8-3
4-17, 4-34
Overlay (OLAY) element.................... 8-4
Lframe (LFRA) attribute .........4-17, 4-34
Overlay Sheet Position (OPOS) attribute
Linear Dimension (LDIM) elements .......
.......................................................... 8-1
....................................... 3-2, 3-47, 4-36
Overshoot (OSHT) attribute ....................
Linestyles...........................................3-23
......................3-5, 3-10, 3-11, 3-43, 3-52
LSHA (Leader Line Shape) attribute
P-lines................................................ 5-12
........................................................4-13
LVIS (Layer Visibility) attribute.8-4, 9-3
index-iv VANTAGE PDMS DRAFT User Guide

Version 11.5
Index
Parallel dimensions ................................. Projection line...................................... 3-3

.............. 3-7, 3-9, 3-14, 3-43, 3-44, 3-52
Projection line direction (PLDI) ....... 3-11
PCENTRE command ........................ 3-39
Projection line text ............................ 3-50
PCIRCUMFERENCE command ...... 3-39
Projection text angle ......................... 3-20
PCOPTION command.......................... 20
Projection Text Character Height
PDIM element ................................... 3-37 (PTCH) attribute...................3-21, 3-51
PERPENDICULAR keyword .............. 14 Projection Text letter height (PTLH)
attribute ......................................... 3-21
Pitch Circle Dimension (PDIM) element
........................................................ 3-37 Projection Text Letter Height (PTLH)
attribute ......................................... 3-51
Pitch Circle Dimension (PDIM)
elements ........................................... 3-2 PROJLINE CLEARANCE command3-10
Pitch Circle Dimension (PDIM) PROJLINE OVERSHOOT command
Elements ........................................ 3-48 ........................................................ 3-11
creating ................................. 3-36, 3-48 PROJLINE PEN command............... 3-23
modifying .............................. 3-36, 3-48 PTANG attribute......................3-20, 3-51
PJUS (projection line text justification) PTFA (point reference) attribute.............
command ............................... 3-19, 3-51 .............................. 9-5, 9-15, 9-17, 9-30
PKDI (p-line distance) attribute4-3, 5-4, PTRF (point reference) attribute.............
7-4, 7-5 ........................................9-5, 9-15, 9-20
PKEY (p-line name) attribute ................. PURP (Purpose) attribute............2-2, 8-4
................................................... 4-3, 7-4
Qualifiers
PLCL (projection line clearance)
in point construction ........................... 6
attribute .......................3-10, 3-43, 3-52
Querying ............................................ 4-26
PLDI (projection line direction) attribute
............................................... 3-11, 3-48 AKEYS............................................ 3-26
PLDI attribute .................................. 3-11 ISODRAFT symbols....................... 10-4
PLTX (Projection Line Text) attribute Radial Dimension (RDIM) elements .. 3-2
................................................... 5-1, 5-6 Radial Dimension (RDIM) Elements ......
Point construction defaults ................. 20 ........................................................ 3-48
POS attribute ............................. 9-9, 9-10 creating..................................3-36, 3-48
PPDI (p-point direction) attribute .......... modifying...............................3-36, 3-48
...............................3-14, 3-42, 3-49, 4-6 Radial Dimension P-Point (RPPT)
PPLINE command .............................. 7-1 element ........................................... 3-37
PROJECTION DIRECTION command Radial Dimension Position Point (RPOI)
............................................... 3-11, 3-48 element ........................................... 3-37
PROJECTION JUSTIFICATION Radial Dimensions
command ........................................ 3-19
VANTAGE PDMS DRAFT User Guide index-v

Version 11.5
Index
including projection arcs with .............. Symbol templates

..............................................3-3, 3-36
ISODRAFT..................................... 10-1
marking the centre of .............3-2, 3-35
SYTM (Symbolic Label Template)
Radius Dimension elements.........4-1, 4-21, 9-3, 9-33, 9-35
obtaining from Diameter ...............3-27 Tabbing
RAYLINE command............................. 17 within intelligent text ..................... 5-8
RCOD (rotation code) attribute ........3-28 TABL (Table) element ...................... 9-34
RECT (rectangle) element .......9-20, 9-29 TAG command ......................... 4-25, 4-39
Reflected points .................................... 16 Tag Rule (TAGR) element ................ 4-23
REPEAT command............................9-13 Tag Rule Library (TRLB) element... 4-23
ROTATE command ..................9-12, 9-38 Tag Ruleset (TRST) element............ 4-23
Rotation sense (SENSE) attribute ...3-43 TAGGING MESSAGES command...........
............................................... 4-28, 4-39
RPOI element ...........................3-37, 3-54
TANGENCY keyword...........................12
RPPT element...........................3-37, 3-54
TANLINE command.............................13
Rubber banding .................................9-14
TCOD (Type Code) attribute..... 9-6, 9-30
SCTN ends
Terminator size
representation of ..............................7-6
controlling........... 3-23, 3-52, 4-11, 4-36
SENSE attribute ......................3-43, 3-49
TEXP (Text Primitive) element9-34,
Sheet Library (SHLB) element...........8-3
9-35
SKETCH command .......... 9-9, 9-33, 9-40
Text
SORT DIMENSIONPOINTS command
alternative character set................. 6-2
....................................... 3-8, 3-42, 3-48
Text alignment (ALIG attribute) .............
SPAN command ................................9-27
................................................. 3-30, 4-8
Special Label (SLAB) element.................
Text alignment (ALIG) attribute ..... 4-34
................................ 4-1, 4-16, 9-3, 9-35
Text colour
STRA (straight line) element............9-30
defining .......................................... 9-34
Straight leader lines .........................4-11
Text extent
Sub-strings
querying ......................................... 9-35
of intelligent text............................5-10
Text justification (JUST) attribute..........
SYMB (Symbol Instance) element...........
........................................ 4-8, 4-17, 4-34
.................................................9-3, 9-33
Text Radius (DTRA) attribute ......... 3-28
Symbol libraries
Text Radius Flag (DTFL) attribute . 3-28
ISODRAFT .....................................10-1
Text, editing ........................................ 6-4
Symbol Library (SYLB) element .............
.................................................9-3, 9-33
index-vi VANTAGE PDMS DRAFT User Guide

Version 11.5
Index
THPT (Through Point) command ........... Units Code (UCOD) attribute....2-2, 5-15
............................................... 9-18, 9-19
UPDATE ANNO command............... 3-45
TLIN (true length) attribute ... 3-12, 3-14
UPDATE INSTANCES command .... 9-34
TMRF (Template Reference) attribute
UPDATE TAGGING command ...............
............ 4-17, 4-19, 4-25, 4-28, 9-3, 9-33
......................................4-23, 4-27, 4-39
TO command ..............3-4, 3-7, 3-47, 3-49
Vertex (VERT) element..................... 9-26
TOLERANCE setting ....................... 9-15
VIEW element ..................................... 9-3
TPEN (Text Pen) attribute......................
Views
..................... 4-11, 4-17, 9-3, 9-34, 9-35
labelling ............................................ 4-5
TPT (To Point) command..... 9-19, 9-31, 2
Visibility
True length (TLIN) attribute ..................
......................................3-12, 3-43, 3-48 of primitives ................................... 9-16
Truncated dimension............................... VNOT (View Note) element .....................
.............................3-14, 3-40, 3-44, 3-52 ......................... 9-3, 9-5, 9-6, 9-12, 9-35
TXTM (Text Label Template) element VRAT attribute.................................. 5-18
........................................4-1, 4-16, 4-29 X, Y filtering ........................................... 3
UCOD attribute ................................ 5-15 Xyposition (XYPS) attribute ....................
UDA (User-defined attribute) codewords ......................4-5, 4-16, 4-18, 4-21, 4-34
........................................................ 5-19 XYSCALE attribute ..........4-22, 8-4, 9-33
VANTAGE PDMS DRAFT User Guide index-vii

Version 11.5

PDMS11 5-Manual-11 2

Uploaded by

Copyright:

Available Formats

PDMS11 5-Manual-11 2

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

PDMS11 5-Manual-11 2

Uploaded by

Copyright:

Available Formats

PDMS DRAFT

 Copyright 1991 through 2003 AVEVA Solutions Limited

Date Version Notes

VANTAGE PDMS DRAFT User Guide

1 Introducing PDMS DRAFT ............................................................................ 1-1

VANTAGE PDMS DRAFT User Guide Contents-i

4 Labelling ........................................................................................................ 4-1

Contents-ii VANTAGE PDMS DRAFT User Guide

5.8.4 # Character ...................................................................................................5-9

VANTAGE PDMS DRAFT User Guide Contents-iii

9.3 The Drafting Elements .............................................................................................. 9-4

Contents-iv VANTAGE PDMS DRAFT User Guide

VANTAGE PDMS DRAFT User Guide Contents-v

1.1 What does DRAFT do?

1.2 The DRAFT Database

VANTAGE PDMS DRAFT User Guide 1-1

1.3 Who Should Read This Manual

1.4 Organisation of the DRAFT User Guide

The DRAFT User Guide has two parts:

1.5 Organisation of this User Guide

1-2 VANTAGE PDMS DRAFT User Guide

VANTAGE PDMS DRAFT User Guide 1-3

2D Drafting Dimensioning Labelling

TEXP ADIM SLAB

SYMB LDIM GLAB

Figure 2-1 Annotation Elements

• View Notes (VNOTs) owned by Views.

VANTAGE PDMS DRAFT User Guide 2-1

2-2 VANTAGE PDMS DRAFT User Guide

VANTAGE PDMS DRAFT User Guide 2-3

LDIM RDIM PDIM ADIM

Figure 3-1 Hierarchy of Dimension and Related Elements

VANTAGE PDMS DRAFT User Guide 3-1

3.2 Dimension Element Types

3.3 Layer Attributes for Dimensioning

3.3.1 Linear Dimensions

3.3.2 Radial Dimensions

3-2 VANTAGE PDMS DRAFT User Guide

3.4 Linear Dimensions

3.4.1 Linear Dimensions and How to Create Them

Figure 3-2 Single Value Linear Dimension

VANTAGE PDMS DRAFT User Guide 3-3

NEW LDIM - Create new linear dimension element

3-4 VANTAGE PDMS DRAFT User Guide

Figure 3-3 Single Value ‘Before/After’ Linear Dimensions

VANTAGE PDMS DRAFT User Guide 3-5

Figure 3-4 ‘Before/After’ Linear Dimensions on a Single Element

3-6 VANTAGE PDMS DRAFT User Guide

3.4.2 Multi-valued Dimensions

Figure 3-5 Chained Linear Dimension

VANTAGE PDMS DRAFT User Guide 3-7

Figure 3-6 Use of the INSERT Command

3-8 VANTAGE PDMS DRAFT User Guide

Figure 3-7 Use of the SORT DIM Command

Figure 3-8 Parallel (or Tail) Linear Dimension

VANTAGE PDMS DRAFT User Guide 3-9

3.4.3 Principal Attributes of Linear Dimensions

Figure 3-9 Key Attributes of a Linear Dimension

3-10 VANTAGE PDMS DRAFT User Guide