EUFAR15/28, flight day 271a/2015, Mont Blanc

[asm]

Data location: ~/arsf_data/2015/flight_data/france/EUFAR15_28-2015_271a_Mont_Blanc

Data arrived from ARSF via SATA disk on 26/10/2015

Scientific objective: Hyperspectral airborne measurements over snow, glaciers and vegetation; intercomparison with ground-based
measurements and modelling.

Priority: Unknown

PI: Antoine Rabatel

EUFAR Project ID: ISOTHERM

Sensors

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

[asm]

General processing
For general processing, will use Rinex data provided by Christian Vincent (already placed on basestation directory).

[dac]

From Gary 05/01/2016 "all LiDAR and RCD to be processed"

[dac]

Fenix

Replaced wavelengths and ran through radiometric calibration using aplcal to get a better ideal of data quality.

[asm]

Basestation Verification

Done. Same results than 271b:

Latitude 45 55 49.13361
Longitude 6 54 52.48238
Ell. Heightt 2133.858 metres
AntHgt 0.440m (LEIAS10, MeasDist 0.360m)

[asm]

Navigation processing

Rinex data provided do not have enough accuracy (±100 m). Will ask PI:
a) Process anyway or provide another basestation data
b) Process using closest GNSS data (Lat separation ±2 m, Lon ±5 m and height ±2.5 m)
c) Use PPP (within limits)

[lah]

RCD Processing

Images converted to Tiffs

[lah]

RCD

Delivery created, ready for checking.

[asm]

Navigation processing

stgo took over me (I was away) and identified the problem as an error with Leica Software when dealing with GLONASS data. An update provided by them solved the issue. He might update this with more details on the future but this is only to point out that navigation processing is now finished with good accuracy.

[asm]

Lidar Processing

Started. There are two different areas recorded, one isolated flightline with no overlaps and one large flightline that looks like an alfa letter (a loop) that overlaps with both regions.

[dac]

RCD Delivery Check

Started delivery check

[dac]

RCD Delivery Check

Everything looks good - some really nice imagery.

Ready to deliver.

[dac]

RCD Delivery

Delivered via FTP (arsf20) 18/03/2016

[dac]

Fenix Processing

Generated config file for apl. Needed to rename raw data from FENIX241a.

Set specim_qsub to start on hot desk computer at ~ 18:00 so SCT files are generated over weekend ready for gej to take over next week.

[gej]

Fenix Processing

Found SCT values:

Flightline	Fenix SCT
1	0.97
2	0.97
3	0.97
4	0.97
5	0.97
6	0.97
7	0.97
8	0.97
9	0.97
10	0.97
11	0.97
12	0.02
13	0.97
14	0.97
15	1.09
16	0.97
17	-0.04
18	0.97
19	1.09
20	0.97
21	-0.07
22	0.97

Fully mapping files now.

[gej]

Fenix Processing

Delivery and Readme created.

Ready for delivery check

[dac]

Fenix Delivery Check

Starting deliver check.

[dac]

Fenix

Checking over notes from Gary after checking screenshots and level1b data PI requested Fenix data to be processed. This was reflected in quote agreed by Gary 26/02/2016

[dac]

Fenix Delivery Check

Fixed a couple of minor points:

• lines 10 to 22 have a large amount of cloud cover -> Lines 10 to 22 have a large amount of cloud cover. Due to this cloud cover there are a large number of bands with overflows for these lines.
• removed .aux.xml files.

Due to clouds a lot of pixels are saturated. PI is aware of this and requested data to be processed anyway.
When comparing with Py6S spectra looks fine - likely because the check for veg pixels skips those which have saturated.

Zipped mapped files. Ready for delivery.

[asm]

Lidar Processing

Found pitch and roll errors for the first two flightlines (that have usable features). Pitch and roll are not consistent trough all lines.

[asm]

Delivery

Fenix delivered on 29/03/2016 via FTP (arsf20) and notification has been sent to PI.

[asm]

Lidar Processing

Found pitch and roll values. Flightline LDR150928_093841_ is do not overlap with any line. Used the closest in time pitch and roll values.

Flightline	Roll	Pitch
LDR150928_085029_1.LAS	-0.001082	-0.002335
LDR150928_085601_1.LAS	-0.001082	-0.002335
LDR150928_090027_1.LAS	-0.001055	-0.002335
LDR150928_090613_1.LAS	-0.0009	-0.002335
LDR150928_091102_1.LAS	-0.0009	-0.00272
LDR150928_091643_1.LAS	-0.0009	-0.00215
LDR150928_092134_1.LAS	-0.0009	-0.0029
LDR150928_092759_1.LAS	-0.0008	-0.00215
LDR150928_093841_1.LAS	-0.0008	-0.00215
LDR150928_094955_1.LAS	-0.0010	-0.0025
LDR150928_095551_1.LAS	-0.001082	-0.0027
LDR150928_100056_1.LAS	-0.00085	-0.002335
LDR150928_100718_1.LAS	-0.00085	-0.00242
LDR150928_101257_1.LAS	-0.00085	-0.00242
LDR150928_101834_1.LAS	-0.00085	-0.00242
LDR150928_102435_1.LAS	-0.00085	-0.00242
LDR150928_102952_1.LAS	-0.00085	-0.00242
LDR150928_103520_1.LAS	-0.0007	-0.00242
LDR150928_104415_1.LAS	-0.00085	-0.00242
LDR150928_104951_1.LAS	-0.0006	-0.0026
LDR150928_105520_1.LAS	-0.00085	-0.00242
LDR150928_110028_1.LAS	-0.0005	-0.0026

[asm]

Lidar Processing

Classification for discrete Lidar is complete. Have created FW files and currently running classification.

[asm]

Lidar Processing

Delivery and readme created. Awaiting delivery check.

[lah]

Lidar DC

• Roll & pitch look fine
• Classification mostly fine. There's a bit of missed rain right at the top end of site b across multiple flightlines, but not enough to worry about.
• Line 9 does have a lot of misclassification. You might be able to do a better job with smaller cross-sections, otherwise mention in the readme that there is a lot of cloud and not all of it can be correctly classified.
• Readme data quality should mention rain in many flightlines and the cloud in line 9. Also say "same values as" rather than "same values than"
• fw look ok
• changed sol file name - to _
• updated utm dem name in header to match file
• demcompare non-absolute mean: 6.35 m

So just recheck line 9 classification and add some more about cloud and rain to the readme

[asm]

Lidar Processing

Have changed classification for flightline 9 as some cloud points were not classified as noise. Have run the classification on the full waveform as well. Recreated asscii, dem and screenshots.
Re-created readme and made hanges suggested.

Ready for DC again.

[asm]

Lidar Processing

There was a problem creating the DEM. Re-creating again.

[asm]

Lidar Processing

DEM re-created.

[lah]

Lidar DC

• copied in DEM .txt warning that disappeared
• renamed las1.0 to las1.2
• changed name in new utm dem hdr to match file

Everything else looks fine now, so ready to deliver (and delete the backup)

[asm]

Delivery

LiDAR delivered on 05/04/2016 via FTP (arsf20) and notification has been sent to PI. This completes requested data for this project.

[asm]

Archiving

Started.

[asm]

Archiving

Finished archiving processed data. Raw data still pending.

[dac]

Archiving

Processed data available from NEODC (​http://browse.ceda.ac.uk/browse/neodc/arsf/2015/EUFAR15_28/EUFAR15_28-2015_271a_Mont_Blanc)

[asm]

Archiving

Data now available from NEODC. Closing ticket.