Changes between Version 39 and Version 40 of Procedures/DeliveryCreation/LIDAR
- Timestamp:
- Jun 6, 2017, 2:09:53 PM (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Procedures/DeliveryCreation/LIDAR
v39 v40 1 = L IDAR data delivery =1 = LiDAR data delivery = 2 2 3 3 Once the data has been processed, it needs to be put into a delivery directory. This is the final file structure in which it will be sent to the customer. … … 25 25 === Semi-scripted method === 26 26 1. See the guide at [wiki:Procedures/DeliveryCreation/pythonlibrary delivery library] 27 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.27 1. If you did not create the DEM and screenshots using the above script then create them manually using [wiki:/Processing/CreateImagePy createimage.py], [wiki:/Help/LeicaLidarDems las_to_dsm.py and create_dem_from_lidar.py] 28 28 1. Generate the readme file. 29 29 1. Create a config file for the read me using the `generate_readme_config.py` script, using the -d option to specify the delivery directory and the -r option to specify the type of config file to generate. … … 33 33 * line_numbering should contain a space separated list of line names linking the logsheet to the processed files. 34 34 * las_files should contain the path to the processed LAS file in order to extract the per flightline statistics 35 * elevation_difference should contain a list of the elevation differences between overlapping flightlines. Enter the lines numbers and the difference in cm followed by a semicolon e.g 001 002 5; 002 003 4.5; etc. From 2017 onwards these numbers should be generated using [wiki:/Procedures/DeliveryCreation/LiDARElevationDiffs `calculate_lidar_elevation_diffs.py`] .35 * elevation_difference should contain a list of the elevation differences between overlapping flightlines. Enter the lines numbers and the difference in cm followed by a semicolon e.g 001 002 5; 002 003 4.5; etc. From 2017 onwards these numbers should be generated using [wiki:/Procedures/DeliveryCreation/LiDARElevationDiffs `calculate_lidar_elevation_diffs.py`] 36 36 * All "compulsory" items should contain data 37 37 1. Create a TeX file. Use the script `create_latex_lidar_readme.py -f <config filename>` '''Use the -w option for creating a full waveform readme''' … … 45 45 1. If you did not create a CSV file with the original names of LAS files versus new names you can create using the above script, you can also create it before renaming files using lidar_naming_csv.py 46 46 1. Move the processed data to the delivery directory 47 * Move the LAS binary files into delivery/flightlines/las1. 047 * Move the LAS binary files into delivery/flightlines/las1.2 48 48 * REMEMBER THAT THESE LAS FILES SHOULD HAVE BEEN QC'ED AND CLASSIFIED FOR NOISY POINTS 49 49 * Rename the files in the convention "LDR-PPPP_PP-yyyydddfnn.LAS" (details in readme, you should have created a CSV file with the new names in previous steps so rename accordingly ). 50 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.''' 51 * OR run `las2txt --parse txyzicrna <lidarfilename> <outputfilename>` for each file, outputting to the ascii_laser directory (may not work with LAS 1.1).52 1. You need to create a DEM from the lidar data to include with the delivery. For more details see the page on [wiki:/Help/LeicaLidarDems 'Creating a DEM from point clouds' ]51 * OR run `las2txt --parse txyzicrna <lidarfilename> <outputfilename>` for each file, outputting to the ascii_laser directory. 52 1. You need to create a DEM from the lidar data to include with the delivery. For more details see the page on [wiki:/Help/LeicaLidarDems 'Creating a DEM from point clouds' ]. 53 53 1. Include a PDF version of the flight logsheet with the delivery 54 54 1. Make sure correct up to date data quality report (pdf version) is included in docs directory 55 1. Create full resolution JPEGs 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]).56 1. Generate the readme using as per point 3above55 1. Create full resolution JPEGs 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/CreateImagePy createimage.py]) 56 1. Generate the readme as per semi-scripted method above 57 57 58 ''' *Note: Be sure that all the files outputted in the above steps conform to the file name formats specified [wiki:Processing/FilenameConventions#Lidardeliveries here]'''58 '''Note: Be sure that all the files outputted in the above steps conform to the file name formats specified [wiki:Processing/FilenameConventions#Lidardeliveries here]''' 59 59 60 60 === Additional Steps for Full Waveform Deliveries === … … 100 100 ------------------- 101 101 102 If you have hyperspectral data to make into a delivery, go to the [wiki:Procedures/DeliveryCreation/Hyperspectral hyperspectral delivery] page. 103 104 If not, or if you've done that already, the delivery is ready for [wiki:Procedures/DeliveryChecking checking]. 102 Once all these steps have been done the delivery is ready for [wiki:Procedures/DeliveryChecking checking].