Many times, we have conduits/pipes that simply daylight a surface and drain on to the ground or into a pond. Please add the ability to place conduit/pipes "Without" the need of a Node. I understand that we can create a sort of null point/node that...
Currently, ORD cannot process more than two attributes from a survey data file into their own unique attribute column. The workaround is tedious and unintuitive: First, modify the CSV file from the data collector (not good practice to modify a sur...
Con sider adding fiber-mesh tools for cross section analysis to RMBRIDGE. This allow the use of different materials in the cross section. This is important in seismic analysis for the definition of the Moment-Curvature properties. This feature is ...
Currently we have generic pipes (ie RCP Class III) and on placement, the user defines the size by using the description field. Because of this, I cannot attach an Item Type and explicitly set the Pay Item information. If I can set what the size of...
Currently, Drainage and Utilities feature definitions get captured via the CIVIL_CONTENTMANAGEMENTDGNLIBLIST variable within the workspace. Many configurations often use wildcards and file names that lump together features of D&U with road, ra...
DU conduits external wall controled by Feature Symbology
We have the option to define a template to pipes external walls, but only through the feature definition. For all other elements of the pipe, OR allows for feature symbology. From my experience, symbologys work better and are more constant.
For large projects, we need the ability to have multiple engineers working on the hydraulic model. We can achieve this by splitting the pipe network into multiple files and creating catchments in separate files. Doing so causes us to lose the abil...