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


Ignore:
Timestamp:
Nov 28, 2012 4:13:01 PM (6 years ago)
Author:
mark1
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Procedures/DeliveryCreation/LIDAR

    v16 v17  
    2626=== Semi-scripted method ===
    2727 1. Create the delivery directory by running `make_lidar_delivery.py` in the main directory. 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 [wiki:Processing/CreateTifs make_lidardem_or_intensity.sh]. [[BR]] You will also need to make a lat long version of the dem (for use with aplcorr) using convert_uk_dem.sh or convert_nonuk_dem.sh appropriately.
     28 1. If you did not create the DEM and screenshots using the above script (-m option) then create them manually using [wiki:Processing/CreateTifs#lidar_intensity.sh lidar_intensity.sh]. [[BR]] You will also need to make a lat long version of the dem (for use with aplcorr) using convert_uk_dem.sh or convert_nonuk_dem.sh appropriately.
    2929 1. Generate the readme file.
    3030  1. Create a config file for the read me using the generate_readme_config.py script.
     
    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 [wiki:Processing/CreateTifs 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. 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 [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
    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
    56  1. Create full resolution JPGs of mosaic of all the LIDAR lines by intensity, a separate one of the intensity with vectors overlaid (if vectors are available) and one of the dem and put in screenshot directory (with [wiki:Processing/CreateTifs make_lidardem_or_intensity.sh]).
     56 1. Create full resolution JPGs of mosaic of all the LIDAR lines by intensity, a separate one of the intensity with vectors overlaid (if vectors are available) and one of the dem and put in screenshot directory (with [wiki:Processing/CreateTifs#lidar_intensity.sh lidar_intensity.sh]).
    5757 1. Generate the readme using as per point 3 above
    5858