Opened 21 months ago

Last modified 18 months ago

#580 new flight processing

RG12/11, flight day 160/2015, Twin Otter Test

Reported by: dac Owned by:
Priority: immediate Milestone: 2015 data processing completion
Component: Processing: general Keywords:
Cc: Other processors:

Description

Data location: ~arsf/arsf_data/2015/flight_data/arsf_internal/RG12_11-2015_160_twin_otter_test

Data arrived from ARSF via SATA disk on 09/07/2015.

Scientific objective: Project objective is generation of high quality land cover maps for input into Land Surface Models (LSMs). However, this flight is being treated as internal to test Twin Otter. A boresight wasn't collected so can't deliver data.

Priority: Urgent

PI: Mathias Disney

Sensors:

  • Fenix (requested)
  • Owl (not requested; 3 lines flown)
  • Leica LIDAR (requested)
  • Leica LiDAR FW (not specified)
  • RCD (requested; not flown)

Change History (9)

comment:1 Changed 20 months ago by asm

Description
There is not a logsheet picture on this project. There is a picture of Gary's notebook.

comment:2 Changed 20 months ago by asm

Navigation
Starting navigation process.

comment:3 Changed 20 months ago by asm

Navigation
Lat: 53 15 00.93558
Lon: -0 31 12.34784
Elipsoidal Height: 103.478 metres
Antenna Height: 0.172 metres

Last edited 20 months ago by asm (previous) (diff)

comment:4 Changed 20 months ago by asm

Hyperspectral - Fenix Processing
Hyperspectral processing started. Since this project is not going to be delivered, a logsheet has been generated without any information. On the other hand, thanks to that you can see that fenix is using binning 4, that was used to replace_wavelenght.py

Last edited 20 months ago by asm (previous) (diff)

comment:5 Changed 20 months ago by asm

Lidar Processing
Starting Lidar processing.

comment:6 Changed 20 months ago by asm

Lidar Processing
Finished. Only two flightlines as output from alspp, there are not visible errors on them. Further corrections have not been done.

comment:7 Changed 20 months ago by asm

Hyperspectral - Fenix Processing
There are not obvious errors. Fenix processing finished without further corrections.

comment:8 follow-up: Changed 18 months ago by lah

Owl Processing
Successfully processed to level 1b using batch scripts and Specim's tool for radiometric calibration. No obvious problems with viewing angle or sensor from Twin Otter.

Failed to process to level 3 (mapped) due to 'navigation data does not cover any of the 3 lines header files' error. Problem with owl nav? Logsheet only mentions 5 lines and all fenix lines processed fine, so should correspond to 3 of these. Needs further investigation as could prevent any owl data being processed regardless of aircraft.

comment:9 in reply to: ↑ 8 Changed 18 months ago by lah

Replying to lah:

Owl Processing
Successfully processed to level 1b using batch scripts and Specim's tool for radiometric calibration. No obvious problems with viewing angle or sensor from Twin Otter.

Failed to process to level 3 (mapped) due to 'navigation data does not cover any of the 3 lines header files' error. Problem with owl nav? Logsheet only mentions 5 lines and all fenix lines processed fine, so should correspond to 3 of these. Needs further investigation as could prevent any owl data being processed regardless of aircraft.

Missing owl nav files seems to only be a problem with this flight, so shouldn't affect any other 2015 data. Checking with Gary to see if there was a software problem not related to the Twin Otter.

Note: See TracTickets for help on using tickets.