Opened 7 weeks ago

Last modified 5 days ago

#661 new flight processing

HyTES/19, flight day 179/2019, Berkshire

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


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


Fenix (requested, flown)

Change History (9)

comment:1 Changed 7 weeks ago by wja

Serveral sites are included in this flight:

  • Duxford
  • Sheepdrove
  • Hendred
  • Grafton Water
  • Alconbury
  • The Fens

comment:2 Changed 7 weeks ago by wja

Navigation Processing
OS Basestation RINEX data downloaded for stations HUNG, NEWR, OXFR, PETE & SNEO as recorded on logsheet.

comment:3 Changed 7 weeks ago by wja

Navigation Processing
Have downloaded GPS nav data 'brdc179.19n' from CDDIS's FTP.

comment:4 Changed 3 weeks ago by wja

  • Cc dac@… added

Navigation Processing
This flight includes three passes over Alconbury - presumably for boresight calibration.

Position Seperation:

  • Latitude data is between -0.06 and -0.05m between 4500 and 6000 seconds into the nav file.
  • Altitude data is between 0.05 and 0.09m between 6100 and 7700 seconds into the nav file.

SOL file has been produced using PPP processing in IPAS-TC.

comment:5 Changed 2 weeks ago by asm

Fenix Processing

Started for assessing fenix boresight accuracy.

comment:6 Changed 6 days ago by asm

Fenix Processing

Flightline 4 had issues with the navigation. Time goes backwards in navigation file at epoch 1044 Selected to force processing and no problems were found. SCT:

Flightline SCT
1 2
2 2
3 1
4 3
5 2
6 2
7 2
8 2
9 1
10 2
11 2
12 1
13 2
14 1
15 2

Boresight values look very good, same than those used in 2018. I will double check if small changes can improve the results but the values look very much correct.

Last edited 6 days ago by asm (previous) (diff)

comment:7 Changed 6 days ago by seg

Logsheet Creation

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

comment:8 Changed 6 days ago by asm

Fenix Processing

Boresight lines are 7, 8 and 9. Looks like there is no pitch and roll errors between lines 7 and 9. Line 8 seems a bit off but within limits, it does not look like an error with pitch and roll. Tried different headings from the original 0.55; tried a few from 0.50 to 0.62 and does not change much the output.

comment:9 Changed 5 days ago by asm

Fenix Processing

Heading 0.50 rather than 0.55 improves a little but it is a bit difficult with only 3 usable lines. Pitch and roll are maintained, any changes seem not to improve the accuracy. Values seem within acceptable limits.

Boresight values: 0.40 -0.76 0.50 (pitch, roll and heading)
Once checked by other member of the team, the csv needs to be updated.

Note: See TracTickets for help on using tickets.