Changes between Version 55 and Version 56 of Processing/Lidarqcprocedure

Timestamp:

Nov 28, 2012, 4:10:27 PM (12 years ago)

Author:

mark1

Comment:

--

Processing/Lidarqcprocedure

@@ -6 +6 @@
 
 ==== Horizontal ====
-The first thing to do here is to load up all lines into a viewer (or if runs out of memory load them up in pairs) and see how well they overlap in the horizontal plane. Use Lag with "Brightness by Intensity". If you have trouble making out the details in the lidar viewer then you can make tiffs of the flightlines by converting the las files to ascii with las2txt.sh then using these with make_lidardem_or_intensity.sh. [[BR]]
+The first thing to do here is to load up all lines into a viewer (or if runs out of memory load them up in pairs) and see how well they overlap in the horizontal plane. Use Lag with "Brightness by Intensity". If you have trouble making out the details in the lidar viewer then you can make tiffs of the flightlines with lidar_intensity.sh. [[BR]]
 Check along features that cross between flight lines, for example, roads/field boundaries/hedgerows do they continue unbroken or are they offset between flight lines. Also, compare against the vectors (if available) for any gross offsets.
 
@@ -23 +23 @@
 If not done in the above step then the flight lines must be checked against vectors (if available). 
 
-To check in Envi: Create ascii versions of the las files with las2txt.sh <las_dir> --parse txyzicrna (may not work with LAS 1.1) and then make an intensity mosaic with make_lidardem_or_intensity.sh [wiki:Processing/CreateTifs Instructions Here]
+To check in Envi: Create ascii versions of the las files with las2txt.sh <las_dir> --parse txyzicrna (may not work with LAS 1.1) and then make an intensity mosaic with lidar_intensity.sh [wiki:Processing/CreateTifs#lidar_intensity.sh Instructions Here]
 
 To check in Terrascan: You need to convert the .shp vectors into .dgn. Instructions [wiki:Processing/shapesintoterrascan here]