SwathS, flight day 223b/2021, Attleborough

[wja]

Data location: /users/rsg/arsf/arsf_data/2021/flight_data/uk/SwathS-2021_223b_Attleborough

Data arrived from Kings College London via FTP on September 20th 2021

Scientific objective: Joint NASA and ESA campaign flying JPL’s HyTES thermal instrument over sites in Europe with a focus on crops and soil.

PI: Martin Wooster

[wja]

Unpacking

Following for flagging when running the unpacking checks:

• `There has been an incident on line 14567 with 50 dropped frames recorded on file: /users/rsg/arsf/arsf_data/2021/fligh

t_data/uk/SwathS-2021_223b_Attleborough/hyperspectral/fenix/FENIX223b-21-5/capture/FENIX223b-21-5.log`

• There are fps_set in Fenix1k header files
• FPS differs in the followng hdr files:

  fps differs from fps_qpf by 0.65 in file: /users/rsg/arsf/arsf_data/2021/flight_data/uk/SwathS-2021_223b_Attleborough/
  hyperspectral/fenix/FENIX223b-21-2/capture/FENIX223b-21-2.hdr
  fps differs from fps_qpf by -0.52 in file: /users/rsg/arsf/arsf_data/2021/flight_data/uk/SwathS-2021_223b_Attleborough
  /hyperspectral/fenix/FENIX223b-21-5/capture/FENIX223b-21-5.hdr 
  fps differs from fps_qpf by 0.6 in file: /users/rsg/arsf/arsf_data/2021/flight_data/uk/SwathS-2021_223b_Attleborough/h
  yperspectral/fenix/FENIX223b-21-8/capture/FENIX223b-21-8.hdr 
  fps differs from fps_qpf by 0.6 in file: /users/rsg/arsf/arsf_data/2021/flight_data/uk/SwathS-2021_223b_Attleborough/h
  yperspectral/fenix/FENIX223b-21-10/capture/FENIX223b-21-10.hdr
  fps differs from fps_qpf by 0.6 in file: /users/rsg/arsf/arsf_data/2021/flight_data/uk/SwathS-2021_223b_Attleborough/h
  yperspectral/fenix/FENIX223b-21-11/capture/FENIX223b-21-11.hdr 
  fps differs from fps_qpf by 0.82 in file: /users/rsg/arsf/arsf_data/2021/flight_data/uk/SwathS-2021_223b_Attleborough/
  hyperspectral/fenix/FENIX223b-21-12/capture/FENIX223b-21-12.hdr
  

• The following error regaring real time nav data:

No date record ($GPZDA) found in nav file - will assume it is binary if cannot find a line starting with '$GPGGA' or '
$PRDID'.                                                                                                              
Error in /users/rsg/arsf/usr/lib/python/site-packages/arsf_unpacking/unpacking_utilities.py : write_message: Nav file 
does not have time stamps or failed to read the file using readAscii: /users/rsg/arsf/arsf_data/2021/flight_data/uk/Sw
athS-2021_223b_Attleborough/hyperspectral/fenix/FENIX223b-21-1/capture/FENIX223b-21-1.nav

[wja]

Navigation Processing

Navigation data processed using the 'SmartBase' method with the following OS basestations:

• ALDB
• ARDL
• ATTLE
• NEWR
• SNEO
• STEE
• WEYB

POSPac data quality report shows an position error RMS of < 2cm vertical and < 1cm horizontal.

[wja]

Hyperspectral Processing

Wavelengths in headers updated with:

replace_wavscale.py -w /users/rsg/arsf/calibration/2021/fenix1k/wlcal2b_vnir_1b_swir.txt hyperspectral/fenix/F*/capture/*hdr

[wja]

Hyperspectral Processing

No clear SCT error present. No offsets required.

However, line 6 part 01 has a large 'wobble' in it which has resulted in poor alignment with other lines. This could be a very slight SCT error exaggerated by the wobble, or possibly poor navigation data when the plane doesa a sharp turn. I will investiage.

[wja]

Hyperspectral Processing

Alignment looks good with minor timing corrections added to two lines only:

Line	SCT Error
6	0.06
8	0.06

Proceeding to process all bands

[wja]

Ready for checking

Delivery created, logsheet and ReadMe generated.

[dac]

Delivery Check

• edges.txt file in delivery folder - removed
• In logsheet 'SwathS/21 -' looks like it is missing something after, should it also have the jday of the flight?
• Nothing in the delivery to say the lines have been split and why - not sure if we normally do this (perhaps we should)
  • There is a lot of cloud shadow in the images, something which should be mentioned in the 'Quality Issues' section of the readme as might cause problems for the atmospheric correction.
• No overlap between lines over site to the south so difficult to evaluate alignment between liens.
• Alignment looks good. Checked against OS District Buildings data and align well with these. Only exception is in the north of lines 3 and 4 they looks slightly off but by a very small amount, not sure could get much better.
• Spectra looks good compared to Py6S simulations.

After checking text in readme and logsheet and either confirming as intended or correcting then good to go.

[wja]

Delivery Check

Have edited ReadMe and logsheet. Zipping mapped data.

[wja]

Delivered

Placed on FTP slot 5, PI notified.