Opened 8 years ago

Last modified 7 years ago

#443 new flight processing

GB12/00, flight day 182/2012, Heerbrugg

Reported by: knpa Owned by:
Priority: immediate Milestone: 2012 data processing completion
Component: Processing: general Keywords:
Cc: Other processors:

Description (last modified by emca)

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.


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

Change History (5)

comment:1 Changed 8 years ago by emca

  • Description modified (diff)
  • Summary changed from GB12/00, flight day 182/2012, Heerbrug to GB12/00, flight day 182/2012, Heerbrugg

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.

comment:2 Changed 8 years ago by knpa

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


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?
Last edited 8 years ago by knpa (previous) (diff)

comment:3 Changed 7 years ago by emca

Processing the LiDAR calibration data

Per Leica's advise, 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.

Version 0, edited 7 years ago by emca (next)

comment:4 Changed 7 years ago by 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.

Last edited 7 years ago by emca (previous) (diff)

comment:5 Changed 7 years ago by 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.

Note: See TracTickets for help on using tickets.