Changes between Version 3 and Version 4 of Procedures/OwlProcessing


Ignore:
Timestamp:
May 6, 2015 4:00:37 PM (4 years ago)
Author:
lah
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Procedures/OwlProcessing

    v3 v4  
    22
    33The Owl thermal hyperspectral sensor is new to the arsf and does not yet have a complete processing chain.  As this is developed this wiki page will be updated.  Details on the Owl sensor are available [https://arsf-dan.nerc.ac.uk/trac/wiki/Sensors/Owl here] and information on Owl testing is available [https://rsg.pml.ac.uk/intranet/trac/wiki/Projects/ARSF-DAN/Users/lah/OwlNotes here].
     4
     5== Rename Files ==
     6
     7Our scripts require that data be named according to the standard convention e.g. OWL219b-14-1, where 219 is the julian day, b the sortie, 14 the year and 1 the flightline. If this is not the case, you must rename both the files and the directories. renameOwl.py can be run with -p specifying the project directory. You will need to set write permissions for all the raw directories and files to do this; taking a backup is strongly recommended.
    48
    59== Radiometric Calibration ==
     
    1317Each flightline should have it's own calibration data in the form of additional files prefixed T1 and T2 in the capture directory.  If these are not present the script will produce a warning.  Run the script again with the option -c auto once the submitted flightlines have produced the required calibration files (Check the log has passed the "Writing calibration file..." step), or manually specify a calibration file with -c <flightline with calibration data_calibration.rad>.
    1418
    15 All output files are written to the /processing/owl/calibration subdirectory of the project folder and logs written to /processing/owl/logs. The output files consist of the data (*_proc.data) and if not specified as inputs, the calibration (*_calibration.rad) and blinker files (*blinkers.dat), all with their own header file. Intermediate files are stored in /users/rsg/airborne/workspace/Owl/ and deleted on completion.
     19All output files are written to the flight line subdirectory of /processing/owl/flightlines/level1b and logs written to /processing/owl/logfiles. The output files consist of the data (*_proc.bil) and if not specified as inputs, the calibration (*_calibration.rad) and blinker files (*blinkers.dat), each with their own header file. During processing a symlink appears in the output flight line folder to prevent simultaneous processing over the same line.  You may need to remove this if processing is aborted before it is automatically removed.
    1620
    1721=== Blinking Pixels/Vertical Stripes ===
     
    2428
    2529
    26 || [[Image(pixstabi238.png, align=centre, height=400)]] ||
     30|| [[Image(pixstabi238.png, align=centre, height=390)]] ||
    2731|| Level 1b Owl data (2014 238) calibrated with different values of pixstabi (default 0.011, 0.005, 0.003, 0.0025, 0.002) ||
    2832
    2933== Geocorrection ==
    3034
    31 This is being incorporated into APL...
     35Create a dem in exactly the same way as for fenix.  This should be saved in the processing/hyperspectral/dem directory, not the owl directories, so only 1 copy is required.  e.g. from the project directory type create_apl_dem.py --aster.
     36
     37Geocorrection is conducted in the same way as for fenix data, using APL. Generate a config file using generate_apl_config.py -o processing/owl/o2014219b.cfg to keep processing separate from fenix. Currently you need to add the boresight values to the config file (owl_boresight = 0.12 -0.32 0.32). You may want to delete or set to false the fenix lines if only processing owl data.  Make sure the project directory structure is complete (same as fenix). Submit to the grid using specim_qsub.py <config_file> and calculate the SCTs. Once you have done this you can generate the mapped data (102 bands) by setting owl_bandlist = ALL and setting the SCT value for each line.
     38
     39== Making a delivery ==
     40
     41This currently needs to be done manually and there are no data quality reports to add yet.
     42
     43== Problems ==
     44
     45There are likely to be problems with this newly developed processing chain. Please add problems (and solutions!) below and they will be fixed in due course.
     46
     47 * The xml files are not produced.
     48 * The boresight needs entering into the config file / needs adding to table.
     49 * Bad pixels remain - will eventually look into a masking routine &/ get a better blinker detection routine from Specim