| 19 | | 1. Generate the readme using `create_lidar_readme.py -d <main project directory> [-l <path to text logsheet>] [-s <path to delivery e.g. .../DATE/PROJ-CODE>]`. For this script an ASCII version of the logsheet needs to be in ./admin - if not there create one. Go through the read_me and edit as required (search for TODO) |
| | 19 | 1. Generate the readme file. |
| | 20 | 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` |
| | 21 | 1. Edit the config file and check all the items are filled in: |
| | 22 | * Any remarks about the data should be entered as a sentence in the "data_quality_remarks" section. |
| | 23 | * If vectors have been used then the accuracy should be entered in "vectors" (e.g. '5-10' if they're within 5m to 10m) |
| | 24 | * line_numbering should contain a space separated list of line names linking the logsheet to the processed files. |
| | 25 | * las_files should contain the path to the processed LAS file in order to extract the per flightline statistics |
| | 26 | * 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... |
| | 27 | * All "compulsory" items should contain data |
| | 28 | 1. Create a TeX file. Use the script `create_latex_lidar_readme.py -f <config filename>` |
| | 29 | 1. This file can be reviewed and edited in any text editor if needed |
| | 30 | 1. Create a PDF file by running `latex <tex_filename>` |
| | 31 | 1. Review the read me and check carefully to see if it looks OK with all relevant information present |
| | 32 | 1. Copy it to the delivery directory and remove any temporary files. Recommended to keep the TeX file until after delivery checking in case any edits are required |
| 33 | | 1. Generate the readme using `create_lidar_readme.py -d <main project directory> [-l <path to text logsheet>] [-s <path to delivery e.g. .../DATE/PROJ-CODE>]`. For this script an ASCII version of the logsheet needs to be in ./admin - if not there create one. |
| 34 | | 1. Go through the read_me file and edit as required |
| 35 | | * Enter all the project details into the table at the top |
| 36 | | * Fill in the contents. Add the lidar filenames on the left and line numbers (from logsheet) on the right. |
| 37 | | * Enter the projection and datum details - get these from ALS PP output dialog when processing. |
| 38 | | * UK flights should be - Horizontal Datum: "ETRF89" Vertical Datum: "Newlyn" Projection: "OSTN02 British National Grid" |
| 39 | | * Insert statistics for each line: `lasinfo --check <lidarfilename>` then cut/paste the required information |
| 40 | | * Check the accuracy of data vs vectors and estimate the average offset, also the average elevation offset between neighbouring lines |
| 41 | | * Search for 'TODO' and change anything that remains to be done |
| 42 | | * Ensure there are no tab characters used (search for \t and remove any that are present) |
| 43 | | * Ensure readme file is in Windows format (run unix2dos on it) and |
| 44 | | |
| | 46 | 1. Generate the readme using as per point 3 above |