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

[asm]

Data location: ~/arsf_data/2015/flight_data/france/EUFAR15_28-2015_271b_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 idea of data quality.

[asm]

Navigation Process

Started.

[asm]

Basestation verification:

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

[asm]

Navigation Process

Really good results, accuracy is one order of magnitude better than limits. Copying files across and navigation process will be finished.

[asm]

RCD Processing

Started. Have already converted raw files to tif.

[asm]

RCD Processing

There are two eventfiles and two PhotoId. The one that gives right values is 150928-053347.

[asm]

RCD Processing

Flightline 009 only had one photo not totally covered by clouds. Everything else looks OK, no data quality remarks. Delivery and readme created. RCD is waiting delivery check.

[dac]

RCD

Started delivery check.

[dac]

RCD Delivery Check

Looks OK. However, images being removed due to cloud coverage isn't mentioned in readme. Once this has been changed ready to deliver.

[stgo]

Lidar processing

Lines generally have the boresight pitch and roll. Only exception is 141626, will adjust manually for this line.

pitch	-0.00226
roll	-0.00101

[stgo]

Lidar processing

141626 pitch and roll adjustments:

pitch	-0.00081
roll	-0.00246

processing full waveform data

[asm]

RCD processing

Have added a note on readme about clouds and pictures not included.

[dac]

RCD

Updated readme looks good. Ready to delivery.

[asm]

Delivery

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

[dac]

Fenix Processing

Set SCT files generating over weekend ready for gej next week.

[stgo]

Lidar processing

Created a delivery, ready for check.

[gej]

Fenix Processing

Data is very cloudy, with not many usable areas
found SCT values of:

Flightline	FENIX
1	1.00
2	1.00
3	1.00
4	1.00
5	0.97
6	1.00
7	1.00

Mapping files now

[gej]

Fenix Processing

Delivery and Readme created

Ready for Delivery check

[lah]

Lidar DC

• Roll & pitch look fine
• There's a bit of missed cloud in a couple of flight lines that you might want to reconsider. They could be patches of mountain, but the surrounding bits are classified as noise, so would make sense to get classify these as noise too.
• Noisy should still be spelled without the e in the readme
• Corrected sol file name
• demcompare masked mean = 4.44
• FW files look ok in waveviewer

Everything ok apart from recheck that classification and the readme typo

[dac]

LiDAR

(taking over from stgo)

• Corrected typo in reame
• Redid classification - copying to FW and redoing ASCII

[dac]

LiDAR

Copied classification to FW files, recreated ASCII and recalculated point cloud statistics for readme.

Marking as ready to deliver.

[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

[asm]

Fenix Delivery Check

Started.

[asm]

Fenix Delivery Check

-Readme and logsheet says that there are only 6 flightlines but 7 flightlines have been included on this delivery. It is the first flight-line the one not included on logsheet we concluded it should be included on the delivery as it has usable data and a great overlapping region. Will need to update the readme to include that flightline and the correct table should look:

Logsheet flightline name	Fenix file identifier
not on logsheet	f271b011b
013	f271b021b
...	...

-Data quality remarks only says: There is a lot of cloud cover across all flightlines. Would be better to specify that caused the fenix saturation.

[dac]

Fenix

Updated names in readme and made note "The first file was not on the logsheet (likely a test line) but has been included as it overlaps the other lines for the flight and may contain useful information."

Added "Due to this cloud cover there are a large number of bands with overflows" - Same as 271a.

Ready to go (once mapped files have been zipped) if Aser is happy comments from DC have been addressed.

[asm]

Fenix Delivery Check

-Also one flightline 016 was aborted but could be delivered as it could have usable data.

-Apl commands tested and working fine.

-Py6S wrapper was failing to find igm files. Tried every single flightline separately and the spectra looks fine (could not find vegetation pixel for flightline 3 and 7)

-All others checks have been done and everything looks OK.

Will zip files files and will ready to go.

[asm]

Delivery

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

[dac]

Archiving

Started uploading processed data to NEODC

[dac]

Archiving

Processed data uploaded to NEODC

[dac]

Archiving

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

[asm]

Archiving

Data now available from NEODC. Closing ticket.