Changes between Version 4 and Version 5 of Procedures/DeliveryCreation/Hyperspectral


Ignore:
Timestamp:
Jul 22, 2010 5:10:31 PM (9 years ago)
Author:
mark1
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Procedures/DeliveryCreation/Hyperspectral

    v4 v5  
    2929 1. Copy the mosaics and jpegs of flightlines created above into the screenshots directory
    3030 1. Ensure that the filenames of the level 1 files and flightline jpegs are correct - they should be [eh]JJJaff1b.*, where [eh] is e for eagle or h for hawk, JJJ is the julian day of the flight, a is a flight letter if appropriate (usually a, b or occasionally c), and ff is the flightline number. There should be one level 1 file (or set of files, if there are .bil and .bil.hdr files in addition to the HDF) per flightline. If any are missing for particular sensors (eg. because the sensor failed), this should be explained in the readme file. 
    31  1. '''New style read me is largely untested - expect some errors.'''
     31 1. '''New style read me is largely untested - expect some errors - let mark1 know so he can fix the scripts.'''
    3232  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`
    3333  1. Edit the config file and check all the items are filled in: