LIDAR and TDS in GIS: Evaluating
LIDAR Data Accuracy Using Ground-Surface Total Station Surveys,
Jason S. Alexander
Graduate Student
Department of Aquatic,
Watershed, and Earth Resources
Introduction and Background
Narrowing
and simplification of channel form on the
The
Channel
form in the experimental reaches is monitored through repeat surveys of channel
cross-sections and sandbar topography using a total station laser survey
instrument (TDS) coupled with sonar data (for subaqueus topography below
wadeable depths). Measures of change
include channel top width at powerplant capacity, mean channel depth at
baseflow (23 m3/second) and powerplant capacity, sand area above
baseflow and powerplant capacity, and sandbar volume above baseflow and powerplant
capacity (Figures 3, 4, and 5).
Volumetric analysis of total alluvial sediments above baseflow or
powerplant capacity would be a robust measure of sedimentation patterns (net
deposition = narrowing, net scour = restoration) in the experimental reaches,
however there is both physical and logistical difficulty in obtaining a
relevant number of survey points efficiently for an entire reach.
LIght
Detection And Ranging (LIDAR) surveys allow for rapid
acquisition of millions of topographic survey points including ground points below
forest canopy. The potential for the
evaluation of long-term sedimentation patterns in
Method of
Evaluation
This
study compares two survey datasets of the
Step 1:
The
link between the TDS data and the LIDAR data is the presence of LIDAR ground targets
installed in some of the experimental reaches (Figure 6). Each ground target consists of a 1.5 x 1.5 m2
ground cloth with a precisely surveyed monument pin at the center. Ground targets were located and surveyed into
each TDS control network. Database files
for the TDS control networks were then brought into ArcGIS as XY events. Using the editor, the XY events were
translated by moving the point group as a whole, using the LIDAR control point
to “lock in” the ground targets visible on .15 meter resolution aerial
orthophotographs (taken during the LIDAR flight) (Figure 7). The LIDAR control point was placed on the
center of the “X” of the ground target while zoomed into the four center pixels
of the ground target (Figure 8). Using
the LIDAR control point as the center, the “rotate” tool was used from the
ArcGIS editor to rotate the control points until the “waters edge” points
matched up with the waters edge visible in the aerial photographs (Figures 9
and 10). Using the waters edge as a
guide for the rotation was reasonable because the discharge on April 1, 2005
was within 5m3/ second of the May 13-15th TDS survey
(stage changes of less than 10 cm). The
control points were then cross-checked with existing maps to ensure the
cross-section endpoints were in their proper positions. After the TDS survey
control points were translated and rotated into place, an empty point feature
class was added. This feature class was
then edited and points were added by snapping to the TDS XY event themes,
creating a TDS control file in UTM Zone 12, NAD 83.
Step 2:
Elevations
of the TDS survey data were resolved for comparison with profiles from the
LIDAR TIN. Elevations of each LIDAR ground
target pin were obtained from Rocky Mountain Surveys, of Vernal,
Step 3:
A
point feature class was created within the LIDAR feature dataset from the LIDAR
survey database. Using ArcGIS 3D
analyst, a TIN of each of the experimental reaches was created from the LIDAR
point feature dataset (reaches without ground targets were excluded) (Figures
11 and 12). Contract specifications for
the LIDAR survey demanded an RMSE of no more than .15 meters in the vertical
and .5 meters in the horizontal. RMSE
values for the LIDAR data were reported as .10 meters in the vertical and .21
meters in the horizontal.
Step 4:
Creation
of cross section profiles in ArcGIS with the standard tools presented some difficulties. The first step in this process is to add an
empty line feature class. This feature
class is then edited and new cross section lines are drawn between cross section
endpoints. After all cross section lines
are drawn between points, the feature class is converted to 3D using the
“convert features to 3D” tool in 3D analyst.
Profiles can then be extracted but points from the lines CANNOT be
exported with the standard tools. A
search of the ESRI support center produced many solutions, mainly Visual Basic
codes. However, a GUI module, the EZ
Profiler, written by Min-Lang Huang, was found to be the most powerful and
user-friendly. The EZ Profiler is an
independent extension written for ArcGIS 9.0 and does not need 3D
Analyst or Spatial Analyst to perform.
EZ Profiler V8.3 can be downloaded at http://arcscripts.esri.com/details.asp?dbid=13688. All that
is needed for the creation of a cross section profile with EZ Profiler is a TIN
surface. EZ profiler provides many
options for creating profiles (Figure 13): (A) the user can draw a profile
line, although this does not allow snapping (B) the user can get a profile from
an existing polyline (C) the user can rapidly obtain multiple profiles from
several polylines and (D) the user can obtain a profile from a 3D
polyline. Once an option for a profile
is chosen and executed, a shapefile and associated attribute table are created
and added to the map (Figure 14). The attribute table for each profile can then
be exported to Microsoft Excel with the touch of a button! The profile attributes include a unique line
identifier, X, Y, and Z coordinates, and distance from the starting point along
the profile (Figure 15). No reduction of the exported data was
required for comparison with the resolved TDS cross sections! Each of the profiles extracted for this study
were created from line feature classes converted to 3D polylines.
Step 5:
Three
parameters were evaluated for each profile comparison: (A) elevation (B) water
surface variation and (3) profile shape.
For each cross section overlay, the total area between cross sections
was calculated in WinXSPRO (Figure 16).
Attributes of each profile created in EZ Profiler were exported to Excel
and formatted for analysis in WinXSPRO.
WinXSPRO is free software developed by the USDS Forest Service,
Davg = (A1 + A2 + Ai….) / (L1 +
L2 + Li….)
Where:
Davg = total average elevation
difference between LIDAR and TDS profiles
Ai = total
area of i increments
Li = total
horizontal length of i increments
Water surface variation
was calculated by simply taking the difference between the maximum and minimum
elevation of water surface profile points.
In order to minimize potential inclusion of ground surface points, water
surface datasets did not include waters edge data points. Cross section shape was qualitatively
evaluated by visual comparison of profile plots in Excel.
Results and Discussion – Elevation
Differences Between LIDAR and TDS Data:
Magnitudes
of elevation differences were generally not consistent between reaches or
between profiles (Figure 17). Average elevation
differences varied from a low of 10cm to a high of 28cm, consistent with or
greater than the error reported by the LIDAR contractor (~10cm vertical
error). Lower Mile 233 was the only
reach to show consistent variation in both profiles. The error reported for the LIDAR control
targets (surveyed using differentially corrected GPS) varied from as large as
35.0cm in Winnies reach to as low as 4.0cm in the lower Mile 233 reach. The combined LIDAR and GPS elevational
reported error is equivalent or, in some cases, greater than the elevational
error found in this study. Ironically,
the reach with the least vertical error in the GPS ground control measurement,
Lower Mile 233, produced the largest error in elevation between surveys. Nevertheless, errors found within this study
are nested closely within the error reported for both the LIDAR and GPS ground
control data.
Consistency
of error within a reach would suggest error in translation, rotation, or
resolution of TDS elevations consistent between cross sections. For example, an erroneous rotation or
translation would create LIDAR profiles oblique to the TDS profiles in a
generally uniform pattern (i.e. Lower Mile 233). Inconsistent error within a reach would
suggest error within the LIDAR data because discrete LIDAR survey points each
have inherent error independent of the surrounding points. For example, a TIN created with LIDAR points,
each with inconsistent error, should produce profiles whose topography is both
above and below that of the TDS survey (i.e. Upper Winnies and Upper
Mile 233).
For
this study, error in translation, rotation and elevation was minimized though
the identification of significant inconsistencies in shape or magnitude of
elevation between profiles. These inconsistencies
were checked, in some cases many times over, by complete repetition of the
analysis. Errors in TDS data were found,
resolved and the analysis was performed no less than a third time to minimize
humanistic error wherever possible.
While the error within this study was found to be consistent with the
reported error, the magnitude of elevation differences presents significant
challenges to data interchange. For
example, a 30.0 cm average elevational difference between the TDS and LIDAR
data would suggest significant scour or deposition in environments such
as river left of Lower Mile 233 where the combined eddy bar and beach are
nearly 40 meters wide (Figure 19). While
local stage discharge relationships allow for us to infer what could be
changing and at what elevation, significant and non-uniform (i.e. left and
right bank) alteration of the cross sections would be necessary to “fit” the
data. This makes TDS survey data, a
necessary component to couple with any LIDAR floodplain analysis.
Results and Discussion – Water Surface Variation:
Water
surface elevation for LIDAR data varied widely and inconsistently within and
between reaches (Figure 18). The lowest
magnitude variation water surface variation within the LIDAR data was 23.0cm. Maximum water surface variation for LIDAR was
71.0cm. If the interpreted water’s edge
were incorporated into the analysis, variance of LIDAR water surface elevation
would have exceeded 1 meter in some cases.
TDS data was found to have a maximum water surface variation of 4.0cm
with the rest of the cross sections showing no more than 2.0cm of variation
(some of this variation may be due to ramping discharges from Flaming Gorge).
Error
in water surface elevation for LIDAR data was assumed to be related to two
factors (1) surface turbulence due to wind and (2) surface turbulence due to
wave pulsation. High resolution aerial
photographs taken during the LIDAR survey show significant water surface
disturbance (in normally placid waters) due to wind. TIN surfaces in all reaches were also
generally more horizontal the farther downstream of riffles or
constrictions. In all reaches for this
study, profiles were in expansion waters or ponded backwaters downstream of
riffles and constrictions. In these
locations wave pulsation is significant and contributes to significant surface
disturbance. The significant error
associated with the LIDAR water surface elevation data makes the usefulness of
the data limited. For example, a stage
change of .5 meters at Lower Mile 233 would result in a decrease or increase of
63 m3/s, a significant difference considering the typical annual
peak discharge is 125 m3/s.
Results and Discussion – Cross Section Shape:
LIDAR data generally produced
cross section shapes that closely followed those of the TDS survey. In some case, the higher resolution LIDAR
data produced superior detail of shape locally.
However, large differences in shape were encountered near overhanging
canyon walls where LIDAR scanning could not reach and steep cutbanks
where sharp edges were rounded or sloped (Figures 19 and 20). While the LIDAR profile shape typically
closely followed that of the TDS survey data, some bank features represent
deposits from specific discharges and may provide important insights for scour
and depositional patterns (i.e. from a bypass flood or local deposition around
riparian vegetation).
Conclusions:
Improvements:
While local GPS ground
control targets provided elevational control on TDS survey data, the presence
of only one ground target in any given reach requires that TDS data must be
rotated by eye around the ground control target. While this may be done carefully using waters
edge and topographic features, some error must remain and therefore some
measure of obliqueness surely exists between profiles from TDS and LIDAR. Quality control could be improved through the
installation of a second ground control station in each reach,
eliminating the need to rotate and translate TDS data.
References Cited:
Publication:
Grams, P.E., Schmidt, J.C., In press. Equilibrium or indeterminate?
Where sediment budgets fail: Sediment mass balance and adjustment of channel
form,
Schmidt, J.C., Rubin, D.M., 1995. Regulated
streamflow, fine-grained deposits, and effective discharge in canyons with
abundant debris fans, in Natural and
anthropogenic influences in fluvial geomorphology: AGU Geophysical Monograph.
P. 177-195. American Geophysical
Web
References (also referenced above):
EZ Profiler, written and published by Min Lang Huang. Information and download at http://arcscripts.esri.com/details.asp?dbid=13688
WinXSPRO, developed and published by the United States
Department of Agriculture, U.S. Forest Service,