Openroads designer annotation groups extend the white space management to all items
Right now only the text element can have the "manage modification" turn to true. This mean that only text will not move when doing annotation. The white space management, or manage modification to placement annotation should be avaiable to all ite...
Option to overwrite Saved views when reprocessing named boundaries to sheets
Allow a checkbox to choose to overwrite or replace existing saved views when re-processing a set of named boundaries for output to sheets. This will help to maintain order in the files and avoid excess unused items. If not creating another 'versio...
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 ...
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...
When creating a new point in a Survey field book using the “New Point” command, allow an option to hand-enter the coordinates.
When using the “New Point” command for a survey point, the user must screen-pick the coordinates. There are times when it would be extremely useful to hand-enter the Northing, Easting, Elevation.
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.
I want to show in our corridor models the areas where we are using erosion control measures vs using general seeding. Currently, the only real way to make this distinction is to either create a new template that uses a different feature definition...
Need the ability to add a predefined template to control codes. For example, I can create curb and gutter templates that would generate the needed linears at the correct horizontal and vertical values.