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 file and adds it to the terrain. There really is no way to control which elements are being added to the terrain. So the tool will (drape) process everything in the 3d model including 3d linestyles. If this tool had some kind of control through level display, fence limits or reference clip then it would be a game changer and probably used as a default terrain creation for most users. As it currently is configure it is difficult for use on complex projects. Currently, In order to exclude objects they need to be in a separate file. 3d linestyles would need to be a separate file. Separated ponds, paths or segments of bridge crossings would need to be in a separate files. This is a difficult workflow for users to manage on large projects.
If anything, please allow an option for the tool to only process levels "on" in the active view or inside a reference clip. That would be a great addition.
| Civil Product Used | OpenSite Designer, OpenRoads Designer, OpenRail Designer |
The other problem with this tool is if you have adjacent corridors which may not have the exact same intervals and hence slightly overlap you can get bad results.
For these reasons I've just gone the graphical filter approach and then just setup the feature definitions carefully to capture what I want, you feel much more in control.
Perhaps a "Include visible elements only" setting so it uses the active views Construction Class display flag, displayset, level display settings, and reference display flags, etc?