Opened 12 years ago

Last modified 8 years ago

#453 closed flight processing

BGS12/01, flight day 251/2012, Merthyr — at Version 10

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

Description (last modified by knpa)

Data location: /users/rsg/arsf/arsf_data/2012/flight_data/uk/BGS12_01-2012_251_Merthyr

Data arrived from ARSF via SATA disk on 24/09/2012

BGS12/01 Scientific objective: unknown

BGS12/01 Priority: ?

PI: Colm Jordan

Notes: This flight has FW Lidar.

Sensors:

Camera (Requested)
Eagle (Requested)
Hawk (Requested)
LiDAR (Requested)
FW LiDAR

Change History (10)

comment:1 Changed 12 years ago by knpa

Various files missing as a result of corrupt delivery disk.

This affects ipas20 data, eagle data and full waveform lidar data.

comment:2 Changed 11 years ago by besm

Navigation processed

comment:3 Changed 11 years ago by besm

Processing RCD and LiDAR

For reference (as there may be pitch and roll problems), I used the following pitch and roll errors from the 206a calibration:
Roll Error: 0.00023
Pitch Error: -0.00298

comment:4 Changed 11 years ago by besm

Noting that I didn't see any over/under exposed images from the RCD at all. rcd_tester.py only throws up false-positives too. Seems odd for 799 images, but not impossible I guess.

comment:5 Changed 11 years ago by knpa

  • Description modified (diff)
  • Priority changed from alpha 4 medium to alpha 4 high

comment:6 Changed 11 years ago by besm

Decided on pitch and roll errors for LiDAR for this flight.

Roll: +0.000358
Pitch: -0.00285

comment:7 Changed 11 years ago by besm

Appears to be some kind of alignment error, but can't tell what. It doesn't seem consistent going by height differences in the north-west corner of the dataset. Out of this corner, the flightlines 001-013 look okay, while the errors get much bigger between 014-016.

Inconsistent heights, where many surfaces are frequently sloped, could be clearly visible if there were some kind of subtle pitch error, but the pitch error as-is lines up houses in the south-eastern corner, so I'm reluctant to change it.

No height error seems consistent (generally, on the whole, it looks kinda right), so I'm leaving the data as-is for now.

SUMMARY: Flightlines 014-016 have erratic height errors in the north-west corner of the dataset, especially line 014.

EDIT: Also, looking at the south-east end, it looks like these errors aren't consistent across the entire flightline. Since I corrected everything for the middle of the flightline with the above pitch and roll errors, I'd just chalk this down to a one-off hiccup (fingers crossed) on the part of the sensor or navigation data, and hope it doesn't come up in other data sets.

Last edited 11 years ago by besm (previous) (diff)

comment:8 Changed 11 years ago by knpa

Regarding missing files:

Have not been able to locate missing FW lidar and ipas files. However, from the date stamps I don't think this data is needed.

Found the missing Eagle lines, however they appear to be corrupted as most are of a significantly smaller size than the header indicates. Have already looked through ops' disks so not sure if these will be recoverable. The following eagle lines are affected: 4a, 4b, 5, 7, 10, 13. Note that these have been re-named to match the Hawk and logsheet, the original file names were a jumble due to crashes.

comment:9 Changed 11 years ago by knpa

  • Summary changed from BGS12/01, flight day 251a/2012, Merthyr to BGS12/01, flight day 251/2012, Merthyr

comment:10 Changed 11 years ago by knpa

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