Opened 5 weeks ago

Last modified 3 weeks ago

#631 new flight processing

GB18/186, flight day 177/2018, Whitsand Bay

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

Description (last modified by dac)

Data location: ~arsf/arsf_data/2018/flight_data/uk/GB18_186-2018_177a_Whitsand_Bay

Data arrived from NERC-ARF via harddrive on 13/07/2018

Scientific objective: Detection of marine litter from hyperspectral data

PI: Victor Martinez Vicente
BAS Code: D186

The following issues were identified during unpacking:

  • Missing log files for some Fenix lines
  • fps differs from fps_set and fps_qpf for 4 Fenix lines
  • Missing GPS starting time for Owl but have starting time
  • Missing dark frames for owl

Sensors:

  • Fenix (requested, flown)
  • OWL (not requested, flown)
  • Phase One (requested, flown)

Change History (14)

comment:1 Changed 5 weeks ago by dac

  • Description modified (diff)

comment:2 Changed 5 weeks ago by dac

Digital Camera

Converted raw images to tiffs.

comment:3 Changed 5 weeks ago by dac

Navigation Processing

Basestation verification. Using antenna height of 1.651 m (from file)

Latitude 50 21 12.80395
Longitude -4 16 20.37751
Ell. Height 88.583

comment:4 Changed 5 weeks ago by dac

Navigation Processing

Processed GPS/IMU data using IPAS TC.

comment:5 Changed 4 weeks ago by dac

Unpacking

Edited Owl headers to change Start Time to GPS Start Time and added start and end location from navigation data. Made backup of original header files.

comment:6 Changed 4 weeks ago by dac

Fenix Processing

Looks like navigation syncing is fixed. Found SCT values for all lines apart from 12 and 16, not sure if these also have a problem with the framerate.

Flightline FENIX
1 2
2 2
3 2
4 2
5 2
6 2
7 1
8 2
9 2
10 1
11 1
12 2
13 ?
14 2
15 2
16 ?
17 1
18 2
19 2
Last edited 3 weeks ago by dac (previous) (diff)

comment:7 Changed 4 weeks ago by dac

Fenix Processing

Mapped all bands for the lines which do have SCT values. As there were multiple flights of each line and logsheet only has up to file 15 not sure if lines 13 and 16 are actually needed.

For 700 m altitude flights could map to higher resolution (~ 1 m rather than 3 m) which would probably be of interest to PI. Will mention in readme.

comment:8 Changed 3 weeks ago by dac

Fenix Processing

Navigation was going backwards for line 17, using -force flag in aplnav resulted in weird geolocation artefacts. As problem is only right at the end of the line cropped to line 2250 which resolved problem.

comment:9 Changed 3 weeks ago by dac

Fenix Processing

Delivery created - waiting for delivery check.

comment:10 Changed 3 weeks ago by asm

Fenix DC

Started.

comment:11 Changed 3 weeks ago by asm

Fenix DC

Looks like all the navigation files have been moved to the delivery and only the sct0.00 has been renamed. This needs to be sorted out carefully to make sure is the right nav for the line. I am checking the apl comands and it looks like flightlines do not overlap OK. Most likely, solving that issue will solve the problem.

comment:12 Changed 3 weeks ago by asm

Fenix DC

-Problems with nav files have been fixed.
-Spectra looks OK with Py6S
-APL commands run OK and lines do overlap.
-Logsheet looks fine. Files not included are not in the overview but this is OK
-Added readme not included. Strangely there was a line that went out of margin so changed to:
"grid-shift file:
\newline
OSTN02\_NTv2.gsb."

Will start zipping files.

comment:13 Changed 3 weeks ago by asm

Fenix DC

Mapped files were zipped correctly. Project ready to be delivered.

comment:14 Changed 3 weeks ago by asm

Fenix Delivery

Delivered on 31/07/2018 using our linux location and notication sent to PI.

Note: See TracTickets for help on using tickets.