An input report should be made available to LARS files similar to the input report generated in LEAP Steel. This allows for a more efficient process for QA/QC of load rating files. This ability was present in LARS v10, but removed in the modernize...
ORD Drainage - new properties for gutter spread/depth at edge of grate (not center)
Ohio DOT likes to see the spread and depth at the edge of the grate. Currently the software reports on the spread and depth at the start and end of the gutter. Would like additional properties to also report the spread and depth at the edge of the...
Enhancement to Add a Selection Set Capability to the Graphics tool (Survey >> Field Book >> Import)
The Graphics tool (Survey >> Field Book >> Import) currently imports all the MicroStation features in the active .dgn to survey features. This idea is a request to enhance the Graphics tool (Survey >> Field Book >> Import) ...
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...
In order for the place bearing tool to work for as many instances as possible, we either need to be able to adjust the bearing's vertical location due to shim plate placement on an individual basis or else allow for different cells to be used at t...
We need to be able to manually rotate survey cells in a 3D file. Yes, I understand there are macros to automate this. But simply put, we should be able to use the microstation rotate command and have the cell respond.
Separate 3D line and 3D object for pipes to different levels.
In Drainage & Utilities, the 3D line and the 3D object for a pipes(conduit/link) is placed on same level. It would be great to have them on different levels - also because it can be a demand from from clients in Denmark, that the line is place...
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).
Ability to lock Survey features when reprocessing field book
I made a change to a specific feature and I want to somehow lock the specific feature so it does not change when the field book is reprocessed. Example If I set Terrain Model Attribute of a point to "Do Not Include" then It should stay as that eve...