GB2007/05, flight day 103c/2007, Loch Leven

[mggr]

Data location: ~arsf/arsf_data/in_progress/2007/flight_data/uk/GB2007_05-2007_103c_Loch_Leven

Data arrived from ARSF via initial SATA disk transfer in June.

Scientific details: Data to inform models of potentially toxic cyanobacterial blooms in lakes. See ~arsf/arsf_data/in_progress/2007/ARSF_Applications-GB_2007/GB07-05_*pdf

This is one of three lakes overflown.

Sensors

• ATM (delivered 19/Nov/2007, will possibly need redelivery after #39)
• Eagle (binning 4 spectral, 1 spatial)
• Hawk (binning 1/1)

Quicklook

[anee]

ATM file numbers in the log sheet are incorrect as in ticket #50. Listed as 010, 011 and 012. Is obvious from the times listed in the terminal output and times in the log sheet ATM file numbers should be 011, 011 and 013. However, line 1 won't process and terminates with error “ no ATM data on this file scans: 0 to: 0”.

[anee]

All lines processed for atm eagle and hawk.

GPTOFFs:

-ATM: line 2, -0.02.
-eagle: line 1, -0.025.
-hawk: line 1, -0.075. line 2, -0.1.

hawk lines 1 and 3 have large gaps in the swath image

[anee]

ATM line 1 doesn't process and terminates with the error: no ATM data on this file scans: 0 to: 0

[mggr]

Took a peek at the data files and it looks like:

• 011 is the navigation data
• 012, 013, 014 are image data

You can see this too if you cd into the atm/ raw directory and run qcdisplay.

[anee]

Pixel size is 5

[anee]

Processed flight data located in: /users/rsg/anee/scratch_space/GB2007_05-2007_103c_Loch_Leven

Delivery directory created and filled. ATM scripts are current.

[mggr]

Copied into ~arsf/arsf_data/in_progress/2007/flight_data/uk/GB2007_05-2007_103c_Loch_Leven, checked (only minor corrections), looks good :)

Ready to burn to DVD.

[mggr]

ATM delivered (adding note to description).