port all Regression tools from OpenRail to OpenRoads
There are some regression tools that were ported from openRail into openRoads in previous releases. However, they didn't port every regression tool. Most notably, they did not port the Vertical regression tools for creating a regressed profile. We...
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...
Annotate Slope of terrain between points in Cross Sections
Civil labeler only works for 3D linear features (points). It`s impossible to annotate the slope from the terrain between two points. If you try that, the whole terrain section is selected and the command fails. A great example is a cross section o...
It would be nice to have the ability to reattach civil labels to a new element or terrain. A good example is for jointing/geometric sheets with a lot of spot elevations. Fairly often a new terrain is created and the spots break and need to be repl...
Separate vertical alignment model from horizonal geometry
One of my biggest pain points about ORD is if the horizontal geometry is dropped or broken, the vertical is consequently lost as well. This creates significant rework from a design and plan production standpoint (connected named boundaries). One w...
Annotating and Labelling Intersecting Alignment Stationing in Cross Sections
Annotating and labeling cross sections within ORD is missing the functionality to label the stationing of intersecting alignments shown on roadway cross sections. While feature names (alignment names) and elevations of intersecting alignments can ...