CA18/208, flight day 233a/2018, Ontario, Canada

[dac]

Data location: /users/rsg/arsf/arsf_data/2018/flight_data/canada/CA18_207-2018_233a_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

• Was originally labelled as 232b (local) renamed 233a (UTC)
• No header for owl line 232b-18_232b-18_2018-08-21_02-24-43 so removed
• Missing Owl calibration data
• 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 11 owl lines and 10 fenix.
-All owl lines have T1 and T2 calibration files
-Log for fenix line 8 is missing

[dac]

Fenix

Generated Level 1b files.

[asm]

Owl Processing

Started in order to create the level1b files.

[wja]

Navigation Processing
Basestation PPP:

Latitude	51°04'01.40040"
Longitude	-93°48'14.26961"
Ellipsoid Height	346.805

GNSS /IMU data processed. SOL solution looks good.

[wja]

Hyperspectral Processing
SRTM DEM created.

[wja]

Fenix/Owl Processing
Starting level 3 processing.
Spatial resolution: Fenix = 4m, Owl = 3m.
Owl SCT values:

Flightline	SCT (")
1	N/A
2	2.00
3	N/A
4	2.00
5	3.00
6	2.00
7	2.00
8	2.00
9	3.00
10	2.00
11	2.00

Owl flightlines 1 & 3 have been omitted from further processing as they are too small (header durations are 25" & 8", respectively).
Have processed all Owl bands and have started creating delivery.

[wja]

Fenix Processing
Fenix SCT values:

Flightline	SCT (")
1	N/A
2	N/A
3	1.00
4	2.00
5	2.00
6	2.00
7	2.00
8	N/A
9	2.00
10	2.00

Flightlines 1, 2 & 8 are featureless and just contain noise. The remainder of the flights contain some features of lights and fire in bands >400 (this is a night time flight). The SCT values have been found where possible by refering to the processed mapped Owl data.

[wja]

Fenix/Owl Processing
All suitable mapped data has been processed with all bands.
Screenshots and GeoTiff mosaic have been generated.
Continuing to populate delivery.

[wja]

Fenix & Owl Deliveries
Deliveries have been generated for Fenix & Owl data. Awaiting delivery check.
Fenix mosaic uses bands 400, 465, 600. This is documented in Read_Me.

[dac]

Fenix Delivery Check

Starting delivery check

[dac]

Fenix Delivery Check

• Suggest this updated text for readme:

This flight relates to a project to observe wildfires and occurred at night. The integration time of the instrument was set to allow data of the fires to be captured without saturating. However, this is resulted in a very low signal for features which don't have a high emissivity. No features in any bands were identified in flightlines 1, 2 & 8 and have therefore been omitted from processing.
Furthermore, the bands present in the quicklook and mosaic images are present in the following
table:

• Need to make sure same band combination are used for other flights.
• Renamed mosaic f233a_3b_mapped_utm15n.tif to f233a_3b_mapped_utm15n_3band.tif
• There were more files in the level1b directory than needed some without headers:

  Checking BIL files in: ./flightlines/level1b                                    
  Could not open ./flightlines/level1b/f233a041b.bil_mask.bil to check size. Possibly the header file is missing
  Could not open ./flightlines/level1b/f233a041b.bil_mask-badpixelmethod.bil to check size. Possibly the header file is missing
  Could not open ./flightlines/level1b/f233a091b.bil_mask.bil to check size. Possibly the header file is missing
  

• Extra files were much older than the delivery data so removed them.
• Didn't run check against simulated spectra as doesn't make sense for this. Looked at some spectra from fires and they look good.
• Fixed '&' in project information XML. Also updated project info in database to use 'and' instead to avoid this problem for future flights.

Started zipping mapped files. Once readme is updated ready to deliver.

[wja]

Fenix Delivery
Read_Me amended. Mapped files zipped successfully. Delivery has been hardlinked onto FTP slot 1.
Will notify PI when Owl delivery is ready to deliver.

[dac]

Owl Delivery Check

Starting delivery check.

[dac]

Owl Delivery Check

• check_apl_cmd ran through fine and outputs look good.
• Renamed mosaic to add '_3band' for consistency with previously delivered data.

Started zipping mapped files, once these are done ready to deliver.

[wja]

Fenix & Owl Delivery
Fenix & Owl deliveries are both on FTP slot 1. Notification e-mail sent to PI.
Deliveries 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_233a_Ontario
• ​https://data.ceda.ac.uk/neodc/arsf/raw_data/2018/CA18_207-2018_233a_Ontario_raw