Opened 14 months ago

Last modified 7 weeks ago

#663 new flight processing

HyTES/19, flight day 174a/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 (16)

comment:1 Changed 14 months 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 13 months ago by wja

  • Cc dac@… added

Navigation Processing
SOL file generated using PPP in IPAS-TC.

comment:3 Changed 13 months ago by seg

Fenix Processing
Started processing

SCT values identified

Flightline FENIX
1 2.00
2 2.00
3 2.00
4 2.00
5 1.00
6 2.00
7 2.00
Last edited 13 months ago by seg (previous) (diff)

comment:4 Changed 13 months ago by seg

Logsheet Creation

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

comment:5 Changed 11 months ago by wja

Hyperspectral Processing
Delivery created.
Still needs 2019 data quality and calibration reports.

comment:6 Changed 11 months ago by asm

Hyperspectral Delivery Check

-xml files are correct for project information but need to be updated for each line information under flightlines directory (still NERC-ARF)
-APL commands are not working
-Readme looks good but most of the SWIR is underflowing so will need to add that to the quality remarks
-SCT look good in the screenshots.
-Vegetation spectra loks good compared with 6S (a bit low in the SWIR but shape matches)

I will resume delivery check once those problems are resolved.

comment:7 Changed 10 months ago by wja

Hyperspectral Delivery
SCTs updated:

LineSCT
11.00
21.00
31.00
41.00
50.00
61.00
71.00

comment:8 Changed 10 months ago by wja

Hyperspectral Delivery
Line info XMLs upated.

comment:9 Changed 10 months ago by dac

Hyperspectral Delivery Check

Starting delivery check.

comment:10 Changed 10 months ago by dac

Hyperspectral Delivery Check

  • Readme:
    • When referring to spectral binning the phrasing using 'affected' makes it sound like a problem rather than being intentional. Suggest rewording to "A spectral binning of 4 was used for flightlines 2, 3, 4 & 5 which have 448 bands, wheras flightline 1 used a spectral binning of 1 and has 622 bands".
    • "The basestation was not used for Differential GNSS navigation processing, only Precise Point Positioning (PPP) processing." > "Precise Point Positioning (PPP) was used to process the GNSS navigation data rather than a GPS basestation, due to problems with processing the basestation data. Due to the length of the lines a similar level of accuracy was achieved using PPP."
  • In project XML BAS is listed as originator not NCEO (using old config). As the rest of the lines likely use this might be better to keep for consistency, BAS did fly data so not incorrect. Flight line XML files are OK.
  • Alignment of lines looks good, correct SCT values.
  • Spectra look good when compared to modelled spectra using Py6S checker

I'll start zipping files now, then fix the readme and deliver tomorrow.

comment:11 Changed 10 months ago by wja

Hyperspectral Delivery

  • Project XML updated
  • ReadMe Updated

comment:12 Changed 10 months ago by dac

Hyperspectral Delivery

Copied to FTP server (slot 15). Will wait for 174b and send them both together.

comment:13 Changed 9 months ago by wja

Hyperspectral Delivery
Delivery finalised, PI notified via e-mail.

comment:14 Changed 3 months 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:15 Changed 2 months ago by wja

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

comment:16 Changed 7 weeks 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.