Skip to content
Lab Overview
This lab focused on understanding geographic datums and how improper datum handling can severely impact UAS datasets. Instead of working with a clean dataset, the lab intentionally used a poorly documented ground control point file to replicate real-world issues that can occur when metadata is missing or incorrect.
The goal was to identify datum-related problems, correctly import XYZ coordinate data, diagnose vertical datum errors, and apply corrections using authoritative geodetic resources. This lab tied directly into lecture topics on datums, coordinate systems, and accuracy in UAS mapping workflows.
Working with Poor Metadata and XYZ Data
The lab began by examining a CSV file containing ground control points with minimal information provided. The file included only basic fields for name, X, Y, and Z, with no supporting metadata. This required interpreting the coordinate values and identifying the coordinate system rather than relying on documentation.
The lack of metadata highlighted why guessing projections or datums is dangerous in GIS. While the horizontal coordinates were eventually identified as latitude and longitude in WGS84, several issues remained unresolved, particularly with vertical values.
Importing XY Data Incorrectly and Diagnosing Errors
XYZ data was first imported incorrectly into ArcGIS Pro using a file with flipped X and Y fields. This caused the points to appear in Antarctica, demonstrating how easily coordinate field order errors can break a dataset.
After removing the incorrect data, the file with the proper YXZ ordering was imported. This placed the points in the correct geographic location in western Wisconsin. At this stage, the horizontal positioning appeared correct, but additional issues were discovered related to point distribution and elevation values.
Evaluating GCP Placement and Vertical Values
Once the GCPs were correctly placed, their spatial distribution was evaluated. The points were clustered toward the edges of the site with limited control in the center, which is not ideal for high-accuracy UAS work.
The Z values of each control point were then reviewed and compared against known terrain elevation. Significant differences were observed when comparing survey values to elevation data viewed in ArcGIS Earth. These discrepancies pointed to a vertical datum mismatch rather than simple measurement error.
Identifying and Correcting the Datum Issue
To resolve the vertical datum issue, the National Geodetic Survey Data Explorer was used to locate a nearby geodetic control point. By reviewing the datasheet, the difference between ellipsoid height and orthometric height was identified.
The dataset was found to be referenced to an ellipsoid rather than NAVD88 orthometric height. Using the appropriate geoid model, vertical offsets were applied to the GCP Z values. After adjustment, the corrected values aligned much more closely with terrain elevations, confirming the datum issue was the root cause of the error.
Creating the Final Map Layout
As a final deliverable, a cartographically correct map was created showing the GCP distribution in western Wisconsin. The layout includes labeled control points, coordinate values, and a latitude and longitude reference grid. The map also clearly communicates the vertical datum used, reinforcing the importance of transparency when working with elevation data.
All required cartographic elements were included, such as a north arrow, scale bar, reference grid, and watermark identifying the map author.
Key Takeaway
This lab demonstrated how critical proper datum handling is in UAS and GIS workflows. Even when horizontal positioning appears correct, vertical datum errors can introduce significant inaccuracies. By working through a flawed dataset, this lab reinforced the importance of metadata, correct XYZ formatting, and verifying datums before using ground control data in any UAS mapping project.
Want to print your doc?
This is not the way.
This is not the way.
Try clicking the ··· in the right corner or using a keyboard shortcut (
CtrlP
) instead.