RG12/09, flight day 127a/2013, Wessex

[knpa]

Data location: /users/rsg/arsf/arsf_data/2013/flight_data/uk/RG12_09-2013_127a_Wessex/

Data arrived from ARSF via network transfer on 13/05/2013

RG12/09 Scientific objective: Biodiversity and the provision of multiple ecosystem services in current and future lowland multifunctional landscapes

RG12/09 Priority: 8+

PI: France Gerard

Sensors:

Camera (dispatched 8/7/2013)
Eagle (dispatched 8/7/2013)
Hawk (dispatched 8/7/2013)
LiDAR (dispatched 17/07/2013)

[tipo]

Started navigation processing.

[tipo]

Completed navigation processing, started RCD processing.

[tipo]

Started Hyperspectral processing

[tipo]

SCT values:
(Hawk 12 was processed with use_nav = false)

Line	Eagle	Hawk
4	-0.01	-0.07
5	-0.01	-0.07
6	-0.01	-0.07
7	-0.01	-0.07
8	-0.01	-0.07
9	-0.01	-0.07
10	-0.01	-0.07
11	-0.01	-0.07
12	-0.01	1.30

[tipo]

LiDAR delivery created.

[anhi]

RCD Delivery check:

No problems found.

[anhi]

LiDAR Delivery check:

• There is a pitch error across the dataset that might be able to be improved.

No other problems.

[tipo]

Created Hyperspectral Delivery

[besm]

Starting HS delivery check.

[besm]

Something looks off about the readme. And check_apl_cmd isn't playing nice with the genreadme file for the hyperspectral readme either, because the aplcorr_command specifies a path to an igm file - this screws up the sed operations in check_apl_cmd because it doesn't escape the forward slashes.

Here's one of the things I took issue with in the readme:

aplmask -lev1 flightlines/level1b/e127a041b.bil -mask
flightlines/level1b/e127a041b.bil_mask.bil -output
flightlines/level1b/e127a041b_masked.bil

I recommend we redo the hyperspectral readme configuration or normalise it to look more like the other hyperspectral readme configurations seen in other projects. Take a look at /users/rsg/arsf/arsf_data/2013/flight_data/uk/GB12_04-2013_106_Eaves_Wood/processing/hyp_genreadme-airborne.cfg, perhaps?

[tipo]

I missed trimming some paths in the example commands when I put them in the config. I've corrected them and regenerated the Readme. check_apl_cmd seems to be ok with it now.

[besm]

Delivery checked hyperspectral data. All now looks good. Ready to deliver.

[tipo]

RCD delivery dispatched.

[tipo]

Hyperspectral delivery dispatched.

[tipo]

Reprocessed LiDAR to correct pitch error.

[anhi]

LiDAR Delivery Check:

• Vector intensity screenshot does not have vectors in and lidar_genreadme-airborne.cfg is not pointing to the vector screenshot.

No other problems.

[tipo]

Screenshot fixed.

[anhi]

LiDAR Delivery recheck:

• No problems in Readme or screenshots.

[besm]

Copying LiDAR to disk 162.

[besm]

Sent LiDAR on disk 162. Delivered to France Gerard at the Centre of Ecology Hydrology at OX108BB. 17 July 2013.

[besm]

Resent LiDAR on disk 169 to France Gerard at same address. 08 August 2013.

[tipo]

Split each hyperspectral and lidar line into 3 sections and redelivered.