Using Labels from Imported Survey Point Data in Text Favourite

Greetings,

I'm learning ORD and have a question regarding Annotations of imported Survey data.  I have an existing process from InRoads that I'm trying to replicated. I use the Import tool to create graphics of my survey point data in a Field Book. I can see a field from my import, "Point Label", which contains the text I'd like to add as graphic elements, not just Text Decorations, to use in plain Microstation.  I am trying to create a Text Favourite using that field but I cannot see the field in my options.  If i use Place Text, go to Fields, select the element, I can see the field and it places the text appropriately.

Question: Do I need to change my  import process to insert that Point Label into an existing field already present in the OpenRoads Label functionality? Or is there a way to create the Text Favourite using that Point Label field?

Thank you.

  • Have you looked at the SmartObject VBA project? See this link: Video: Example using VBA Macros to Draw Pipes as 3D when Importing Survey Data

    The code include many other macro modules with comments explaining how to generate labels based upon survey data. These require you to use the Use VBA Macro property set to True in the General Survey Settings and then, in the VBA Feature Macros property, define the Object Type, Field Code and VBA Macro using the example coding from the macro.

    There are also newer Survey Annotation tools that use text favorites and I believe there are videos showing how to set those up as well.

    When we first looked at Open Roads Survey, it was in V8i Ss4/Ss10 which only supported the VBA Macro labeling capabilities. So as we began working on the CONNECT workspace, we retained their use and have not really spent time on the other labeling methods for Survey.

    If you visit our CAD Standards web page, you can download our V8i workspace and see the customized version of that VBA Project which expanded a lot on the examples supplied by Bentley. We parse survey attributes for additional labels which may or may not be in the examples, but in our code, we evaluate the values and react to any issues that are found in their values. For example, if two ends of the same pipe are coded with two different attributes, we turn the labels red as a flag that there is an issue.


    Charles (Chuck) Rheault
    CADD Manager

    MDOT State Highway Administration

    • MicroStation user since IGDS, InRoads user since TDP.
    • AutoCAD, Land Desktop and Civil 3D, off and on since 1996

    Answer Verified By: Scott T Anderson 

  • Hey Chuck, thanks!  I wanted to make sure there wasn't something obvious I was overlooking, like a magic "Convert Text Decorations to Text Elements" button, which would be very handy.  Or the ability to access those extra fields being created in the survey features with the Text Favourites functionality.  I'll check out the VBA as the alternative and grit my teeth while doing so.  :-)

    Cheers,

    Scott..

  • Chuck is correct about VBA macro labeling. That process works great but does have to follow a process to work correctly. When ORD landed in our laps I stopped using macros for anything but storm pipes. Macro labeling feels heavy handed and not flexible enough to provide a good presentation without more development from the user.....I'm not a programing or coding guy.

    For topo features such as street signs, utility poles and other simple point features my workflow is as follows:

    • Create a 2d or 3d design model
    • ref in survey features isolated so you can select them.
    • Open Civil Labeler and annotate the selection.
    • Optionally I drop the labels to simple text. I have had instances where the labels were affected by subtle edits to the survey model and thus effort was lost. 

    The labels can then be consumed by downstream users and or edited easily as text. For survey chains I follow a similar workflow of isolating the features and apply Civil labeler annotation in separate model.

    If your working in a State kit workspace you may not have access to the LIB files needed to customize the annotations to get what you need or want. I get the feeling survey annotation workflows might see a major overhaul in the near future.

    Take care,

    Cliff

    Answer Verified By: Scott T Anderson 

  • Thanks Cliff.  And yeah I finally kinda figured it out.  For anyone that follows:

    1. The survey .dc file imports and I have access to the topo codes on the points/lines and they are able to be seen via Text Decorations

    2. I have to Annotate to make "permanent" labels that can be used in basic Microstation.

    3. The key step I missed: Use Place Text, click on Fields, select Element Properties, select a survey point, pick the attribute you want to use for the Place Text command.  This will put text in the Text Editor window.  Right-click on this piece of text and select "Save Text Favourite".  You now have a Text Favourite that stores that field and it's called whatever the piece of text was that you were getting.  Rename it to your desired Annotation ID, like, "SurveyFieldNote".  You now have access to that Text Favourite in the next part.

    4. Modify the DGNLIB/Explorer information to create an Annotation Group for that item, say, "SurveyPointLabels".  Add a New Annotation.  Select the Text Favourite and save.

    5. Find the Features in the Feature Symbologies list and associate it to the SurveyPointLabels Annotation Group.

    6. Finally, select all the survey points in a view and click on Annotate Element.  It will now annotated the survey points using the Text Favourite associated to the Feature. 

    There may be a simpler way, but that worked for me, uses my old Feature structure from InRoads and is not completely onerous.  You can also assign Text Styles to each Text Favourite and Symbols for each point using the Feature Symbology.  I have to document this internally, maybe I'll post a video or PowerPoint on how to do this, it's pretty fundamental and a bit of a hurdle coming from InRoads.  Or maybe I'm just dumber than the average post..  :-)

    Thank you Chuck and Cliff.  You guys pointed me in the right direction.