Need to have an option for manual/automatic corridor processing
There is an existing option to deviate rules on a corridor. This is inconvenient and difficult to use because of the workflow associated this it: select A corridor -> deactivate rules, then select A corridor -> enable rules -> process (th...
Annotation Group Definition Copied to Active File when Used
When labeling civil geometry (alignments for example), whichever annotation group that is utilized is copied from the DNGLIB and saved with the active DGN. This is only the case when the geometry being annotated is stored within the active DGN, no...
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...
Additional Measure and Draw tools for Dynamic Sections
I would like a set of tools that I can measure and draw slopes with in the dynamic sections. I can use temporary dimensions for the active corridor elements only, but I would like to get the slopes of elements in adjacent corridors that are in my ...
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)
It would be very helpful if there was a way to simply Add a Conduit to an existing Profile Run. For example, I have a storm network modeled and a bunch of drawings created by using a Profile Run, but now I needed to add another conduit at the end ...
Want a warning when import xml when geometry chord/arc definitions different than the dgn "degree of curve method" setting
Would be very helpful to get some kind of warning that pops up when someone tries to import geometry from an xml file where the chord/arc defined on some of the xml file geometry is different than the “degree of curve method’ setting assigned to t...