Please add a property to all the chambers including both catchbasins and manhole which specify the back drop height (multiple values if we have multiple incoming pipes)

This would work the same as the current boolean UDE field, but it would have options that can be predefined when creating the UDE field, this would be especially helpful since our custom control input variables are defined using UDE fields (it req...

These are super useful for measuring locations of change in between scenarios. These are similar to the results points, core functionality.

Creating videos from the 2D run

particularly normal depth

It would be very helpful if ORD drainage model calculates the velocity and normal depth in the gutter- especially when we use gutter as a user defined gutter/channel in the medians to analyze median channel.

Pipe standards vary their minimum and maximum pipe cover values based on the size of the pipes. There needs to be an ability to set this per conduit size so that when running a design you can consider these different cover depths. As of now, you w...

When exporting a drainage flex table in ESRI format, the default field names include names longer than 10 characters. This throws the error message: "The Esri Shapefile field name <Middle_Flow> for column <Flow (Middle)> cannot be long...

This can be used to identify drops in straight line because of some clashes, etc. Also this should be able to highlight based on the value of drop depth.

Currently there is only an option to add Rational Method Frequency Adjustment Factors for the entire storm, which affects all catchments. Our GDOT standards require modification of the factor for only C values less than 0.6.