I have been using Geopak since V8i and I was able to do this using native tools.
I suppose I still can. But if I go that route, it will involve breaking the elements down from civil features and such, doing a selection set around the ones I want to contribute to my terrain, then grabbing the elevations from them, then sending them through TIN processing, and then re-importing as an OpenRoads terrain. No part of that complies with the usual use of OpenRoads tools.
I'm not suggesting that this is my first observation that OpenRoads technology doesn't support this kind of workflow, but it is the first time I realized I should probably make a customer request for it. I had previously solved this problem by constructing by hand the terrain clipping boundary. That, too, violates the usual benefits OpenRoads tools often provide.
I suppose I still can. But if I go that route, it will involve breaking the elements down from civil features and such, doing a selection set around the ones I want to contribute to my terrain, then grabbing the elevations from them, then sending them through TIN processing, and then re-importing as an OpenRoads terrain. No part of that complies with the usual use of OpenRoads tools.
I'm not suggesting that this is my first observation that OpenRoads technology doesn't support this kind of workflow, but it is the first time I realized I should probably make a customer request for it. I had previously solved this problem by constructing by hand the terrain clipping boundary. That, too, violates the usual benefits OpenRoads tools often provide.