Opened 4 months ago

Last modified 10 days ago

#655 new flight processing

HyTES/19, flight day 171a/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 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_20:06:27:48.840 -e 2019_06_20:15:09:15.860 +nav Default_9488_2006_062748.19n Default_9488_0509_114526.m00 > Default_9488_2006_062748.19o

comment:2 Changed 3 months ago by wja

  • Cc dac@… added

Navigation Processing
PPP processing is hanging and reporting Warning: Non-sequential IMU record times detected (-0.001) Cur Time: 369526.007 Prev Time: 369526.006.
Will continue processing other flights before returning to this.

comment:3 Changed 3 months ago by asm

Navigation Processing

Aser took over this project. Seems that the error was during the first second of navigation so processed all data except that. Processed using PPP:
-Lat and lon separation under 0.05 m (except 3 spikes of lon separation that goes to 0.1m but within range for processing)
-Position separation better than 0.02
-Everything else looking good, will copy the data across and will be ready to start Fenix processing

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

comment:4 Changed 3 months ago by seg

Fenix Processing
Started processing.
GPS end time had to be changed for

  • FENIX171a-19-1.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:5 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:6 Changed 3 months ago by seg

Fenix Processing

SCT values identified

Flightline FENIX
1.00 80.3
1.01 80.3
2 1.87
3 1.86
4 2.57
5 14.02
6 2.45
7 0.96
8 2.23

DEM file had to be increased in size to allow processing of 1.01

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

comment:7 Changed 8 weeks ago by wja

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

comment:8 Changed 7 weeks ago by asm

Hyperspectral Delivery Check

Started

comment:9 Changed 7 weeks ago by asm

Hyperspectral Delivery Check

Looks like the 2 parts from flightline 1 are showing different SCTs, this is either a problem with the SCT or the fps (more likely). It will need further processing.

Apart from that I had a quick look:
-Lines 03 and 05 look a bit wobbly in the curves of the aircraft, it could be a problem with the SCT (second decimal perhaps). If not a note should be added on the quality remarks
-APL commands are not working, the igm file has different name in aplcorr and aplmap examples
-Readme looks good, specially the data quality remarks (except content on previous messages)

comment:10 Changed 4 weeks ago by seg

Fenix Processing

Fixed FPS for Flighline 1 from 31 to 20.949. Split lines now have same sct of 80.3
Fixed FPS for Flightline 5 from 93 to 92.453.
Fixed FPS for Flightline 3 from 93 to 92.599
Fixed FPS for Flightline 7 from 93 to 92.611
Fixed FPS for Flightline 4 from 93 to 92.6085
Fixed FPS for Flightline 2 from 93 to 92.511

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

comment:11 Changed 3 weeks ago by seg

Fenix Processing

Ready for delivery check again

comment:12 Changed 12 days ago by wja

Starting Delivery Check

comment:13 Changed 12 days ago by wja

Delivery Check

  • The 'Logsheet flightline name' table in the readme has the wrong numbers lined up with the flightline names (also missing flightline 1).
  • Strange formatting in the 'Quality and issues with data ' section of the ReadMe (e.g words split over new lines).
  • Remove fodis directory (flightlines/fodis/)
  • Change the underflows in the readme to the following:
    • Line 1:
      • Part 0: Underflows from 347 - 621
      • Part 1: Underflows from 241 - 621
    • Line 2: Underflows from 1 - 6 & 174 - 447 (SWIR)
    • Line 3: Underflows from 155 - 447 (SWIR) *Line 4: Underflows from 174 - 447 (SWIR)
    • Line 5: Underflows from 1 - 7 & 174 - 447 (SWIR)
    • Line 6: Underflows from 1 - 4 & 174 - 447 (SWIR) *Line 7: Underflows from 1 - 6 & 174 - 447 (SWIR)
    • Line 8: Underflows from 1 - 7 & 174 - 447 (SWIR)

comment:14 Changed 11 days ago by wja

Delivery Check
Looks ready to delivery, once mapped BIL files are zipped.

comment:15 Changed 10 days ago by wja

Hyperspectral Delivery
Zipping mapped data

comment:16 Changed 10 days ago by wja

Delivery Sent to PI
Delivery finalised

Note: See TracTickets for help on using tickets.