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


Ignore:
Timestamp:
Jan 25, 2013 2:46:36 PM (6 years ago)
Author:
mark1
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Procedures/DeliveryCreation/LIDAR

    v18 v19  
    5151   * run las2txt.sh <delivery/flightlines/las1.0> <delivery/flightlines/ascii>
    5252   * OR run `las2txt --parse txyzicrna <lidarfilename> <outputfilename>` for each file, outputting to the ascii_laser directory (may not work with LAS 1.1). 
    53  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
     53 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 (this is the default behaviour). 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, or run the script again specifying the different output projection. This DEM should be name ***_wgs84_latlong.dem
    5454 1. Include a pdf version of the flight logsheet with the delivery 
    5555 1. Make sure correct up to date data quality report (pdf version) is included in docs directory