Changes between Version 17 and Version 18 of Procedures/OwlProcessing
- Timestamp:
- Sep 3, 2015, 10:46:36 AM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Procedures/OwlProcessing
v17 v18 49 49 Early owl files have corrupt nav files, so if you get this message in the log or 'Requested sync time index is out of bounds in GetSyncDelay()' set the config file to use_nav = false. 50 50 51 If there appears to be strip ping across the mapped files, bright and dark lines, or sections of a flight line don't match up the sensor has probably dropped frames. These can be checked in the .log file in the capture directory. These empty lines need to be inserted into the level 1b data file before geocorrection to map the flight line correctly.51 If there appears to be striping across the mapped files, bright and dark lines, or sections of a flight line don't match up the sensor has probably dropped frames. These can be checked in the .log file in the capture directory. These empty lines need to be inserted into the level 1b data file before geocorrection to map the flight line correctly. 52 52 53 53 == Create mask files == … … 59 59 Use the make_arsf_delivery.py script, specifying owl as the sensor type: 60 60 61 make_arsf_delivery.py --projectlocation <project directory> --deliverytype owl 62 63 Make sure that there is no 'cal' directory or 'blinkers' directory in the flightlines directory, or the script will error. 61 make_arsf_delivery.py --projectlocation <project directory> --deliverytype owl --final 64 62 65 63 An error will be raised by COPYDOCS as there is yet no data quality report for the owl.