RE: Edited triangles and LandXML

We're having the same issue with PowerGEOPAK.  We have a workaround to create an external boundary, using a "drape boundary" (see thread: communities.bentley.com/.../92188.aspx).  This works fine for the boundary of the project, but as noted above, leaves all internal edits at risk of reverting.  What I think we'll have to tell our users is to NOT edit triangles internally.  Instead, they'll need to edit the source data to provide the desired result.  In many cases, this is actually the proper way to address a problem with triangles anyway.  However, this is a problem that Bentley needs to address directly.  All of these "workarounds" don't solve the problem.  A way for PowerGEOPAK or InROADS to keep track of triangle edits is needed.  

Frank Boston, Michigan DOT Survey Support