GB09/05, flight day 278b, Leighton moss

[mark1]

Data location: ~arsf/arsf_data/2009/flight_data/uk/GB09_05-2009_278b_Leighton_moss

Data arrived from ARSF via SATA disk LETTER L on 7th October 2009.

Scientific objective: /users/rsg/arsf/arsf_data/2009/ARSF_Applications/GB09-05.pdf

Priority: alpha-4-low

PI: A. Blackburn

Sensors:

• Eagle (26/02/2010)
• Hawk (26/02/2010)
• Leica LIDAR (26/02/2010)

[mark1]

Still awaiting logsheet. When it arrives, need to go through the eagle and hawk files and see why they have been put in 2 separate folders (278b and 278c) and move/rename as necessary. Can then create a DEM.

[mark1]

logsheet arrived and unpacked

[mark1]

Have split the project up into 2 separate ones (GB09/05 278b and 278c). Both contain duplicates of the same applanix and rinex data but have independent logsheets and raw eagle/hawk data. The Leica lidar data has been kept as one data set in this project (GB09/05 278b). If when it has been processed one can tell if it should be split (and into which project to put it) then do so. See ticket #279

[mggr]

Re: #281 (Hawk frame rates are double what they should be), the following lines are affected and the .hdr file will need to be edited to halve the fps number:

uk/GB09_05-2009_278b_Leighton_moss/hawk/SWIR278b-09-1.hdr: predicted length half recorded length, frame rate doubling problem?
uk/GB09_05-2009_278b_Leighton_moss/hawk/SWIR278b-09-2.hdr: predicted length half recorded length, frame rate doubling problem?
uk/GB09_05-2009_278b_Leighton_moss/hawk/SWIR278b-09-3.hdr: predicted length half recorded length, frame rate doubling problem?
uk/GB09_05-2009_278b_Leighton_moss/hawk/SWIR278b-09-4.hdr: predicted length half recorded length, frame rate doubling problem?
uk/GB09_05-2009_278b_Leighton_moss/hawk/SWIR278b-09-5.hdr: predicted length half recorded length, frame rate doubling problem?
uk/GB09_05-2009_278b_Leighton_moss/hawk/SWIR278b-09-6.hdr: predicted length half recorded length, frame rate doubling problem?
uk/GB09_05-2009_278b_Leighton_moss/hawk/SWIR278b-09-7.hdr: predicted length half recorded length, frame rate doubling problem?
uk/GB09_05-2009_278b_Leighton_moss/hawk/SWIR278b-09-8.hdr: predicted length half recorded length, frame rate doubling problem?

[mark1]

IPAS processing has been done.

[mark1]

Started Hyperspectral processing

[mark1]

None of the Hawk lines have specim sync messages or dark frames.

[emca]

Starting LIDAR processing.
Data in raw_laser relates to 278c, raw_laser for this project was bundled in with 278a.
Have moved the raw_laser files into the correct directories.

[emca]

LIDAR processing complete. Ready for delivery check at:
~airborne/workspace/GB09_05-2009_278b_Leighton_moss/delivery/20100218/GB09_05

[mark1]

Eagle Line	SCT Offset
1	0
2	0
3	0.03
4	0.03
5	0.03
6	0
7	0
8	0

Hawk Line	SCT Offset
1	-4.7
2	-4.6
3	-4.4
4	-5.3
5	-5.05
6	-5.24
7	-4.45
8	5.2

[mark1]

Hyperspectral delivery created at:

~airborne/workspace/GB09_05-2009_278b_Leighton_moss/delivery/20100223/GB09_05

[mark1]

LIDAR delivery checked. All lines open up in grass and look good and data checked for missing records. Ready to deliver.

[knpa]

Hyperspectral delivery checked

All fine apart from:

• Readme contents list; should be gap between last lev1 and misc listings
• Cloud overflow on e3
• Lots of underflows in H08
• Need to mention blank band 232 in all hawk
• Overflows on h03
• Serious underflows on H06 - last 3 appear blank

[mark1]

Hyperspectral and LIDAR data delivered to PI on 26/02/2010