OpenRoads Designer - Surface selection with non-triangulated features only

I have a surface that contains features only (non-triangulated). I am attempting to add it as a corridor reference so that I can set a style constraint in my templates. When I go to add the surface as a corridor reference, it prompts me to select the surface. Since the surface does not include any triangles, the surface is not selectable. So I figured I would add a boundary to the surface... but when I went into the surface and attempted to add a boundary, it prompts me to select the surface. I am unable to select the surface once again. Am I missing something obvious? It seems that there should be an option to select a surface from a list if the surface is not selectable. Any help is appreciated.

  • When adding in the corridor references, it should prompt you to "Locate First Reference".  This shouldn't be the entire terrain because the surface itself cannot be targeted as a reference.  It is looking for element such as linear elements, shapes, etc.  It wants to pick up the individual element(s) so you should be picking the features graphics.

    You have an OpenRoads Terrain Model created or are you trying to work with a native DTM or TIN?  You should be able to select the civil terrain model to add the boundary but it must be a civil element, not just the native surfaces from InRoads or GEOPAK.


    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

  • Thanks for the response. I will explain my typical workflow. In SS2, I would create a DTM with features in it. The features would have specific feature styles applied to them so that the template style constraints will locate them. Once I do that, I can set my active surface in the corridor to the feature DTM and I don't have to set up a bunch of point controls.

    I am trying to duplicate this method, or figure out the best way to handle it in ORD. My thought was to add the surface as a reference to mimic the old SS2 workflow. Do I need to select each linear element and add it as a reference? Is there an easy way to keep track of which elements are referenced?

    As far as adding the boundary to the surface, yes, the surface is an ORD terrain model. It only contains non-triangulated features. When using a command that prompts the user to select a terrain model, the feature only terrain is not selectable. I am trying to add a boundary so that I can at least select the terrain but since there are no triangles, I can't select the terrain, even to add a boundary to it. An example of when I would use this type of surface is for Right of Way. We drape the RoW onto an existing ground so that we can display it in cross sections.

    Maybe I am holding on to old workflows and need to adapt. If there is a better way to handle these items, I am eager to learn it. Any tips are appreciated.

  • It does work a little different since the corridors are graphic based.  Instead of looking for multiple elements which reside in a DTM, it can look for different elements which are added to the corridor references.  But they will have to all be added into the corridor references into the corridor first. 

    https://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki/17902/video-corridor-references-template-point-targets-linear-feature

    As far as an easy way to see what is added as a reference, you would use the Corridor Objects command to bring up the objects dialog of what defines that corridor.  It will list the External References which the corridor can target.  Sorry I didn't have any corridor references on this corridor, but it will list each element here:


    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

  • Thanks for the response. It took me a bit to understand that we have really lost intelligent DTM's in ORD. Instead, we are just dealing with features now.

    I really liked using the intelligent DTM's as it was much easier to add features to the corridor when using style constraints. I will get used to the new way but I do feel there is a need for a better way to manage corridor references in ORD. I would be nice to see some visual display of which features are added, or a way to batch add/remove features. As far as I can tell, you have to add them one by one.