🚧 Under construction — VoTechWorks is being built. A free tech program — complimentary, as our commitment to get America working.
voTechWorksGrade 13 · a vocational technology learning center, by urbanicity
newSchoolWorks.com › VoTechWorks › Technology & Design › GIS / Surveying / Drone Operations › GNSS Field Operations and Data Processing › Lesson 8
TEC-GIS45-03 · Lesson 8 · 12 clock hours · lab

GNSS Data Download, File Formats, and Quality Control

Objective. Students will transfer GNSS field data from a data collector to a workstation, convert or export to at least two standard file formats (CSV and LandXML or similar), and perform a documented quality-control review.

⚠ Pending professional review

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.

GNSS Data Download, File Formats, and Quality Control

Why This Workflow Matters

Field observations are only valuable when they reach the office as complete, correctly formatted, and verified data. A single missed point or a misassigned coordinate system can invalidate a survey deliverable. This lesson walks through every step from the moment you unplug the data collector to the moment you hand a QC-approved file to a project manager.

Step 1 – Transferring Data from the Data Collector

Most modern data collectors connect to a lab workstation by USB or wireless sync. Before you connect:

Once connected, open the manufacturer's office software (examples include Trimble Business Center, Leica Infinity, or similar). Import or open the job file. The software will display a point list: record the file name, point count, date/time stamp, and any error flags in your lab notebook. If the point count does not match your field tally from Lesson 7, stop and troubleshoot before proceeding.

Step 2 – Standard File Formats

CSV (Comma-Separated Values)

A CSV is a plain-text table. For surveying, the standard column order is: Point ID, Easting, Northing, Elevation, Description. CSV files are universal — any GIS, CAD, or spreadsheet application can read them. They carry no projection metadata, so the coordinate system must be documented separately and applied when the file is imported.

LandXML

LandXML is an open, XML-based schema designed specifically for civil engineering and surveying data. It stores points, alignments, surfaces, and parcels along with metadata such as coordinate system name and datum. Because it is schema-validated, it is far less likely to lose projection information than a CSV. Most manufacturer office programs export LandXML directly from the job file.

Job Files (Proprietary)

Each manufacturer's native format (e.g., .job, .jxl, .vce) preserves raw observations, epochs, and processing logs. Keep the original job file archived even after exporting to open formats.

Step 3 – Importing CSV into ArcGIS Pro

1. In ArcGIS Pro, go to Map → Add Data → XY Point Data (or use the Make XY Event Layer geoprocessing tool).

2. Set the X field to Easting and the Y field to Northing. If you have elevation, set the Z field.

3. Assign the coordinate system that matches your field configuration — for example, a State Plane zone in US Survey Feet, or a UTM zone in meters. This step is critical: assigning the wrong system will shift every point by thousands of feet.

4. Export the event layer to a permanent feature class or shapefile so it persists after the project closes.

5. Open the attribute table and confirm that point count, field names, and a sample of coordinates match your field notebook.

Step 4 – Quality Control Review

QC is a systematic check, not a glance. Work through your printed QC checklist and compare it against the ArcGIS Pro attribute table:

Point codes. Each point description (e.g., MON, IPF, EOP) must match the field notebook. A wrong code misclassifies the feature.

Observation count (epochs). GNSS receivers log a configurable number of measurement epochs per point. Fewer epochs than the project minimum indicates a rushed or interrupted observation.

PDOP (Position Dilution of Precision). PDOP quantifies satellite geometry quality. Lower is better. Flag any point with PDOP greater than 4 as suspect; high PDOP inflates positional error. A PDOP below 2 is excellent; 2–4 is acceptable for most surveys.

Solution type. A fixed integer-ambiguity solution is required for centimeter-level RTK work. A float solution means the receiver did not resolve carrier-phase ambiguities and the position is less reliable — typically decimeter-level at best. Flag every float-solution point for re-observation.

Remediation options for flagged points. Return to the field and re-observe under better sky conditions, or post-process the raw data using CORS (Continuously Operating Reference Station) base data if your equipment supports it.

Written QC Summary

Your QC summary is a professional document. It must include:

Safety and Data-Handling Notes

Key terms8

CSV (Comma-Separated Values)A plain-text file format in which data fields are separated by commas; used to exchange point data between survey, GIS, and CAD applications but carries no embedded projection metadata.
LandXMLAn open XML-based file schema designed for civil engineering and surveying data; stores points, surfaces, alignments, and coordinate system metadata in a single validated file.
PDOP (Position Dilution of Precision)A dimensionless number expressing how satellite geometry affects three-dimensional positional accuracy; lower values indicate better geometry and smaller amplification of ranging errors.
Fixed SolutionA GNSS RTK result in which the receiver has resolved carrier-phase integer ambiguities, yielding centimeter-level accuracy; the required solution type for most control and boundary surveys.
Float SolutionA GNSS result in which integer ambiguities are estimated but not resolved, producing decimeter-level accuracy at best; such points must be flagged and re-observed or re-processed.
XY Event LayerA temporary GIS layer created in ArcGIS Pro by reading easting and northing columns from a table and rendering them as point features in a specified coordinate system.
EpochA single measurement interval during which a GNSS receiver records carrier-phase and pseudorange data; surveyors set a minimum epoch count per point to ensure observation quality.
CORS (Continuously Operating Reference Station)A fixed, permanently operating GNSS base station whose data is archived and publicly available; used to post-process field observations for improved accuracy when an RTK fix was not achieved.

Worked examples4

