[ORD 2022 R1] Exported Terrains Don't Match Original

RE: [ORD 2022 R1] Exported Terrains Don't Match Original

Josh M — Mon, 07 Nov 2022 17:05:53 GMT

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.

RE: [ORD 2022 R1] Exported Terrains Don't Match Original

Ray Thwaits — Mon, 07 Nov 2022 16:14:40 GMT

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.

RE: [ORD 2022 R1] Exported Terrains Don't Match Original

Josh M — Mon, 07 Nov 2022 13:29:07 GMT

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

RE: [ORD 2022 R1] Exported Terrains Don't Match Original

caddcop — Fri, 04 Nov 2022 16:24:22 GMT

In my experience, Triangle Swaps are very fragile in Bentley software. Nothing is written to the terrain to preserve them if any recalculation of the triangles is required. I even tried manually adding breaklines to force swaps, but sometimes that impacts how surrounding triangles are formed. I try to avoid swapping triangles unless it is absolutely required and only late in the design process.

RE: [ORD 2022 R1] Exported Terrains Don't Match Original

Ray Thwaits — Fri, 04 Nov 2022 15:36:23 GMT

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.

RE: [ORD 2022 R1] Exported Terrains Don't Match Original

Mark Shamoun — Fri, 28 Oct 2022 22:30:52 GMT

Hi Josh,

Perhaps try adding a boundary to the Terrain when it is how you want it and perhaps the extra breakline definition will now have enough definition to reproduce properly (haven't tested it though).

RE: [ORD 2022 R1] Exported Terrains Don't Match Original

Josh M — Fri, 28 Oct 2022 14:20:04 GMT

Mark,

That may be part of what I'm experiencing. I notice triangle orientation is not propagated either. My original terrain had some triangle-swap edits, and some edge triangles were deleted prior to exporting. None of these edits were carried through.

Josh

RE: [ORD 2022 R1] Exported Terrains Don't Match Original

Mark Shamoun — Thu, 27 Oct 2022 22:22:55 GMT

Hi Josh,

Triangle Edge length does not get propagated into export. Is this the issue you see?