Azspec-processed level 1b hawk data does not appear to be correct - it contains large anomalous spikes in some bands, seemingly correlated to very low data values. Eg from Nigg Bay line 3:

Compared to Caligeo spectrum from same pixel:

Could be underflowing, but would expect a much higher value for the spikes (~65k) in this case. Might still be underflowing and then changed by maths in azspec though.

Note extended from ticket #106, but separate to Hawk noise issue

Data location: /users/rsg/arsf/arsf_data/2014/flight_data/uk/BAS13_01-2014_068b_Tamar

Data arrived from ARSF via network transfer on 10/03/2014

BAS13/01 Scientific objective: unknown

BAS13/01 Priority: ?

PI: France Gerard

Sensors:

Camera (Delivered, Submitted to NEODC 05/04/2015) LiDAR (Delivered, Submitted to NEODC 05/04/2015)

Data location: ~arsf/arsf_data/in_progress/2007/flight_data/med/BGS07_02-2007_248_Latera

Data arrived from ARSF via 2 day FTP download completing on 10 Jan 2008.

Scientific details: Details of application not available at PML, but basically was to measure ground CO2 release by remote sensing.

PI: Jonathan Pearce / Stuart Marsh / Luke Bateson @ BGS

Sensors:

• ATM
• CASI (delivered 26/03/2008)
• Eagle (delivered 26/03/2008)
• Hawk (delivered 26/03/2008)

Quicklook

TBD.