Expand range options of Horizontal Feature Constraints
Horizontal feature constraints are a huge benefit to streamlining corridor modeling and tying design intent to civil geometry. The range options (-, 0, +) are pretty limited and often trigger components to behave improperly. Adding more options to...
Update the tool "Create 3D By Slope To Target" to add better functionality when applied to regular 3D MicroStation linework
The tool "Create 3D By Slope To Target" can currently be applied to regular 3D MicroStation linework, but it doesn't work very well at all, assuming due to it's reliance on stroking. It is often much more efficient/simple to create certain design ...
When using parametric constraints to transition between default template values and the desired value, a separate parametric constraint is often required to control the transition length. (ex. Default to New, New to New, New to Default) An optiona...
Currently in the XSection viewer in OpenRoads Designer if you have a corridor or linear template that touches our butts up against another corridor you can't place temporary dimension lines on those components to make measurements if the linear or...
In order for the place bearing tool to work for as many instances as possible, we either need to be able to adjust the bearing's vertical location due to shim plate placement on an individual basis or else allow for different cells to be used at t...
Civil configuration variables exist for opening a default/workset template library (CIVIL_ROADWAY_TEMPLATE_LIBRARY) and for the default path when performing a save as on a template library (CIVIL_ROADWAY_TEMPLATE_LIBRARY_SAVEAS) but when opening a...
Control the level/feature definition of surface templates selection layer
Currently when you select a surface template in 3D view, a ghost mesh element under the "Default" level appears. I believe this element defines the surface template as a whole. There is presently no way of controlling this element to assign it a f...
For the modeling and model review process, it would be helpful to have Description fields for common corridor inputs, such as Parametric Constraints, Point Controls, etc. that can be easily discovered using the Corridor Objects tool.
Add groups and filters to Parametric Constraints so that I can limit the list to where I am working
Would be nice to be able to group the parametric constraints by what they are, similar to how event points can be grouped. Say I am adjusting pavement depths, would be nice to see only the pavement depth constraints. Similarly, would also like to ...
Many templates utilize null points to feature constraint or parametrically move to influence display rules within templates (switches). The ability to move those null points to see how they influence template display rules within the testing end c...