Trimble Business Center

 View Only

 Surface models not exporting to LandXML properly?

Jason Kuiack's profile image
Jason Kuiack posted 08-16-2024 09:33

Hey all

Wondering if anyone else has this problem with exporting surfaces as XML. It seems to only be this one specific engineering office that I'm having this problem with, but maybe someone else has seen this before as well. When I export a surface to LandXML from TBC, there are options for Surface Description.

1- Points and Breaklines

2- Triangles

Optimize for Data

Both 1&2

With the variety of export settings, is there one that Civil3D "likes" better? Or is easier for a newbie CAD guy on the other end to make it work? What would be causing "only half of the surface showing up" as the guy on the other end is claiming. I'm 99% sure its on his end, but I want to see if there's something I can do to help.

Thanks

Jason

Andrew Klingenberg's profile image
Andrew Klingenberg

I always use "2 - Triangles" for surface export.  That way you'll be writing the definition of the surface (triangles) as you see them in TBC.  Importing applications should be using the exact same definition as well so it theory there should not be any discrepancies.  This should have maximum compatibility.

If you export the SourceData, that is with option "1 - Points and Breaklines" or "1 &2" or possibly with "Optimize for data", you run the risk of the importing application deciding that it will rebuild the surface and possibly end up with a different result.  This even happens with TBC (getting a different result when rebuilding from source data that it exported).  Occasionally you might want the importing application to rebuild the surface, but unless you know that you need to export that data I would omit it.  Some applications only accept the Definition for a surface, so if you use "1 - Points and Breaklines" for your export (which omits the Definition), those applications reading your file won't import anything at all.

This has been my experience anyway.

Andrew