Complex Line Numbers in Isometrics

6/3/2016
ComplexLineNumbersinIsometrics|ProcessDesign,fromtheOutside
Menu
Search
COMPLEXLINENUMBERSINISOMETRICS
Posted on JULY12,201311:55AM by DAVEWOLFE
Out of the box, the line number tag, size and spec are called out on isometrics.
One of the most frequent requests we get is to alter that line callout to match our line number. The
diculty lies in the fact that in the isocong.xml, when you tell it which elds to place, you cant mix and
match the component properties with the line group properties. So, for example, setting up a line number
like this Size-Service-Number-Spec, seemed impossible (where size and spec are the component
properties.
However, thanks to some recent insight from the forums thanks to Bernd Gerstenberger, we have a
workable (though complicated) solution.
http://www.pdoteam.com/2013/07/complexlinenumbersinisometrics/
1/8
6/3/2016
The key to our scenario is to use a little know feature called calculated properties
(PLANTDEFINECALCPROPERTIES).
Overview
We still have to work with the limitation of placing component elds separately from line group properties,
but by using the Calculated properties option, we can create a new eld/elds that includes our line group
properties in the order we want. We do have to workaround a limitation in that calculated properties
cannot include the size property (from components).
What is a Calculated property?

Before diving headlong into this, we need to understand what a calculated property is. A calculated
property is a combination of existing properties for a class. Calculated properties may be dened and
edited using the PLANTDEFINECALCPROPERTIES command.
Below is a screenshot of a calculated property called LineDisplay that was created on the P3dLineGroup
class.
In the Data Manager, the LineDisplay Property looks like this:
2/8
6/3/2016
The format of the calculated property is important. Typically, everything should be wrapped in the
ToString function. The double bars || is a symbol that indicates concatenation. You use single quotes to
wrap text.
So, the value used for the LineDisplay property is this: ToString(NominalSize) || - || ToString(Service) || -
|| ToString(Number) || - || ToString(NominalSpec)
Im sure I overuse ToString, but it cant hurt anything.
So, how does this help? Bernds post above shows how to include any component property in an
annotation. So, now we can create a property similar to LineDisplay on our PipeRunComponents class.
The only dierence being that due to limitations in calculated properties, we cant include the Size
property.
So, I created a property called LineSux on the PipeRunComponent class as shown below:
3/8
6/3/2016
In our model, the property looks like this:
Now, we need to map the property so that we can use it in our isocong.xml.
Open the iso.atr, in the style you want to modify, and add a row that maps the
PipeRunComponent.LineSux property.
4/8
6/3/2016
Now, in the isocong.xml, navigate to Themes > Theme (default) > Annotations > AnnotationSchemes >
LineNumberScheme.
The attributes we are interested in are the Format, ComponentFormat, and ComponentFields.
In ComponentFields, we indicate that we want to make two properties available (Size and LineSux).
In ComponentFormat, we indicate that the format will that the rst item (Size) and separate it from the
second item (LineSux) with a dash.
By default, the Format property puts the LineFormat items rst (think Line Group properties), so we use
{1} which will only include the ComponentFormat properties. Save that and generate an iso.
5/8
6/3/2016
Magically, we have the physical size called out with the line number format that matches the LineDisplay
property.
Related Posts:
Share this:
Facebook
Google
LinkedIn
Twitter
Email
More
AUTOCADPLANT3D, ISOMETRICS
Tags: ISOMETRICS
Previous post
Next post
6/8
6/3/2016
WELCOME,SRI
Dashboard
Prole
Log Out
SERIES
AutoCAD Plant 3D on SQL Express (6)

Converting CADWorx Specs (2)
Creating a Nozzle Report (2)
Custom Piping Components Plant 3D (3)
Custom PnID Lines (2)
Getting Started (1)
Report Creator Scripts (2)
Sharing Projects with AutoCAD Plant 3D (3)
TOPPOSTS
Complex Line Numbers in Isometrics

Custom Components in AutoCAD Plant 3D
RECENTPOSTS
Fasttrack Navisworks Available in App Store

Fasttrack Navisworks 1.26 Update
Automatic Line Lists from AutoCAD P&ID
Using Expressions for Forcing Uppercase Letters in the Report Creator
Alternate component auto-selection
7/8
6/3/2016
POSTCATEGORIES
AUTODESK
+ AutoCAD Plant 3D 2014 Object Enablers
SelectCategory
+ Plant Exchange The Plant Exchange site that hosts

content and updates for the AutoCAD Plant platform
ARCHIVES
ECAD
+ ECAD Plugins
SelectMonth
+ ECAD, Inc.
+ MDO Team
+ Plant 3d WishList
2015 ECAD, Inc. CW Magazine powered by WordPress
8/8

Complex Line Numbers in Isometrics - Process Design, From The Outside

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Complex Line Numbers in Isometrics - Process Design, From The Outside

Încărcat de

Drepturi de autor:

Formate disponibile

6/3/2016

What is a Calculated property?

In the Data Manager, the LineDisplay Property looks like this:

Im sure I overuse ToString, but it cant hurt anything.

In our model, the property looks like this:

AutoCAD Plant 3D on SQL Express (6)

Fasttrack Navisworks Available in App Store

+ Plant Exchange The Plant Exchange site that hosts

S-ar putea să vă placă și