A SWITCH/CASE function would be easier to use than having to nest multiple IF functions.

From rail companies in Switzerland we receive their rail alignment in form of an .xtr file. This file includes geometry, station, cant, construction and destruction phase and turnout information. Currently the import of an XTR-file in OpenRoads is...

Currently, annotation groups are limited to certain feature definition categories. This limits our ability to automatically annotate point features such as signs or geotech borings or drainage/utility nodes. It would be desirable to extract data f...

Please include ability to model curtain wall under end bent, similar to backwall. This curtain wall is a great tool when working on projects when new fill required to place is not significant enough to just an independent retaining wall but is sig...

Please allow the use of guidelines of a deck template to be used for barrier placement. Right now it's limited to regular decks only. WIth advanced deck, only the Alignment can be used.

When applying a point control, users should have the ability to choose the individual point name when there is also a Feature Name Override on the point. As of now only the override name shows up in the point control pick list, and it currently do...

The RIM Elevation is a stagnant number once you enter an elevation it does not update in relation to any surface changes. RIM Elevation would be better suited for use if it can be defined with an offset. Another field would be needed: RIM Depressi...

Similar to the new Station/Offset Expressions, it would be great to query a terrain in an item type on an element and return the elevation. It would be used primarily for point cells, but I could also see it being useful for linework.

Currently, the detailed design report in RCPIER only shows shear/torsion calculations for the column. Suggest also including detailed moment, crack control and all other AASHTO checks in the detailed checks so reviewers know which equations were c...

The "Export to IFC" tool only exports the default model, not the active one. This is a big problem with OR since in most cases, the default model is the 2D. So we have to have the 3D reference turned on for it to export our objects. We end up with...