Opened 11 years ago
Last modified 6 years ago
#515 new flight processing
GB14/00, flight day 078/2014, Little Riss
Reported by: | knpa | Owned by: | stgo |
---|---|---|---|
Priority: | immediate | Milestone: | 2014 data processing completion |
Component: | Processing: general | Keywords: | |
Cc: | Other processors: |
Description
Data location: /users/rsg/arsf/arsf_data/2014/flight_data/arsf_internal/GB14_00-2014_078_Little_Riss/
Data arrived from ARSF via network transfer on 19/03/2014
GB14/00 Scientific objective: Boresight
GB14/00 Priority: urgent
PI: ARSF
Notes: FENIX 25 lines
Sensors:
LiDAR (Requested)
FENIX (Requested?)
Change History (15)
comment:1 Changed 11 years ago by stgo
comment:2 Changed 11 years ago by stgo
Beginning lidar calibration, Range cal results:
Range Offset A1: 0
Range Offset A2: 0.006
Range Offset A3: 0.040
Range Offset A4: -0.011
Range Offset B1: 0.000
Range Offset B2: 0.002
Range Offset B3: -0.002
Range Offset B4: 0.020
comment:3 Changed 11 years ago by stgo
Have computed scanner offsets and most (all) flightlines are way off the scan correct value given by leica (-10340) averaging them all has resulted in 16640 as a potential value.
There is however one flightline that carries a value of -172016 which is considerably above the other values given, removing this from the averaging results in a value of 10310. I will try to run the calibration using both values to see differences.
comment:4 Changed 11 years ago by stgo
Pitch roll and heading values found as:
roll | -0.003918414 |
pitch | 0.00113716 |
heading | 0.00056484 |
The roll error is an average of the best values for high and low alt lines being:
high | −0.003991482 |
low | −0.003845345 |
comment:5 Changed 11 years ago by stgo
Range calibration completed using averaged roll error.
Lascontrol gave a result of -1.58854 which was used with RangeCardCal to get the following values:
A1 | -1.58854 | B1 | -1.589 |
A2 | -1.582 | B2 | -1.587 |
A3 | -1.548 | B3 | -1.591 |
A4 | -1.599 | B4 | -1.569 |
Lascontrol gave an average dz of 0.0164776 with std dev of 0.0206099 on low altitude and
0.0525533 with std dev of 0.0377199 on high altitude.
comment:6 Changed 11 years ago by stgo
The full wave form files were not present so this has not been calibrated.
comment:7 Changed 11 years ago by stgo
Beginning hyperspectral boresight.
comment:8 Changed 11 years ago by stgo
Fenix lines 1 and 2 are errored lines with less than a second of data. Will not be used from here on. SCT values are:
Flightline | Fenix |
1 | 0.00 |
2 | 0.00 |
3 | 0.91 |
4 | 0.96 |
5 | 0.91 |
6 | 0.90 |
7 | -0.06 |
8 | 0.96 |
9 | 0.95 |
10 | 0.96 |
11 | 0.92 |
12 | 0.90 |
13 | 0.95 |
14 | 0.90 |
15 | 0.96 |
16 | 0.93 |
17 | 0.96 |
18 | 0.96 |
19 | 0.96 |
20 | 0.96 |
21 | 0.96 |
22 | -0.04 |
23 | 0.95 |
24 | 0.95 |
25 | 0.94 |
26 | 0.91 |
27 | 0.95 |
comment:9 Changed 11 years ago by stgo
Provisional hyperspectral boresight values are:
pitch | 0.286 |
roll | 0.112 |
heading | 0.20 |
comment:10 Changed 10 years ago by mark1
Second attempt at LiDAR calibration, based on the results of the first one but trying to convert to using torsion and pitch error slope (pes) rather than forward laser angle (FLA). Fiddled with boresight parameters and range correction after changing over to torsion and pes.
comment:11 Changed 10 years ago by stgo
I've moved the original processing for the hyperspectral boresight to processing/original_hyperspectral, will move back when dap is finished learning some hyperspectral processing.
comment:12 Changed 9 years ago by stgo
Fenix
This flight did not have dark frames
comment:13 Changed 8 years ago by stgo
comment:14 Changed 8 years ago by stgo
Test2
comment:15 Changed 6 years ago by dac
Moved hyperspectral processing back.
Nav data processed, good solution achieved