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?
These are our settings
Just out of curiosity, not sure if it is the cause. Why your cross sections are going backwards? The start station is 613+XX and the stop station is 565+XX.
Took a quick screenshot of the settings after taking screenshot of the XSEC which was already made. Stations limits in that dialogue aren't what we used for that sample XSEC, everything else is the same.
Hi Brad,
Someone correct me if im wrong, but I dont believe XS Named Boundaries work like the Profile ones do (where there is an option to include Terrains for clearance). It would be good to have an additional option for something like this. If you the Idea here: OpenCivil Ideas im sure we'll all vote for it.
Regards,
Mark
OpenRoads Designer 2022 R3 (10.12) | Microstation 2023.1 | ProjectWise CE 3.4
Mark - Took it upon my liberty to request it! Need you all to vote it! Thanks!