Sometimes we need to have larger models for large projects to maintain flow continuity.

We have the option to define a template to pipes external walls, but only through the feature definition. For all other elements of the pipe, OR allows for feature symbology. From my experience, symbologys work better and are more constant.

It would be helpful if multiple drainage nodes could be assigned to a terrain in one step. This would solve a problem if someone deletes the proposed terrain that was used to initially layout the drainage system. Currently users have to update the...

Is there a way to add constructed length and constructed slope to a conduit flex table? I can build annotation for these fields for plan production, but I haven't found these fields to add to a conduit flex table. This would allow for more options...

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...

I get close to 40-50 rows of data when I assign a "pond" to a terrian. I only need data every 0.1ft but it is providing much more.

Add support for nodes that accept multiple types of conduit families.

Currently it is not possible to export the alignment and profile from Profile Run with same station as it considers the nodes in the profile. We can select the conduit and export it, but this would be actual conduit length not the center to center...

Geopak Drainage could read a TIN file to establish the cross slopes for spread. This functionality should still existing in Drainage and Utilities by reading corridor models and terrain models. Users should be allowed to define an infinite number ...

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...