ORD - Cross Section Annotation Inconsistent

RE: ORD - Cross Section Annotation Inconsistent

Edward Davis — Tue, 04 Feb 2020 17:32:01 GMT

Thanks, Holly! I appreciate your help.

ED DAVIS | Crawford, Murphy & Tilly | w 630.907.7069 | m 630.824.8331
Senior Technician

RE: ORD - Cross Section Annotation Inconsistent

Holly Herring — Tue, 04 Feb 2020 17:22:35 GMT

You will first want to make sure that the points are added at the bottom of the dialog to be filtered through the filter you are using. Either have them added, or keep the filter completely blank. Then create the expression that you want for the filter. If you just want points with two specific Feature Definitions then do something like "Feature 1" OR "Feature 2". Be sure to use an OR and not AND. A point cannot have two Feature Definitions.

RE: ORD - Cross Section Annotation Inconsistent

Edward Davis — Tue, 04 Feb 2020 16:41:24 GMT

I'm trying to annotate the median using feature definitions but with no luck,

Is there an expression that I could use to achieve this? thanks!

RE: ORD - Cross Section Annotation Inconsistent

Louis van Amerongen — Thu, 21 Nov 2019 17:25:36 GMT

Hi Holly,

Thanks for investigating this problem. I can confirm annotating cross sections is very hard to get stable. Indeed, annotating feature definitions is the most reliable ( by my experience), but even this results are not always chown. Results in Templates with the same annotated features (or for example point name) seems to be random.

also colleagues from other companies are complaining about this.

I hope this heavy used function will be reliable in the near feature.

Regards Louis

RE: ORD - Cross Section Annotation Inconsistent

Aaron McCown — Wed, 20 Nov 2019 18:24:24 GMT

Holly,

I am trying this expression in my own template and I am not able to get it to work?

Have things changed since 2018 that would not let me do so?

Appreciate any and all help!

RE: ORD - Cross Section Annotation Inconsistent

TN — Thu, 22 Mar 2018 19:19:44 GMT

Thanks Holly. Would there be a quick trick to have it work on both side slopes? That expression seems to label left to right from that template point so the right side slope labels correctly and the left labels the sidewalk side instead of side slope.

RE: ORD - Cross Section Annotation Inconsistent

Holly Herring — Tue, 06 Mar 2018 17:28:26 GMT

Thanks for the data. I ended up having to log Defect 857286 for development to review. I experienced the same output that you describe. You could work around this by filtering the data a different way. I think annotating based on the Feature Definition will be quicker. All of your End Conditions start from a point with a Feature Definition called TL_Grass Berm Normal.

Set the Segments to be Filtered to Use All Segments.

Then, type in this expression: point1_feature_definition = "Linear\Template Points\Shoulder and Berm\TL_Grass Berm Normal"

This will annotate any segment whose first point has this feature definition. You may think of a better way to work around this defect, but I thought this might be clean and simple for you to use.

Holly

RE: ORD - Cross Section Annotation Inconsistent

TN — Mon, 05 Mar 2018 16:33:59 GMT

Hi Holly,

When in the default model this annotation group shows up for me:

It shows up when I open with No Workspace too.

I'm looking to at least show the side slopes and the GP elevation at the CL. Here is a typical issue with the side slope missing:

The superelevation label is the only one that seems to show consistently:

RE: ORD - Cross Section Annotation Inconsistent

Holly Herring — Mon, 05 Mar 2018 16:06:33 GMT

Hi TN,

To further assist you I will need more information. First, the dgn you sent me has not been annotated using Annotation Groups. If it would have been, I would see Annotation Groups populated within the OpenRoads Standards for the dgn. Please see a screenshot below. I need you to annotate a model with the Annotation Group you are wanting me to inspect. Otherwise, it stays contained in the dgnlib which you did not send me. As of now, I do not have access to it.

Also, I need screenshots of what exactly you are trying to annotate. What isn't annotating/what is annotating. Maybe an example station screenshot of where it annotates correctly and an example station screenshot of where it does not annotate correctly. I'll be able to help after I get this info.

Holly

RE: ORD - Cross Section Annotation Inconsistent

Holly Herring — Mon, 05 Mar 2018 14:35:28 GMT

If you want to change annotation groups to be specific for that dgn, make the changes in the dgn. If you wants the changes reflected in the workspace, do it in the dgnlib.

RE: ORD - Cross Section Annotation Inconsistent

TN — Mon, 05 Mar 2018 14:33:14 GMT

Thanks, I've uploaded the files. You'll see it's happening on one side slope for most of the project. For the cross section annotation group, should all the editing be done in the dgnlib or can you manage it once it's copied into the cross section sheet dgn?

RE: ORD - Cross Section Annotation Inconsistent

Holly Herring — Mon, 05 Mar 2018 14:16:22 GMT

Hi TN,

I haven't seen what you are describing when I've annotated cross sections in ORD. Could you provide me with your data and some screenshots that show stations where the annotation appears and where it doesn't? I can take a look to see what might be happening. This wiki shows how to upload data: https://communities.bentley.com/help/w/be_communities_help/7079/communities-secure-file-upload. If you include annotation when setting annotation filters, will all the points display on each cross section? I wonder if some of your point expressions might be conflicting.

If you have multiple corridors, it will depend on your design as to what will be better to do. For example, you may want a more frequent cross section cut along your alignment for one corridor as opposed to the other. Then, you would want multiple named boundaries. Either way, you can annotate all models at once, and create sheets of all named boundaries at once. It may be easier for you to pick and choose which sheets you want to create if you break up the named boundaries by corridor.

Holly