Changes between Version 2 and Version 3 of Sensors/LeicaLIDAR/MarksNotes

Timestamp:

Aug 22, 2008, 5:11:12 PM (16 years ago)

Author:

mark1

Comment:

--

Sensors/LeicaLIDAR/MarksNotes

@@ -234 +234 @@
    * These are the points which can be used as a model (?)
 
-
-
-
-
-
-
-
-Figure 1. Cross section of opposing flight lines (red and black) with a roll (boresight) error.  Small difference between flight lines at nadir, larger error at swath edges.
-Figure 2. Plan view of opposing flight lines. A pitch error will result in a (sloped) feature being moved along track, this is easy to spot when comparing cross sections of the opposing flight lines. The pitch slope error causes a “smile effect” to the data.
-
-Figure 3. Check for torsion corrections on a cross flight. Line 1 (black) will see no effect at points B and D, whereas line 2 (red) will show full effect at these points.  The opposite is true for points A and C.  Using TerraScan to view cross sections at these 4 points should highlight if there is a torsion correction to be made.
-
-
 == Summary of work required ==
 
@@ -277 +264 @@
    * ALS estimate 2-3hrs
    * QCing 2-3hrs
+
+
+
+=== Figure captions ===
+
+Figure 1. Cross section of opposing flight lines (red and black) with a roll (boresight) error.  Small difference between flight lines at nadir, larger error at swath edges.
+
+Figure 2. Plan view of opposing flight lines. A pitch error will result in a (sloped) feature being moved along track, this is easy to spot when comparing cross sections of the opposing flight lines. The pitch slope error causes a “smile effect” to the data.
+
+Figure 3. Check for torsion corrections on a cross flight. Line 1 (black) will see no effect at points B and D, whereas line 2 (red) will show full effect at these points.  The opposite is true for points A and C.  Using TerraScan to view cross sections at these 4 points should highlight if there is a torsion correction to be made.
+