HyTES/19, flight day 179/2019, Berkshire

[wja]

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)

[wja]

Unpacking
Serveral sites are included in this flight:

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

[wja]

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

[wja]

Navigation Processing
Have downloaded GPS nav data 'brdc179.19n' from CDDIS's FTP. ​https://cddis.nasa.gov/Data_and_Derived_Products/GNSS/broadcast_ephemeris_data.html

[wja]

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.

[asm]

Fenix Processing

Started for assessing fenix boresight accuracy.

[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	2
4	3
5	2
6	2
7	3
8	2
9	2
10	3
11	3
12	2
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.

[seg]

Logsheet Creation

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

[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.

[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.

[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.

[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.

[dac]

Boresight Check

Values look good to me. Will update file.

[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.

[wja]

Fenix Delivery
Creating delivery

[wja]

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

• the mosaic
• data quality remarks

[wja]

Hyperspectral Delivery
Now using updated NEODAAS ReadMe.

[wja]

Hyperspectral Delivery
Updated line information to NEODAAS information.

[asm]

Hyperspectral DC

Started. A few things need changing already
-Delivery to be split in 2
-xml files for each flightline look good but the project version is outdated (NERC-ARF)
-Too many underflows, to be added at the quality remarks (I will help with this and another remarks needed to be added)
-Check_tmp_cmds looks good

I will resume tomorrow

[asm]

Hyperspectral DC

-Fenix spectra looks good compare with 6S, just low for the SWIR region specially.

I have split the delivery in two sorties:
-179a: lines 1, 6-15
-179b: lines 2-5
And have renamed files with sorties "a" and "b" accordingly as well as renaming the files. Need to sort out readme tables and data quality remarks and should be ready to be delivered.

[asm]

Hyperspectral DC

-Spectra looks good on 6S
-Sorted out readme tables, data quality remarks and recreated screensohts.
-Updated the apl commands, all checked.

This project should be ready to be delivered once the map files are happy.

[asm]

Hyperspectral DC

Mapped files were zipped accordingly. Also updated the Readmes title with its sortie. Marking this project as ready to be delivered.

[wja]

Hyperspectral Delivery
Data placed on FTP slot 15 and PI notified.
Finalised delivery (1/11/19)

[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

[wja]

Archiving
Separate project directories created for 179a and 179b deliveries in order to archive as delivered.
JSONs created, added to internal database.
Waiting for account with CEDA to be renewed in order to rsync

[wja]

Archiving
Rsync to CEDA complete. Have sent an e-mail to ask for their confirmation that the data has been received.