Opened 9 years ago
Last modified 8 years ago
#582 new flight processing
GB15/00, flight day 190/2015, Little Rissington
Reported by: | dac | Owned by: | |
---|---|---|---|
Priority: | immediate | Milestone: | 2015 data processing completion |
Component: | Processing: general | Keywords: | |
Cc: | Other processors: |
Description
Data location: ~arsf/arsf_data/2015/flight_data/arsf_internal/GB15_00-2015_190_Little_Riss
Data arrived from ARSF via hard drive on 21/07/2015
Scientific objective: Boresight
Priority: Urgent
PI: Internal
Sensors:
Fenix (requested)
Leica LIDAR (requested)
Owl (requested)
Change History (8)
comment:1 Changed 9 years ago by lah
comment:2 Changed 9 years ago by lah
Fenix Processing
Found SCTs for boresight lines:
Flightline | FENIX |
5 | 2.31 |
6 | 30.60 |
7 | 3.13 |
8 | 3.77 |
9 | 2.71 |
comment:3 Changed 9 years ago by lah
comment:4 Changed 9 years ago by lah
Fenix Processing
Found boresight values: 0.08 0.13 0.32 and tested on extra lines. Needed line 10 for decent overlap to check heading as line 9 was short and didn't have useful overlap. Final scts:
Flightline | FENIX |
1 | 2.93 |
3 | 4.90 |
4 | 3.15 |
5 | 2.31 |
6 | 30.56 |
7 | 3.15 |
8 | 3.77 |
9 | 2.77 |
10 | 12.16 |
comment:5 Changed 9 years ago by stgo
Navigation processing
This was done ages ago but I didn't make a not here:
basestation (OXFR):
Lat | 51 49 26.25421 |
Long | -1 17 18.72265 |
Height | 119.763 |
Actual nav data resulted in a good solution with default IPAS TC settings.
This was processed using old lever arm values until the survey data is available.
Lidar processing
Processing has resulted in one value for pitch and 2 values for roll dependant on flightline altitude.
pitch | -0.00226 |
roll low | -0.0009 |
roll high | -0.00106 |
heading has a value of 0 until confirmed otherwise
comment:6 Changed 9 years ago by stgo
Lidar Processing
Range corrections:
A1 | -2.153 |
A2 | -2.109 |
A3 | -2.122 |
A4 | -2.178 |
B1 | -2.153 |
B2 | -2.204 |
B3 | -2.151 |
B4 | -2.117 |
These were checked for variations at different altitudes to try and explain the variable roll. There was no difference found.
Waveform trigger delay offsets:
under TPR | 6750 |
over TPR | 8200 |
Forward laser angle value has not been used for this calibration to ensure compatibility with alsproc.
comment:7 Changed 9 years ago by lah
Owl Boresight
owl_boresight = -0.08 -0.08 0.16
SCTs:
Flightline | OWL |
3 | 2.48 |
4 | 3.24 |
5 | 2.90 |
6 | 2.45 |
7 | 3.04 |
8 | 2.35 |
11 | 2.76 |
comment:8 Changed 8 years ago by dac
Hyperspectral
Replaced wavelengths using the most recent version (201509).
Fenix Processing
aplnav returned error: "Requested sync time index is out of bounds in GetSyncDelay()", so processing without nav.