Opened 5 years ago

Last modified 4 years ago

#659 new flight processing

HyTES/19, flight day 174b/2019, Grosseto

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

Description

Data location: /users/rsg/arsf/arsf_data/2019/flight_data/italy/HyTES19-2019_169_Grosseto

Data arrived from Kings College London via hardisk on July 15 2019.

Scientific objective: Joint NASA and ESA campaign flying JPL’s HyTES thermal instrument over sites in Europe with a focus on crops and soil. Aim is to inform the future Land Surface Temperature Monitoring (LSTM) satellite mission. The NCEO Fenix instrument was flown alongside HyTES to provide visible – SWIR hyperspectral data.

PI: Martin Wooster

Sensors:

Fenix (requested, flown)

Change History (15)

comment:1 Changed 5 years ago by wja

Navigation Processing
*m00 nav file converted to RINEX Default_9488_0623_062003.19[no] which only contains data from this date.

comment:2 Changed 5 years ago by wja

  • Cc dac@… added

Navigation Processing
As far as I'm aware, this is not a boresite flight. However, the flight route resembles one at one location and could be useful even if it is not intended to be for boresight calibration.
SOL file produced using PPP in IPAS-TC.

comment:3 Changed 5 years ago by seg

Fenix Processing
Started processing.

SCT values identified

Flightline FENIX
1 2.00
2 1.00
3 2.00
4 2.00
5 2.00
6 1.00
7 2.00
7.00 2.00
7.01 2.00
7.02 2.00
8 1.00
9 1.00
Last edited 5 years ago by seg (previous) (diff)

comment:4 Changed 5 years ago by seg

Logsheet Creation

Log Sheets generated, flight line plot not generated so used flight KML instead.

comment:5 Changed 4 years ago by asm

Fenix Processing

Moved back the original headers and replaced the wavelengths with the new calibration file. Emptied igm, navigation and level1b dirs as well. Tried re-processing 3 bands, slow_mode=false and lines are looking good. Will create files with all bands mapped on slow mode.

comment:6 Changed 4 years ago by wja

Starting Delivery Check

comment:7 Changed 4 years ago by wja

Delivery Check

  • Deleted flihgtlines/fodis/ directory

comment:8 Changed 4 years ago by wja

Hyperspectral Delivery Check

  • Old readme template is being used. Need re-creating from the readme config (APL commands ran fine thogh check_apl_cmd)
  • Current readme has the wrong flightlines in the 'Logsheet flightline name' table on page 3
  • Add more detailed text regarding the issues in the the SWIR and flightlines with different binning
  • check_apl_cmd outputs for flightlines 4 & 5 look like they have FPS issues
  • Project/line information *XML files contain the outdated NERC-ARF information. Need to re-create with current template.

It might be easier to rerun the processing to corrent some of these issues, remember to correct the SCTs.

comment:9 Changed 4 years ago by dac

Hyperspectral Processing

  • Rerunning processing as suggested to fix issues.

comment:10 Changed 4 years ago by wja

Hyperspectral Delivery
Recreated delivery with reprocessed flightlines.
check_apl_cmd & check_fenix_spectra_py6s.py has been run - outputs in processing/

comment:11 Changed 4 years ago by dac

Hyperspectral Delivery Check

  • Removed first line as looks like it was a mistake during transit, updated screenshots and readme

Everything else looks good. Zipping files.

comment:12 Changed 4 years ago by wja

Hyperspectral Delivery
Mapped lines zipped, delivery placed on FTP slot 15 (same as previous HyTES/.19 data), delivery finalised, PI notified via e-mail.

comment:13 Changed 4 years ago by wja

Atmospheric correction
Atmospheric correction has been applied to create level2 and mapped data.

Delivered to PI on June 22nd 2020

Needs archiving at CEDA

comment:14 Changed 4 years ago by wja

Archiving
JSONs created, added to internal database.
Waiting for account with CEDA to be renewed in order to rsync

comment:15 Changed 4 years ago by wja

Archiving
Rsync to CEDA complete. Have sent an e-mail to ask for their confirmation that the data has been received.

Note: See TracTickets for help on using tickets.