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

[dac]

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)

[asm]

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

[asm]

Navigation
Starting navigation process.

[asm]

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

[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

[asm]

Lidar Processing
Starting Lidar processing.

[asm]

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

[asm]

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

[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.

[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.