Notifications
Clear all

Civil 3D and Description (NOT POINT CODE) Labels

26 Posts
5 Users
0 Reactions
33 Views
(@scott-in-indianapolis)
Posts: 222
Member
Topic starter
 

Can Civil 3D add description labels or notes (not referring to the point code here) to point label style or to point style (point style in a block attribute or something).

What I am trying to do is pick up a capped rebar and note the land surveyor's number as a description on the shot. The land surveyor's number would then be added to the point style block or in the point label. So I shoot (code) the rebar as "RB", but I add a description or note of 9900113.

This could also work for other shot information. Ie. diameter of the tree, tree canopy radius (up to 2 descriptions per shot, so dia. and canopy), type of section corner monument, monument status (found or set), etc.

-Scott B.

 
Posted : March 7, 2017 8:50 am
(@trundle)
Posts: 82
Member
 

You can edit your descriptor key. Under the "format" column, you can type $* What you see on the screen for your description will be everything in the raw description (including diameters, LS #'s, etc...).

You can also add too it....for example "Capped Rebar $*" Then you would see on your screen "Capped Rebar RB 9900113"

There is some even fancier coding you can do so it reads "capped rebar LS#9900113" but you are probabaly much better off just using text (the coding is complex and very sensitive to case, formatting, etc..."

 
Posted : March 7, 2017 9:23 am
(@scott-in-indianapolis)
Posts: 222
Member
Topic starter
 

OK, so would the shot be coded "RB 9900113" on the data collector?

 
Posted : March 7, 2017 9:33 am
(@trundle)
Posts: 82
Member
 

Yes, although you could code it anything you want. The descriptor keys assigns a point style, layer, and point label style to a point based on its code (you can set this up any way you want, and change any of those attributes after your import the points).

If you coded a point "RB 9900113" in the data collector, you would make code "RB*" come in with a rebar symbol. Under the format column, type in $* - and this will cause the description (that shows up on your screen) to be identical to the description you typed into you collector (typos and all!).

 
Posted : March 7, 2017 9:42 am
(@pa-pls)
Posts: 44
Member
 

To do that in C3D 2010 I would set my description key code to "RB" and have the description set to "Capped Rebar $1). As long as you enter it into the data collector as "RB 9900113" the description in the drawing should come up as you want. As Trundle mentioned, they are very picky.

 
Posted : March 7, 2017 9:43 am

(@scott-in-indianapolis)
Posts: 222
Member
Topic starter
 

how does having the "description" after the code and separated by a space affect the linework?

 
Posted : March 7, 2017 9:46 am
(@trundle)
Posts: 82
Member
 

Scott Bordenet, post: 417309, member: 10097 wrote: how does having the "description" after the code and separated by a space affect the linework?

It depends on how you get your linework in (there are several different methods). But it shouldn't affect it as long as you use the correct seprator (space, forward slash, etc...).

 
Posted : March 7, 2017 9:58 am
(@kabonski)
Posts: 58
Member
 

You can absolutely add a note column to your points and have civil 3D display that as text on a point label. It takes some setup but once you have the correct point input style, and label style set up in Civil 3D it's pretty automatic. We do it with everything such as tree types, pipe sizes, and as you mentioned, monument or cap stampings.

Sent from my iPhone using Tapatalk

 
Posted : March 8, 2017 6:09 am
(@scott-in-indianapolis)
Posts: 222
Member
Topic starter
 

kabonski, how do you set up the survey/point database so that there is other data (an extra "column" as you describe). I am trying to import a P,N,E,Z,D,C (C for comment) file from my data collector. I then intend to add the comment in a point label style with the point number and description.

 
Posted : March 8, 2017 7:41 am
(@scott-in-indianapolis)
Posts: 222
Member
Topic starter
 

kabonski, never mind, I found how to add additional data.
http://www.cansel.ca/en/our-blog/171-civil-3d-import-points-with-survey-notes-and-photo-names

 
Posted : March 8, 2017 8:21 am

(@kabonski)
Posts: 58
Member
 

Scott Bordenet, post: 417466, member: 10097 wrote: kabonski, never mind, I found how to add additional data.
http://www.cansel.ca/en/our-blog/171-civil-3d-import-points-with-survey-notes-and-photo-names

Glad you found that! In addition to notes you can even take it further and have Civil 3D calculate and label pipe inverts and many other things. But it's all based on the same concept if adding User-Defined Property Classifications and then combining that with Expressions in the Point Label Styles tab. Like I mentioned earlier, it takes a bit to set up but once you have it in a template you never have to touch it again!

Sent from my iPhone using Tapatalk

 
Posted : March 8, 2017 8:56 am
(@scott-in-indianapolis)
Posts: 222
Member
Topic starter
 

Pipe inverts? hmmm.....if you have the time, please tell me about your method.

 
Posted : March 8, 2017 8:59 am
(@kabonski)
Posts: 58
Member
 

Scott Bordenet, post: 417473, member: 10097 wrote: Pipe inverts? hmmm.....if you have the time, please tell me about your method.

Scott try this link. I did a half ass job of explaining it here. It's not a perfectly automated process but it works nicely for us.

https://surveyorconnect.com/community/threads/rim-inverts.252130/page-2

Let me know if you have any questions and I can try and answer them in more detail later.

Sent from my iPhone using Tapatalk

 
Posted : March 8, 2017 9:44 am
(@scott-in-indianapolis)
Posts: 222
Member
Topic starter
 

kabonski, the pictures are gone.

 
Posted : March 8, 2017 10:07 am
(@kabonski)
Posts: 58
Member
 

Scott Bordenet, post: 417490, member: 10097 wrote: kabonski, the pictures are gone.

Scott, not sure where the pics went but here are a few screen shots and a description of my settings.

First I set up 6 UDPCs (User Defined Property Classifications), one for each possible pipe that may be in a structure such as a manhole or catch basin, you can make more as needed.

Then I set up three elements for each pipe (Size, Direction, and Measurement down from rim of manhole down to pipe invert). You should now see those fields available to fill in under the properties tab of each point you import.

Next, under Point-Label Styles I set up an Expression for each pipe (the point elevation minus the measurement to the invert)

Finally you set up a new Point Label Style. Under the Layout tab you should now be able to choose the new UDPCs and Expressions you made as part of your label.

As for our field and office procedures, I have our crews just make a note in the collector for each structure. The note contains the pipe size, direction, and measurement down to the invert. When I bring the points into Civil 3D with the notes I simply key them into the point properties and Civil 3D computes the pipe invert and labels the points correctly.

It's a lot of setup but it's a pretty nice workflow once you have it set up. Here is what my final point looks like.

Hope this helps and sorry if it's a bit confusing and long winded!

Sent from my iPhone using Tapatalk

 
Posted : March 10, 2017 12:31 pm

(@briniker)
Posts: 59
Member
 

kabonski, post: 417844, member: 1518 wrote: Scott, not sure where the pics went but here are a few screen shots and a description of my settings.

Hope this helps and sorry if it's a bit confusing and long winded!

Sent from my iPhone using Tapatalk

I have done the same thing but you skipped over the most important part of setting the components in your label style so they hide when an UDP is blank.

Another note of caution is that in 16 and older (havent tried 17 yet) is that you will lose all UDPS if you delete and undo a point. We used the Survey datbase to hold the UDPs for that reason alone - it was easily restorable.

 
Posted : March 10, 2017 12:41 pm
(@kabonski)
Posts: 58
Member
 

briniker, post: 417845, member: 9386 wrote: I have done the same thing but you skipped over the most important part of setting the components in your label style so they hide when an UDP is blank.

Another note of caution is that in 16 and older (havent tried 17 yet) is that you will lose all UDPS if you delete and undo a point. We used the Survey datbase to hold the UDPs for that reason alone - it was easily restorable.

Briniker,

I think I skipped it because I didn't know about it! Right now my points display information only if I have entered it into a UDP field. But, I have to go in pipe order (1-6 in my case) or it will leave a gap where the missing pipe data should have been. Where do I find the setting you mentioned?

Also, I haven't had the issue you mentioned in 16 or 17 yet but now I'll be on the lookout for it.

Thanks!

Sent from my iPhone using Tapatalk

 
Posted : March 10, 2017 12:54 pm
(@briniker)
Posts: 59
Member
 

Theres 2 ways of doing it.

1. anchor each piece of text to each other per line and choose one piece of that label to anchor to the line above it, the only text that actually appears always is the INV or FL label and it stacks on the one above or below.

2. Write an expression and use an if then function to reduce the text size to something tiny when it has a dip values of less than 0.00

 
Posted : March 10, 2017 1:00 pm
(@scott-in-indianapolis)
Posts: 222
Member
Topic starter
 

briniker and kabonski, thanks for your input!!!! I have added this ability to to my coding and label styles. You know, this actually makes it possible to perform ant entire survey without a firld book or paper notes (don't tell anybody I said that).

briniker, can you give more info on your second option on hiding pipe sticks/dips of 0.oo (aka non-existant)? I get the if then function, but I don't see how to use an if then option for FORMATTING. Calcs, yes, but formatting no. Are you doing this in the expression? In label style?

I want to figure out how to make a point table of structures that shows all 4 (5, 6, 7,etc.?) pipe sticks, but those sticks of 0 (where inv = t/c) to have a height so small that it can't be seen. Maybe an entry of "-" or "NA"?

-Scott

 
Posted : March 10, 2017 7:36 pm
(@briniker)
Posts: 59
Member
 

Your if then function logic test would be (Dip>0, .10.0.000001) the first argument being the test, the second the return if true, the third the return if false. That return would be plugged in as the text height for that pipes information. Youll need an expression for each pipe. A good text height for no dip would be .00001 or something along those lines.

 
Posted : March 11, 2017 9:24 am

Page 1 / 2