Changes between Version 45 and Version 46 of Procedures/EndUserDelivery


Ignore:
Timestamp:
May 13, 2009 12:57:46 PM (10 years ago)
Author:
mark1
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Procedures/EndUserDelivery

    v45 v46  
    7979
    8080Once a dataset has been prepared for burning and delivery, a second person should go over it and:
     81=== For Hyperspectral Data ===
    8182 1. Verify we have the correct PI (check against application, call Kidlington if unsure) and address (application, google, Kidlington)
    8283 1. Check against the logsheet that all data that should be present is.
     
    8586 1. Test out the level 3 processing command for one or more of the level 1 files (definitely one per sensor).
    8687 1. All level 1 files should be looked at visually (ideally in all bands, though this is only practical for ATM and casi).
    87 
     88=== For LIDAR Data ===
     89 1. Verify we have the correct PI (check against application, call Kidlington if unsure) and address (application, google, Kidlington)
     90 1. Check against the logsheet that all data that should be present is.
     91 1. Check for typos, etc in the documentation.
     92 1. Ensure the readme and other text files are Windows compatible (use the 'file' command on the .txt files: they should be ASCII with CRLF terminators) (run `unix2dos ReadMe.txt`)
     93 1. Open all the ASCII LIDAR files into a GIS and check they open/load ok
     94 1. Check overlaps with neighbouring lines for obvious errors
     95 1. Check against vectors if available
     96 1. use tail/head to check the ASCII LIDAR files have all the required columns in the order specified in the readme.txt
     97   * `head <lidarfilename>`
    8898------------------------
    8999== Final steps ==