By: Kenneth Crawford
Last Entry Recap: Data Interoperability, or “Why it’s important to play nice with others!”
We talked last time about the need for sharing our work with others in the process, and the bottom line conclusion is that we need the tools that make this an easier process, and we need tools that give us the confidence to stand behind our work and not have to hide behind the “PDF shield” which often masks the thought processes that went into the resulting drawing. A drawing is no longer enough . . . stakeholders want —and need— the data to build on.
Some Problems . . .
Some of the obvious problems include delivery formats and target application that will use our data, the thoroughness of the understanding on the recipients’ part about the nature of the data they will receive from our work, who holds ultimate responsibility (i.e., liability) for the content delivered, etc.
Some Solutions:
Much progress has already been made through attempts at defining a common language for the interchange of civil engineering and surveying information, most notably through such stands as
LandXML. LandXML is a joint specification crafted by participating software vendors and information technology specialists that defines a standard file format for civil engineering design and survey measurement data.
The primary goals for providing a standard data format are:
- Data exchange between software applications
- Long–term data archival
Hundreds of software developers and government organization around the world have adopted LandXML. LandXML data types include:
- Points
- Survey measurements
- Alignments
- Profiles
- Cross Sections
- Surfaces
- Parcels
- Pipe Network
and more . . . For more information, visit the official site at http://LandXML.org.
LandXML is a tried and true solution for moving encapsulated data back and forth between different design platforms, and is often the tool of choice to transfer the data. I have found, however, that we often will need to make sure the recipient even knows how to use this data once they receive it, and chances are that whatever platform they work on, it has a means of importing this information.
We should also not hesitate to request the same information via LandXML from our own sub consultants to assist our own work . . . there is no need to reinvent the wheel, which sometimes also introduces additional errors into the process for work that has already been accomplished.
Finally, the good old “text file” or “ASCII transfer” Alternative is still alive and well. Sometimes the simplest exchange of data that both originating and receiving platforms can understand is a simple text file “Import/Export” Function. Again, consult your Help system to see what options you may have.
As for the “who owns the liability” Question, this will likely keep our attorney friends gainfully employed moving forward, but a standard statement —delivered with the data— should be an absolute must! Work with your attorney to craft language that will cover the situation, and always keep adequate submittal records. This should go without stating.
Your assignment . . .
So, take a few minutes to explore the LandXML options your software provides. You can usually find the tools under the “File” menus, look under “Import” and “Export” Options, or better yet, just open the Help system and search for the term “LandXML” (or even just “XML”). Being familiar with the tools can provide you with good information to discuss with the other stakeholders in the process, and can open up a much smoother hand-off of information that will keep errors and rework to a minimum.
And don’t forget . . . the telephone is still a very viable tool in getting the work successfully delivered; don’t hide behind the project specs and just pick up the phone and talk to the other folks who will use our data! It will pay dividends.