Community
Civil 3D Forum
Welcome to Autodesk’s Civil 3D Forums. Share your knowledge, ask questions, and explore popular AutoCAD Civil 3D topics.
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Advanced Description Keys Lesson

6 REPLIES 6
SOLVED
Reply
Message 1 of 7
DaveM
423 Views, 6 Replies

Advanced Description Keys Lesson

I found the following Message from Sinc and did not want to hijack and old link so I brought it here.

The Original Post

 

Sinc Wrote:

The $1 $2 etc. parameters use spaces as a delimiter.

 

So in the following key:

 

TREE 12 PINE

 

$0 = TREE

$1 = 12

$2 = PINE

$+ = 12 PINE

$* = TREE 12 PINE

 

That's about the only options you have.  There's no way to "split up" stuff unless there's a space.  So you can't use these codes to substitute part of a parameter while leaving the remainder untouched.

 

I found this very useful and was curious to take my knowlege a step further.

 

IF I had

 

EP B SW B

 

How does this get interperted would it be

 

$0 = EP

$1 = B

$2 = SW

$+ = B SW B

$* = EP B SW B

 

Also the B is begin in my linework code set.

 

Or would the use of an additional code Create 2 $0 & 2$1

 

Are the B's considered Parameters?

 

 

Thanks,
Dave

Civil 3D 2013
HP Z400 Workstation
6GB of RAM
296GB HDD
ATI FirePro V5700(FireGL)
Win 7 Home Professional
Please use Kudos Where Deserved



6 REPLIES 6
Message 2 of 7
IanMcClain
in reply to: DaveM

The B is also considered a parameter as far as the description key is concerened. The description keys don't know what the linework codes are. It's like having two interpreters translate your speach into two completely different languages.

 

There are some additional matching options for your codes: http://docs.autodesk.com/CIV3D/2012/ENU/filesCUG/GUID-8AA5D606-5D3D-49F3-B34B-05FA834A39D-756.htm

Ian McClain
Message 3 of 7
DaveM
in reply to: IanMcClain

That makes sense know that I think about it. Those tools are in seperate area's. The linework has nothing to do with the style of the points.

 

Thank you for this explanation.

Thanks,
Dave

Civil 3D 2013
HP Z400 Workstation
6GB of RAM
296GB HDD
ATI FirePro V5700(FireGL)
Win 7 Home Professional
Please use Kudos Where Deserved



Message 4 of 7
ToddRogers-WPM
in reply to: DaveM

You change your linework code set to something like BEG instead of B.  However, you have to make sure the surveyors honor that Smiley Happy.



Todd Rogers
BIM Manager
Blog | Twitter | LinkedIn

Message 5 of 7
IanMcClain
in reply to: ToddRogers-WPM

I'm don't think the B was an issue with the description code. I think the OP was just asking a conceptual question about description parameters. You do bring up a good point though: if you are using linwork and description keys, be mindful of any overlap in the codes.

 

Fortunately I have found the out-of-the-box linework codes did not overlap with description or linework codes I use so implementing them was easy. I wouldn't change them unless you have to, because anyone looking up the C3D see references to the defualt codes.

Ian McClain
Message 6 of 7
ToddRogers-WPM
in reply to: IanMcClain

Agreed!



Todd Rogers
BIM Manager
Blog | Twitter | LinkedIn

Message 7 of 7
DaveM
in reply to: DaveM

Thanks for walking me through that guys. Very helpful.

 

I will accept any additional information anyone would like to share on Figure Prefix, Linework codes, or description keys, But I feel Ian did answer my OP!

 

Thanks,
Dave

Civil 3D 2013
HP Z400 Workstation
6GB of RAM
296GB HDD
ATI FirePro V5700(FireGL)
Win 7 Home Professional
Please use Kudos Where Deserved



Can't find what you're looking for? Ask the community or share your knowledge.

Post to forums  

Rail Community


Autodesk Design & Make Report