Separate 3D line and 3D object for pipes to different levels.
In Drainage & Utilities, the 3D line and the 3D object for a pipes(conduit/link) is placed on same level. It would be great to have them on different levels - also because it can be a demand from from clients in Denmark, that the line is place...
Allow Design Scenarios to change proposed conduit properties and class based on depth of conduit.
The class of a pipe is primarily selected by the depth of cover over a pipe. Sometimes vehicle loads or construction loads have an influence on the class selection
The ability to use an offset to create a single line alignment based on a regression line that was created by points. This ability would allow the user to create a centerline alignment based on monuments/survey points located a specified distance ...
Addition of a new Linear Terrain Triangle Void Feature to automate precision Terrain triangle trimming
One very important piece of functionality that is currently missing in OpenRoads is a Linear Terrain Void feature type. This Linear Terrain feature would void/null any Terrain triangles it crosses, allowing users to add these features into their t...
I would ensure that my vertical and horizontal alignments are the same length by using the Trim/Extend buttonn in geomtery editior in Power Rail Track - can we have the same functionility in ORD please? I know I can snap vertical alignment to the ...
With the integration of ProjectWise, I would like to see if the preview window in the document properties can display a view of the sign design as it does with OpenRoads Designer and the last view.
Add minimum vertical clearance results to delta surface tool
After creating the delta surface, we could not determine the location of minimum vertical clearance. We tried the analyze surface tool and it showed us coordinates of the min/max locations. However, the locations were outside of the delta surface....
Ability to lock Survey features when reprocessing field book
I made a change to a specific feature and I want to somehow lock the specific feature so it does not change when the field book is reprocessed. Example If I set Terrain Model Attribute of a point to "Do Not Include" then It should stay as that eve...