Changes between Version 17 and Version 18 of Procedures/DeliveryCreation/LIDAR

Timestamp:

Nov 28, 2012, 4:14:03 PM (12 years ago)

Author:

mark1

Comment:

--

Procedures/DeliveryCreation/LIDAR

@@ -51 +51 @@
    * run las2txt.sh <delivery/flightlines/las1.0> <delivery/flightlines/ascii>
    * OR run `las2txt --parse txyzicrna <lidarfilename> <outputfilename>` for each file, outputting to the ascii_laser directory (may not work with LAS 1.1).  
- 1. You need to create a DEM from the lidar data to include with the delivery. Use [wiki:Processing/CreateTifs#lidar_intensity.sh lidar_intensity.sh] and put the output file in a directory named 'dem'. Noisy points (those with classification 7) should not be included in the DEM so remember to specify the -C option. You should also create a second DEM that is suitable for use in aplcor. Use either convert_uk_dem.sh or convert_nonuk_dem.sh depending on where your project is located. This DEM should be name ***_wgs84_latlong.dem
+ 1. You need to create a DEM from the lidar data to include with the delivery. Use lidar_aster_dem.sh and put the output file in a directory named 'dem'. Noisy points (those with classification 7) should not be included in the DEM so remember to specify the -C option. You should also create a second DEM that is suitable for use in aplcor. Use either convert_uk_dem.sh or convert_nonuk_dem.sh depending on where your project is located. This DEM should be name ***_wgs84_latlong.dem
  1. Include a pdf version of the flight logsheet with the delivery  
  1. Make sure correct up to date data quality report (pdf version) is included in docs directory