Changes between Version 8 and Version 9 of Procedures/DeliveryCreation/LIDAR


Ignore:
Timestamp:
Jul 1, 2011 11:07:26 AM (8 years ago)
Author:
emca
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Procedures/DeliveryCreation/LIDAR

    v8 v9  
    44
    55== What should be included ==
    6  1. ASCII LIDAR pointcloud data 
     6 1. ASCII LIDAR point cloud data 
     7 1. LAS point cloud data
    78 1. pdf version of flight logsheet
    89 1. readme file describing the data set + copyright notice
     
    2425
    2526=== Semi-scripted method ===
    26  1. Create the delivery directory using `make_lidar_delivery.sh <full path to main project dir> <year> <proj-code> <julian_day>`. The .LAS files that have been QC'ed and classified for noisy points should be in the main project directory under leica/proc_laser/ for this script. Check it's created everything correctly. If it fails, create the directory manually as per below.
    27  1. If it is a UK project then dem and screenshots will be created. A screenshot of the intensity image with vectors overlaid will be created if there are vectors in ~arsf/vectors/from_os/PROJ_CODE. If the project is outside the UK then this script will not generate the dem or screenshots so these need to be created manually using make_lidardem_or_intensity.sh.
     27 1. Create the delivery directory using `make_lidar_delivery.py` (run `make_lidar_delivery -h` for details). The .LAS files that have been QC'ed and classified for noisy points should be in processing/als50/las-classified. Check it's created everything correctly. If it fails, create the directory manually as per below.
     28 1. If you did not create the DEM and screenshots using the above script (-m option) then create them manually using make_lidardem_or_intensity.sh.
    2829 1. Generate the readme file.
    2930  1. Create a config file for the read me using the generate_readme_config.py script. Use a command such as `generate_readme_config.py -d <delivery_directory> -r lidar`
     
    4344
    4445=== Manual Method ===
    45  1. Copy the template directory over to the project directory. Template directory at `~arsf/arsf_data/2009/delivery/lidar/template`
    46  1. Convert the LAS binary files into ASCII files, ensuring to output all the appropriate information
    47    * run las2txt.sh <lasdirectory>
     46 1. Copy the template directory over to the project directory. Template directory at `~arsf/arsf_data/2011/delivery/lidar/template`
     47 1. Move the processed data to the delivery directory
     48   * Move the LAS binary files into delivery/flightlines/las1.0
     49   * REMEMBER THAT THESE LAS FILES SHOULD HAVE BEEN QC'ED AND CLASSIFIED FOR NOISY POINTS
     50   * Rename the files in the convention "LDR-PPPP_PP-yyyydddfnn.txt" (details in readme).
     51   * run las2txt.sh <delivery/flightlines/las1.0> <delivery/flightlines/ascii>
    4852   * OR run `las2txt --parse txyzicrna <lidarfilename> <outputfilename>` for each file, outputting to the ascii_laser directory (may not work with LAS 1.1). 
    49    * REMEMBER THAT THESE LAS FILES SHOULD HAVE BEEN QC'ED AND CLASSIFIED FOR NOISY POINTS
    50    * If not already done, rename the files in the convention "LDR-PPPP_PP-yyyydddfnn.txt" (details in readme).
    5153 1. You need to create a DEM from the lidar data to include with the delivery. Use make_lidardem_or_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.
    5254 1. Include a pdf version of the flight logsheet with the delivery