Opened 6 years ago

Closed 3 years ago

#640 closed flight processing (fixed)

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

Reported by: dac Owned by:
Priority: immediate Milestone:
Component: Processing: general Keywords:
Cc: Other processors:

Description (last modified by dac)

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

  • Labelled as 226 (local time) but renamed as 227a (UTC)
  • Owl calibration are stored in separate folders to capture data.
  • Missing navigation synchronisation 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)

Change History (20)

comment:1 Changed 6 years ago by dac

  • Description modified (diff)

comment:2 Changed 5 years ago by asm

Unpacking checks

-There are 14 owl lines and 3 fenix, navigation files don't have timestamps. Will need to find SCTs manually.
-All owl lines have T1 and T2 calibration files
-Dropped frames:

-Fenix: 2 incidents for f1. No log for fenix line 2.

Last edited 5 years ago by asm (previous) (diff)

comment:3 Changed 5 years ago by asm

Owl Processing

Started in order to create the level1b files.

comment:4 Changed 5 years ago by wja

Basestation PPP:

Latitude51°04'01.40051"
Longitude-93°48'14.27003"
Ellipsoid Height346.795

Looks like navigation data is for 227b, which has 16 flightlines, not 3 like is present in the 227a project directory.
There are two *.dat.000 (+ consequential data) navigation datasets. The latter (20180815_052458.dat.000, *.dat.001 & *.dat.002) does not look like they cover any data acquisition flightlines.

Solution looks good until 2:05 into recording. The antiquity fix goes to 1 and the position seperation goes to ~+-1m. This could affect the final flightlines.
All new data put in relevant project subdirectories.

Last edited 5 years ago by wja (previous) (diff)

comment:5 Changed 5 years ago by wja

Fenix/Owl Processing
SRTM DEM generated.

comment:6 Changed 5 years ago by wja

Owl Processing
Starting Owl processing.

comment:7 Changed 5 years ago by wja

Owl Processing
Level1b data reprocessed.
SRTM DEM extent has been enlarged in order to generate APL config.
Currently identifying SCT error values.

comment:8 Changed 5 years ago by wja

Owl Processing
The following SCT Values have been identified (precision of 0.1):

FlightlineSCT Value
14.80
24.20
33.60
44.60
54.30
63.80
75.40
83.80
95.70
104.80
114.40
125.20
134.60
14N/A

Flightline 14 is outside of the navigation data and is leading away from the other flightlines. Could be the route back to the airport.

Fenix Processing
All three Fenix lines have been processed, but no features can be identified in any bands.

comment:9 Changed 5 years ago by wja

Owl Delivery
Generating Owl delivery. Flightline 14 will not be included.

comment:10 Changed 5 years ago by wja

Owl Delivery
Owl delivery created. Ready for delivery check.

comment:11 Changed 5 years ago by wja

Fenix Processing
All three Fenix bands will not be processed further as they only contain noise.
For reference with Owl lines:
Fenix line 1 was recorded simultaneously to Owl line 11.
Fenix line 2 was recorded simultaneously to Owl line 12.
Fenix line 3 was recorded simultaneously to Owl line 13.

comment:12 Changed 5 years ago by dac

Owl Delivery Check

Starting delivery check.

comment:13 Changed 5 years ago by dac

Owl Delivery Check

Looks good. Just found two problems which need fixing before delivery.

  • Don't need comma after line number in readme.
  • SCT for line 5 looks a bit off, doesn't line up so well with surrounding data. Worth having another look to see if it could be improved.

comment:14 Changed 5 years ago by wja

Owl Processing
Have improved flightline 5 SCT value to 4.40.

FlightlineSCT Value
14.80
24.20
33.60
44.60
54.40
63.80
75.40
83.80
95.70
104.80
114.40
125.20
134.60
14N/A

comment:15 Changed 5 years ago by dac

Owl Delivery Check

Updated SCT value is much better than previous delivery. Ready to deliver.

comment:16 Changed 5 years ago by wja

Owl Delivery Sent
Mapped flightlines zipped. Delivery places on FTP slot 1. Notification e-mail sent to PI.

comment:17 Changed 5 years ago by wja

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

comment:18 Changed 5 years ago by wja

Archiving
Started rsync to CEDA.

comment:19 Changed 5 years ago by wja

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

Note: See TracTickets for help on using tickets.