I found the following Message from Sinc and did not want to hijack and old link so I brought it here.
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?
Solved! Go to Solution.
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/G
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.
You change your linework code set to something like BEG instead of B. However, you have to make sure the surveyors honor that .
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.
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!
Log into access your profile, ask and answer questions, share ideas and more. Haven't signed up yet? Register