Opened 9 years ago
Last modified 8 years ago
#611 new flight processing
RG15/18, flight day 290a, Ribble — at Version 16
Reported by: | asm | Owned by: | |
---|---|---|---|
Priority: | immediate | Milestone: | 2015 data processing completion |
Component: | Processing: general | Keywords: | |
Cc: | Other processors: |
Description (last modified by dac)
Data location: /users/rsg/arsf/arsf_data/2015/flight_data/uk/RG15_18-2015_290a_Ribble
Data arrived from ARSF via SATA disk on 26/10/2015.
Scientific objective:
Priority: Unknown
PI: Andrew Tyler
Also offered PI EA LiDAR with project. To be delivered at same time (exact format to be determined).
Sensors:
- Fenix (requested)
- RCD (not flown)
- Leica LIDAR (requested)
- Leica LIDAR FWD (not flown)
- Owl (requested)
Change History (16)
comment:1 Changed 9 years ago by asm
- Description modified (diff)
comment:2 Changed 9 years ago by asm
- Description modified (diff)
comment:3 Changed 9 years ago by dac
comment:4 Changed 9 years ago by dac
Fenix
Replaced wavelengths and ran through radiometric calibration using aplcal to get a better idea of data quality.
comment:5 Changed 9 years ago by dac
Fenix
Level 1b files sent to PIs via FTP for quality checking before proceeding with processing.
comment:6 Changed 8 years ago by dac
- Description modified (diff)
- Summary changed from RG15/08, flight day 290a, Ribble to RG15/18, flight day 290a, Ribble
comment:7 Changed 8 years ago by dac
- Milestone set to 2015 data processing completion
comment:8 Changed 8 years ago by dac
Started navigation processing.
comment:9 Changed 8 years ago by dac
Navigation processing
Basestation PPP result for BLAP
lat | 53 46 36.94753 |
long | -3 02 05.890607 |
height | 66.2 |
comment:10 Changed 8 years ago by dac
Navigation processing
Good position separation result obtained with default parameters.
comment:11 Changed 8 years ago by dac
Hyperspectral
Processed all files using updated aplnav and default SCT of 1 second. Some lines are off so will try with 0 second offset instead.
comment:12 Changed 8 years ago by dac
LiDAR
Started LiDAR processing.
comment:13 Changed 8 years ago by dac
Hyperspectral
The default offset of 1 didn't work for all lines so needed to use 0:
Flightline | Fenix SCT |
1 | 0 |
2 | 0 |
3 | 1 |
4 | 1 |
5 | 1 |
6 | 0 |
7 | 1 |
8 | 1 |
9 | 1 |
10 | 1 |
11 | 1 |
12 | 1 |
13 | 1 |
14 | 1 |
15 | 1 |
16 | 1 |
17 | 1 |
18 | 1 |
19 | 1 |
20 | 1 |
21 | 1 |
Mapping all bands.
comment:14 Changed 8 years ago by dac
Hyperspectral
Bands mapped - making delivery.
comment:15 Changed 8 years ago by lah
Fenix DC
- Do we need Eagle & Hawk pages in logsheet?
- xml files wrong operator
- DQ report has ARSF & doesn't mention sct fixed.
- Needs a readme (with some quality comments)
- Spectra look ok apart from the spike between the VNIR and SWIR, which is masked.
Line 4 low intensity and no return from bands below 30 for part of the line. Visible bands are quite low in other lines e.g. 12. Some weird striping in line 21.
- scts look good.
comment:16 Changed 8 years ago by dac
- Description modified (diff)
From Gary 05/01/2016 "all LiDAR and RCD to be processed. Customer to decide regarding Fenix data."