Changes between Version 23 and Version 24 of Procedures/DeliveryCreation/Hyperspectral


Ignore:
Timestamp:
Feb 4, 2011 11:53:59 AM (8 years ago)
Author:
knpa
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Procedures/DeliveryCreation/Hyperspectral

    v23 v24  
    2222     1. Move images into jpgs directory.
    2323    - If all else fails, open tifs in ENVI and manually take screenshots and crop them using gimp. Envi also has mosaicking functions. Move images into jpgs directory.
    24  1. Create the delivery directory: run make_delivery_folder.sh. Check it's created everything you expect correctly. If it fails, you can create the directory manually as follows:
     24 1. Create the delivery directory: run make_delivery_folder.sh. Check it's done all the steps below correctly and do them yourself if not:
    2525   1. In the project directory in the workspace, create a directory called "delivery". Within this create a directory named after the date as YYYYMMDD, and within this create one named after the project code.
    2626   1. Copy the contents of ~arsf/arsf_data/<year>/delivery/template into your new delivery directory
     
    2929   1. Copy the pdf logsheet into the logsheet directory
    3030   1. Move the level 1 files from the directory they were processed into (<project_dir>/lev1/) into the lev1 directory in the delivery directory.
     31   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 later.
    3132   1. If the dem file was generated with non-NEXTMAP data then make a dem directory in the delivery and copy this to it.
    32  1. In the delivery directory create a directory called "misc". Copy files into it as follows:
    33    * For UK flights, copy in ~arsf/dems/geoid-spheroid/osgb02.cgrf
    34    * For non-UK flights, copy in ~arsf/dems/geoid-spheroid/sphsep15lx.grd UNLESS we supply a LIDAR DEM in which case they will not need this file.
    35  1. If the script has not done so, copy the mosaics and jpegs of flightlines created above into the screenshots directory
    36  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.
     33   1. In the delivery directory create a directory called "misc". Copy files into it as follows:
     34    * For UK flights, copy in ~arsf/dems/geoid-spheroid/osgb02.cgrf
     35    * For non-UK flights, copy in ~arsf/dems/geoid-spheroid/sphsep15lx.grd UNLESS we supply a LIDAR DEM in which case they will not need this file.
     36   1. Copy the mosaics and jpegs of flightlines created above into the screenshots directory
    3737 1. Create Readme: [[BR]]
    3838  '''New style read me is largely untested - expect some errors - let mark1 know so he can fix the scripts.'''