One specific drawing type that we need to create is an Index Sheet for identifying the location of the plans and profiles for a given project. The index requires some project features such as the projects alignment displayed but all are shown at a smaller scale such as 1"=100' and 500' station interval.
Our workflow in InRoads was to display the alignment at the specified interval in a separate model in the alignment file(s) or a totally separate file and then reference the model or file to the index sheet. The necessary stationing and text was displayed at the size based on the scale.
So the requirements haven't changed, can we reference the horiz alignment to another file or model and annotate it similarly as I described above with OpenRoads? Maybe override the feature definition when referenced to another that has a different annotation group assigned to it?
I did reference a geom file to another file and annotated it at a different scale, BUT I couldn't change the interval. YES, I understand that I can just delete the stations in between, but that seems kludgie to me. I am a huge proponent of references to keep and maintain a certain "source of truth". I was hoping we could update the workflow to just using the defined geometry not need another alignment file just for these specific plan types...
I looked at the OpenRoads Model/referenced models in my project explorer, I was hoping I could override the feature definition there, but no can do.
Anyone have any luck with that or am I missing something?
ORD Connect Ed 2020
Release 3 Update 9
Ver 10.09.00.91
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
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
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.