BAS13/01, flight day 070/2014, Tamar

[knpa]

Data location: /users/rsg/arsf/arsf_data/2014/flight_data/uk/BAS13_01-2014_070_Tamar/

Data arrived from ARSF via network transfer on 11/03/2014

BAS13/01 Scientific objective: unknown

BAS13/01 Priority: a4m

PI: France Gerard

Sensors:

Camera (Requested)
LiDAR (Requested)

[knpa]

France would like the flightlines divided into manageable chunks, 3 per flightline was suggested.

[benj]

Gary has confirmed that the PI would like FW LiDAR data for this flight (if we have any).

[stgo]

Tipo has completed nav processing already, have begun LiDAR processing.

[tipo]

Created hyperspectral delivery.

[stgo]

LiDAR pitch and roll values for lines 1221 and 1209:

pitch	0.00110916
roll	-0.003909414

Testing against other lines.

[stgo]

Beginning RCD D/C

[stgo]

Strange mark to top right corner of all images, scratch on lens? Will investigate other days to check for presence.

[stgo]

D/C complete:

• in data details, partialy needs to be spelled partially. Also need notes on how clouds effect data. (Effects on contrast etc)

• Strange white tint round edges (possibly cloud though) present from image 76 onwards

• some images, particularly 46 and 114 have high levels of cloud cover, is it worth delivering these?

• mention artefact in top right, have we got a better explanation about this?

[tipo]

Corrected readme.
White tint is just due to the direction of the sun.
#46, #114 etc do have a lot of cloud cover, but they also have quite a bit of the ground showing, so they may still be useful.

[stgo]

RCD d/c in progress.

[stgo]

Changes are fine, prepping for delivery.

[stgo]

RCD data dispatched on 04/06/2014

[stgo]

LiDAR roll values:

105232	-0.003650414
110145	-0.003450414
110457	-0.004080414
111817	-0.003850414
113038	-0.003900414
114318	-0.003709414
115604	-0.004100414
120905	-0.003909414
122134	-0.003909414
124730	-0.003650414
130040	-0.003895214
131333	-0.003909414
132746	-0.004100414
134117	-0.003690414
135412	-0.004265414

[stgo]

LiDAR delivery created. Awaiting D/C

[mark1]

Delivery check comments:

• Lidar are las 1.2 but in directory named 1.0, and in readme contents it says they are 1.0 (and later in data details). Also need to update hyperlink in read me to 1.2 format descriptors.
• PI name spelt incorrectly on logsheet
• please don't split line 01 or 03, they are only small anyway
• recreate the DEM (and screenshots) without so much ASTER patching
• only checked one line (02_parta vs 04_partc) but looks like some roll/pitch residual errors > 50cm - these need fixing if possible

[stgo]

Corrected values for line 2 (105232):
pitch: 0.00070916
roll: -0.003595214

Variable pitch was the cause of the error, will continue with lines 3 and 1.

[stgo]

Line 3 corrected values:
Pitch:0.000909160
Roll:-0.003445214

[stgo]

Fixed delivery according to above comments. Now reflects 1.2 status. 1 and 3 are no longer split.

[mark1]

delivery check (lidar):

• ascii filenames need renaming (remove *part_a* etc).
• projected dem needs renaming to include projection (-bng)
• do we need to send the sup file? Probably just confusing - I'd remove it from delivery.
• logsheet still has name spelt wrong

Other than the above the data looks fine - fix above and should be ready to deliver.

[stgo]

Made changes requested. Setting to ready to deliver.

[stgo]

Camera and lidar deliveries sent to NEODC for archiving 30/07/2014

[mark1]

Edited KML file in-place in RCD delivery to correct data paths for rcd thumbnails.