EU15/18, flight day 174, Toulouse

[lah]

Data location: /users/rsg/arsf/arsf_data/2015/flight_data/france/EUFAR15_18-2015_174_Toulouse

Data arrived from ARSF via SATA disk on 09/07/2015.

Scientific objective: Hyperspectral measurements over agro-forestry areas for landscape assessment of agricultural health, ecophysiology, and satellite product validation.

Priority: Unknown

PI: Jean-Louis Roujean
EUFAR Project ID: AHSPECT

Sensors:

• Fenix (requested)
• Leica LIDAR (not requested)
• Leica FW LIDAR (not requested but flown anyway)
• Owl (not requested but flown anyway)

[gej]

Navigation Processing complete

Basestation:
Lat: 43 38 13.01189
Long: 1 21 58.49814
Ell. Height: 199.663

Position Seperation: Slight spike to -0.06 towards end of flight line, rest below -0.04
Position Accuracy: Lat and long all within +-0.035 Height within +-0.05

[lah]

Unpacking
Removed corrupt webcam images:

• 150623_095016_000.jpg
• 150623_123907_000.jpg
• 150623_124117_000.jpg

[asm]

Lidar Processing
Started.

[gej]

Hyperspectral Processing
Started.

[dac]

Sent notification email to PI with links to KML

[asm]

Lidar Processing

Found pitch and roll consistent with all lines

Roll	-0.0010109
Pitch	-0.0022489

[asm]

Lidar Processing

Classification started.

[asm]

Lidar Processing

Classification for discrete lidar finished.

[asm]

Lidar Processing

Classification for lidar full wave form started.

[asm]

Lidar Processing
Two flightlines are bigger than 50gbs. Process is killed due to that, stgo is splitting the lines on the spare machine.

[gej]

Hyperspectral Processing
found SCT values

Long flightlines, some had a varying SCT value, have currently gone for best throughout line, but if it looks like they may be have too much variance in the line will change

Flightline	FENIX
1	23.45
2	3.2
3	2.90
4	2.25
5	3.675
6	2.75
7	2.5
8	1.45

[asm]

Lidar Processing
Classification for full wave form finished. Elevation difference measured, delivery created including Readme file. Ready for Delivery Check'.

[gej]

Lidar Delivery Check

Read Me
Need to add N/S to UTM projection,

Data qaulity remarks needs reworkding. instead of:
"This might have as a result that the elevation difference on overlapping areas could be not precise",
try:
"This may have resulted in the elevation difference on overlapping areas being less precise"

Navigation
There are only 6 trj files, but 8 flightlines. Not sure if this is due to the flightlines being split or not, if it is should maybe make a comment about it somewhere.

Screenshots
Don't think anything can be done, but maybe make a comment in readme that the screenshots aren't of the best quality due to the length of the flightlines.