Opened 5 years ago
Last modified 4 years ago
#653 new flight processing
HyTES/19, flight day 169/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 (22)
comment:1 Changed 5 years ago by wja
comment:2 Changed 5 years ago by wja
Navigation Processing
PPP processing in IPAS-TC hung at 57% of the reverse process step. Will return to processing this.
comment:3 Changed 5 years ago by wja
Navigation Processing
PPP processing completed using IPAS-TC. SOL file generated.
comment:4 Changed 5 years ago by wja
- Cc dac@… added
comment:5 Changed 5 years ago by seg
Fenix Processing
Started processing
GPS end time had to be changed for
- FENIX-169-12.hdr
- FENIX-169-14.hdr
- FENIX-169-3hdr
- FENIX-169-4hdr
- FENIX-169-6hdr
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
comment:6 Changed 5 years ago by seg
Fenix Processing
SCT values identified
| Flightline | FENIX |
| 1 .00 | 4 |
| 1.01 | 4.4 |
| 1.02 | 5.1 |
| 2 | 3.2 |
| 3 | 79.7 |
| 4 | 12.4 |
| 5 | 15.7 |
| 6 | 67 |
| 7 | 3.2 |
| 8 | 2.7 |
| 10 | 3.2 |
| 11 | 2.6 |
| 13.00 | 4.4 |
| 13.01 | 5 |
| 13.02 | 5.7 |
| 14 | 159.9 |
| 15 | 4 |
| 16 | 2.9 |
| 17 | 3.4 |
Flight Lines 9 and 12 were broken flightlines so will not be processed
comment:7 Changed 5 years ago by seg
Fenix Processing
Possible FPS issues, requires other opinion
comment:8 Changed 5 years ago by wja
Fenix Prcoessing
Checking
comment:9 Changed 5 years ago by wja
Fenix Processing
I reprocessed 3-band lines and found:
- Flightlines 1, 13 & 14 look like there is a Frames per Second (FPS) error.
- It is hard to initially tell if lines 7, 8, 10, 11, 15, 16 & 17 have FPS errors.
- Lines that look fine: 2, 3, 4, 5 & 6.
Probably best to manually determine a suitable FPS value (can be changed in the Fenix header files grep *hdr -e 'fps =').
Lines 1 & 13 have FPS values of 79.000.
All other lines have values of 27.000.
Perhaps it is worth see if FPS values of 27.000 works well with lines 1 & 13 (two of the three immediately visible FPS errors).
Also note that if a line is split (e.g lines 1 & 13), all parts should have the same SCT values.
comment:10 Changed 5 years ago by wja
Hyperspectral Process
I have changed the FPS of lines 1 & 13 from 79.000 to 27.000 and processed all lines.
The new FPS for lines 1 & 13 is clearly worse. However, the reprocessed lines 14, 15, 16 & 17 also show significant SCT (and/or possible FPS errors).
Will continue to investigate.
comment:11 Changed 5 years ago by wja
Hyperspectral Processing
Line 13 FPS is 78.750 with an SCT of 3.2
comment:12 Changed 5 years ago by wja
Hyperspectral Processing
Line 1 FPS is 78.750 with SCT of 2.75
comment:13 Changed 5 years ago by wja
Hyperspectral Processing
Line 14 FPS is 27.025 with SCT of 158.98
comment:14 Changed 5 years ago by wja
Hyperspectral Processing
| Line | SCT | FPS (if different) |
| 1 | 2.75 | 78.750 |
| 2 | 2.20 | |
| 3 | 78.70 | |
| 4 | 11.20 | |
| 5 | 14.70 | |
| 6 | 66.00 | |
| 7 | 2.20 | |
| 8 | 1.70 | |
| 9 | - | - |
| 10 | 2.20 | |
| 11 | 1.60 | |
| 12 | - | - |
| 13 | 3.20 | 78.750 |
| 14 | 158.98 | 27.025 |
| 15 | 3.00 | |
| 16 | 1.90 | |
| 17 | 2.40 |
Processing all bands
comment:15 Changed 5 years ago by wja
Hyperspectral Delivery
Ready for checking
comment:16 Changed 5 years ago by asm
Hyperspectral Delivery Check
Started.
comment:17 Changed 5 years ago by asm
Hyperspectral Delivery Check
-Replaced the hyperspectral data quality report with the latest one up to date.
-Renamed ".bil.jpg" screneshots to ".jpg"
-APL commands run without problems showing good overlaps (fine combination of SCT and FPS)
-All xml files have been updated to NCEO references
-Vegetation spectra shape matches 6S, only low levels in SWIR
I will start zipping files now.
comment:18 Changed 5 years ago by asm
Hyperspectral Delivery Check
Mapped files have been zipped just fine. Marking this project as ready to be delivered.
comment:19 Changed 5 years ago by wja
Hyperspectral Delivery
Data placed on FTP slot 15 and PI notified.
Finalised delivery (1/11/19)
comment:20 Changed 4 years ago by 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
comment:21 Changed 4 years ago by wja
Archiving
JSONs created, added to internal database.
Waiting for account with CEDA to be renewed in order to rsync
comment:22 Changed 4 years ago by wja
Archiving
Rsync to CEDA complete. Have sent an e-mail to ask for their confirmation that the data has been received.
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: