Enhancing Named Boundaries: Updating Named Boundaries and Applying Geometry Rules
To enhance productivity and efficiency in live projects, we need dynamic Named Boundaries linked to Geometry. This includes the ability to update the shape or location of a named boundary after creating a sheet model, with the changes reflected in...
Option to show Stopping Sight Distance instead of K-Value for vertical parabolas
Current default setting shows Vertical Curve Parameter or K-Value below the parabola length in the dynamic display of a vertical alignment. The geometry report has to be run or the annotation must be displayed to see the available SSD. It would be...
It would really be helpful for users with OBD to not have to open OBD prior to opening OBM. That is a big pain point that I get a lot of complaints about. Also it is very confusing for users at first, they don't understand why they can't just clic...
It would be nice to be able to export a drainage network into 2D linework that can be edited for plan sheets. Currently, we don't use our modeled files directly in our plan sheets as we cannot adjust the conduit line styles and it takes longer to ...
A physical report containing all surface areas and total area. Application use cases for this would include: -Useful for project planning and cost estimation. -Help determine material quantities. -Assists in environmental impact assessments by pro...
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...
Ability to define the slope of any points within the dynamic section using the measure tools
Having the ability to quickly check both existing and design crossfall/superelevation would increase efficiency within the program as there would be no requirement to run a template and report to evaluate existing cross slopes
Live nesting set to 99 when using "Create 3d cut" in Profile View
When using "Create 3d cut" in Profile View the live nesting depth is by default set equal to 99. Basically file becomes heavy when live nesting automatically in the depth of 99 set with the tool "Create 3d Cut" in Profile.
Ability to export and import all corridor objects such as point controls to enable rebuilding of corridors
I know parametric constraints can be exported but if a corridor becomes corrupt then being able to rebuild it from scratch easily would be useful. Similar to an input file in MX