Ability to use Cross Section Named Boundaries across references
We would like to be able to create cross section sheets by referencing previously created boundaries in a similar manner to how we currently are able to use Plan and Profile Named Boundaries across references.
Currently our only option is to bring in Navisworks Simulate models is find the .DWGs that possibly populate it and bring each one in individually. The individual reference option misses out on any files from other software (such as smartplant) su...
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.
It would be great to have a set of tools to model a contact (third) rail - this is used by many transit systems as a traction power source for trains. There are enough nuances to the design of this rail that it warrants a dedicated tool with the a...
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 ...
The graphical filter is limited to feature element symbology and feature definition. Multiple, redundant, feature definitions must be created in order to import features to multiple surfaces. The feature names, assigned in the template, can be use...
Would it be possible to add a graphical change button, similar to the one in the template library, to allow graphical modifications of the event points directly from the alignment? This would eliminate the need for the delete/create process. Addit...
This would give us the ability to make our models more complete within OBM rather than having to either model using MicroStation tools or another software (ProStructures).
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.
2
Future consideration