Changes between Version 11 and Version 12 of Processing/laguserguide

Timestamp:

May 24, 2012, 4:05:05 PM (12 years ago)

Author:

jaho

Comment:

--

Processing/laguserguide

@@ -23 +23 @@
     These two values control the construction of the quadtree and directly affect both loading times and rendering speed of the data. Each leaf (point bucket) in the quadtree can have a number of sub-buckets which store points to display at different zoom level. For example when viewing a whole flightline in the overview window there is no need to render every single point or store all the points in memory at once. Thus sub-buckets containing every n-th point are used instead. \\
     The Resolution Depth determines the number of sub-buckets for each bucket and Resolution Base determines the number of points at each level by specifying the interval between included points based on the formula of Resolution Base^(Level - 1)^. For example the default values of 5 and 4 create 4 sub-buckets per bucket: one containing every point (5^0^), second containing every 5th point (5^1^), third containing every 25th point (5^2^) and fourth with every 125th point (5^3^). \\
-    Adjusting these values should be done carefully and based on the density, volume and coverage of the data. Generally increasing the Resolution Base and decreasing Resolution Depth will result in faster loading and quadtree operations (eg. classifying), but less smooth rendering. Creating more and denser sub-buckets may improve the interaction with the GUI but at the cost of slower quadtree and bigger memory footprint.
+    Adjusting these values should be done carefully and based on the density, volume and coverage of the data. Generally increasing the Resolution Base and decreasing Resolution Depth will result in faster loading and quadtree operations (eg. classifying), but less smooth rendering. Creating more and denser sub-buckets may improve the interaction with the GUI but at the cost of slower quadtree.
     For example for big flightlines that cover a vast area (like very long but thin lines, eg. 2011 29x London flights) it may be beneficial to create more sparse sub-buckets by increasing the Resolution Base. At the same time you can try to speed up loading times by decreasing the number of resolution levels, so values like 6 4 and 10 3 are worth testing.
 * **Points to hold in cache**
@@ -34 +34 @@
     Pressing middle mouse button (scroll wheel) can be used for moving the camera at any time also with profile/fence/ruler enabled and can be used instead of zooming in and out to change the view.
 * **Keyboard Shortcuts**
-    The WASD cluster can be used for moving the camera (A - left, D - right, W - up, S down). The move speed can be changed in Advanced Options window. Additionaly: \\
+    The **WASD** cluster can be used for moving the camera (A - left, D - right, W - up, S - down). The move speed can be changed in Advanced Options window. Additionaly: \\
 
-    B, G - zooms in and out \\
-    X - toggles the profile \\
-    F - toggles the fence \\
-    T - switches between orthogonal and slanted \\
-    C - classifies selected points \\
-    Z - refresh \\
-    SPACE - loads currently selected profile into profile window \\
+    **B**, **G** - zooms in and out \\
+    **X** - toggles the profile \\
+    **F** - toggles the fence \\
+    **T** - switches between orthogonal and slanted \\
+    **C** - classifies selected points \\
+    **Z** - refresh \\
+    **SPACE** - loads currently selected profile into profile window \\
+    **1** through **7** - quickly selects classification level in profile window \\
 
 [[Image(advopts.png,align=center)]]