Opened 3 months ago

Last modified 4 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 (16)

comment:1 Changed 3 months ago by wja

Serveral sites are included in this flight:

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

comment:2 Changed 3 months ago by wja

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

comment:3 Changed 3 months ago by wja

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

comment:4 Changed 7 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 7 weeks ago by asm

Fenix Processing

Started for assessing fenix boresight accuracy.

comment:6 Changed 5 weeks 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 5 weeks ago by asm (previous) (diff)

comment:7 Changed 5 weeks ago by seg

Logsheet Creation

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

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

comment:10 Changed 4 weeks ago by dac

Boresight Processing

174b also contains lines flown in a boresight pattern but with more lines. Using this and checking with the lines over Alconbury was able to get better results using 0.30 -0.80 0.50 (pitch, roll, heading).

Also tried processing with higher resolution DSM created using EA LiDAR data to see if this improved things.

Will have another look on Monday confirm these are the best values we can get out of the two flights.

comment:11 Changed 3 weeks ago by asm

Boresight Processing

Using 174b 2019 have found the best fit for 0.32 -0.85 and 0.60 (pitch, roll, heading). I think I can't get better values than this and all look good for 170 2019. Please, I recommend another member of the team to have a second look.

comment:12 Changed 3 weeks ago by dac

Boresight Check

Values look good to me. Will update file.

comment:13 Changed 2 weeks 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. Created files with all bands mapped on slow mode.

comment:14 Changed 2 weeks ago by wja

Fenix Delivery
Creating delivery

comment:15 Changed 2 weeks ago by wja

Fenix Delivery
Ready for checking. Please give me your opinion on:

  • the mosaic
  • data quality remarks

comment:16 Changed 4 days ago by wja

Hyperspectral Delivery
Now using updated NEODAAS ReadMe.

Note: See TracTickets for help on using tickets.