GB08/10, flight day 268c, Denny Wood

[mark1]

Data location: ~arsf/arsf_data/2009/flight_data/uk/GB08_10-2009_268c_Denny_wood

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

Scientific objective: see /users/rsg/arsf/arsf_data/2008/ARSF_Applications/GB_and_NL/GB08-10 Science Case.pdf

Priority: alpha-4-High

PI: Ross Hill

Sensors:

• Eagle (14/12/2009)
• Hawk (14/12/2009)
• Leica LIDAR (26/04/2010)

[mark1]

Still awaiting flight logsheet.

DEM creation caused errors in Grass but still outputted a DEM. Check DEM is good when processing.

[mark1]

Eagle and Hawk files in wrong project. Have moved the Eagle/Hawk files to boresight_2009-268a_little_riss.

Eagle/Hawk files from GB08_08-2009_268b_Wytham_woods have been moved into this project (during unpacking)

[mark1]

Have renamed Eagle files 5-13 to have VNIR prefix

[mark1]

logsheet arrived and unpacked

[mark1]

have renamed hawk files from 268* to SWIR268*

[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/GB08_10-2009_268c_Denny_wood/hawk/SWIR268c-09-1.hdr: predicted length half recorded length, frame rate doubling problem?
uk/GB08_10-2009_268c_Denny_wood/hawk/SWIR268c-09-2.hdr: predicted length half recorded length, frame rate doubling problem?
uk/GB08_10-2009_268c_Denny_wood/hawk/SWIR268c-09-3.hdr: predicted length half recorded length, frame rate doubling problem?
uk/GB08_10-2009_268c_Denny_wood/hawk/SWIR268c-09-4.hdr: predicted length half recorded length, frame rate doubling problem?
uk/GB08_10-2009_268c_Denny_wood/hawk/SWIR268c-09-5.hdr: predicted length half recorded length, frame rate doubling problem?
uk/GB08_10-2009_268c_Denny_wood/hawk/SWIR268c-09-6.hdr: predicted length half recorded length, frame rate doubling problem?
uk/GB08_10-2009_268c_Denny_wood/hawk/SWIR268c-09-7.hdr: predicted length half recorded length, frame rate doubling problem?
uk/GB08_10-2009_268c_Denny_wood/hawk/SWIR268c-09-8.hdr: predicted length half recorded length, frame rate doubling problem?

[emca]

Per flight line SCT values for Eagle and Hawk

Flight line	Eagle	Hawk
1	-	0.16
2	-	0.17
3	-	0.10
4	0.02	0.10
5	0.04	0.16
6	-0.01	0.18
7	0.04	0.10
8	0.07	0.11
9	0.04	-
10	0.11	-
11	0.01	-
12	0.05	-
13	0.06	-

[emca]

Eagle lines 1, 2 and 3 are very short and are not included in the delivery (2 and 3 do not appear on the log sheet). Eagle line 7 has an incorrect number of lines in the header file and no dark frames. This line was processed using the dark frames from Eagle line 8.

Project is ready for delivery checking and delivery directory has been created at
~airborne/workspace/GB08_10-2009_268c_Denny_wood/delivery

[mark1]

Starting delivery check

[mark1]

Minor edits made to read me file, all data viewed and example commands tested (without dem). Data looks good.

Ready to deliver - data has not been rsynced back.

[emca]

Eagle and Hawk data sent to PI 14/12/09

[emca]

Starting LIDAR processing

[emca]

LIDAR processing complete

Ready for delivery check at
~airborne/workspace/GB08_10-2009_268c_Denny_wood/delivery/20100422/GB08_10

[mark1]

LIDAR delivery checked and all looks good.

Ready for delivery.

[emca]

LiDAR data dispatched to PI 26/04/2010

LiDAR and Hyperspectral rsync'd to
~arsf/arsf_data/2009/flight_data/uk/GB08_10-2009_268c_Denny_wood

Ready for archiving