Opened 6 years ago
Last modified 6 years ago
#628 new flight processing
GB18_00, flight day 129/2018, Boresight
Reported by: | mark1 | Owned by: | |
---|---|---|---|
Priority: | immediate | Milestone: | |
Component: | Processing: general | Keywords: | |
Cc: | Other processors: |
Description (last modified by dac)
Data location: /users/rsg/arsf/arsf_data/2018/flight_data/nerc-arf_internal/GB18_00-2018_129_Boresite_Calibration_Wooster
Data arrived from NERC-ARF via external hard disk on 15/05/18.
Delivery of owl data was requested for GB18/196.
Scientific objective: Boresight
Priority: Urgent
PI: NERC-ARF (Boresight) / Martin Wooster (Procesed Owl)
Sensors:
- Fenix (requested)
- OWL (requested)
Change History (29)
comment:1 Changed 6 years ago by mark1
comment:2 Changed 6 years ago by mark1
Basestation PPP processing:
Latitude: 52 04 27.10312
Longitude: -0 37 24.83725
Ell Height: 149.835m
NOTE: above are for the ARF basestation which in the end we did not use (we used St Neots) with:
Latitude: 52 11 07.31238
Longitude: -0 06 44.99323
Ell Height: 120.016
comment:3 Changed 6 years ago by mark1
Ended up using the St Neots basestation rather than the ARF one as it was closer to the survey site.
comment:4 Changed 6 years ago by wja
Fenix Processing
Fenix line 10 has same starting time and ending time. Need to correct for or not process it.
comment:5 Changed 6 years ago by wja
Fenix processing
Also the same problem for fenix lines 06 and 11. Moving them to a dir called hyperspectral/problematic_lines for now (to show Will how to process - asm writing here).
comment:6 follow-up: ↓ 7 Changed 6 years ago by wja
Fenix
For processing the boresight until the new cal is done, we have replaced the wavelenghts with the 2016 cal. Will use also this one for the calibration (asm)
comment:7 in reply to: ↑ 6 Changed 6 years ago by asm
Replying to wja:
Fenix
For processing the boresight until the new cal is done, we have replaced the wavelenghts with the 2016 cal. Will use also this one for the calibration (asm)
Correction, used the 2015 calibration (we did not fly on 2016).
comment:8 Changed 6 years ago by asm
Also run the unpacked checks:
-Fenix line 13: 2 incident with a total of 25 dropped frames
-Fenix line 14: 2 incident with a total of 59 dropped frames
-Fenix line 18: 2 incident with a total of 32 dropped frames
-fps differs from fps_qpf by 0.631 in file: fenix 14
-Owl lines 2 and 6 have 1 dropped frame incident
-No use owl nav as well
-No GPS starting point and ending point for Owl line 1
comment:9 Changed 6 years ago by asm
Fenix Processing
Added a calculated ending time for 6, 10 and 11 and put them with the others for processing (original headers are safe in the usual place). Recreated the APL config file, all looking good.
comment:10 Changed 6 years ago by asm
Owl Processing
Added GPS Start Time to owl hdr 1 (it was there but it was not GPS time but only UTC start time). Recreated the APL config that now contais the owl sensor as well.
comment:11 Changed 6 years ago by wja
Fenix Processing
Currently finding flightline SCT values.
comment:12 Changed 6 years ago by dac
Owl Processing
Took over owl processing - started calibration.
comment:13 Changed 6 years ago by wja
Fenix Processing
SCT values found:
Flightline | SCT Value |
1 | 41.33 |
2 | 2.53 |
3 | 3.09 |
4 | 3.64 |
5 | 48.31 |
6 | 4.23 |
7 | 3.39 |
8 | 3.30 |
9 | 3.66 |
10 | 5.74 |
11 | 38.5 |
12 | 2.20 |
13 | 31.19 |
14 | 3.39 |
comment:14 Changed 6 years ago by dac
Owl Processing
First three lines of Owl don't contain usable data. Recording on logsheet starts at file #4.
comment:15 Changed 6 years ago by wja
Fenix Processing
SCT value for flightline 10 (5.74) displays some error (wobble) but is clearly more accurate than values ±0.01.
comment:16 Changed 6 years ago by dac
Owl Processing
SCT values for all lines are between 4 - 6 seconds (see ~dac/scratch_network/nerc-arf-processing/2018-129_owl_scts.ods).
Have run through all lines using SCTs of 4 - 6 seconds at 0.1 s intervals. Handing back to Aser to continue processing.
comment:17 Changed 6 years ago by asm
Owl Processing
Have found SCT values:
Flightline | OWL |
4 | 4.72 |
5 | 4.53 |
6 | 4.69 |
7 | 5.09 |
8 | 5.00 |
9 | 4.35 |
10 | 4.98 |
11 | 4.85 |
12 | 4.03 |
13 | 4.82 |
14 | 5.01 |
15 | 3.84 |
16 | 5.67 |
17 | 4.17 |
comment:18 Changed 6 years ago by asm
Owl Boresight
Owl boresight values:
Pitch: 0.28
Roll: 0.17
Heading: 0.20
Please have a check and confirm. The SCT for lines 14 and 15 were a bit difficult to find so might be a bit unreliable. Flightline 13 was however very clear.
comment:19 Changed 6 years ago by wja
Fenix Processing
The FPS and associated SCT values have been identified for the following flightlines:
Flightline | SCT Value | FPS Value |
2 | 2.44 | 54.95 |
3 | 2.99 | 54.95 |
4 | 3.51 | 30.95 |
6 | 4.10 | 30.96 |
7 | 3.31 | 30.95 |
Note that the FPS values are -0.05 from the original in the header (apart from flightline 6). Might be a good starting point to note if this issue arises again.
comment:20 Changed 6 years ago by wja
Fenix processing
Fenix boresight values:
Pitch: 0.45
Roll: -0.75
Heading: 0.50
I found these buy processing the flightlines with SCT and FPS values documented on this ticket previously. Flightline 2 seems to have a constant offset that does not seem to be boresight related.
These may be improved whilst I have a look at more flightlines.
comment:21 Changed 6 years ago by wja
Fenix Processing
Additional flightline SCT / FPS values:
Flightline | SCT Value | FPS Value | |
12 | 2.2 | 21 | same FPS as original header. |
13 | 31.19 | 21 | same FPS as original header. |
Revised Fenix Boresight values:
Pitch: 0.40
Roll: -0.76
Heading: 0.55
comment:22 Changed 6 years ago by wja
Fenix Processing
Fenix pitch boresight value falsely reported as -0.40 (now corrected) when it is in fact +0.40.
To clarify, Fenix Boresight values:
Pitch: 0.40
Roll: -0.76
Heading: 0.55
comment:23 Changed 6 years ago by dac
Owl Processing
Processed Owl data was requested for this flight. Mapping all bands.
comment:24 Changed 6 years ago by dac
Owl Processing
Delivery has been created ready to be checked but still needs a logsheet, which will need manual edits.
comment:25 Changed 6 years ago by wja
Owl Delivery Check
- PI Details: NERC internal flight.
- Two DEMs - ASTER & EA LIDAR, APL config used ASTER only.
- Level1b flightlines 1-3 are present in delivery but not processed further (no level3 or screenshot). These are small in size - overwritten by aux.xml files?
- Bands 81+ on flightline 13 do not look right.
- Overflows don't seem to be more prevelant in bands specified in Read_Me (there's a roof that overflows in many bands).
- Issues with plotting owl spectra vs Py6s due to flightline 1 excisiting as level1b but not level3 - will redo when this is changed/clarified. *
- Logsheet currently being produced.
Edit: I now know that Py6S does not run on OWL wavelengths - disregard that point.
comment:26 Changed 6 years ago by dac
Owl Processing
Produced logsheet and fixed the following issues:
- PI for delivery is Martin Wooster
- Removed EA DEM, was used for boresight processing but redid for delivery to use standard ASTER
- Removed lines 1 - 3
Ready for another check.
comment:27 Changed 6 years ago by wja
Owl Delivery Check
All looks good.
Ready to deliver.
comment:28 Changed 6 years ago by dac
- Description modified (diff)
comment:29 Changed 6 years ago by dac
Owl
Delivered via FTP slot 1.
Fenix and Owl are missing Specim timestamps. Have informed Gary and James.
Also, Owl line 1 is missing the nav file completely (but logsheet says lines 4 onwards are the ones to use)