Opened 6 years ago

Last modified 4 years ago

#542 closed flight processing

MA14/16, flight day 241/2014, Bosnia — at Version 5

Reported by: dac Owned by:
Priority: alpha 4 medium Milestone: 2014 data processing completion
Component: Processing: general Keywords:
Cc: Other processors:

Description (last modified by dap)

Data location: /users/rsg/arsf/arsf_data/2014/flight_data/malaysia/MA14_16-2014_241_Sarajavo

Data arrived from ARSF via network transfer on 19/12/2014

MA14/16 Scientific objective: Unknown

MA14/16 Priority: Currently unfunded

PI: Andy Ford

Notes: No RCD data Large difference between fps_set and fps_qpf


Fenix (Requested)
LiDAR (Requested)
RCD (Requested)
FW LiDAR (Requested)

Change History (5)

comment:1 Changed 6 years ago by dac

Basestation position, through PPP is:

Lat 43 49 33.277701
Lon 18 19 59.53932
Height 554.971

comment:2 Changed 6 years ago by dac

Processed Nav data. Solution is acceptable for most of the flightlines (+/- 5 cm lat, +/- 10 cm lon). Ambiguity fix is 1 (should be 2).

Will need refining later but sufficient for now to process hyperspectral data in order to check for potential frame rate problems (high priority).

comment:3 Changed 6 years ago by dac

  • Processed 4 fenix flightlines.
  • Changed fps to fps_qpf in header.
  • Needed to set realtime_nav to false in header, with true flightlines were curved and half had missing lines.
  • Checked overlapping lines (10 and 11), line up well with SCT values of 0.8 and 2 respectively.
  • Confirmed location using Landsat 8 panchromatic scene (15 m res) and GoogleEarth
  • Emailed Ops to notify of frame rate issue.

comment:4 Changed 6 years ago by dac

Processed 4 lidar lines to check they were OK.
No problems observed. Waiting for remaining lines to be downloaded and lidar boresight before proceeding.

comment:5 Changed 6 years ago by dap

  • Description modified (diff)
Note: See TracTickets for help on using tickets.