RG15/18, flight day 290a, Ribble

[asm]

Data location: /users/rsg/arsf/arsf_data/2015/flight_data/uk/RG15_18-2015_290a_Ribble

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

Scientific objective:

Priority: Unknown

PI: Andrew Tyler

Also offered PI EA LiDAR with project. To be delivered at same time (exact format to be determined).

Sensors:

• Fenix (requested)
• RCD (not flown)
• Leica LIDAR (requested)
• Leica LIDAR FWD (not flown)
• Owl (requested)

[dac]

From Gary 05/01/2016 "all LiDAR and RCD to be processed. Customer to decide regarding Fenix data."

[dac]

Fenix

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

[dac]

Fenix

Level 1b files sent to PIs via FTP for quality checking before proceeding with processing.

[dac]

Started navigation processing.

[dac]

Navigation processing

Basestation PPP result for BLAP

lat	53 46 36.94753
long	-3 02 05.890607
height	66.2

[dac]

Navigation processing

Good position separation result obtained with default parameters.

[dac]

Hyperspectral

Processed all files using updated aplnav and default SCT of 1 second. Some lines are off so will try with 0 second offset instead.

[dac]

LiDAR

Started LiDAR processing.

[dac]

Hyperspectral

The default offset of 1 didn't work for all lines so needed to use 0:

Flightline	Fenix SCT
1	0
2	0
3	1
4	1
5	1
6	0
7	1
8	1
9	1
10	1
11	1
12	1
13	1
14	1
15	1
16	1
17	1
18	1
19	1
20	1
21	1

Mapping all bands.

[dac]

Hyperspectral

Bands mapped - making delivery.

[lah]

Fenix DC

• Do we need Eagle & Hawk pages in logsheet?
• xml files wrong operator
• DQ report has ARSF & doesn't mention sct fixed.
• Needs a readme (with some quality comments)
• Spectra look ok apart from the spike between the VNIR and SWIR, which is masked.

Line 4 low intensity and no return from bands below 30 for part of the line. Visible bands are quite low in other lines e.g. 12. Some weird striping in line 21.

• scts look good.

[dac]

Hyperspectral

Created delivery. Addressed some of lah's comments:

Do we need Eagle & Hawk pages in logsheet?

Removed these and regenerated

xml files wrong operator

Changed from Tom to James

DQ report has ARSF & doesn't mention sct fixed.

This is the 2015 data quality report. I suggest if the 2016 is ready we also include this and explain in Readme or delivery email.

Needs a readme (with some quality comments)

Have added, mentioned dropped frames and low signal. PI was informed of both before these data were processed and provided 1b data to confirm processing was required. In the readme NERC-ARF is used with a footnote to explain data were acquired when the facility was NERC ARSF.

Ready to delivery once Readme has been checked.

[mark1]

Hyperspectral DC

Read me looks OK.

check_apl_cmd commands all ran OK.

[dac]

Hypserpectral

Started zipping mapped files.

[dac]

Hyperspectral

Delivered via FTP (arsf2). Added note about SCTs in email. Will send 2016 data quality report when ready.

[dac]

LiDAR Processing

Good alignment with boresight pitch and roll, although not many buildings to confirm with.

Lots of noise in LAS files. Best automated results using -cloud above -cloud below -below -5 -isolated 4 5. Refining manually.

[dac]

LiDAR Processing

Created delivery. Needs readme before checking.

[dac]

LiDAR Processing

Generated Readme. Ready for delivery check.

[lah]

Lidar DC

• Bit odd that the elevation difference table in readme uses the logsheet name instead of file number, and should really include all 3 digits of the lines not labelled UL*.
• Can we add a reason why the lines are missing data down the middle of the swath? I assume that the lidar was not set for the correct altitude when it was reset in line 9, but could it have been fixed? You've also used a comma between "track" and "As".
• Where you've recommended to merge the point clouds before generating a DEM to minimise gaps, might be worth saying that we could so this/ why we haven't provided this.
• No owl info on logsheet, but not important for a lidar delivery.
• Roll & pitch look ok.
• Lines 5, 6 and 8 appear to have some missed noise (above ground near below ground classified noise)
• demcompare mean = 3.33

[dac]

LiDAR

• Have included all three digits of flightline names. It should be flightline name and not file name.
• I'm not sure why there is missing data, and why it would be OK for files 16 - 19 then start again. Will leave the readme as is rather than trying to guess.
• Replaced comma with full stop.
• I've generated a merged point cloud DSM patched with EA lidar which will also be included when this is delivered but in a separate folder. From next year we will be merging point clouds before generating the DSM.
• Improved classification for 5, 6 and 8 and regenerated ASCII files and DEMs.

[dac]

Have copied EA LiDAR to the FTP server (arsf2), including patched mosaic for use in APL. Will include in notification email once lah is happy with changes made to LiDAR delivery.

[dac]

LiDAR

• Classified some additional noise missed in line 5 (mistook for shrubs) and regenerated ASCII file.

[lah]

Lidar DC

Readme is now ok and most noise has been classified. Still quite a bit of unclassified noise in line 5, but apart from that it is ready to deliver.

[dac]

LiDAR

Revisited line 5 and classified some more missed noise points.

[dac]

LiDAR Delivery

Delivered via FTP (arsf2) and notified PI.