Currently, Graphical Filter will use all elements in the DGN to create the terrain based on the filter created. However, in certain cases, that might not be ideal as we may not need the entire terrain model to be created. As such, having the abili...

Currently we can Analyze Element to obtain the range high and range low for XYZ of a terrain, but that XY value does not reflect the coordinate of the actual range high/low Z, it just gives the highest/lowest XY in terms of the coordinate number. ...

In case the reference terrain needs to be re-done, this would allow to keep the clipped terrain and link it to the new active terrain.

Suggest renaming the "merge" and "append" functions when creating a complex terrain to something more descriptive of the action being performed. For instance, merge could be renamed to "overwrite" and append could be renamed to "use both". Users h...

The following idea is related to the survey tool gap analysis that is already being considered. The Extract Contour tool should be enhanced to place a graphic line at a specific elevation. Currently, you have to change the contour interval of my t...

surface templates apply depth vertically, in many cases it is desired a true depth that is perpendicular to the terrain.

We need the ability to display terrain slopes at a specified grid interval. This technique is used to present to other stakeholders (non ORD users) for analysis and confirmation that all the slopes of a terrain meet design criteria. InRoads had a ...

When a text style like Tahoma05_CC has no color explicitly set, MicroStation behaves differently depending on how the text is placed: Regular text placement: It correctly uses the color from the active level. Contour labels (e.g., placed via t...

Please add the support to import an .laz file directly to a terrain. If it ORD can read an laz into a point cloud it seems like a pointless extra step where I have to convert an laz into a pod or las before I can import it into a terrain.

In OpenRoads Designer 2023, under the Terrain tab, add the ability to export a ORD surface to a .tif file. The HEC-RAS RAS-Mapper can only use .tif surfaces.