XSEC Named Boundaries not respecting active terrain model?

Question

Hi, 
 
 We've run into an issue where, when making Cross-Section Named Boundaries, specifying a nonzero clearance (10' up and 10' down in our case), Openroads doesn't seem to be using the active terrain. Seems like the 10' is only respecting the corridor components. From what I understand, it would be respecting the existing terrain as well. 
 This results in the terrain being "cut off". See picture for example.

Anyone know what's happening here?

Mark Shamoun · Accepted Answer

Agree, having existing considered by default is not ideal. Adding an additional option to use them like Profiles do would give users control to be able to use it if needed.

Adam Wieczorek · Answer

I create Dummy terrain models with the Feature Definition Volume Option set to Design at fixed elevation to get constant datum for Cross-Sections. Clearance works against these terrain models and XS boundary limits. 
 I understand this approach to use Design and not Existing, as it is easier to control. I had road reconstruction project, it was in high embankments and on bridges. Using Existing terrain models for XS boundary would make XS very high and with design, I can easily control this. If you need to use the existing, just create Delta Terrain model with planum eg. value of your clearance and then set clearance in XS Boundry definition to 0, just to avoid of Terrain Ovelrlap. I create this dummmy terrains in XS definition file just to be sure it will not make any mess when creating Cut/Fill Volumes.

Adam Wieczorek · Answer

hi 
 I think XS considers terrain models, see this: communities.bentley.com/.../video-defining-a-constant-top-and-bottom-elevation-when-creating-cross-sections

XSEC Named Boundaries not respecting active terrain model?

Top Replies