I am attampting to create a terrain model from several corridors. The location is in an area where several ramps converge and would like to use the terrain model to define the detailed grading that a simple corridor can not produce.
What is the preferred method for something like this? Is the terrain model even considered the best practice here?
If I import various features from the corridor they come in as a whole entity which is much longer than what I need. Also, these features can not be modified in any way to trim them to the desired length.
I have thought about making horz. and vert. geometry along the desired features but this seems labor intensive.
I have add good success doing the following:
Hope this helps someone.
Could you not create a terrain from the original elements, which are too long, and then - from the resultant terrain - just create a clipped terrain? That would probably be quicker than creating the offset features, I would say.
I suppose that would be a solution. Although, it does present several other challenges, namely:
The boundary element could be just a graphical shape that defines the area - if the original terrain has a feature set to 'Boundary' (to prevent the slivers forming) the clipped terrain will respect that setting, with no slivers being created.
The problem is in creating that boundary element in the first place. Some of the elements can extend far beyond the area where the terrain model is required and some still can cross each other at some point due to the nature of the interchange. Having to trace over the elements is not the answer since a change in ramp alignment would require a manual edit of the element.
To me, the best approach here would be to allow the editing of a terrain model element similar to to geometry behaves. An element could be added to the terrain. It could then be partially deleted creating an "interval" similar to the geometry workflow. In this way the element still maintains the linkage to the original element but the limits are as shown graphically.