Data Prep Tips, Tricks & Techniques: How can I build this in the field?

Written by Chad Cooper

Created on Saturday, 02 May 2009 23:03

I would assume that everyone, regardless of what field they work in, has had experiences that helped define how they do what they do. It may have been as simple as a suggestion from a co-worker, or as hard as a lesson learned from a critical mistake. However it comes about, I feel safe in saying that we have all had these moments.

For me, one critical lesson came almost 15 years ago. I was working for a small civil engineer office as an engineer technician. I walked into the job with only AutoCAD experience, so everything about engineering design that I learned was on the job. Being young, I was quite confident (falsely so) in my ability to design just about anything. After completing one of my first designs, our surveyor came in to talk to. She asked one simple question:

“With these plans, how can I build this in the field?”
At first, I thought she meant that my design itself was lacking. But it was not my design that was lacking. It was how my paper plans failed to accurately define and communicate my design. The following conversation with our surveyor presented some of the most practical advice I have ever received on what a surveyor really wants and needs to see in the field. While this question and her advice originally applied to civil design, the same question can be asked to those who built data:

How is my client going to use this data in the field?
Over the years, this is a question that I have asked myself over, and over. When I first started building data, I would add dozens of line work and point layers in my data files with information that I thought would be important to our clients. But afterwards I was told that much of the detail was useless and that only core items were needed. Everything else was just a layer that they turned off and never used despite all the additional work I had put forth to provide that information. While there are instances a client will need something very specific, I have found that the vast majority needs the same basic information regardless of job size or job type. Everything else bloats the file size and can distract field personnel.

While it is impossible to predict and list all that may be needed for a client’s data, I usually start with a series of questions to help me better understand their needs. These include:
1.    Are you providing staking?
2.    Are you providing utility layout?
3.    Are you using automatic machine control?
4.    Are you just looking for a rough file to do mass grading?
5.    Do you require multiple surfaces representing different sub-grade levels?
6.    Are the areas outside paved surfaces critical?

And so on.

In the end, understanding the needs of your client is paramount. Clients need to divulge to their data prep. provider, or in-house personnel, exactly what it is that they need.  In building good data, the more concise the data the better. The proverbial balance closer achieved with experience.

[ Back ]