I tried exporting a complex terrain to all of the available export formats (dtm, tin, .xml, fil, and txt). When I create a new terrain from any of these exported files the triangles don't match the original terrain. I think the underlying terrain is being reprocessed, thereby losing any terrain edits that may have been done. I think this happens on any edited terrain, not just complex terrains.
This seems like a defect. Am I expecting too much?
Are you exporting features or the terrain?
If terrain, I believe that shouldn't happen. You may end up with unwanted triangles around the exterior but triangulation should match within the terrain.
If features, the terrain will be retriangulated on import. The only way to maintain your edits is to create features that force the desired triangulation.
Ray,
I only export the terrain. None of the export formats have options for specifying triangles, features, etc. It's an all-or-nothing process. Even then, the triangles revert back to their pre-edit orientation/existence. I will try the other suggestions in this thread.
Josh
That's surprising. I know InRoads and previous (V8i) versions of MicroStation imported only the points from surface definitions, ignoring the triangles. They then triangulated all those points as random points. I haven't tried MicroStation CONNECT, but I thought ORD actually used the triangle definitions.
That leaves you with creating features to hold your edits. LandXML and InRoads DTM exports allow for the export of features only, terrain only or both.
My Mistake. I found the "triangles only" option, exported to LandXML file, imported LandXML file into a blank 3D file. Now the triangles match.
Thank you.