Opened 18 months ago

Last modified 9 months ago

#701 new flight processing

LiDAR and Ibis Test, flight day 231/2022, Wytham Woods

Reported by: wja Owned by:
Priority: immediate Milestone:
Component: Processing: general Keywords:
Cc: Other processors:

Description

Received via hard drive 13/09/2022.

LWIR and MWIR frame sensors also flown.

Flight over Wytham Woods and then Little Shelford (6 lines, without LiDAR).

Issue with Ibis reported from instrument operator: "Ibis frame rate issue: 65 FPS only sustainable on Interal Trigger Mode. Possible NavSync issue resultant".

Change History (5)

comment:1 Changed 18 months ago by wja

Unpacking

Code for running QC needs updating for new sensors.

comment:2 Changed 11 months ago by wja

Updated project code to GB22/02

comment:3 Changed 11 months ago by wja

Applanix (IBIS) navigation data processed

Last edited 11 months ago by wja (previous) (diff)

comment:4 Changed 9 months ago by wja

Infratec

Farrer (KCL) gave wja two lines of Infratec data during the sensor calibration at Rothamsted in Feb 2022. These have been unpacked but please note this incomplete flight data.

comment:5 Changed 9 months ago by wja

Infratec

Directories for three lines have been provided:

  • 220819_140710_fire_line1_radcorr
  • 220819_142042_fire_line4_radcorr
  • 220819_143119_fire_line6_radcorr

However, lines 4 & 6 don't seem to have copied properly. The following error is encountered when unzipping:

Archive:  220819_142042_fire_line4_radcorr.zip                                                       
warning [220819_142042_fire_line4_radcorr.zip]:  552151206 extra bytes at beginning or within zipfile
  (attempting to process anyway)                                                                     
error [220819_142042_fire_line4_radcorr.zip]:  start of central directory not found;
  zipfile corrupt.                                                                                   
  (please check that you have transferred or created the zipfile in the
  appropriate BINARY mode and that you have compiled UnZip properly)
Note: See TracTickets for help on using tickets.