There's often talk here about the expense, usability or interoperability of different cogo and drafting softwares and instrument controllers and data collectors. And i often think that LandXML ought to go a long way towards addressing those concerns.
(For a quick primer on LandXML, see ProfSurv 2011 article.)
Have you had any experience where a client has required, or even accepted, survey or CAD data in LandXML format?
Have you had any experience where hardware or software has required survey or CAD data only in LandXML format?
Have you had any experience where a service provider has provided data only in LandXML format?
Also, if you've had significant experience with LandXML, what are its functional limitations?
Note, i'm not asking if your software does import/export LandXML data, nor am i asking if you've ever had to use LandXML as an intermediary between source and destination.
This is not really a poll: i'm certain most answers would be "no", but i do welcome thoughts on the topic.
Thanks.
We supply XML files to our outside engineering clients, DTM's, Nodes etc
I have a client with an engineering department that utilizes Bentley MicroStation and some aftermarket software specific to their concerns. They also routinely contract out quite a bit of topo work.
Most of the deliverables they receive are dwg files, which is no biggy with MS. A LandXML file can easily be imported to produce a surface for their specific needs.
I think they like them. Aren't they just a big ascii file with tri-vector data for a TIN?
PS -Biggest problem? Exporting an XML file on a project with SPC in International Feet and not US Survey Feet...:-(
Carlson has capability to import/export LandXML files.
Seems like it would be a good way to transfer dtm's, etc, but I haven't tried it.
Working on a few projects a couple years ago where we requested and were always given a XML file for the design surface model. It's an easy way to provide interchangeability between cad packages. I always export my surface data as xml to import to my machine control files.
> Have you had any experience where a client has required, or even accepted, survey or CAD data in LandXML format?
I can't remember it ever being required, nor can I be certain that it has been used, but I have delivered it with several projects. I usually also leave the TIN lines and point blocks/objects in the drawing file, so I can't be sure. I might add that I can't remember ever delivering the LDT DTM files either.
I think that it is distressingly common for Engineering CAD Techs to create DTMs from the contours even when DTM data has been scoped and delivered. There is very frequently a disconnect between the engineering manager and the engineering tech. I have a number of stories. Some other time, perhaps. For now let me say that if I can learn the name of the lowly tech who is using my data I will call them.
>
> Have you had any experience where hardware or software has required survey or CAD data only in LandXML format?
No.
> Have you had any experience where a service provider has provided data only in LandXML format?
I don't recall that ever happening.
> Also, if you've had significant experience with LandXML, what are its functional limitations?
The conversion of surfaces is not always 100% identical. I have seen TINS from xml imports that differed, very slightly, but significantly, from the source TIN. That is, triangles were flipped differently.
So true..
Although I believe in the last few years most digital surface creating software gets real close, they all definitely differ in minor ways.
I've had several clients mention that the contours they generated varied a little from the contours I supplied in the dgn. I'm sure it probably a case of "the devil's in the details"...meaning entity type, proximity settings and rounding criteria.
Contours are definitely the least precise calculated portion of a drawing. I've got some "use-at-your-own-risk" verbage somewhere on the sheet...just to keep somebody from trying to get me to buy some unclassified fill...:snarky:
So true..
I don't think AutoCAD exports break lines for DTM in the LandXML output. This is the little devil.
As far as the earlier comment on US vs Int Feet, there is a pick box in AutoCAD.
John
So true..
> As far as the earlier comment on US vs Int Feet, there is a pick box in AutoCAD.
The whole US/Int'l feet thing is second nature to those from the Pacific NW. For Oklahomans the Int'l feet setting is nothing more than a trap to get snared in. It has no other purpose.
> Have you had any experience where a service provider has provided data only in LandXML format?
Landonline - New Zealand's central titles and survey data registry deals primarily in LandXML - you want boundary, or control data, its going to be in LandXML format.
I've done a lot of roading and surface modelling where LandXML is the best way to move data between different systems
