Good Afternoon,
We've been fine tuning our desired Annotation Definitions and Groups for plan and profiles. We have determined that we will require alignments that are able to be stationed on top of a tick mark, being stationed both right to left and left to right. Additionally, we have different annotation requirements based on whether we are in our regular plan views, or a particular detail, such as structure, intersection or interchange. To satisfy that requirement, we could, theoretically, add all required annotation definitions into a single annotation group, creating a different level and element template for each required annotation group. We would prefer, obviously, to have a different annotation set to toggle depending on what view/plan/detail we were in.
Right now, we can accomplish this switching of annotation via changing the Feature Definition. Unfortunately, we can only have one Feature Definition per feature, and therefore only one Annotation Group. Ideally, we could accomplish this by either overriding the Feature Definition or Annotation Group, similar to the "Override Feature Symbology" property when looking at the Element Information for a Terrain Model. We would then annotate our baselines outside of the baseline container file. Without such a method, we have developed a somewhat laborious workaround.
1) Maintain baseline in its own file. We annotate this baseline and profile within this file using our default plan/profile annotation. Plan, using Element Annotation; Profile, using Model Annotation and the Named Boundary Civil Tools.
2) Create a new file for each desirable alternate annotation. We contain these alternate files within subfolders of our "Geometry" folder.
3) Create a new Feature Definition for each type of Annotation Group desired. Create the associated Feature Symbologies, Feature Definitions, Annotation Groups, and Annotation Definitions. Create associated new containers for each.
4) In each "alternative annotation" file, use the "Single Offset Entire Element" Horizontal Geometry tool to copy plan and profile into the "alternative annotation" file with 0 offset.. This also creates a Civil Rule with the new baseline married to the original baseline in time and space.
5) Set new Feature Definition corresponding to alternate Annotation Group.
6) Use the "Start Station" tool in the Modify Horizontal Geometry tool group to create equivalence. It would be useful if there was an option to copy the Start Station properties of the target baseline in the Horizontal Geometry offset tools. At this point, if we have to modify the baseline, we are able to update our "alternative annotation" files as soon as we open them. I would probably then create a Batch Process to open all of our files prior to plotting to update the properties.
The laborious part of this is that we have several dozen alignments to update every time we have a design modification, or if someone wants to see our annotation represented differently.
If anyone has any tips to streamline this workflow, please feel free to let me know! Thanks in advance as always.
Robert, thank you for this thread.
ONE Feature Definition = ONE Annotation Group is blind conception for design annotation. The real projects are different.It seems the concept of annotation were developed by IT people without cooperation with designers. There are better conceptions ways:- Annotation is property of designed feature, not part of feature definition.- Annotation content is dependent on scale of model- Possibility to change Annotation for selected featuresMultiple layers in a single annotation group with different favorites texts can be useful for small projects. For more kilometres long profiles it is consumption of time. But good idea and workflow for current condition of product.Please Bentley, change the conception.
Fully agree - single CL needs different annotation on our overview plan and detailed plans. I wish there is an override option when annotating element, eg. you can pick up Annotation Group of your choice, when annotating element or annotate automatically as per Annotation Group assosciated with the Feature Definition of the element. Sorry to say it again, but in this field SS2 was superrior to ORD.
I ve never worked on a project when we had a single way of annotating CL in different kind of plans.
Best,
Adam
OpenRoads Designer 2023 | OpenRail Designer 2023
There is this enhancement request in the backlog: Enhancement 807875:[Annotation] Override Annotation Groups Assigned to Feature Definitions
I've added that more users are asking for it.
Thanks again for the response Marc.
Josef, you are welcome! Thanks for the feedback.