Objective. Students transfer raw field data from the data collector to office software, process observations into a coordinate file, and export deliverables in formats usable by AutoCAD Civil 3D and ArcGIS.
This lesson, its worked examples and its practice questions has not yet been verified by an industry-certified professional or by a certification or approval body. It is a study draft and may contain errors. Do not use it as instructions for work on a job site or on live equipment. Always follow your instructor, your supervising professional, and current official references and regulations.
VoTechWorks program approval and accreditation are still in progress. Credentials are issued only by the certifying bodies named in each program, after their own exams.
Field observations recorded by a total station are raw measurements: horizontal angles, vertical angles, and slope distances. Those numbers must be transferred to office software, corrected for physical effects, and organized into a usable coordinate file before any deliverable can be produced. A mistake at this stage—skipped corrections, a misread point number, or a wrong export format—can corrupt every downstream product: the CAD drawing, the GIS layer, and ultimately the client's decisions. Precision in the office is just as important as precision in the field.
Most modern data collectors connect to an office workstation via USB cable. Before connecting, power down the data collector and inspect the cable for damaged insulation; a frayed USB cable near a powered workstation is an electrical hazard—replace it before use. Once connected, the operating system recognizes the device as a removable drive or a COM port, depending on the manufacturer.
Open the manufacturer's office software (Trimble Business Center or Leica Infinity are common choices in this program). Use the import or transfer function to pull the raw job file from the collector. The raw file typically stores every observation in a proprietary binary or ASCII format. After import, the software displays each observation in a list: the instrument point, the backsight point, foresight point, horizontal circle reading, zenith angle, and slope distance. Review this list completely before processing. Look for:
Annotate any suspect observation in the software's notes field with a reason code before you decide to keep or reject it. Common reason codes used in this program: BL (blunder), DUP (duplicate), NV (not visited / incomplete shot).
Raw slope distances require two physical corrections before they become ground distances.
Atmospheric correction accounts for the fact that the instrument's EDM (electronic distance measurement) light travels through air whose density depends on temperature and pressure. The instrument applies a parts-per-million (ppm) correction using the temperature and pressure values entered at setup. Verify in the job file that those values were recorded; if the field crew left the defaults, the correction may be wrong. The office software allows you to override the atmospheric parameters and reprocess.
Curvature and refraction correction is needed when shots are long enough for the Earth's curvature and atmospheric refraction to affect the elevation difference derived from a zenith angle measurement. Most office software applies this automatically when you enable it in the project settings. Confirm it is turned on for any traverse leg or elevation shot longer than a few hundred feet.
After corrections, the software reduces the slope distance to a horizontal distance and computes a ΔZ (change in elevation). Combined with the instrument height, reflector height, and the elevation of the instrument point, it calculates the northing (N), easting (E), and elevation (Z) of each foresight point.
The coordinate solution is only as good as the control it is built on. Confirm that the instrument point coordinates and the backsight azimuth or backsight coordinates in the job file match the values from your control network documentation. A single transposed digit in a control coordinate will shift every derived point by the same amount—the traverse will close perfectly but be in the wrong location.
After processing, inspect the traverse closure. The office software reports a linear error of closure and a precision ratio (e.g., 1:10,000). Compare this to the required precision for your project class. If closure is outside tolerance, do not export until the problem is found and documented.
Once the traverse closes within tolerance and corrections are applied, generate the final coordinate list. The list should contain every accepted point with its Point ID, N, E, Z, and description. In the software, mark rejected shots with the appropriate reason code so the list and the audit trail both reflect what was excluded and why.
The most portable export format for point data is a comma-delimited text file (.csv) with columns in this order: Point, N, E, Z, Description. This column order is the convention expected by AutoCAD Civil 3D's Point Import command and is compatible with ArcGIS Pro's Add XY Data tool (you will map the E column to X-longitude and the N column to Y-latitude within the dialog).
Steps to verify the export:
1. Open the .csv in a plain text editor and confirm the header row matches the expected column names and that decimal places are consistent.
2. In ArcGIS Pro, use Map > Add Data > Add XY Data, select the .csv, set X Field = E and Y Field = N, assign the correct projected coordinate system, and verify that points plot in the correct location relative to a reference layer.
3. In Civil 3D, use Home > Import Points, select the PNEZD (comma-delimited) format, browse to the .csv, and confirm the point cloud appears in the correct position in the drawing.
If points appear in the wrong location or at the wrong elevation, recheck the coordinate system assignment and the N/E column mapping before assuming a processing error.
Save the processed job file and the exported .csv with a clear naming convention that includes the project name, date, and version (e.g., `RiverRd_Traverse_2025-06-10_v1.csv`). Keep the raw imported file untouched as the original record. Never overwrite raw data with processed data.
Answer each question, then check it. Nothing is recorded; this is your own practice.
A free tech program — complimentary, as our commitment to get America working. Help us build VoTechWorks. Tell us what works, what doesn’t, and what you want to learn.