GB08/06, flight day 167/2010, Bleaklow

[ella]

Location of unpacked data: /users/rsg/arsf/workspace/GB08_06-2010_167_Bleaklow

Scientific purpose: Study of peatlands in the uplands of the Peak District National Park.

Scientific objectives: To evaluate the ability of SPECIM images to distinguish between moorland restoration treatments and provide new
knowledge on thresholds for estimating habitat condition for sparse vegetation growth on carbon-rich soils, building on work on hyperspectral remote sensing of bare peat.

Data arrived from ARSF via network transfer on 28th June 2010.

PI: Ms Julia McMorrow

Sensors:

• Eagle
• Hawk
• Leica LIDAR
• RCD Digital photography

[ella]

This project has not yet been fast copied into the arsf repoistry.

[ella]

Applanix navigation processing done.

[ella]

IPAS navigation processing is done.

[jb362]

Starting hyperspectral processing.

[jb362]

North end of eagle flightline 8 will not line up with other flightlines.The 0.03 offset seems to be the best fit for the rest of the flightline.

[jb362]

Playing around with the gpt offsets doesn't appear to sort out the above problem

[jb362]

I think I may just cut off the top of flight line 8 off since changing the sct or gpt offests doesn't have any effect

[benj]

No, you shouldn't ever cut data off the flightline. If it can't be rectified completely then put a comment to that effect in the readme prior to delivery, but the data itself is still fine even if not quite in the right place.

[jb362]

OK will do.

SCT Offsets:

e1: 0.03
e2: 0.01
e3: 0.04
e4: 0.01
e5: 0.00
e6: 0.01
e7: -0.01
e8: 0.03
e9: 0.03
e10: 0.08
e11: 0.05
e12: -0.01
e13: 0.05
e14: 0.02
e15: 0.03
e16: 0.85
e17: 0.01
e18: -0.01
e19: 0.03
e20: 0.04
e21: 0.02
e22: 0.02
e23: 0.05
e24: 0.04
e25: -0.01
e26: 0.03

Sync error on flightline 16 accounts for very large offset

[mark1]

OS vectors have arrived and have been unpacked to ~arsf/vectors/GB08_06-second

[jb362]

Flight line e23 split into 4 parts:

e24a:0.05
e24b:0.1
e24c:0.1
e24d:0.06

Flight lines e11, e21, e22 had end of flight line cut off as these sections were out the target area and had large bends resulting in turn errors.

[jb362]

Typo!

Flight line e23 split into 4 parts:

e23a:0.05
e23b:0.1
e23c:0.1
e23d:0.06

[iopa]

Taking up LIDAR processing.

[jb362]

Hawk SCT offsets:

h1: 0.02
h2: 0.01
h3: 0.06
h4: 0.00
h5: 0.03
h6: 1.70
h7: 0.01
h8: 0.02
h9: 0.00
h10: 0.01
h11: 0.02
h12: -0.01
h13: 0.02
h14: 0.03
h15: 0.02
h16: 1.35
h17: 0.00
h18: 0.03
h19: 0.01
h20: 0.03
h21: 0.02
h22: 0.03
h23: 0.02
h24: 0.05
h25: 0.06
h26: 0.01

Sync errors on flight lines 16 & 6 account for very large offsets

[iopa]

Missing .sup file from IPAS output, will re-process IPAS before proceeding to LIDAR.

[jb362]

Hyperspectral processing complete and ready for delivery check

[anch]

Delivery checking the hyperspectral data for this project now.

[jb362]

Delivery check fixes complete

[jb362]

Delivery checking LiDAR

[jb362]

Check complete. Change "Ordance survey" to "Ordnance survey" in data quality remarks.

[iopa]

Dispatched USB disk containing Eagle and LiDAR on the 19/08/2010.
PI and collaborators have been emailed.

Note: Collaborator 2 will be unavailable and would like any contact regarding remote sensing to be diverted to Stuart Masheder.

Hawk data will be delivered individually when calibration issue has been resolved.

[iopa]

Processing camera.