Issue

As the civil design industry continues to embrace model-centric workflows, many agencies are now undertaking efforts to generate models for existing content, specifically for subsurface utility facilities. Two common workflows for this effort leverage OpenRoads Designer’s Extract from Graphics command. This command works well for modeling utility content when using surface elevations from a Terrain Model, but in all tested version, an error exists in extraction when elevations are sourced from the graphic’s elevation.

When extracting Features that use a Shape Orientation other than Invert, the software properly evaluates elevations at each internal vertex of the source geometry but places the invert of both ends at the expected elevation as defined by the Shape Orientation (typically Soffit, a common setting for most non-gravity flow systems). In the case of a soffit orientation, this causes a vertical offset equal the conduit’s rise.

Resolution

While the primary hope for this tip is to make you aware of the issue in extraction using element elevation, it is worth a few comments on resolution. The exact behavior of the nodes and links will depend on the specifics of a give situation, including the configuration of the node and link, Feature Definitions, and version of OpenRoads Designer being used. One of the following actions should resolve this issue.

Note: The profile model view of the utility is typically the easiest location in which to adjust this value.

• If editable, lower the Start Invert and Stop Invert by the conduit diameter inside the Properties Dialog or on the textual manipulators in the Profile Model.

It is worth noting that in the situation described in this tip, there is a visual disconnect between the graphical (dot) and textual manipulators on these link elements. Moving the link with the graphical manipulator will update the textual manipulator value, but the value displayed is the invert of the link, not the elevation of the reference line. Therefore, use of the textual manipulators should provide a cleaner workflow.

• Adjust the node invert (and ground elevation, if desired for visual consistency). Some configurations lock the link to the node’s invert, allowing the link’s elevation to be corrected by updating the node.

In some cases, depending on the node Feature Definition, adjusting the node may require moving both the ground elevation and invert elevation for the locked link to follow along. This behavior has been observed primarily in older versions.

• If neither of these methods work, a new profile can be created using standard Vertical Geometry tools from the OpenRoads Modeling workflow and setting that profile as active. This option will remove some of the dynamic functionality that resides in ORD, but should fix any remaining stubborn situations. One key consideration here is to not create any persistent snaps to the elements created in the initial extraction.