Changes between Version 3 and Version 4 of Processing/BadATMScans


Ignore:
Timestamp:
Sep 3, 2008 2:24:25 PM (11 years ago)
Author:
anee
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Processing/BadATMScans

    v3 v4  
    22
    33 * Replace the azatm section of your script (for lines containing bad scan lines) with the two azatm commands below and run the script.
    4    * azatm -v -eds -1 -NOCAL -sNO -i atm/${ATM_PREFIX}${ATM_FILE_NO}.* -h ${LEV1_HDF} -cal ${CALIBRATION_FILE} \
    5    * azatm -v -bbtt 9 3 0.002 1 -bbf 7 7 -sNO -h ${LEV1_HDF} -cal ${CALIBRATION_FILE} \
     4   * azatm -v -eds -1 -sNO -NOCAL -v -tc 0 -i atm/${ATM_PREFIX}${ATM_FILE_NO}.* -h ${LEV1_HDF} \
     5   * azatm -v -bbtt 5 3 0.02 1 -bbf 7 7 -sNO -h ${LEV1_HDF} -cal ${CALIBRATION_FILE} \
    66
    77
    88 * Convert each raw ATM hdf file containing bad scan lines into bil files with headers by running '''''azexhdf -h <hdf_filename.hdf> -Be <bil_filename.bil>''''' (note: you may wish to place the bil files into their own directory as if they are in the same dir as the hdf files, envi gets confused when opening the hdfs and displays garbage).
    99
    10  * Once the bil files have been created, navigate to the dir where the bils are and run '''''atm_bad_scans.py'''''. This will read band 7 of all the bil files and returns all the bad scan lines it finds (and writes these into a txt file with the same name as the bil file for easy copy and paste into the scripts). Currently these are just lines which contain significant numbers of 0 values or complete lines of high values. Other, harder to detect bad scans may exist so it is worth keeping an eye out for these.
     10 * Once the bil files have been created, run '''''atm_bad_scans.py -f <filename> -t <pixel_threshold> -m <multiple> -b <bands>'''''.
     11   * -f file to scan
     12   * -t number of pixels which have to be bad for a line to be considered bad
     13   * -m if a pixel in the current line is -m times larger or smaller than a pixel in previous the line it is considered bad
     14
     15This will read band 7 of all the bil files and returns all the bad scan lines it finds (and writes these into a txt file with the same name as the bil file for easy copy and paste into the scripts). Currently these are just lines which contain significant numbers of 0 values or complete lines of high values. Other, harder to detect bad scans may exist so it is worth keeping an eye out for these.
    1116
    1217 * Copy the bad scan line numbers from the txt files into the corresponding scripts after the -eds option. The lines numbers entered into the scripts will be marked as bad in the hdfs after running the scripts. These will still be visible when viewing the hdfs but will not be present in the level 3 GeoTIFFs.