Hi All, I wonder if anybody could enlighten me on this topic.
As known superelevation can only be applied to a corridor. Therefore, I have created a Civil Cell with an embedded corridor onto which I would like to assign superelevation once the Civil Cell is placed in a corridor file.
From the explorer panel for the placed Civil Cell, you can access the corridor element and corridor creation tools and should be able to assign superelevation sections to it (see snip below). However, when doing so the corridor is not being processed and is not reflecting the superelevation application. Even when trying to apply the superlevation manually from the "point control" tab in the corridor object panel, the superelevation sections are not present in the drop down list, however other elements can be modified from here, for example the parametric constraints respond to changes.
Anybody came across this issue? Is this a bug, or is there a specific workflow to follow and make this work?
Thank you, Regards.
Vera
It is surprising to see no response in this thread.
I wonder if simply none has a solution or because ORD users do not see the need in using superelevation with civil cells?
Since civil cells are so useful in designing junctions - specifically priority T-junctions, and as such are used to define a minor road approach to a mainline, surely there are design configurations where the minor road geometry includes a horizontal curve and a transition curve. Similarly, approaches to roundabouts can be based on curved horizontal alignment. In fact this is very common scenario in many projects.
I see a very valid point in Vera's query.
OpenRoads WIKI page How to Add Superelevation to a Civil Cell suggests that it is possible to apply superelevation to a civil cell corridor after the cell placement. Is it the case that this functionality was removed in OpenRoads Designer? Or is it a defect in Connect?
It would be good if we could get some clarification from Bentley and users experience in this aspect.
Regards,
Mariusz
OpenRoads Designer 2022 R1
Hi, if anyone interested, there is now a bug number 909695 filed for this issue.