We have a large engineering firm client that uses C3D. We plan on sending them a CAD file of a topographic detail survey that we have completed using our ancient LDD 2005. They also would like surfaces, alignments, etc.
In the past we have sent clients using a newer version of AutoCAD an eTransmit zip file which was simply the DWG along with the tin etc. This has always worked for us and I assume they were able to read an older version of AutoCAD dwg and convert it to whatever they need.
A much younger and more energetic colleague of mine mentioned that I might want to go the LandXML route. From what I have read it looks to me that the XML is a text file that contains the associated data files to a drawing. Is that true? Do I also have to still send a dwg for the linework etc?
I am assuming that any answers would also apply to Carlson which we also use.
Please speak slowly and clearly as I am an older gentleman who still carries a plumb bob.
Thank you for any help it will be appreciated.
Hack
I never used LDD, but i have used C3D for 4 years and I use XML to send surfaces to all of my engineering clients. I haven't had anyone comlplain (except for one dude that was using vanilla autocad). I have one client that still uses LDD and XML was the only way I could send him a surface. Seems like your colleague has the right idea.
> I never used LDD, but i have used C3D for 4 years and I use XML to send surfaces to all of my engineering clients. I haven't had anyone comlplain (except for one dude that was using vanilla autocad). I have one client that still uses LDD and XML was the only way I could send him a surface. Seems like your colleague has the right idea.
How do they get the line work in the drawing?
The XML file for a surface is a listing of points and the associated link lines to those points. I always export surfaces to XML format and have not had a problem yet. Just send the CAD file and the xml for the surface.
Just send them lines, arcs, polylines, blocks, whatever you have. The surface is the only thing that is XML.
> Just send them lines, arcs, polylines, blocks, whatever you have. The surface is the only thing that is XML.
Got it Thanks....
I don't do it often but recently had to. I run LDD3.
The xml will send all your breaklines, points, etc. That way, nobody is taking your contours and just making a surface with them and ignoring low points, breaklines, etc.
> A much younger and more energetic colleague of mine mentioned that I might want to go the LandXML route. ....
I'm not sure about energetic. XML is a very low effort way to go.
>From what I have read it looks to me that the XML is a text file that contains the associated data ....
It is a text file. Just think of it as a data format that almost all software can read. Analogous, in a sense, to an ascii file for points.
>Do I also have to still send a dwg for the linework etc?
Yes, you will still send the dwg file as well.
Go for it. It is really very straightforward.
Thanks for the help.
Land XML is a cross platform tool and like
so the target program may not be CURRENT to Xml version and thus the XML
import may not import the certain surface edits like flip face etc etc etc
I only use XML from soft to soft for real basic items like CL's and BASIC profiles
after that do NOT expect Cross software XMLs to work.
XML is a mine field pretending to be a push up well fill it in
To answer your question, yes XML files are simple text.
XML = eXtensible Markup Language.
You can zip them and unzip just fine.
I was one of the contributor to another standardizing thing called SOAP. Simple Object Access Protocol. It was an follow on to XML but was more to do with computer to computer speak.
Just do a right click and open with notepad or something. It's plain ole text but wrapped around all kind of tags. Back in the day we called it "payloading".
Your dwg file with tin, points, etc.... is much better than the XML file IMO. We have had mixed results with the XML files not holding edits or recognizing breaklines. Or if you must send the XML definitely send the dwg file and state which surface holds over the other in case of discrepancies.
My 2c.
From experience, LandXML works well for point data, alignment, profiles and surfaces (3D faces and/or 3D lines) but requires sometimes a bit of editing (obvious spikes) cross-sections. That could be caused by an error in importing on my behalf too, lack of experience with the routine.
Not perfect but certainly useable and a good transfer utility overall.
LandXML will certainly work, but Civil3d can also read data directly from a Land Desktop project. Just zip up your project directory including drawings, and send them the whole thing.