GB12/00, flight day 182/2012, Heerbrugg

[knpa]

Data location: /users/rsg/arsf/arsf_data/2012/flight_data/arsf_internal/GB12_00-2012_182_Heerbrugg_Cal

Data arrived from ARSF via SATA disk on 11/07/2012

GB12/00 Scientific objective: Covers several flights for the 2012 season. Boresight and calibration flights

GB12/00 Priority: urgent

PI: ARSF Internal

Notes: This is a calibration "check" over Heerbrugg.

Sensors:

Camera (Requested)
Eagle (Requested)
LiDAR (Requested)

[emca]

Processed the navigation data. As with the last Heerbrugg flight, had to change the L2 offset to 0 (from -0.25) to get a fixed ambiguity solution.

Starting the LiDAR processing.

[knpa]

Processed the Eagle and it looks fine - no significant boresight errors or other problems.

SCTs:

	eagle
1	-0.03
2	-0.02
3	-0.02
4	-0.02
5	-0.03
6	-0.02
7	-0.04?
8	-0.02
9	-0.03
10	-0.04?

[emca]

Processing the LiDAR calibration data

Per Leica's advice, ran Compute Scanner Offsets and changed the scan encoder value to -12160 ticks. Roll error is still evident in this data between the high and mid altitude flightlines.

[emca]

Best roll value for mid altitude flightlines is 0.000327110, which gives vertical errors in the high altitude flightlines of ~40-50cm.

Best roll value for high altitude flightlines is 0.000107110, which gives vertical errors in the mid altitude flightlines of ~15-20cm.

This is similar to previous errors observed so I don't think altering the scan encoder has any bearing on the roll error.

[emca]

Completed the range correction - have the same problem with #440 (GCP's are not in the the +/-7 deg swath). When I use the whole swath I get range values that are too high when comparing the little riss data from 082.

Keeping the range correction as it was for the previous calibration.

Doing the other final checks now and then will process some of the data from earlier this season to see what effect the new calibration values has on the data.