1. Your field notebook records 47 points collected during the day. After transferring the job file, the manufacturer software shows 45 points in the point list. How many points are unaccounted for, and what is the percentage of data missing?
  1. Subtract the transferred count from the expected count: 47 − 45 = 2 missing points.
  2. Divide missing points by total expected points: 2 ÷ 47 = 0.04255…
  3. Multiply by 100 to convert to a percentage: 0.04255 × 100 ≈ 4.3%.
Answer: 2 points are unaccounted for, representing approximately 4.3% of the day's data. Investigate the transfer log for errors before the project can proceed.
2. During QC you examine five points with the following PDOP values: 1.8, 2.4, 3.9, 4.2, and 5.1. Using the project threshold of PDOP > 4, how many points must be flagged, and what percentage of the five observations is acceptable?
  1. Apply the threshold: flag any point with PDOP greater than 4. Identify values above 4: 4.2 and 5.1.
  2. Count flagged points: 2.
  3. Count acceptable points: 5 − 2 = 3.
  4. Calculate the percentage acceptable: 3 ÷ 5 = 0.60, so 60%.
Answer: 2 points (PDOP 4.2 and 5.1) must be flagged for re-observation. 3 of the 5 observations (60%) meet the quality threshold.
3. A CSV exported from the data collector lists Easting = 1,523,847.23 ft and Northing = 412,339.88 ft for Point 12. When imported into ArcGIS Pro, the attribute table shows X = 1,523,847.23 and Y = 412,339.88, but the point plots thousands of feet from the survey area. What is the most likely cause, and how do you confirm it?
  1. Recognize that CSV files carry no projection metadata; the coordinate system must be assigned manually during import.
  2. Check the coordinate system assigned to the XY event layer in ArcGIS Pro (right-click layer → Properties → Source tab). Compare it to the coordinate system recorded in the field notebook.
  3. If they do not match (for example, a UTM zone was assigned instead of the correct State Plane zone), remove the layer, re-run Make XY Event Layer, and assign the correct coordinate system.
  4. After reassignment, verify that the point plots within the expected survey area by comparing to a basemap or known control point.
Answer: The most likely cause is an incorrect coordinate system assignment during import. The numeric coordinate values are correct but are being interpreted in the wrong projection, causing a large spatial offset. Reassigning the correct coordinate system resolves the issue.
4. A project requires a minimum of 180 epochs per static point at a 1-second logging interval. A point in the attribute table shows an observation duration of 2 minutes and 45 seconds. Does it meet the minimum? Show your work.
  1. Convert observation duration to seconds: 2 minutes × 60 seconds/minute = 120 seconds; 120 + 45 = 165 seconds total.
  2. At a 1-second logging interval, epochs recorded = 165 epochs.
  3. Compare to the minimum: 165 < 180.
Answer: No. The point has only 165 epochs, which is 15 epochs short of the 180-epoch minimum. It must be flagged and re-observed for at least 15 additional seconds under the same logging interval.

The math in this lesson1

Learners compute 2 missing of 47 expected points as about 4.3% of the day's data.
7.RP.3
Brush up in the math halls at newSchoolWorks.com:
In class: Data transfer exercise: students connect data collectors to lab computers via USB or wireless sync and use the manufacturer's office software to transfer the day's field file; they document file names, point counts, and any transfer errors. · Export and format conversion: students export the data as a CSV (easting, northing, elevation, description) and as a LandXML or job file, then import the CSV into ArcGIS Pro as an XY event layer and verify coordinate system assignment matches the field configuration. · QC review: students use ArcGIS Pro attribute table and a printout of the field notebook to check that point codes, observation counts, and PDOP values are consistent; they flag any point with PDOP > 4 or solution type 'float,' prepare a written QC summary listing flagged points and recommended remediation.
Materials: Lab computers with manufacturer office software and ArcGIS Pro, USB cables, student field data from Lesson 7, printed QC checklist, LandXML schema reference
Check: Instructor reviews exported CSV and ArcGIS Pro project file; all points must be present with correct coordinate system, at least two file formats produced, and a written QC summary identifying any flagged observations; passing standard: zero missing points and correctly assigned coordinate system.

Practice check8

Answer each question, then check it. Nothing is recorded; this is your own practice.

GNSS field operations and data management
1. Before transferring a job file from a data collector to a workstation, what is the most important first step?
Surveying file formats and data exchange
2. Which file format is specifically designed for civil engineering and surveying data and can store coordinate system metadata, points, and surfaces in a single schema-validated file?
Esri ArcGIS Pro – data import and coordinate systems
3. When importing a CSV of surveyed points into ArcGIS Pro using the Make XY Event Layer tool, which action is critical to ensure the points plot in the correct geographic location?
GNSS quality control
4. A point in your GNSS data has a PDOP of 4.7 and a solution type of 'fixed.' According to a project QC threshold of PDOP > 4, how should this point be treated?
GNSS quality control
5. What does a 'float' solution type indicate about a GNSS observation?
GIS data management and quality control
6. After transferring data, your field notebook shows 62 points collected. The office software point list shows 62 points, but when you export to CSV and import into ArcGIS Pro, only 60 points appear. What is the most likely explanation?
Surveying professional practice and documentation
7. Which of the following items is NOT required in a professional written QC summary for a GNSS data transfer?
GNSS field operations and quality control
8. A static GNSS point was logged at a 1-second epoch interval for 3 minutes and 10 seconds. The project minimum is 200 epochs. Does this observation meet the requirement?
Record this lesson on my transcript. Sign in with your key and enrollment email to record lessons (enroll free if you have no key). This page stays open to read and practise.
← Previous lessonProgram planNext lesson →