Terrain Model vs. Terrain element

A terrain model is a civil element, a terrain element is just a microstation element. you can convert the terrain element to a civil element by assigning a feature to it.

Nico, thanks for your reply. We've dug into this a little more, and have more questions than answers.

First, I don't know what you mean by "converting the terrain element to a civil element by assigning a feature". We've tried changing the feature template that is assigned, with no result. Were you talking about something different?

Secondly, we would like to prevent MicroStation from creating the terrain in some cases. Our workflow calls for a "triangle" dgn file to be created. (We realize this is redundant, but for now that's what we want from our consultants.) We've been using "Export to DGN Graphics" to obtain this from a terrain element with a feature template assigned that shows only triangles and the clip boundary, and we turn off the field book check mark so nothing else gets exported. We've only just discovered that this creates a terrain element. Can you suggest a better way to create the triangle dgn file?

Third, we've found a problem using reference merge to insert an existing map with a terrain model into a new clean seed file. This has always worked for us to resolve many issues in a consultant file. It seems that the reference merge is converting the terrain model into a terrain element. We have anecdotal advice that this may be related to locking/unlocking the survey processing rules, but haven't been able to pinpoint the issue. Shouldn't reference merge work without losing the terrain model?

We are using Power GEOPAK SS3 version 08.11.09.722.

Thanks very much for your help.

Frank Boston, CP
Michigan Department of Transportation
Design Survey Support

425 W. Ottawa, Lansing, MI 48933
Voice: 517-241-3561 / Fax: 517-241-4631
BostonF@michigan.gov

You are welcome. I think we have a few issues here.

First, you can use the Set Feature definition tool to set any element or terrain and make it a Civil element.

Second, you could just export a tin file from the terrain.

Third, I tested this and you are correct. what is happening is that the merge reference tool is not truly copying the terrain.  I tried placing a fence around the terrain and copying the elements from the reference file into the new file and this worked.  You would need to refresh the dgn (close and come back or type rd= in the microstation key in) for it to show in your project explorer as a terrain model.

I hope this helps

Nico - Cool, the very first item here will definitely help.

The second item, I'll play with and probably revise our workflow.

The third item, using copy with a fence from a reference file, I have considered but hadn't tried. Is the fact that the REF MERGE doesn't work a bug? Should that be reported, either as a bug or a desired feature?

Thanks again for your help!

Frank