EU10/03 & EUFAR10/01 (AIMWETLAB), flight day 232b/2010, Aimwetlab (Kis Balaton)

[iopa]

Data location: ~arsf/arsf_data/2010/flight_data/hungary/EU10_03-2010_232b_Aimwetlab_Kis_Balaton

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

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 - the data set as a whole is listed as a5 due to it being part of EU10/03, however the PI of EU10/03 has lowered the LiDAR priority to a4m, and therefore LiDAR stands with a priority of a4h due to being part of EUFAR10/01.

PI: A. Tyler (EU10/03) & A. Zlinszky (EUFAR10/01)

When data is processed it should be dispatched to both PIs individually for their respective projects.

Sensors:

• Eagle (27/10/2010 & 28/10/2010)
• Hawk (28/01/2011)
• Leica LIDAR (28/02/2011)
• Digital Photography (27/10/2010 & 28/10/2010)

[emca]

Starting Eagle and Camera processing

[emca]

IPAS and Applanix processing is complete

[emca]

Changed the file structure from EUFAR10-01 to EU10_03 to match the other two projects that have the same dual PIs (#358 & #373)

[emca]

Hyperspectral is ready for delivery check
~airborne/workspace/EU10_03-2010_232b_Aimwetlab_Kis_Balaton/delivery/20101018/EU10_03

[emca]

Camera is ready for delivery check
~airborne/workspace/EU10_03-2010_232b_Aimwetlab_Kis_Balaton/delivery/20101019/EU10_03

[iopa]

Delivery checked eagle; all's good and ready to deliver.

Delivery checked camera; all's good except the eagle/hawk lines 1,2 and 3 are drawn out of place on googleearth,
lines 1 should start at ~ ( 46°38'3.39"N, 17° 3'33.42"E)
lines 2 should end at ~ ( 46°38'31.15"N, 17° 3'55.78"E)
lines 3 should end at ~ ( 46°31'33.07"N, 17° 6'27.03"E)

sorry for the degrees! it's googleearth.

otherwise ready to deliver.

[iopa]

Also for the camera readme, since this flight has a flight letter, the filename convention for the kml etc. needs an 'f', and then an extra line written in the description underneath.

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

[emca]

Eagle and Camera sent to PI 27/10/2010

[emca]

Note above delivery relate to A Tyler. Data also needs to be sent to A Zlinszky.

[iopa]

Dispatched Eagle and Camera to Dr. Zlinszky on 28/10/2010.

[anch]

Starting hawk processing...

[anch]

SCTs found.

-1: 0.00
-2: 0.00
-3: 0.00
-4: 0.00
-5: 0.00
-6: 0.00

[anch]

Hawk submitted for delivery check

[emca]

Starting LiDAR processing

[iopa]

Finished checking Hawk delivery;

no errors were found, ready to deliver... twice!

[anch]

Hawk delivered 28/01/2011

[emca]

LiDAR ready for delivery check at
~airborne/workspace/EU10_03-2010_232b_Aimwetlab_Kis_Balaton/delivery/20110211/EU10_03

[knpa]

Taking LIDAR delivery check.

[knpa]

Delivery check complete.

All looks good apart from:

All ascii files are one column too long! (9 instead of 8) txyzicra?

Also, remember that this project needs to be delievered to Dr. Zlinszky also, under separate project code.

[emca]

ASCII file format has been changed and now contain 9 columns so no changes made to LiDAR delivery.

LiDAR data sent to A. Tyler 28/02/2011

Hawk and LiDAR need to be sent to A Zlinszky

[anch]

Hawk and LiDAR sent to A. Zlinkszky

[knpa]

Projects has been r-synced. Beginning archiving.

[knpa]

AIMMS/GRIM data present.

Tabi data present.

[knpa]

applanix/gps files missing.

[knpa]

Project has been tarballed and made available to NEODC (12/05/11)

[knpa]

Backed-up by NEODC.

Moved to archive disk.

[emca]

Reprocessed hyperspectral data using apl

[knpa]

Removed non-reprocessing workspace version. Leaving ticket open for reprocessing.

[emca]

Hyperspectral data ready for delivery check

[knpa]

Delivery checking hyperspectral.

[knpa]

Delivery check complete.

All looks fine apart from:

• ReadMe first page gives jday as 232, think this should be 232b to uniquely identify it.
• DEM in ReadMe and config has incorrect name (actual file name is correct). Let me know when this is fixed so I can run apl_cmd_check.
• There appears to be a residual sct offset in e5
• Need to mention regular dropped frames in Eagle in ReadMe
• logsheet name incorrect

[emca]

Made above changes - reprocessing eagle 5 for all sct values to check value used.

[emca]

Eagle line 5 sct was good for the position but not for the wobble. Had to use a gpt offset (-posattoff in aplnav) to get the dewobbled line to match with the others.

New offset for Eagle line 5:
sct: -0.14
gpt: 0.10

Reprocessing line 5 for all bands and will add to delivery.

[emca]

Replaced Eagle line 5 files in the delivery, recreated the screenshot + mosaic and updated Readme.

Reprocessing complete and ready for delivery.

[emca]

Data sent to PI 16/08/2012

[dac]

Checked and data available from NEODC (including reprocessed hyperspectral) - marked as archived.