Opened 5 years ago

Closed 3 years ago

#639 closed flight processing (fixed)

CA18/208, flight day 225a/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_224a_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 224b (local time) but renamed as 225a (UTC)
  • Missing navigation synchronisation data
  • Fenix line 9 didn't have a log file so made a dummy one for renaming
  • 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 (24)

comment:1 Changed 5 years ago by dac

  • Description modified (diff)

comment:2 Changed 5 years ago by asm

Unpacking checks

-There are 12 owl lines and 12 fenix, navigation files don't have timestamps. Will need to find SCTs manually.
-Only T2 cal files for flightline 1, 3 and 4. There is a different of roughly ~45 minutes between line 4 and last line so this is above the 30 minutes window that Specim suggests.
-Dropped frames:

-Fenix: 2 incidents for f8, 2 for f5.
-Owl: 3 for o1, 2 for o3, 5 for o4, 1 for o5, 28 for o6, 4 for o8, 2 for o9, 1 for o10, 3 for o11 and 1 for o12

comment:3 Changed 5 years ago by asm

Owl processing

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

comment:4 Changed 5 years ago by asm

Owl Processing

Started in order to create the level1b files.

comment:5 Changed 5 years ago by wja

Navigation Processing
Basestation PPP identified as:

Latitude51°04'01.40004"
Longitude-93°48'14.26963"
Ellipsoid Height346.818

comment:6 Changed 5 years ago by wja

Navigation Processing
GNSS/IMU processed in IPAS TC.
Height position separation exceeds 0.05 in places but otherwise solution looks good.
RINEX, GPB, PPP and SOL put in relevant locations in the project directory.

comment:7 Changed 5 years ago by wja

Fenix/Owl Processing
SRTM DEM generated.

comment:8 Changed 5 years ago by wja

Owl Processing
Starting Owl processing.
This is a night flight, so once Owl SCT values are identified, Owl flightlines will be used to find SCTs for Fenix.

comment:9 Changed 5 years ago by wja

Owl Processing
Owl SCT values (0.05 precision):

14.55
24.55
35.00
43.80
54.50
65.35
74.55
85.45
94.50
104.90
114.40
125.35

Will identify Fenix SCT values Owl data using these offsets.

comment:10 Changed 5 years ago by wja

Fenix Processing
Lines 1-3 & 6-7 do not appear to have any features. These will be omitted from further processing.
Fenix SCT values identified:

1N/A
2N/A
33.00
42.75
5N/A
6N/A
7N/A
838.35
9N/A
10108.40
113.30
123.00

Processing all bands.
Will start creating Fenix & Owl deliveries.

comment:11 Changed 5 years ago by wja

Fenix/Owl Delivery
Processing complete, generating delivery.
Creating logsheet.

comment:12 Changed 5 years ago by wja

Owl & Fenix Delivery
Owl and Hyperspectral deliveries are ready for delivery check.

comment:13 Changed 5 years ago by dac

Fenix Delivery Check

Starting deliver check.

comment:14 Changed 5 years ago by dac

Fenix Delivery Check

  • Readme looks good.
  • Removed fodis directory
  • Ran check_apl_cmd using bands used for quicklooks, can't see much but features which are visible line up between lines.
  • Data are very noisy but this is explained in the readme.
  • Started zipping files.

comment:15 Changed 5 years ago by dac

Owl Delivery Check

Starting delivery check.

comment:16 Changed 5 years ago by wja

Owl Delivery Check
Reprocessed flightline 7. Navigation and mapped data with correct SCT value has been added to delivery.

comment:17 Changed 5 years ago by wja

Owl Delivery
Zipped mapped flightlines.

comment:18 Changed 5 years ago by dac

Owl Delivery Check

Resuming delivery check.

comment:19 Changed 5 years ago by dac

Owl Delivery Check

  • Results from check_apl_cmd look better now navigation has been updated for line 7. Existing metadata is fine as lists the correct SCT value.
  • Everything else in delivery looks good

Ready to deliver.

comment:20 Changed 5 years ago by wja

Fenix & Owl Deliveries
Placed on FTP 1. Notification sent to PI (along with 233b). Delivery finalised.

comment:21 Changed 5 years ago by wja

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

comment:22 Changed 5 years ago by wja

Archiving
Started rsync to CEDA.

comment:23 Changed 5 years ago by wja

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

Note: See TracTickets for help on using tickets.