EU10/03, flight day 233a/2010, Lake Balaton East Area D

[knpa]

Data location: ~arsf/arsf_data/2010/flight_data/archive-overflow/EU10_03-2010_233a_Lake_Balaton_East_Area_D

Data arrived from ARSF via SATA disk Q on 15/09/10.

Scientific objective: Lake Balaton provides an ideal area for testing emerging algorithms on retrieval of in-water constituents and on mapping bloom-forming cyanobacteria using in-situ radiometric, airborne and satellite data.

Priority: a5
*note: lidar is low priority for this project*

PI: A. Tyler

Sensors:

• Eagle (20/10/2010)
• Hawk (28/01/2011)
• Leica LIDAR (Requested but low priority)
• RCD (20/10/2010)

[emca]

Starting the Eagle and Camera processing

[emca]

IPAS and Applanix processing is complete

[emca]

Eagle SCT offsets:

Line No.	SCT
01	0.00
02	+0.04
03	0.00
04	0.00
05	+0.05
06	+0.01
07	+0.03
08	+0.03
09	+0.01
10	+0.03
11	+0.03
12	+0.03
13	+0.03
14	+0.04
15	0.00

[emca]

Hyperspectral and camera ready for delivery check at

H: ~airborne/workspace/EU10_03-2010_233a_Lake_Balaton_East_Area_D/delivery/20101011/EU10_03
C: ~airborne/workspace/EU10_03-2010_233a_Lake_Balaton_East_Area_D/delivery/20101012/EU10_03

Removed raw camera images 1-14, 31, 73, 82, 115, 122, 123, 143-146 as they either did not cover the project area or were over/under exposed

Images 151-413 relate to EUFAR10_01 233b so have moved the processed camera images to the relevant directory

[iopa]

Checking eagle and camera.

[iopa]

Eagle checked; nothing wrong to report, ready to deliver.
Camera checked; nothing wrong to report,

perhaps for the kml file to look better the eagle/hawk lines drawn can be straightened
to fit the line of photos. Since the kml file is meant as a helpful visual reference it could be
fixed without it being incorrect. The start coordinates of eagle/hawk lines would need to be something like;
lat,lon = 47.005225,18.082444

otherwise camera is ready to deliver as well.

[iopa]

Sorry the line I was referring to for the camera is line 4, eagle/hawk.

[emca]

Camera and Eagle sent to A Tyler 20/10/2010

[knpa]

Appears to be an issue with the bandset labels in the header files, they start at 900nm which is lower than it should be. Possibly incorrect bandset selected or none specified. Will leave this until end of the year and new Hawk calibration.

[anch]

Starting Hawk processing

[anch]

SCT offsets for Hawk:

Once again lots of zeros

-1: 0.03
-2: 0.00
-3: 0.00
-4: 0.00
-5: 0.00
-6: 0.00
-7: 0.00
-8: 0.00
-9: 0.00
-10: 0.00
-11: 0.00
-12: 0.00
-13: 0.00
-14: 0.00
-15: 0.00

Submitted for delivery check

[emca]

Delivery checked the hawk data at
~airborne/workspace/EU10_03-2010_233a_Lake_Balaton_East_Area_D/delivery/20101222

Data all looks good.
The caption of the screenshot in the Readme needs to be changed to say Hawk (currently says Eagle). Apart from that, the data is ready for delivery.

[anch]

Hawk delivered 28/01/2011

[emca]

Starting LiDAR processing

[emca]

The LiDAR data for this project was deemed low priority, has not been processed.

[emca]

Restarting the LiDAR processing.

Reprocessed the navigation data. PPP result for basestation SIOF:

Lat: 46 54 24.70928
Long: 18 03 07.17215
Ell: 167.030

[emca]

Created LiDAR delivery, ready for checking.

[stgo]

LiDAR delivery checked, no problems found.

[knpa]

Merged and deleted workspace version.

[dac]

Archiving

Data available from NEODC (​http://browse.ceda.ac.uk/browse/neodc/arsf/2010/EU10_03/EU10_03-2010_233a_Lake_Balaton_East_Area_D)

Marking as closed.