CA18/208, flight day 230/2018, Ontario, Canada

[dac]

Data location: /users/rsg/arsf/arsf_data/2018/flight_data/canada/CA18_207-2018_230_Ontario

Data arrived from NERC-ARF via hard driver on 12/09/2018

Scientific objective: Canadian Wildfire Observations with SLSTR & Aircraft: Directional Effects of Thermally Emitted Radiation & Exploration of Flaming/Smouldering Partitioning and Plume Trace Gas Emission Ratios. Fenix and Owl data are being processed to aid geocorrection of other thermal sensors flown on the aircraft.

PI: Martin Wooster

BAS Project Code: D207

• Navigation data (.sol format) and level1b (unmapped) data to be delivered first. The level1b data will be used to determine which lines map.

Sensors:

• Fenix (requested, flown)
• Owl (requested, flown)

[asm]

Unpacking checks

-There are 5 owl lines and 5 fenix. Nav files look OK
-All owl lines have T1 and T2 calibration files except the first one that is missing T2.

[asm]

Owl processing

Symlinked missing T2 owl files using existing ones for processing purposes and renamed the files according with the flightline number.

[asm]

Owl Processing

Started in order to create the level1b files.

[wja]

Navigation Processing
Basestation PPP:

Latitude	51°04'01.40143"
Longitude	-93°48'14.26998"
Ellipsoid Height	346.759

Three differnt *.dat.000 datasets present.
Three SOL files have been generated.
20180818_161529.dat.000 contains flightlines but it does not all five.
There is a gap of ~9 mins to the previous navigation data and a gap of ~4 minutes to the next navigation data.
20180818_165619.dat.sol solution seperation exceeds 1m at the begging of this navigation data. This may need revisiting if this is a relevant area.
Generated folders (including three SOL files) but in project directory in Linux system.

[wja]

Fenix/Owl Processing
Two SRTM DEM generated for two SOL files: 20180818_161529.dat.sol & 20180818_165619.dat.sol. The remaining sol file (20180818_155139.dat.sol) does not correspond with header times.

[dac]

Navigation

Created combined sol file by opening three files using navigation library and stacking them using numpy.hstack function.

[wja]

Hypderspectral & Owl Processing
Processed with new DEM with extent of previous two DEMs combined.
The gap between sol files 161529 & 165619 occur at the start of flightline 4. Therefore no navigation data exist for this line and it cannot be mapped with APL.

SCT Values:

Flightline	Fenix SCT	Owl SCT
1	2	2
2	2	2
3	2	2
4	N/A	N/A
5	2	2

Processing all Fenix & Owl bands for flightlines 1, 2, 3 & 5 with combined sol file.

[wja]

Hyperspectral & Owl Delivery
Fenix and Owl deliveries created. Ready for delivery check.

[dac]

Fenix Delivery Check

Starting delivery check.

[dac]

Fenix Delivery Check

• SCT values look good. Checked against Owl.
• Readme needs to be updated as Level 1b for Line 4 isn't going to be included.
• Started zipping mapped files.

Once readme is updated ready to deliver.

[wja]

Fenix Delivery Check
ReadMe updated. Ready to deliver.

[dac]

Owl Delivery Check

• check_apl_cmd runs through OK
• SCT values correct
• Readme looks good
• Spectra looks a bit odd but same as for rest of campaign and explained in Readme.

Zipping mapped files then ready to deliver.

[wja]

Hyperspectral & Owl Delivery
Files were zipped successfully. Delivery has been placed on FTP slot 1 and notification e-mail has been sent to PI. Delivery finalised.

[wja]

Archiving
JSONs created and added to PostGIS. In the queue to rsync to CEDA.

[wja]

Archiving
Upload to CEDA complete (18/01/2019)

[dac]

Data archived at CEDA:

• ​https://data.ceda.ac.uk/neodc/arsf/2018/CA18_207/CA18_207-2018_230_Ontario
• ​https://data.ceda.ac.uk/neodc/arsf/raw_data/2018/CA18_207-2018_230_Ontario_raw