In trying to setup some ideas for our ROW people, I created some Linear Feature Definitions for property takes. I also created their Feature Symbology and an Annotation Group.
The ROW people may use a lot of different approaches to define the takes. So for this to work, it should not matter how the graphics get created, anly that I show them how to assign the Feature and then to annotate it.
And therein lies the rub! I seem to have a complete hit or miss when it comes to getting annotation to display. I set the active feature and the use active feature lock. If we draw using line between points, they get the feature and will annotate. In many cases, someone will supply them with a complex shape and they will need to "civil"-ize that shape to be a Take and have it symbolize as such and also annotate.
I cannot for the life of me determine why some of the figures annotate and others do not. I have some with Rules and some without rules. Some we imported into the geometry builder and others we simply assigned a Feature Definitions. And dome annotate and some do not.
Is there some hidden toggle I am missing? At least one of these was refusing to annotate and something I did made it suddenly start - but I have no idea what it was.
We had issues with complex elements nested within complex elements and their annotation, specifically for RoW. Once we simplified these situations, they obeyed our Annotation Definitions inside Cross Sections and Dynamic Cross Sections.
I'm still at plan view Annotation. But apparently the more complex, the more likely it won't annotate.
Charles (Chuck) Rheault CADD Manager
MDOT State Highway Administration Maryland DOT - State Highway Administration User Communities Page
I have literally never had this issue here. I tested our various ROW types with ruled and unruled elements from alignments, and a variety of vertices and curves created for ROW takes. All of them annotated- and continue to annotate- just fine. However (and there is always a however) in testing all of these annotation groups and elements, I have found it necessary that- when a glitch occurs (and this program can do some odd things in such regard)- to get out of the program, get in again, and display all of these sorts of elements/ annotations again (only during the creation process). In both new and existing design files, they have been working well.
Mark
As I was working on this yesterday, one of my feature definitions became corrupt. It lost one of the panels in its properties. It was the panel that contains references to Feature Symbologies. I could not get it to accept the proper graphics settings even though it was accepting a Feature Definition. When I changed it to one that was not corrupted, it took on its standards, but when I tried changing back, it retained them. I had to make sure no elements were using the bad definition so I could delete it and then assign it so it recopied from the DGNLIB.