FW10/02, flight day 101/2010, Cumbria

[benj]

Data location: ~arsf/arsf_data/2010/flight_data/uk/FW10_02-2010_101_full_waveform_test

Data arrived from ARSF via network transfer on 12th April 2010.

Scientific objective: Test flight for full-waveform LiDAR

Priority: a4m (not graded by SC, assigned following consultation with ppu)

PI: Doreen Boyd

Full waveform test flight. Will be delivered to PI but not specifically requested.

Sensors:

• Eagle (19/08/2010)
• Hawk
• Leica LIDAR (Full Waveform) (06/08/2010)

[]

[mggr]

Fix summary line (in case we ever automate this).

[mark1]

IPAS data has been processed.

[emca]

No sync message for Hawk lines 20, 21 or 22

[emca]

Per Line SCT values. GPT values, where applicable, are given second:

Line No:	Eagle	Hawk
01	-0.18, -0.18	+0.02
02	+0.07	+0.07
03	-0.14, -0.16	+0.04
04	+0.06	+0.04
05	-0.06	0
06	+0.06	+0.04
07	-0.10	+0.01
08	+0.05	+0.04
09	+0.01	-0.02
10	+0.02	+0.05
11	+0.01	+0.01
12	+0.05	+0.05
13	+0.04	-0.03
14	+0.04	+0.04
15	+0.06	0
16	-0.01, -0.12	+0.03
17	+0.08	-0.03
18	-0.09, -0.12	+0.03
19	+0.06	-0.03
20	-0.13, -0.12	+0.26
21	+0.03	+0.43
22	-0.12, -0.16	+0.90, +0.04
23	+0.08, +0.04	-0.03
24	-0.18, -0.18	+0.02
25	+0.19, +0.15	-0.01

[emca]

The following photographs have been removed as they are outside the project area:
1-13, 135-138, 218, 219

[emca]

Hyperspectral, Camera and LIDAR are ready for delivery check.

H: ~airborne/workspace/FW10_02-2010_101_Cumbria/delivery/20100706
C: ~airborne/workspace/FW10_02-2010_101_Cumbria/delivery/20100707
L: ~airborne/workspace/FW10_02-2010_101_Cumbria/delivery/20100708

[knpa]

Beginning LiDAR delivery check.

[knpa]

Delivery checked LIDAR.

Looks good apart from the following points:

Logsheet has incorrect format, should be: FW10_02-2010_101_Cumbria.pdf
Logsheet shouldn't be executable.
Project code in Readme should be FW10_02
line 132 "These points have been classified rather than removed incase they are"
Why SRTM and not nextmap used for DEM?
Strange files in N1 and N2: os and sys.

Note: could not check LAS 1.3 Files as no .trj files in delivery. Should these be included?

[mggr]

Replying to knpa:

Note: could not check LAS 1.3 Files as no .trj files in delivery. Should these be included?

Tricky.. it's specific to TerraScan but given that's the only tool we have, I'd agree they should be included.

Perhaps we should also include the sol/sbet file to give people another option for navigation info? Thoughts?

Note also that we should point out the LAS 1.3 files are not compliant to the specification, though are compatible with TerraScan - we'll have to redeliver these when Leica give us an updated processor.

[jb362]

Beginning hyperspectral delivery check

[jb362]

Hyperspectral delivery check complete.

1) Read_Me is in .txt format and should be in .pdf.

2) Logsheet should be named FW10_02-2010_101_Cumbria.pdf

Apart from that all fine.

Hawk band 160 blank for all flight lines.

[jb362]

Beginning camera delivery check

[jb362]

Camera delivery check complete. Everything fine.

[emca]

LiDAR and Photography data dispatched to both D. Boyd and K. Anderson 06/08/2010

[emca]

LiDAR and Photography have been rsync'd to
/users/rsg/arsf/arsf_data/2010/flight_data/uk/FW10_02-2010_101_Cumbria

Did not rsync the leica/proc_laser folder as the .LAS files were included in the delivery.

[emca]

Eagle data dispatched to PI 19/08/2010

[anch]

I have created FW extractions for some interesting areas in the flightlines including roads, trees, buildings etc.

There are inside delivery directory 20100924.