GB07/07, flight day 277, Inverclyde

[mark1]

Data location: ~arsf/arsf_data/2009/flight_data/uk/GB07_07-2009_277_Inverclyde

Data arrived from ARSF via SATA disk L on 7th October 2009.

Scientific objective: Effect on spectral reflectance by heather type and biophysical properties

Priority: alpha-4-High

PI: Alasdair MacArthur

Sensors:

• Eagle (07/01/2010)
• Hawk (07/01/2010)
• Leica LIDAR (27/04/2010)

[mark1]

Still awaiting flight logsheet. When it arrives check eagle flight lines are correct - they are named 274 not 277 (date stamps match those of hawk though).

DEM creation gave errors in Grass but output a DEM. Check its good when processing.

[mark1]

logsheet arrived and unpacked

[mark1]

Have renamed eagle lines from VNIR274-09 to VNIR277-09, and from VNIRdatacube to VNIR274-09-1

[mark1]

Have renamed Hawk lines from Hawk277* to SWIR277*

[mggr]

Re: #281 (Hawk frame rates are double what they should be), the following lines are affected and the .hdr file will need to be edited to halve the fps number:

uk/GB07_07-2009_277_Inverclyde/hawk/SWIR277-09-1.hdr: predicted length half recorded length, frame rate doubling problem?
uk/GB07_07-2009_277_Inverclyde/hawk/SWIR277-09-2.hdr: predicted length half recorded length, frame rate doubling problem?
uk/GB07_07-2009_277_Inverclyde/hawk/SWIR277-09rec-1.hdr: predicted length half recorded length, frame rate doubling problem?
uk/GB07_07-2009_277_Inverclyde/hawk/SWIR277-09rec-2.hdr: predicted length half recorded length, frame rate doubling problem?

[chrfi]

hawk flight line 3 no .hdr file

[chrfi]

hawk line 3 lacking dark frames, used dark frames from line 2

[chrfi]

last 111 lines of eagle 3 were removed to allow the line to process

[chrfi]

eagle

line	sct	gpt
1	-0.02	-0.05
2	0.04	0.00
3	0.00	0.00
4	-0.065	0.04
5	-0.03	0.02

hawk

line	sct	gpt
1	1.60	0.00
2	0.82	0.06
3	77.7	0.10
4	18.65	0.00
5	0.10	0.00

[benj]

Doing delivery check

[benj]

Updated copyright notice to 2010, a few minor readme changes, removed superfluous readme template file. Two of the Hawk files appear to have the wrong filenames (should be fixed before delivery).

Data values in Hawk line 3 are very low - underflows in a lot of bands, which means probably the values in the rest of the bands are wrong. This should be mentioned in the readme. Also the cause should be checked, may just have been that the sensor was having problems on line 3 (hence why the end had to be cut off).

Otherwise ready for delivery.

[benj]

Low data values in Hawk line 3 appear to be a result of the dark frame substitution - substituting dark frames on another line on the same flight causes the same problem. Suggests that the data values on all of the Hawk lines are suspect and shouldn't be relied on to be correct.

[chrfi]

hyperspectral data delivered 07/01/2010

[chrfi]

files in workspace need to be rsynced back to arsf_data as soon as space is available

[benj]

There's now space on the disk, you can rsync this back.

[emca]

LiDAR delivery folder created by chrfi at
~airborne/workspace/GB07_07-2009_277_Inverclyde/delivery/20100426/GB07_07

Changed PI on logsheet & readme to Alasdair MacArthur.
Removed .xml file from DEM directory.

Accuracy to vectors needs to be added to read_me. Once that is added the data is ready to deliver.

[chrfi]

lidar roll offsets

115948	0.003903
115218	0.003903
121017	-0.003663
123771	-0.00343
122647	-0.004

[chrfi]

my mistake, afaik it needs archiving

[chrfi]

waiting for more space before rsyncing back

[knpa]

Beginning archiving.