Changes between Version 23 and Version 24 of Sensors/LeicaLIDAR/MikesNotes

Timestamp:

Sep 5, 2008, 3:45:35 PM (16 years ago)

Author:

mggr

Comment:

--

Sensors/LeicaLIDAR/MikesNotes

@@ -1 @@
-== Mirror torsion error correction ==
-
-This shouldn't need to be done with newer LIDARs, but included here in case.  Leica suggests checking for torsion errors if there seem to be problems in the boresight calibration and reporting to them if found.
-
-Visible sign of torsion error is a smile effect.
-
-Detect torsion by:
- * choose highest altitude pair of crossing lines
- * pick a point at nadir on one swath and at the edge on the other
-   * torsion will be at max for the edge swath and at 0 for the nadir swath
- * take cross sections to see if there is any consistent vertical difference
+
 
 == Ground classification ==
@@ -362 +352 @@
    * A road running up a hill is good for pitch (vertical change in surface easily found in the image).  These are good for measuring along-track shifts.
    * Slopes with peaks (house rooftops are ideal) with the peak cutting across the line of flight ( --->  /\ ).  Again good for measuring along-track shifts.
+
+=== Mirror torsion error correction ===
+
+This shouldn't need to be done with newer LIDARs, but included here in case.  Leica suggests checking for torsion errors if there seem to be problems in the boresight calibration and reporting to them if found.
+
+Visible sign of torsion error is a smile effect.
+
+Detect torsion by:
+ * choose highest altitude pair of crossing lines
+ * pick a point at nadir on one swath and at the edge on the other
+   * torsion will be at max for the edge swath and at 0 for the nadir swath
+ * take cross sections to see if there is any consistent vertical difference
 
 == Automatic method (using Attune) ==
@@ -409 +411 @@
    * Some outside the core intersection area
    * Try to include some on slopes(?)
+
+
 --------------
 = Random snippets =