Land XML import problems

Question

The attached .xml file was produced by Civil3D 2014. When imported into InRoads 08.11.07.615 the results are shown in xml in inroads.jpg. When imported into Civil3D 2012 the results are shown in xml in civil3d.jpg. What can be done to improve the results in InRoads?

neilw · Accepted Answer

I've experienced this problem as well. When I export a C3D surface to XML and import into Land Desktop or Power Civil the boundary is not honored. However if the XML file is imported back into C3D the boundary is honored. My conclusion is the problem is with Civil 3D, so it must be addressed on that end. 
 In Civil 3D surface boundaries may be created by a combination of corridor models, grading tools and other means. I think the problem is those boundaries are not translated to the XML file properly during export. One solution I've found is to manually extract the limits of the TIN and add it as a boundary to the surface definition in Civil 3D prior to export. That hard boundary will then be honored when the XML file is imported into other applications.

Paul-PennDOT · Answer

InRoads uses a featured based DTM. If you import an xml file with features into InRoads, it will be retriangulated. The rules for triangulation are not the same between softwares. If you want better agreement between contours I would suggest viewing out the tin in C3D and saving the triangle mesh as a DXF file. Then import the lines as breaklines into InRoads. If you intend to share design work between the two softwares then this is not practical.