An issue surfaced yesterday where a customer of mine exported his LDD surface out to LandXML, then imported the LandXML surface into Civil 3D. The results were that the surface came in being 27’ off south, and 4’ off west.
I had the customer check his coordinate systems in both softwares. They were spot on. I also had him check his units. They were spot on. Then I had him check the LandXML settings, and they were spot on.
I told the customer to use the Import>Land Desktop (IMPORTLDTDATA) option. The surface then came in correctly at the correct location. Weird? Yes, definitely!
I’m not sure what would have caused this. Like I said I checked all the settings that would have possibly caused this. So, this is a head’s up for those of you using the import LandXML option.
Me, personally, recommend using the Import>Land Desktop option when bringing in legacy projects.