GB09/04, flight day 062/2010, Coed-y-Brenin

[benj]

Data location: ~arsf/arsf_data/2010/flight_data/uk/GB09_04-2010_062_Coed_Y_Brenin

Data arrived from ARSF via network transfer on 19th March 2010.

Scientific objective: Mapping Rhododendron sites using combination hyperspectral and LiDAR.

Priority: a4l

PI: Sarah Taylor

Sensors:

• Eagle (03/09/2010 & 18/11/2010)
• Hawk (09/12/2010)
• Leica LIDAR (03/09/2010)
• RCD Digital Photography (03/09/2010)

[benj]

There are 24 eagle and hawk lines but only 22 recorded on the logsheet, presumably two were re-flown. Have asked ARSF-ops which two are affected (though looking at file sizes I think the bad ones are probably 1 and 13 for Eagle and 1 and 2 for Hawk).

[mggr]

When the photos are processed, please let Mike know - Bill is interested in copies of high-relief photos purely for internal testing purposes.

[pmlvis10]

IPAS navigation for this project has been processed.

[ella]

Looks like applanix navigation processing has been done. Copied to arsf workspace in Samba.

[iopa]

Processing Hyperspectral.

[iopa]

Hyperspectral data has been processed. PI will now be contacted to determine whether OS vector verification is required.

[iopa]

Regarding my message above, no contact with PI is required since we already have the vectors.

[iopa]

Eagle/Hawk SCT Offsets attached. Hawk ones have been significantly over the 0.1 positive limit in this project and above 1 second. There were also two peaks of 28.75 and 43.3 seconds.

[jb362]

Starting delivery check

[jb362]

Hyperspectral delivery check complete. Everything fine, although worth noting:

1) Only 60 bands for eagle data although this is because of 8,1 binning as shown in eagle header file.

2) Pixel overflow for eagle flight lines:

e2: bands 0-14
e10: bands 0-25
e11: bands 0-29
e12: bands 0-24
e13: bands 0-16
e20: bands 0-23
e22: bands 0-32

3) Hawk band 160 blank for all flight lines

[jb362]

4) Also, you need to put the DEM in the delivery directory

[iopa]

Hyperspectral is ready to deliver.

[iopa]

Taking up LiDAR.

[iopa]

Taking camera processing.

[jb362]

Delivery checking camera.

[jb362]

Camera delivery looks fine.

[iopa]

LiDAR processing complete and ready for checking.

[ella]

Starting LiDAR checking.

[ella]

Aborting delivery check.

[iopa]

Roll offset used for LiDAR processing: 0.00089950 (rad)

[emca]

Delivery checked LiDAR delivery at
~airborne/workspace/GB09_04-2010_062_Coed_Y_Brenin/delivery/20100901/GB09_04

Need to update logsheet to typed version and ensure the name is in the correct format. Also Julian day on the logsheet says 063 - should this be changed to 062?

Remove hidden files from delivery directory (.nfs*)

[iopa]

Dispatched USB Disk on 03/09/2010 containing Eagle, LiDAR and Photography data.

[anch]

Rechecked after discovering that incorrect images were dispatched to PI (Due to has_sync being set to false by accident).

Everything fine with images after reprocessing with has_sync set to true.

Logsheet is still handwritten - this should be updated to a typed version

[iopa]

During email correspondence with the PI and collaborators, ARSF discovered the delivered level 1 data was not adjusted for the timing offsets and the eagle dataset was re-processed with the timing offsets for eagle as listed in the attachment syncOffsets.sync.

Logsheet for the new delivery was converted from abw to pdf and the corrected Eagle data has been dispatched to PI on 18/11/2010.

[iopa]

Hawk is ready for checking.

[knpa]

Beginning delivery check.

[knpa]

Delivery check complete.

All looks good and ready to deliver.

There is one thing that might be worth investigating: On band 0 for every line the rightmost samples are blacked out.

[benj]

I noticed that on another dataset - I suspect it's a bad pixel (or more than one).

[iopa]

Hawk data dispatched on 09/12/2010.

[iopa]

Eagle/Hawk SCT offsets