EU09/02, flight day 212b/2010, Alps

[ella]

Data location: ~/arsf_data/2010/flight_data/archive-overflow/EU09_02-2010_212b_Alps
Project has been fast copied to ~arsf/workspace/EU09_02-2010_212b_Alps

Data arrived from ARSF via network transfer on 9th August 2010.

Scientific objectives: This project will utilise an integrated remote sensing dataset to:

• resolve the spatial extent of glacial debris and determine debris thickness;
• contribute to improvements in glacier mass balance modelling;
• investigate up-scaling of field to satellite measurements, to determine the accuracy of our remote technique.

Priority: a4

PI: Dr David Rippin

Sensors:

• Eagle (24/05/11)
• Hawk (24/05/11)
• Leica LIDAR (22/09/10)
• Leica RCD (16/09/10)

[ella]

This flight was flown on the same day as GB070/09-212a and the two study areas are less than 11 minutes fling time apart, so the Applanix and Ipas navigation were processed once and sbet/sol files copied into each project directory.

[jb362]

The steep terrain for this project area means that an SRTM dem will be useless here and therefore hyperspectral processing should be held until a LiDAR dem has been produced.

[ella]

Starting camera processing.

[jb362]

Image event file has been edited for images which failed to
record a time (using time differences from sensorstat log). Images
affected are 1-5

[ella]

Beginning camera delivery check.

[jb362]

I actually did the camera processing for this project. Ella put a note on the ticket that she was starting the processing because I forgot to!

[ella]

Camera check complete. Everything looks good, just need to move the camera_delivery.log file out of the delivery directory.

[jb362]

Camera ready for delivery.

[jb362]

Iopa will be delivering this for me since I'm leaving.

[emca]

Processing the LiDAR for this project along with Alps ​212a

[iopa]

RCD camera was dispatched today, 16th September 2010.

[emca]

LiDAR data ready for delivery check at
~airborne/workspace/EU09_02-2010_212b_Alps/delivery/20100910/EU09_02

[iopa]

Checking LiDAR delivery.

[iopa]

LiDAR delivery check; nothing wrong to report, ready to go.

[emca]

LiDAR data sent to PI 22/09/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.

[knpa]

Taking HS.

[knpa]

Logsheet incorrectly gives project code as EU09_07, have corrected.

[knpa]

SCTs

Note: There were no straight lines to dewobble in this project so these were estimated from overlaying with the LiDAR.

	Eagle	Hawk
1	0.02	0.03
2	0.03	0.03
3	0.04	0.04
4	0.03	0.06

[knpa]

The Eagle and Hawk lines have large wobbles/distortions at the ends of the flightlines. It looks like they switched off after the lidar, when the plane was starting to turn.

[knpa]

There is a serious issue of misalignment (in a direction perpendicular to flight path, mostly in specific places). Doesn't look it's due to boresight or sct but is something to do with abrupt changes in height. Investigating.

[knpa]

The above issue was fixed by regenerating the DEM (LIDAR patched with ASTER) at 1m resolution.

[knpa]

Hyperspectral delivery created (20110518). Ready for checking.

[mark1]

Delivery has been checked. All data viewed and looks good.

Couple of things to check prior to delivery:

Overflows on level1 data should be mentioned in the readme
DEM name is different in directory and example command
Is the geoid-spheroid grid required? I assume the DEM is wgs84 referenced in which case it is not and should be removed from the example command.

[knpa]

Above issues have been corrected. Preparing for dispatch.

[knpa]

Hyperspectral delivered today to David Rippin in York (24/05/11)