Opened 4 months ago

Last modified 2 weeks ago

#654 new flight processing

HyTES/19, flight day 170/2019, Grosseto

Reported by: wja Owned by: wja
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 (17)

comment:1 Changed 4 months ago by wja

Unpacking
No logsheet for '170' is available. Will check if this is falsely labeled or if James has additional logsheets.

comment:2 Changed 4 months ago by wja

Navigation Processing
Basestation data converted to RINEX. Of the three RINEX files (which contain multiple days of data), a file for this date has been created with the following command:

teqc -st 2019_06_19:07:16:26.290 -e 2019_06_19:14:27:39.700 +nav Default_9488_1906_071626.19n Default_9488_0509_114526.m00 > Default_9488_1906_071626.19o

comment:3 Changed 3 months ago by wja

Navigation Processing
Two DAT files are present:

  • 20190619_080344.dat.000: SOL generated using PPP.
  • 20190619_115406.dat.000: This data is recorded after Fenix data was collected. However, a SOL has been processed as it might be needed for HyTES processing. The quality of this SOL is not good for the first ~2250 seconds of the nav data (until 12:32PM) - specifically, the position separation of longitude is poor and exceeds 0.05.
Last edited 3 months ago by wja (previous) (diff)

comment:4 Changed 3 months ago by wja

  • Owner set to wja
  • Status changed from new to assigned

comment:5 Changed 3 months ago by wja

  • Cc dac@… added
  • Status changed from assigned to new

comment:6 Changed 3 months ago by seg

Fenix Processing
Started processing.
Added folder post_nav_not _usable and put in the SOL file that was not usable for processing has been put in here
GPS end time had to be changed for

  • FENIX-170-19-4.hdr
  • FENIX-170-19-8.hdr

This was because the start time was the same as the end time. Minute was added to end time for these files to allow generation of config file

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

comment:7 Changed 3 months ago by seg

Logsheet Creation

Log Sheets generated, flight line plot not generated and no KML file either so there is no plot at the moment

comment:8 Changed 3 months ago by seg

Fenix Processing

SCT values identified

Flightline FENIX
1 3.40
2 2.2
3 2.9
4 110.8
5 2.8
6 3.3
7 3.9
8 61.14
9 3.1
10.00 4.2
10.01 4.6
10.02 5.2
10.03 5.3

Flightline 10.04 entirely in ocean and therefore was unable to find sct value

comment:9 Changed 8 weeks ago by wja

Hyperspectral Delivery

Created delivery.
Flightline 10 is split into parts which have different SCT values, this probably means this line in fact has a FPS issue.

comment:10 Changed 6 weeks ago by asm

Fenix Processing

Found correct values for lines 9 and 10

flightline fps SCT
9 78.74 2.08
10 78.74 2.87

Note that the SCT were found with the latest APL version that works on fedora29. The other lines SCT are incorrect in this version and need to use APL version with f21 compatibility (also they need refining, most of them need the second decimal to remove remaining offset).

comment:11 Changed 4 weeks ago by asm

Fenix Processing

Most of the SCTs needed refining. Found new values:

Flightline FENIX
1 2.46
2 1.27
3 1.91
4 109.8
5 1.85
6 2.3
7 2.89
8 60.17
9 2.08
10.00 2.87

I will create a delivery with the new values.

Last edited 4 weeks ago by asm (previous) (diff)

comment:12 Changed 4 weeks ago by asm

Fenix Processing

Mapped all Fenix bands. Created delivery and readme. Updated the logsheet with a flight overview. Project is ready for DC.

comment:13 Changed 3 weeks ago by wja

Performing delivery check

comment:14 Changed 3 weeks ago by wja

Delivery Check

  • No project information XML, need to run aplxml.py.

Everything else looks good, ready to delivery after this has been added and mapped data has been zipped.

comment:15 Changed 3 weeks ago by asm

Fenix Delivery

Project xml file created.

comment:16 Changed 3 weeks ago by wja

Ready to deliver

comment:17 Changed 2 weeks ago by asm

Fenix Delivery

Project delivered, finalised and notification sent to PI on 22nd November 2019.

Note: See TracTickets for help on using tickets.