The Geometry Builder allows us to force tangent restrictions. In some cases there might be some lines/arcs that are tangent and some that are not. It would be an improvement to have the ability to force tangent where needed instead of on all eleme...
Key stations can now solely be places with a station input. In many cases the location of your Key Stations depends on the position of other elements, like geometry for example. Being able to give key stations a civil rule - like the Persist Snap ...
In order to use Cant Tables, a significant number of Cant Tables need to be created. As such, the ability to organize the tables into folders within the DGNLIB is needed.
Define Template Library Name and Location from Workset creation
Add capability to define Template Libray's Name and Location through Workset creation. See attached image. This information could be populate Workset.cfg file.
Create multiple field books w/o terrain connecting
The ability to create multiple field books without
the terrain connecting to each. This would be necessary when surveying multiple sites for one given road project. Currently, this
is done by importing the data and then going to the survey setti...
Provide a property for Corridors that shows the associated ITL
Corridors may use a variety of template drops that come from a non-default ITL (i.e. the one defined by the configuration variable CIVIL_ROADWAY_TEMPLATE_LIBRARY). A property of the corridor could be shown that identifies any of the ITLs associate...
Add the ability to import/export geometry elements from an imodel into your file. Similar to land xml or gpk. Then you retain the ability to archive files without worrying about their civil schema.
When starting a DU, OpenRoads creates a whole DU project inside the file and brings a lot of hidroly/hidraulic properties with it. That's fine if the goal is to run an analysis. But what if I just want to model a whole network and never run it? Di...
Provide an option to quickly apply combined horizontal and vertical constraints to geometry elements. Where geometry lines (breaklines) intersect, they need to share a common elevation. The current process requires creating profile intersection po...
Ability to superscript and underline the decimal digits for spot elevation annotation
Currently it is not possible to format only the decimal digits of the annotation. The user wants to annotate the spot elevation in a custom format where the decimal units are having superscript and the underline. The option from DIN Dimensioning o...