DTM Surface with non-contiguous triangulated areas

Question

I have an InRoads DTM from survey data with a couple triangulated areas that don't touch each other. I have to get it to a client for use in Power Geopak. 
 Initially, the surface was triangulated with a 100 foot max triangle length to eliminate 'bad' triangles. The result was two areas of triangulation (streets) that are not touching or connected. This is the way it ought to be, i.e. true to life. I cleaned it up (deleted) other 'bad' triangle slivers and saved. I am satisfied with the results, it's a keeper. 
 I translated to XML then checked in InRoads before sending. I used the translator to import. Although the triangle vertices and faces are included, InRoads likes to ignore them and requires re-triangulation. The result is they are re-connected again and all clean-up is lost. 
 What's up with that? 
 I found that importing to a Terrain Model from File does not seem to honor the boundary, because triangles show up outside my boundary. 
 What's up with that?

Chris Key · Accepted Answer

In InRoads, you need separate surfaces for areas that will have boundaries around triangulated data. I am not sure on the GEOPAK side if they can work with split areas with triangulated data and store boundaries. 
 
InRoads doesn't store the surface as a triangulated model but is instead feature driven, therefore we want to retriangulate surfaces when imported from LandXML because we don't store that information from the XML.