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

[dac]

Data location: /users/rsg/arsf/arsf_data/2018/flight_data/canada/CA18_207-2018_233b_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 233 (local) but previous flight was on same UTC day so became 233b
• 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 13 owl lines and 12 fenix, navigation files don't have timestamps. Will need to find SCTs manually.
-All owl lines have T1 and T2 calibration files
-Fenix line 4 missing the hdr fiile.

[dac]

Fenix

Generated Level 1b files.

[asm]

Owl Processing

Started in order to create the level1b files.

[wja]

Basestation PPP:

Latitude	51°04'01.40139"
Longitude	-93°48'14.26917"
Ellipsoid Height	346.736

[wja]

Navigation Processing
Solution when using basestation was poor. Separation was ranging between +-2m, ambiguity fix was 0 for data acquisition.
Processing has been attempted with elevation mask of 8 degrees and L2 Phase cycles of -0.25, 0.00, 0.25 & 0.50 with no improvement.
PPP has been used to generate an acceptable solution (X and Y position separation is between +-0.025m for the majority of the flight, Z is mostly between -0.02-0.05m).
Note that this flight is ~140km away from the basestation location.

[wja]

Hyperspectral Processing
SRTM DEM created.

[dac]

Hyperspectral Processing

Started geocorrection.

[dac]

Hyperspectral Processing

Found SCT values:

Flightline	FENIX
1	2
2	2
3	2
4	1
5	2
6	2
7	2
8	2
9	1
10	2
11	2
12	2

Mapping all bands.

[dac]

Hyperspectral Processing

All bands mapped. Creating delivery.

[dac]

Hyperspectral Processing

Created delivery ready for checking.

As there were a lot of overflows and these look odd when they are masked out I didn't mask out values to create the three band mosaic so it looks better. Have detailed in readme.

[wja]

Hyperspectral Delivery Check

• Logsheet line information are for the Owl. Line 1 is present although no data processed for it.
  
• Logsheet needs renaming to CA18_207-2018_233b_Ontario.pdf.

Otherwise ready to deliver. Mapped files are being zipped.

[dac]

Hyperspectral Processing

• Redid logsheet.
• Line 1 wasn't short as initially thought so should be included in delivery. Have processed and added
• Ready for rechecking.

[wja]

Hyperspectral Delivery Check

• Logsheet plot needs to include flightline 1.
  
• Page 1 logsheet is using Owl times and locations.
  
• Page 2 logsheet flightline 1 has the wrong direction, speed etc. Unsure if this is from Owl or not.
  
• Have submitted flightline 1 mapped *bil for zipping.

[dac]

Owl Processing

Started processing mapped owl data.

[dac]

Owl Processing

Found SCT values. Mapping all bands.

Flightline	OWL
1
2	2
3	2
4	2
5	2
6	2
7	2
8	2
9	2
10	2
11	3
12	2

[dac]

Owl Processing

Started creating delivery.

[dac]

Owl Processing

Delivery created, waiting for checking.

[wja]

Owl Delivery Check
Starting delivery check.

[wja]

Owl Delivery Check

• Flightline 1 level1b should be removed.
• Logsheet:
  • X-axis labels are overlapping on logsheet plot.
  • The 'Basic Line Information' (alt, dir, hdng) and other data are off by one line (logsheet value 12 is header value 13, logsheet value 11 is header value 12 etc.). All other values on the logsheet look correct but need shifting. However these 'BLI' values corrsepond to the Fenix lines. ReadMe refers to flightline 1 as o233b021b (which matches with the Fenix line but the logsheet number, timings and locations would need changing if delivered this way).
• ReadMe:
  • No mention of missing flightline.
  • No over-/under-flows listed. Perhaps insert the following for this section:

    This flight relates to a project to observe wildfires. As such, settings for the Owl instrument (such as
    integration time) have been set to try and capture these very bright targets. Therefore the dataset
    will likely contain a high number of under- and overflows.
    

Looks good apart from that.

[dac]

Owl Delivery

• Removed over-/under-flow section of readme and replaced with suggested text.
• Fixed readme, also updated one for Fenix.
• Starting zipping mapped files.

[wja]

Owl Delivery
Owl logsheet plot flightline numbers need to be subtracted by 1.
Otherwise ready to deliver.

[wja]

Fenix & Owl Deliveries
Placed on FTP 1. Notification sent to PI (along with 225a). 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_233b_Ontario
• ​https://data.ceda.ac.uk/neodc/arsf/raw_data/2018/CA18_207-2018_233b_Ontario_raw