| 31 | | 1. Ensure that an ASCII version of the logsheet exists in the project admin/ directory. To create one, start open office and save logsheet as .txt format. Also ensure no other file in the admin dir as a .txt extension. |
| 32 | | 1. Generate the readme file. Run `create_readme.py -d <project_workspace_dir> -D <dem_type (One of either LIDAR, SRTM or NEXTMAP)>`. I suggest you first run 'create_readme.py -h` to check the usage of the script. |
| 33 | | '''If using the new style config run scripts''' then you must use the switch -N to disable the azgcorr example command search (since runh/rune do not exist). |
| 34 | | 1. Edit the readme file to ensure that it is correct and to add any desired notes (eg. explanations on why there is no data for a particular sensor for a particular line). |
| 35 | | |
| 36 | | === Necessary comments to make in the readme file === |
| 37 | | |
| 38 | | 1. Update anything marked TODO in the template |
| 39 | | 1. Appropriate pixel size |
| 40 | | 1. Appropriate bands for the sensor |
| 41 | | 1. Comments on the quality of the data (accuracy vs vectors, any bad bands, etc) and any specific problems encountered |
| 42 | | 1. Include a tested example command to convert the data from level 1 to level 3 |
| 43 | | 1. Ensure the text file is in Windows format (run unix2dos on it if necessary) |
| 44 | | |
| 45 | | This list may not be exhaustive, check the readme carefully. |
| | 31 | 1. '''New style read me is largely untested - expect some errors.''' |
| | 32 | 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 hyper |
| | 33 | 1. Edit the config file and check all the items are filled in: |
| | 34 | 1. If an instrument has no dark frames for all flight lines then enter instrument name in "dark_frames" |
| | 35 | 1. Any remarks about the data should be entered as a sentence in the "data_quality_remarks" section. |
| | 36 | 1. If vectors have been used then the accuracy should be entered in "vectors" (e.g. '5-10' if they're within 5m to 10m) |
| | 37 | 1. line_numbering should contain a space separated list of line names linking the logsheet to the processed files. |
| | 38 | 1. All "compulsory" items should contain data |
| | 39 | 1. Create a TeX file. Use the script create_latex_hyperspectral_readme.py -f <config filename> |
| | 40 | 1. This file can be reviewed and edited in any text editor if needed. |
| | 41 | 1. Create a PDF file by running latex <tex_filename> |
| | 42 | 1. Review the read me and check carefully to see if it looks OK with all relevant information present. |
| | 43 | 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. |