ORD - Cross Section Annotation Inconsistent

Question

Hi, 
 Is there a reason annotation works for some cross sections but not others even when the template point names are the same. When managing the annotation group for the cross sections, the points are highlighted in the preview. Some annotation displays but it's not consistent. Each of the side slopes is highlighted in the manage window as well but maybe 50% display. 
 Additionally, when you have multiple corridors, is it best to split up the named boundaries and cross section models by corridor? 
 Thanks!

Holly Herring · Answer

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

Holly Herring · Answer

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.

Holly Herring · Answer

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

Holly Herring · Answer

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.

For more information about the Road and Site design tools, visit the Road and Site design WIKI at: http://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki

ORD - Cross Section Annotation Inconsistent

Top Replies