GB08/08, flight day 268b/2009, Wytham woods

[mark1]

Data location: ~arsf/arsf_data/2009/flight_data/uk/GB08_08-2009_268b_Wytham_woods

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

Scientific objective: see ~/arsf/arsf_data/in_progress/2008/ARSF_Applications/GB_and_NL/GB08-08 Science Case.pdf

Priority: alpha-4-High

PI: Richard Harding

Sensors:

• Eagle (09/04/2010)
• Hawk (09/04/2010)
• Leica LIDAR (25/03/2010)

[mark1]

Still awaiting flight logsheet.

Also, errors when generating DEM in Grass but it still output a DEM, check it is good when processing.

When logsheet arrives check eagle / hawk files and rename them - currently all named with 268c - need to check they are for 268b and not 268c.

[mark1]

Eagle and Hawk files in wrong project.

Eagle and Hawk files have been moved to GB08_10-2009_268c_Denny_wood/. Eagle files from boresight_2009-268a_little_riss have moved into this project. Currently no Hawk files.

[mark1]

logsheet arrived and unpacked

[mggr]

Hawk data recovered from aircraft disks, put in directory and renamed from Hawk268b-09-* to SWIR268b-09-*.

[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/GB08_08-2009_268b_Wytham_woods/hawk/SWIR268b-09-1.hdr: predicted length half recorded length, frame rate doubling problem?
uk/GB08_08-2009_268b_Wytham_woods/hawk/SWIR268b-09-2.hdr: predicted length half recorded length, frame rate doubling problem?
uk/GB08_08-2009_268b_Wytham_woods/hawk/SWIR268b-09-3.hdr: predicted length half recorded length, frame rate doubling problem?
uk/GB08_08-2009_268b_Wytham_woods/hawk/SWIR268b-09-4.hdr: predicted length half recorded length, frame rate doubling problem?
uk/GB08_08-2009_268b_Wytham_woods/hawk/SWIR268b-09-5.hdr: predicted length half recorded length, frame rate doubling problem?
uk/GB08_08-2009_268b_Wytham_woods/hawk/SWIR268b-09-6.hdr: predicted length half recorded length, frame rate doubling problem?
uk/GB08_08-2009_268b_Wytham_woods/hawk/SWIR268b-09-7.hdr: predicted length half recorded length, frame rate doubling problem?

[emca]

Starting LIDAR processing

[emca]

LIDAR delivery directory created at
~airborne/workspace/GB08_08-2009_268b_Wytham_woods/delivery/20100322
Ready for delivery check.

Starting Hyperspectral processing

[mark1]

LIDAR delivery checked. Data viewed in lag and looks good.
Ready to deliver.

[mark1]

LIDAR dispatched to PI on 25/03/2010

[emca]

No specim sync for Eagle line 1 or any of the Hawk lines.

Per line SCT's

Line	Eagle	Hawk
1	-0.01	-0.02
2	0.04	-0.04
3	-0.02	0.08
4	-0.03	-0.02
5	-0.04	-0.03
6	-0.02	-0.01
7	0.02	-0.02

[emca]

Hyperspectral data ready for delivery check at
~airborne/workspace/GB08_08-2009_268b_Wytham_woods/delivery/20100331

[knpa]

Delivery Check Complete.

All looks good apart from the following:

1. One misnamed file: e268061b.bil should be e268b061b.bil
2. File e268061b.bil will not open - unix says it is a "DOS executable (device driver)"
3. Need hawk and eagle mosaic's overlayed with vectors screenshots
4. No listing for bin dir in Readme contents
5. README_DEM_MAY_NOT_BE_ACCURATE.txt: needs to be unix2dos'd
6. Example azexhdf command is wrong:

azexhdf -h e268b011b.hdf -G e268b013b.hdf
Should be something like:
azexhdf -h e268b013b.hdf -G e268b013b.tif

[emca]

File name amended and read_me corrected
Hyperspectral data sent to PI 09/04/2010

[emca]

LIDAR and Hyperspectral data rsync'd to
arsf/arsf_data/2009/flight_data/uk/GB08_08-2009_268b_Wytham_woods

Ready for archiving