Changes between Version 31 and Version 32 of Procedures/DeliveryCreation/LIDAR


Ignore:
Timestamp:
Nov 6, 2014 12:04:21 PM (5 years ago)
Author:
dap
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Procedures/DeliveryCreation/LIDAR

    v31 v32  
    4848   * REMEMBER THAT THESE LAS FILES SHOULD HAVE BEEN QC'ED AND CLASSIFIED FOR NOISY POINTS
    4949   * Rename the files in the convention "LDR-PPPP_PP-yyyydddfnn.LAS" (details in readme).
    50    * run las2txt.sh <delivery/flightlines/las1.0> <delivery/flightlines/ascii> '''Note, it is important to use las2txt.sh (as opposed to the las2txt executable) as las2txt does not output in the correct format.'''
     50   * run las2txt.sh <delivery/flightlines/las1.0> <delivery/flightlines/ascii> '''Note, it is important to ensure that the correct options are used with this. Otherwise it will output the wrong format.'''
    5151   * OR run `las2txt --parse txyzicrna <lidarfilename> <outputfilename>` for each file, outputting to the ascii_laser directory (may not work with LAS 1.1). 
    5252 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