Opened 11 months ago

Last modified 3 months ago

#707 new flight processing

SwathS, flight day 146/2023, Grosseto

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

Description

Data location: /users/rsg/airborne/2023_arsf_data/flight_data/italy/SwathS_23-2023_146_Grosseto

Data arrived from NERC-ARF via hard drive September/October 2023

PI: Martin Wooster

Sensors:
Fenix1k (requested, flown)
IBIS ( main requested, flown)
OWL ( requested, flown)

Change History (25)

comment:1 Changed 11 months ago by jann

Notes from unpacking

OWL: Some lines don't have nav data, these are data recorded of NASA JPL's blackbody when the aircraft was stationary on the runway.

Final checks - warning about the real time navigation time stamps was flagged.

comment:2 Changed 11 months ago by wja

Navigation Processing

Basestation data converted to RINEX. All previous flights are also included in the basestation data, so just this flights data needed to be extracted (done with teqc).

GPS and GLONASS broadcast ephermides, along with precise ephemeris data accessed from CDDIS. PosPac could not access these itself.

Completed processing using the single base method.

This navigation data is a priority to be shared with collaborators working on the SWING instrument

comment:3 Changed 10 months ago by wja

Exported post-processed navigation data in ASCII at collaborator's request.

comment:4 Changed 9 months ago by jann

Missing calibration files for flight line 10, have used calibration files for flight line 9.

comment:5 Changed 9 months ago by jann

Missing calibration files for flight line 10, have used calibration files for flight line 9.

comment:6 Changed 9 months ago by jann

Radiometric calibration completed for all flightlines.

comment:7 Changed 9 months ago by wja

Fenix1k Processing

Geoaccuracy looks great, but the swath mask needs updating (looks like this will be the case for all flights between jdays 143 - 152).

comment:8 Changed 9 months ago by asm

Owl Processing

Flightlines 21 - 29 don't have GPS, are outside the navigation data and don't have usable data. Likely those were collected with the aircraft landed so will not process and move to another directory as are causing problems.

comment:9 Changed 8 months ago by asm

Owl Processing

Delivery has been created, this is now waiting for delivery check now.

comment:10 Changed 8 months ago by wja

Fenix1k Processing

Processing running through, mapping looks good.

Processing all bands.

comment:11 Changed 8 months ago by dac

Owl Delivery Check

  • check_apl_cmd ran through OK.
  • Logsheet overview image doesn't show any flightlines, also still lists aircraft as VP-FAZ rather than VP-FLB and copyright as 2021.
  • Line information also lists aircraft as VP-FAZ.

Apart from updates to logsheet and metadata is good to go. Started zipping mapped files.

comment:12 Changed 8 months ago by wja

Aircraft is VP-FBL

comment:13 Changed 8 months ago by asm

Owl Delivery

Updated image on logsheet and corrected the plane name. Thanks for bringing this to my attention.

comment:14 Changed 8 months ago by wja

Fenix Delivery Check

Starting checking

comment:15 Changed 7 months ago by wja

Fenix Delivery Check

I have done:

  • Removed *aux.xml files
  • Updated ReadMe (screenshots, filename table)
  • Removed fodis directory

Everything else looks line (bands chacked with fastQC, spectra looks fine compared to 6S, mapping looks good enough with the APL command outputs and the mapped files).

Zipping mapped, then ready to delivery.

comment:16 Changed 7 months ago by wja

Fenix1K Delivery

Added geometry files (aplcorr --atmosfile outputs) to the deliveries at PI's request.

comment:17 Changed 4 months ago by wja

Atmospheric Correction

Started pre-processing steps for ATCOR

comment:18 Changed 4 months ago by wja

Atmospheric Correction

Preprocessing complete. Reviewed microtops data from KCL

comment:19 Changed 3 months ago by wja

Atmospheric Correction

Creating new sensor definition for Fenix1K.

Calculating visibility from Microtops AOD data.

comment:20 Changed 3 months ago by wja

Atmospheric Correction

Visibility calculations per flightline (derived from microtops data):

  1. 17.55
  2. 17.16
  3. 16.79
  4. 18.42
  5. 19.03
  6. 17.18
  7. 17.00
  8. 15.94
  9. 15.32

data ignore value = 0 added to all input header files, this should avoid the obstructed swatch edge (which has been masked) from causing problems with ATCOR.

Pixel sizes vary with altitude:

  • Lines 1 - 7: ~1.8m
  • Line 8: 0.8
  • Line 9: 1.4

Processing all lines in ATCOR.

Will need to check header files, remask swath edge and map afterwards.

Last edited 3 months ago by wja (previous) (diff)

comment:21 Changed 3 months ago by wja

Atmospheric Correction

Data is currently being reprocessed in ATCOR4. So some reason each flightlines INN config file had incorrect heading values. I've open an issue about this.

comment:22 Changed 3 months ago by wja

Atmospheric Correction

Data processed through ATCOR.

Have remasked (to remove swath edge obscured by aircraft), corrected data ignore value, converted back to BIL and currently mapping the L2 data.

comment:23 Changed 3 months ago by wja

Atmospheric Correction

Data is mapped. Updated masked and mapped BIL headers for delivery.

Creating delivery.

comment:24 Changed 3 months ago by wja

Delivery created.

Awaiting Delivery Check

comment:25 Changed 3 months ago by wja

Fenix1k L2 Delivery Delivered

Checked by asm, delivered via FPT, PI notified, delivery finalised.

Last edited 3 months ago by wja (previous) (diff)
Note: See TracTickets for help on using tickets.