Changes between Version 8 and Version 9 of Procedures/DeliveryChecking
- Timestamp:
- Sep 9, 2010, 11:58:15 AM (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Procedures/DeliveryChecking
v8 v9 9 9 1. Check that [wiki:Processing/FilenameConventions#Delivereddata all other folders] and contents are present. 10 10 1. Check for typos, etc in the documentation. 11 1. Ensure the readme and othertext files are Windows compatible (use the 'file' command on the .txt files: they should be ASCII with CRLF terminators) (run unix2dos !ReadMe.txt)11 1. Ensure the text files are Windows compatible (use the 'file' command on the .txt files: they should be ASCII with CRLF terminators) (run unix2dos !ReadMe.txt) 12 12 1. Test out the readme level 3 processing command for one or more of the level 1 files (definitely one per sensor). 13 13 1. Check each of the screenshots … … 22 22 1. Only PDF versions of logsheet should be present. 23 23 1. Check for typos, etc in the documentation. 24 1. Ensure the readme and othertext files are Windows compatible (use the 'file' command on the .txt files: they should be ASCII with CRLF terminators) (run unix2dos !ReadMe.txt)24 1. Ensure the text files are Windows compatible (use the 'file' command on the .txt files: they should be ASCII with CRLF terminators) (run unix2dos !ReadMe.txt) 25 25 1. Check all the ASCII LIDAR files open/load, look OK and fit together 26 26 * Use lag to view the data … … 49 49 1. Check against the readme that all data that should be present is. 50 50 1. Check for typos, etc in the documentation. 51 1. Ensure the readme and othertext files are Windows compatible (use the 'file' command on the .txt files: they should be ASCII with CRLF terminators) (run unix2dos !ReadMe.txt)51 1. Ensure the text files are Windows compatible (use the 'file' command on the .txt files: they should be ASCII with CRLF terminators) (run unix2dos !ReadMe.txt) 52 52 1. View all of the thumbnail images 53 53 * Remove any that are very over/under exposed or not relevant to the project. This could include: very bright images, very dark images, images of the instrument bay door, images not overlapping with any of the Eagle/Hawk data