Changes between Version 2 and Version 3 of Procedures/DeliveryCreation/Hyperspectral

Jul 14, 2010 9:26:54 AM (9 years ago)



  • Procedures/DeliveryCreation/Hyperspectral

    v2 v3  
    2929 1. Copy the mosaics and jpegs of flightlines created above into the screenshots directory
    32  1. Generate the readme file. Run ` -d <project_workspace_dir> -D <dem_type (One of either LIDAR, SRTM or NEXTMAP)>`. I suggest you first run ' -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).
    36 === Necessary comments to make in the readme file ===
    38  1. Update anything marked TODO in the template
    39  1. Appropriate pixel size
    40  1. Appropriate bands for the sensor
    43  1. Ensure the text file is in Windows format (run unix2dos on it if necessary)
    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 script. Use a command such as -d <delivery_directory> -r hyper
     33  1. Edit the config file and check all the items are filled in:
     35   1. Any remarks about the data should be entered as a sentence in the "data_quality_remarks" section.
     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 -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>