The prompt for compressing the drainage database needs some work: It really should be removed. Salvaging anything marked for deletion but not compressed isn't really feasible in OpenRoads environment. Do not prompt me twice. It should be assumed t...
ORD SUDA - Single gradient property - False for stormwater and wastewater conduit
Hi, We were wondering if it would be possible to change the single gradient property function for stormwater and wastewater conduit.
"Single Gradient - This is always set to true for storm and sanitary conduits. For other types of conduit, it i...
Including OverBridges, Noise wall and Large Gantries for Sight distance analysis
For the sight distance analysis, it would be good to include more complex scenarios, like OverBridges, noisewalls, Large Signage Gantries etc. which cannot be included in composite design surfaces.
Improve and simplify the named boundary drawing/sheet seed creation workflow
The way it is now, It's just too complex to create and custum the seeds for each client. Too many files, too many things to control and in too many folders/.cgf. You have to create many seeds with different specifics for each sheet size/scale/plan...
Developing turnouts in the new software can be quite cumbersome. If there was a wizard that allowed users to input known common pieces of geometry in a more descriptive and graphical fashion, it would help significantly. When geometry elements are...
When i call a Feature Definition in a text favorite or in my element symbology (Analytic Symbology), it allways comes with it's path. It's usually a long path and it just mess my view display with too much info. The ability to just show the name w...
Ability to assign varying ledge heights on either side of an inverted tee cap.
useful feature when we have varying girder depth on either side of an inverted tee cap. currently ledge depth has to be same on either side , and the pgl is achieved by using thickened bearing seats
For steel beams- When we create stiffeners and use them in cross frame definition, regardless of the method used, the stiffener tables when opened default to the first stiffener in the OBM library rather than the stiffener used in cross frame definition
Currently when we create a new stiffener and then when we create cross frames using those stiffeners, they don't show up when you open stiffener definition after creating cross frames (the first stiffener definition within the selection is shown)