GB18/56, flight day 135/2018, Suffolk, Nottinghamshire and Lincolnshire

[asm]

Data location: ~arsf/arsf_data/2018/flight_data/uk/GB18_56-2018_135_Methane_Sites

Data arrived via USB hard drive on 11/June/2018.

Scientific objective: Investigate well-defined local methane emission sources in the UK to apply and evaluate the hyperspectral processing method currently developed at the University of Leicester.

Priority: High for Fenix, medium for Owl

PI: Hartmut Boesch

Sensors:

• Fenix (requested, flown)
• OWL (requested, flown)
• PhaseOne (not requested, flown)

[asm]

Unpacking.

Project unpacked. Problems found so far:
-Owl has not been renamed for now as the GPS starting time is not recorded in the files.
-No owl darkframes recorded
-Calibration files also placed in different directories (will need to identify each one by the time)
-No timestamps for the nav files.
-All fenix f98 are empty.
-A few dropped frames incidents for the Fenix:
There has been 2 incidents on different lines with a total of 34 dropped frames recorded on file FENIX135-18-14.log
There has been 2 incidents on different lines with a total of 39 dropped frames recorded on file FENIX135-18-7.log
There has been 2 incidents on different lines with a total of 32 dropped frames recorded on file FENIX135-18-1.log
There has been 2 incidents on different lines with a total of 33 dropped frames recorded on file FENIX135-18-5.log

[asm]

Unpacking.

-Renamed Owl files as the time in the header (not GPS but internal) will help processing. Will need to add GPS Starting time to process
-The owl lines do not have darkframes so will need to use the calibration files. Match each calibration with each file and stitch them. Time consuming, specially combined with no navigation files to use and the GPS timing issue.
No KML created yet or logsheet but project but otherwise the unpacking is done.

[asm]

Navigation Processing

Started in order to assess if the fps problem with the Fenix still persists. Needed to use teqc:
teqc -st 180515094209 -e 180515150330 +nav /tmp/teqc_135_2018/135_2018.nav > /tmp/teqc_135_2018/135_2018.18o

Done basestation verification:
Lat: 52 04 27.12178
Lon: -0 37 24.79006
EllHeight: 151.206 m

Done navigation as well. Good results, accuracy is always better than 0.2m in lat and lon sepparation and with ambiguity fix 2. All parameters looking good, best results we have in a long time. Copying files across and navigation will be finished.

[asm]

Fenix processing

Used most recent boresight values found by wja. FPS problems with the Fenix still persists on this flight, I did manually estimated the fps for each flightline over the last week to have a valid geocorrection. Used qgis Open Street Map vector data and google maps to confirm the best values. The results are:

FENIX	SCT	FPS
1	3.52	30.96
2	3.01	31.00
3	2.97	30.98
4	27.87	31.00
5	4.16	30.96
6	22.27	30.96
7	52.05	30.96
8	2.41	30.96
9	53.98	30.96
10	3.30	30.95
11	53.98	30.95
12	7.79	31.00
13	2.92	30.95
14	3.10	31.00
15	30.98	31.00

[asm]

Fenix processing

Delivery created. It has been suggested to split the delivery into the 3 location with 3 sorties but keep them together as raw data so will address that. Logsheet can't be automatically generated so will tailor one for each site.

[asm]

Fenix Delivery

I have created 3 different deliveries with sorties a, b and c with each readme. I am finalising the logsheets and filling them manually but otherwise the project is ready for DC in the meantime.

[dac]

Fenix Delivery Check

Starting delivery check

[dac]

Fenix Delivery Check

All three projects :

• Readme contains a photo of the Dornier - remove it
• Wierd characters in 'Quality and issues with data' section (likely LaTeX problem)
• "framerate...not recorded correctly" change to "framerate ...not set correctly" If the correct framerate was recorded in the logsheet but not the file it wouldn't be a problem as could just update the header based on the logsheet.
• "obtained and validated using Google Maps and Open Street Map vector data via qgis." change to "obtained, checked against Google Maps and Open Street Map data via QGIS." (I assumed you used the raster version of open street map not the actual vector files).
• The DEM covers the area of all projects. However, the filesize is only 170 MB so I think OK.
• Metadata needs to be edited to contain site letter and only the name of the site it contains (sed -i is your friend here!)

Looking into individual areas now.

[asm]

Fenix Delivery

Placed one logsheet in each delivery using the screenshot created by the JSON scripts with the linestring option. Will address comments by dac now.

[asm]

Fenix Delivery

Mapped files have been zipped correctly, no problems in the logfiles.

[dac]

*Fenix Delivery Check

• check_apl_cmd runs through OK
• Checked spectra using Py6S script and look good
• Issues resolved with readme
• Metadata fixed
• Logsheets look good
• b is nearer Lincoln than Nottingham but within the Nottinghamshire boundary county.

Everything else looks good. Ready to deliver.

[asm]

Fenix Delivery

Delivered via FTP (slot 2) and email sent to PI on 06/July/2018.

[dac]

Digital Camera

Converted raw images to tiff to check GPS sync