Opened 9 years ago
Last modified 9 years ago
#592 new flight processing
GB15/00, flight day 234c/2015, Alconbury
Reported by: | lah | Owned by: | |
---|---|---|---|
Priority: | immediate | Milestone: | 2015 data processing completion |
Component: | Processing: general | Keywords: | |
Cc: | Other processors: |
Description (last modified by dac)
Data location: ~arsf/arsf_data/2015/flight_data/arsf_internal/GB15_00-2015_234c_Alconbury
Data arrived from ARSF via USB on 27/08/2015.
Scientific objective: Acquisition of data to check potential new location for boresight flights. Processing of RCD data is highest priority. LiDAR should also be processed to check if there are sufficient features to be used for a boresight.
Priority: Unknown
PI: Internal
Flown on same day as Cambridge and Monks Wood(RG13/08).
Sensors:
- Fenix
- Leica LIDAR
- FW Leica LIDAR
- RCD
Change History (7)
comment:1 Changed 9 years ago by lah
comment:2 Changed 9 years ago by dac
- Description modified (diff)
comment:3 Changed 9 years ago by gej
Navigation Processing
Gravnav base station values:
longitude: 52 11 07.32947
Latitude: -0 06 44.97118
elevation 120.032m
ant: 1.046m
Complete using IPas TC, position separation and accuracy within acceptable limits.
comment:4 Changed 9 years ago by dac
Fenix Processing
Processed Fenix data to provide up to date imagery of site.
Replaced wavelengths in raw data. Found SCT values:
Flightline | SCT |
10 | 0.96 |
11 | 1.01 |
12 | 0.98 |
Haven't created delivery as not required.
comment:5 Changed 9 years ago by dac
Marking Camera, Fenix and LiDAR as finished - only required processing to sufficient level for us to check suitability as a boresight location.
comment:6 Changed 9 years ago by lah
Fenix 2016 calibration test
I have reprocessed (to level 1b only) this data using the new 2016 calibration for comparison purposes. Previous data has been moved to 2015cal folders. New spectra look much better.
comment:7 Changed 9 years ago by lah
Fenix 2015 new wavescale test
I've also used this data to test a new wavescale from the 2015 calibration, improved with additional anchors from the new spectral lines file. Although there is no overlap region, there is still a large spike which is not present in the 2016 calibration. Perhaps the sensor was still unstable from Malaysia at the 2015 calibration?
I've moved the tests into subfolders and the original data back into it's original place now.
Unpacking
All extra files have been split out except from RCD, which is duplicated for 234a, 234b and 234c. Please only process RCD for one of these projects, then split once processed.