Opened 4 months ago
Last modified 4 weeks ago
#652 new flight processing
HyTES/19, flight day 168/2019, Grosseto
Reported by: | wja | Owned by: | |
---|---|---|---|
Priority: | immediate | Milestone: | |
Component: | Processing: general | Keywords: | |
Cc: | Other processors: |
Description (last modified by wja)
Data location: /users/rsg/arsf/arsf_data/2019/flight_data/italy/HyTES19-2019_168_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 (17)
comment:1 Changed 4 months ago by wja
- Description modified (diff)
comment:2 Changed 4 months ago by wja
comment:3 Changed 4 months ago by wja
Unpacking
No GPS location for Fenix flightline 1.
comment:4 Changed 3 months ago by wja
Navigation Processing
IPAS SOL file produced using Precision Point Processing using IPASTC.
comment:5 Changed 3 months ago by wja
Navigation Processing
Note that processing has been done on 20190617_083415.dat.*. There is an additional data file (20190617_102656.dat.000) but it does not contain data during the flihgt (start = 10:27, end = 10:34 and last Fenix line was recorded at 9:58).
comment:6 Changed 3 months ago by seg
Fenix Processing
Started. Fenix Nav file not working. Holding for now while waiting for bore-sight
comment:7 Changed 3 months ago by seg
Logsheet Creation
Log Sheets generated, flight line plot not generated so used flight KML instead.
comment:8 Changed 3 months ago by seg
Fenix Processing
SCT values identified
Flightline | FENIX |
1 | 56.30 |
2 | 1.85 |
3 | 2.55 |
4 | 1.42 |
5 | 130.39 |
comment:9 Changed 2 months ago by dac
Fenix Processing
Looks like one of the lines could have a framerate issue. Need to resolve this before mapping all bands.
comment:10 Changed 8 weeks ago by wja
Hyperspectral Processing
Issues with flightlines:
- Line 2 & 3: looks like the wrong FPS was used in the processing.
- Line 5: Bad SCT - perhaps a FPS issue?
comment:11 Changed 7 weeks ago by seg
Fenix Processing
Issues with flightlines FPS:
- Line 2 FPS changed from 31 to 30.944
- Line 3 FPS changed from 93 to 92.5415
- Line 5 FPS changed from 93 to 92.715
- Line 4 FPS Changed from 93 to 92.419
comment:12 Changed 6 weeks ago by wja
Delivery Check
Starting delivery check
comment:13 Changed 6 weeks ago by wja
Delivery Check
- fodis/ directory needs removing
- Old files in line_information/, navigation/, need removing. New files need renaming so they don't contain the SCT value in the name.
- Some of the misnamed BIL files in navigation/ do not have HDRs
- *.xml is missing in project_information/. Use aplxml.py --meta_type p --project_dir [PATH] --output [PATH] --config_file [PATH] --lev1_dir [PATH] --igm_dir [PATH] to produce it.
- Remove *aux.xml file in dem/
- `check_apl_cmd ran through fine. But SCTs (or FPS) look wrong on flightlines 1 & 3 - is it using values before the conversion?
Let me know when this is fixed
comment:14 Changed 5 weeks ago by seg
Delivery Check
Problems from above comment resolved
comment:15 Changed 4 weeks ago by wja
Delivery Check
Few minor changes:
- Table in logsheet with 'Logsheet flightline name' hs the wrong flightline names.
- Update the data quality text in the ReadMe
comment:16 Changed 4 weeks ago by wja
Issues resolved
Ready to Deliver
comment:17 Changed 4 weeks ago by asm
Fenix Delivery
Project delivered, finalised and notification sent to PI on 5th November 2019.
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: