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

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

At the current OpenRoads version, we need to select the terrains at 3D view then click properties in order to rename. It would be better if it can be renamed just by selecting the terrain name from Explorer list>(right click) properties.

It would be very useful to big back the user option for stroking linear elements when creating terrains. This was available in v8i and greatly enhanced our surface models. Right now there is a configuration variable but it can't be set by users. A...

We really need some kind of optimization setting available which will improve the performance of OpenRoads when Existing Ground Terrain Contours are Displayed. I believe this setting in Civil 3D is called "Level of Detail" or something. The proble...

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

Need ability to toggle slope percentage annotations above/below the flow arrows on terrains. This will help with design and analysis. An option could be added in the flow arrow properties, please refer to the attached snapshot.

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

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.

When I first saw this tool I was so excited. I could drape the design meshes from top or bottom and create a terrain . Then I started using it and realize the tool may need some improvement because it processes everything in the file or reference ...