Changes between Version 1 and Version 2 of Processing/Boresighting
- Timestamp:
- Feb 28, 2012, 4:22:17 PM (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Processing/Boresighting
v1 v2 5 5 Every time the instruments are placed in the aircraft a new boresight flight has to be undertaken over the [wiki:Processing/CalibSite calibration site]. This may just be at the start of the flying season or multiple times throughout the year. At the end of the flying season a boresight flight is undertaken to check if any change has occurred. 6 6 7 == Hyperspectral Boresight Procedure == 7 == Hyperspectral Boresight Procedure ==#Hyperspectral 8 8 9 Flight requirements: 9 === Flight requirements: === 10 10 11 11 * Multiple flight lines taken along different flight paths … … 16 16 Typically we collect fully overlapping flight lines going along the compass directions: N, NE, E, SE, S, SW, W, NW 17 17 18 Processing technique: 18 === Processing technique: === 19 19 20 The first stage of the processing is to remove possible timing offsets due to the [wiki:Processing/Corrections/Timing navigation synchronisation problems]. This is because an along track shift occurs as consequence of the timing error and needs to be resolved first. 20 21 22 When these timing offsets have been identified the boresight procedure can begin. This is currently a case of processing the data with different boresight values (given in roll, pitch and heading angular offsets) and finding a set which appears to minimise location errors for all the flight lines. 23 24 As a good starting point it is useful to use the opposite flight direction flight lines to solve for roll and pitch. As a roll error will manifest itself as an across track shift and a pitch error as an along track shift. Be wary though that heading errors will also appear as a mixture of across and along track shifts. Heading errors are best identified using parallel lines with a 50% along track overlap.