RG13/08, flight day 234a/2015, Cambridge

[lah]

Data location: ~arsf/arsf_data/2015/flight_data/uk/RG13_08-2015_234a_Cambridge

Data arrived from ARSF via USB on 27/08/2015.

Scientific objective: Measuring ash die back.

Priority: Unknown

PI: David Coomes

Flown on same day as Monks Wood (RG13/08) and Alconbury(GB15/00).

Sensors:

• Fenix
• Leica LIDAR
• FW Leica LIDAR
• RCD

[lah]

Unpacking

All extra files have been split out except from RCD, which is duplicated for 234a, 234b and 234c. Please only process RCD for one of these projects, then split once processed.

[dac]

Fenix data needs processing for this (at least up to finding SCT values) as a priority to check everything is working OK with the instrument - in particular the navigation data.

[gej]

Navigation Processing Started

Lat: 52 11 07.32948
Long: -0 06 44.97121
ell.Height 120.043

[gej]

Navigation Processing Finished
Starting Fenix Processing

[gej]

Fenix Processing

Flight line 1 has been removed as it isn't in the logsheet and before plane aligned in.

had to specify nav2_args_extra in config file for flight lines 2 and 6 as specim_qsub.py couldn't find the files.

found sct values

Flightline	FENIX
2	0.96
3	1.10
4	1.01
5	0.98
6	0.97

Nav sync problems appear to be fixed, no other problems to this point

[dac]

RCD Processing

Processed RCD files from raw to tif to test calibration file. Used file for 60 mm lens (S/N 27).

[stgo]

Lidar processing

Starting processing

[stgo]

Lidar Processing

There's no overlap in the Lidar data and the files are very small. Processing full waveform.

[stgo]

Lidar Processing

Ready for delivery check

[gej]

Lidar Delivery check

No problems found.

Ready for delivery

[asm]

Lidar Delivery

Delivered via FTP (arsf19). Notification has been sent to PI.

[gej]

Hyperspectral Processing
Fenix processed using new calibration.
Have created delivery and readme.

Ready for Delivery check

[asm]

Hyperspectral Delivery Check

Found some problems with flightline 03, gej to check again SCT values.

[gej]

Hyperspectral processing

Found correct SCT for flight 3
SCT is now 1.00

Creating mapped file now.

[gej]

Hyperspectral Processing

flightline 3 has been remapped, screenshots, mosaic and readme created.

Ready for Re-DC

[asm]

Fenix DC

-All flightlines seems to have correct SCT values now.
-Checked green vegetation spectra with Py6S. Good match for all flightlines.
-Tested all tif files created from apl commands.
-Corrected new line starting with lowercase on readme and changed slightly the sentence.
-All checks made, no further problems ecountered.

A check on spectra will be done by lah, after that will zip files and project will be ready to go.

[lah]

Fenix DC - spectra
Spectra for all lines look good. There is a narrow spike at the end of the VNIR region which is quite intense for the start of line 2 where there is a lower signal level, but this is well within the mask region. Spectral offset looks to be well within the 5nm spectral resolution of the SWIR bands, and generally looks better than Malaysian data.

Would be nice to keep the Py6S outputs for spectra checking. Don't forget to delete tmp_cmd_check though.

Ready to deliver once files have finished zipping.

[asm]

Fenix delivery

Zipped files has been created. Fenix delivery is ready to go.

[asm]

Fenix Delivery

Delivered via FTP (arsf19). Notification has been sent to PI.

[gej]

RCD processing

Tiff images tagged. Creating delivery

[gej]

RCD processing

Delivery and Readme created, ready for delivery check

[dac]

RCD Delivery Check

Starting delivery check.

[dac]

RCD Delivery Check

All looks fine - ready to deliver.

[dac]

RCD Delivery

Sent to PI via FTP (arsf19) 17/12/2015

[stgo]

LiDAR processing

An issue was discovered with the scan angle filtering, the lidar data has been reprocessed with a wider scan angle of 45 degrees. The wider scanline size has created an overlap region between lines 2 and 3 and lines 3 and 4, this has not introduced a pitch or roll error.

I have created a new delivery which is ready for check.

[gej]

Starting Lidar Delivery Check

[gej]

Lidar deliver check

All looks fine,

Ready to deliver

[dac]

LiDAR data delivery

Redelivered via FTP (arsf19) - 26/02/2016

[mark1]

Fenix zipped mapped line 03 is corrupt and won't unzip - this file should be re-created before archiving.

[dac]

Looks like this line was modified after being delivered. Not sure how this happened. Have started reprocessing.

[dac]

Reprocessed line 3 and replaced mapped zipped file.

[dac]

Archiving

Started uploading to NEODC.

[dac]

Archiving

Data now available from NEODC. Closing ticket.