@castled071049 wrote:What do you mean by "static"?
Typically, when someone talks about "Dynamic" and "Static", Dynamic would be such that it automatically updates when the thing/object to which it refers changes and Static would be the opposite. And since I can't imagine any other use of those two words as they relate to C3D labels, I'll assume that's what the OP means.
To that end, I have to ask: "WHY would you want to do this?" That just opens up the possibility for errors. What is your end goal. (But to answer the question asked, I really doubt there's a way to have it directly create a static label).
Don Ireland
Engineering Design Technician
I was thinking that by "static" the OP might be confusing the term with "non-associative," and hence my question.
@Joe-Bouza wrote:
Why would your company want to do that? It defeats the purpose of civil3d.
I was just getting ready to ask the same thing. The way things are dynamically linked is one of the absolute hands down best things about C3D (as far as the things I use go). I used to deal with drawings in which every thing was static and it was a nightmare trying to keep it all straight.
I love the fact that when one thing changes, everything that depends upon it also get changed.
Don Ireland
Engineering Design Technician
P.S.
If you're going to explode everything down (so that it's static, you might as well use vanilla acad, perform the calculations manually and be done with it.
Don Ireland
Engineering Design Technician
well let me ask you this - when you draw a plot plan using plot bearings and distances then the crew goes into the field and comes back with field bearings and distances - how do you enter that information onto your plan keeping everything dynamic? we do hundreds of those a day for builders and it is just easier if the text does not stay dynamic - we are not working on large sets of drawings
Rick Jackson
Survey CAD Technician VI
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
@lgraham wrote:well let me ask you this - when you draw a plot plan using plot bearings and distances then the crew goes into the field and comes back with field bearings and distances - how do you enter that information onto your plan keeping everything dynamic? we do hundreds of those a day for builders and it is just easier if the text does not stay dynamic - we are not working on large sets of drawings
Hmmm. You've just presented a situation that I've never had to deal with. That's the first time I've seen a situation in which I wouldn't want them linked.
Don Ireland
Engineering Design Technician
@lgraham wrote:well let me ask you this - when you draw a plot plan using plot bearings and distances then the crew goes into the field and comes back with field bearings and distances - how do you enter that information onto your plan keeping everything dynamic? we do hundreds of those a day for builders and it is just easier if the text does not stay dynamic - we are not working on large sets of drawings
Having done many plats and boundary surveys in my lifetime, I understand your predicament.
I haven't done any since Land Desktop, though, but if I were doing one now I would probably keep the field measurements dynamic than add alternate or deviating historical information as simple text.
We have done a number of boundaries with deed and surveyed data. We have either kept the surveyed boundary as a parcel and added txt for the deed boundary OR one file w/ a parcel for each. XREF both in to sheet, move & rotate deed to survey and set deed parcel segement layer to No-Plot.
John Mayo
As a land surveyor I COGO and dimension the record bearings and distances and then save that as a block. This way I can drop the block on top of the field measurements and explode, delete/insert, rotate, etc. I use a no-plot layer to do the linework and dimensions on the field measurements. So basically I guess the short answer here is to have 2 sets of linework, one for record and one for measured. As far as combining the data you can either edit the label like mentioned earlier or place an MTEXT near the dynamic label with your record info.
It would have been helpful is 50% of this thread wasn't people asking "Ugh, why would you want to do this??!!!" My reason is I need hundreds of surface labels which are shown as proposed on project A to show up in project B as existing/under construction in a new under construction base plan I need to create from the project A base files and I don't want the surface from project A to be referenced in project B since project B will have its own surface.
ANYWAY..... Has anyone found an easy way to convert the labels from dynamic to static? So that the text inside the label doesn't read as <[Surface Elevation(Uft|P2|RN|AP|GC|UN|Sn|OF)]> to automatically get the surface elevation, but instead reads as 100.00? Yes I know I can edit them manually and yes I know I can explode them, but it sure would be nice to be able to convert several hundred labels to be static all at once without exploding them so that the scaling properties of the label aren't lost when exploding it.
As far as I know there isn't a way to make them static.
Is simply xreffing them in on a layer from project A not an option?
or
If project A file are used to make project B file and that same surface is to be further modified in project B but you still want the same labels as A, you could make a new surface, paste the surface from A into it, lock this new surface, redirect the surface labels to this new surface. That would set the labels to a locked copy of the surface and allow the surface that came from A to be edited without affecting the labels. They would in essence, be static.