For large projects, we need the ability to have multiple engineers working on the hydraulic model. We can achieve this by splitting the pipe network into multiple files and creating catchments in separate files. Doing so causes us to lose the abil...
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...
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) ...
Be able to view on & off "Name, Field Code, Elevations, & Descriptions" for Geometry Points
I can view on & off "Name, Field Code, Elevations, & Descriptions" for Survey Points but for Geometry Points you have to annotate text graphics into your model. Seems to me that you should be able to view those the same weather it's a Geom...
When stepping through model builder there is an option to set the units that are to be used in the design file; however, when the property is set in the field mappings, it does not automatically default to what was selected on a previous screen. T...
There needs to be an option to import utilities from LandXML with the option to specify the import units. I have sewer information from a utility in LandXML format, but the units need to be set to US Survey Feet. Using the import from LandXML clas...
Unable to report on Geometric Points direction relative to an Alignment.
In OpenRail Designer, unable to output the direction information when comparing geometry points to a baseline alignment. In Bentley Rail Track we were able to create clearance reports that included the direction. It appears OpenRailDesigner's repo...
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...