CAM11_03, flight day 141/2011, Madrid

[knpa]

Data location: /users/rsg/arsf/arsf_data/2011/flight_data/spain_portugal/CAM11_03-2011_141_Madrid

Data arrived from ARSF via network transfer on 24/05/2011

CAM11_03 Scientific objective: We wish to measure how these forests change over gradients of topography‐controlled climate and soil properties.

CAM11_03 Priority: Alpha 4h

PI: David Coomes

Sensors:

Camera (24/06/2011)
Eagle (27/06/2011)
Hawk (27/06/2011)
LiDAR (15/08/2011)

Note: This project is actually part of EU11_03 but has a different project code as it was funded separately, and has higher priority.

[iopa]

Taking LiDAR and camera.

[iopa]

Camera is ready for checking @ ~arsf/arsf_data/2011/flight_data/spain_portugal/CAM11_03-2011_141_Madrid/processing/delivery/camera-CAM11_03-100-20110615

Raw images taken during preparation and removed ;
1-28
Raw images with cloud or saturation and removed ;
155,194,276,607-615,699

[knpa]

Taking Camera delivery check.

[knpa]

Delivery check complete. All looks good apart from:

1. Looks like the calibration certificate from last year. Is that OK?
2. Noticed in the tiff tags that the gps time is given as 10/04/11, not 10/05/11 when the project was flown.

[benj]

LiDAR processing currently blocked until we get a new boresight flight

[anch]

Hyperspectral ready for delivery check

[knpa]

Taking hyperspectral delivery check.

[knpa]

Delivery check complete.

All looks good apart from:

1. Logsheet top section has lots missing. Can fill this out from the scanned logsheet.
2. Readme: aplcorr command needs altering. e141011b_post_processed_nav.bil should be e141011b_nav_post_processed.bil (script needs editing also)
3. Blank bands at 127 and 0 (eagle)
4. Blank band at 0 (hawk)

[anch]

Issues with delivery resolved.

Now putting the delivery on a disk

[anch]

Hawk and Eagle data sent to PI on 27/06/2011

[emca]

Starting LiDAR processing. Navigation has already been processed.

[emca]

LiDAR lines 7 and 8 (lines '3-4' and '1-2' on the logsheet) have short sections where there was an issue with scan angle.

The scan angle should oscillate regularly between approx. +-20 degrees. During flight line 8 the scan angle reduces down to 1, then goes up to ~34/35 before stabilising again. A similar pattern occurs several times over the two lines (the attached image explains better).

Both of these lines were repeat lines so the small sections in question are covered by other lines.

[emca]

scan_angle_issue

[emca]

CORRECTION: The scan line issue referred to above occurs on lines 6 and 7 - these are lines '5-6b' and '3-4b' on the logsheet.

LiDAR data is now ready for delivery check.

[jaho]

LIDAR delivery check:

In addition to mentioned scan angle issue in lines 6 and 7, there seem to be some gaps and minor artifacts in lines: 3, 4 and 5.

Other than that the data looks good to go.

[emca]

Data gaps in lines 3,4 5 are due to cloud cover. Have added this info to readme.

Data is on disk 112 and will be sent along with data from day 142.

[emca]

Above comments refer to LiDAR data delivery

[emca]

Delivered to PI 15/08/2011 along with data from day 142 (ticket #401)