Changes between Version 1 and Version 2 of Processing/BadATMScans
- Timestamp:
- Jul 7, 2008, 1:07:12 PM (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Processing/BadATMScans
v1 v2 11 11 12 12 * 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. 13 14 * Rerun the processing and manually view the lev1/lev3, looking out for slipped scans (line starts late and is offset) or white streaks. Find the line number of these in ENVI using the cursor location (subtract 1 from the Y value as azatm counts from 0 and ENVI counts from 1) and add these line numbers to the -eds part of the azatm command, then rerun and repeat.