Opened 7 years ago

Closed 4 years ago

#453 closed flight processing (fixed)

BGS12/01, flight day 251/2012, Merthyr

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 besm)

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 (05/12/2012)
Eagle (05/12/2012)
Hawk (05/12/2012)
LiDAR (05/12/2012)
FW LiDAR

Change History (30)

comment:1 Changed 7 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 7 years ago by besm

Navigation processed

comment:3 Changed 7 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 7 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 7 years ago by knpa

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

comment:6 Changed 7 years ago by besm

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

Roll: +0.000358
Pitch: -0.00285

comment:7 Changed 7 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 7 years ago by besm (previous) (diff)

comment:8 Changed 6 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 6 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 6 years ago by knpa

  • Description modified (diff)

comment:11 Changed 6 years ago by anhi

Hyperspectral delivery created

comment:12 Changed 6 years ago by besm

Beginning delivery check. Showing Ed how to.

comment:13 Changed 6 years ago by edfi

Delivery check complete, missing cross flightline in Hyperspectral but was not flown

comment:14 Changed 6 years ago by besm

On my todo list I have "deliver w/o FW" next to 251. Since the full-waveform boresight might be a little while yet, we can make do with the standard lidar delivery already created. Marking as ready to DC.

NOTE TO THE FULL-WAVEFORM LIDAR PROCESSOR (probably me): ONE FLIGHTLINE IS ADJUSTED IN HEIGHT IN THE FINAL DELIVERY.

comment:15 Changed 6 years ago by edfi

Beginning LiDAR delivery check

Last edited 6 years ago by edfi (previous) (diff)

comment:16 Changed 6 years ago by edfi

LiDAR delivery check complete. FW missing however will be added latter. ASCII files adjusted into Windows friendly format. Everything else ok

comment:17 Changed 6 years ago by besm

Delivered eagle, hawk, camera and lidar all on one disk to Colm Jordan at British Geological Survey, Kingsley Dunham Centre, Keyworth, Nottingham, NG12 2AY. Sent on 5th December.

Still need to check OS vectors against hyperspectral and LiDAR data.

comment:18 Changed 6 years ago by besm

  • Description modified (diff)

comment:19 Changed 6 years ago by anhi

SCT Values

LineEagle SCTHawk SCT
1 -0.04 -0.05
2 -0.06 -0.03
3a -0.03
3b -0.03 -0.04
3c -0.05 -0.04
4a corrupt -0.05
4b corrupt -0.03
5 corrupt -0.02
6 -0.06 -0.07
7 corrupt -0.06
8 -0.01 -0.05
9 -0.04 -0.04
10 corrupt -0.02
11 0.00 -0.03
12 -0.02 -0.05
13 corrupt -0.05
14 -0.05 -0.04
15 -0.02 -0.05
16 2.86 -0.06

comment:20 Changed 6 years ago by anhi

Hyperspectral vector screenshots and readme created

comment:21 Changed 6 years ago by edfi

Adjustment to Hyperspectral readme look fine, ready to re-deliver

comment:22 Changed 6 years ago by anhi

LiDAR vector screenshots and readme created

comment:23 Changed 6 years ago by tipo

LiDAR delivery checked, no problems found.

comment:24 Changed 5 years ago by emca

Starting archiving

comment:25 Changed 5 years ago by emca

Full waveform lidar data has not been delivered (or processed).
Going to investigate this before going any further with the archiving.

comment:26 Changed 5 years ago by emca

Started processing the full waveform lidar data.

Lines 1316, 1324 and 1341 have files missing (due to corrupt disk mentioned above) and are not processable. These lines correspond to lines 001, 002 and 004.

Line 1349 (line 005) is missing some of the later files, so the end of the flight line will be missing (raw files 51 - 66).

comment:27 Changed 5 years ago by emca

Created full waveform delivery and finished preparing for archive.

comment:28 Changed 5 years ago by emca

Email sent to Wendy 09/04/2014

comment:29 Changed 4 years ago by dac

Archiving

Checked and data now available through NEODC.

comment:30 Changed 4 years ago by dac

  • Resolution set to fixed
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.