Element/Model Annotation of Referenced Elements

RE: Element/Model Annotation of Referenced Elements

Ray Thwaits — Thu, 28 Jan 2021 22:46:22 GMT

Our workaround to this is to include multiple annotations with a feature definition. For instance, our CL_MAIN feature definition calls an annotation group that places tics and labels for 1"=100' plotting on levels defined for that scale and simultaneously places tics and labels for 1"=20' on levels defined for that scale. The proper annotation is shown by turning levels on and off. Still a bit of a kludge but at least it allows you to maintain the source of truth.

1"=100':

1"=20':

These are the same feature definition, I've simply changed the level display.

RE: Element/Model Annotation of Referenced Elements

Charles Meuser — Thu, 28 Jan 2021 19:28:43 GMT

Thanks for the reply Robert, I kind of suspected this, but figured I'd ask. I'll submit another request to help gain some traction

RE: Element/Model Annotation of Referenced Elements

Robert Huston — Thu, 28 Jan 2021 18:01:00 GMT

We had a forum post in June 2019 requesting the ability to override an Annotation Group for a given Feature Definition. The Enhancement Request # is 807875. I think the standard procedure is to submit an SR with the Enhancement Request number and they use that to adjust priority for a given defect/enhancement.

The solution that I utilized is as you suggested, keeping a separate file with all of our alignments that have a separate Feature Definition and Annotation Group. As you have suggested, this is not optimal as it creates a copy of an alignment, but it has been very clearly communicated to our project team that I am to be notified of any horizontal geometry changes and I take responsibility for going in and updating this, what I call, "Alternate Annotation" geometry file. Using LandXML import/export, its not a process that takes very long.

e: Including my post from 2019

communities.bentley.com/.../ord-2018r4-most-efficient-way-to-annotate-same-civil-feature-multiple-ways