MA14/08, flight day 317/2014, North Selangor Peat Swamp Forest

[dap]

Data location: ~arsf/arsf_data/2014/flight_data/malaysia/MA14_08-2014_317_Selangor

Data arrived from ARSF via network transfer on 05/01/2015.

Scientific objective: to characterise spatially how oil palm cultivation is degrading tropical peatland ecosystem services, using airborne hyperspectral and LiDAR imagery, and supported by an intensive field campaign, in Malaysia’s North Selangor tropical peat swamp forest.

Priority:

PI: Paul Aplin

PI is happy to receive data by USB Hard Disk, network transfer or DVD
Co-I Doreen Boyd requested delivery via USB Hard Drive

The following webcam images were removed as they are corrupt:
141113_025040_000.jpg
141113_004729_000.jpg
141113_014456_000.jpg

OWL data were collected and are present. proj_tidy does, however, suggest that too few dark frames were collected for file Peninsular_Selangor_Paul_Aplin_0305.hdr (only 44 dark frames collected).

Sensors: ¶

• Fenix (requested)
• LiDAR (requested)
• FW LiDAR (requested)
• RCD (requested, lower priority)

[mark1]

Have added a 'gps stop time' to flight line 18 .hdr file based on start time of next line, to replace the original time of xx.xx.xx.x

[asm]

Navigation Processing
Started navigation processing

[asm]

Basestation data
Have had to convert the basestation using teqc

Latitude	3 07 31.68506
Longitude	01 33 43.26778
ELL. Height	18.839 m

[asm]

Lidar Processing
Started. There is a lack of useful features for geo-corrections (No roofs or edges), pitch and roll errors expected to be less accurate.

[asm]

Hyperspectral Processing
Starting hyperspectral processing.

[asm]

Hyperspectral Processing - SCT values
Found SCT values. Flightline 18 did not pass the navigation process.

Flightline	FENIX
1	0.97
2	0.89
3	0.93
4	0.94
5	1.01
6	0.90
7	0.98
8	0.95
9	0.95
10	0.95
11	0.97
12	0.90
13	0.95
14	0.97
15	0.98
16	1.00
17	0.98
18	N/A
19	0.98
20	1.02
21	0.99

[asm]

Hyperspectral Processing
Awaiting new calibration for fenix

[asm]

LiDAR Processing
Found pitch and roll values, consistent for all lines:

Roll	-0.0061
Pitch	-0.00055

Starting classification.

[asm]

LiDAR Processing
Finished classification. Due to the extend of low clouds on flightline 011 (LDR13112_025741_1.LAS), some points could be wrong classified (vegetation classified as noise).

[asm]

LiDAR Processing
The elevation difference could not be calulated between several flightlines because the amount vegetation was dominant and therefore, they lack of usable features.

[asm]

LiDAR Processing
Delivery created.

[asm]

LiDAR Processing
Readme created. Ready for Delivery Check.

[stgo]

Lidar Delivery check
Beginning Lidar check

[stgo]

Lidar Delivery check

• Link to aster policies 404s in readme, check with dap if his changes to the template have been accepted.

• Data quality remarks:

extend - extents

"Moreover, the elevation difference could not be calulated between several flightlines because the amount vegetation was dominant and therefore, they lack of usable features."

would read better as

"The elevation difference between several flightlines could not be measured due to a dominance of vegetation masking usable features"

I still don't like several flightlines though, it would be better to specify which ones (unless its all of them)

• flightlines/discrete_laser/las1.0 should be called las1.2

• The fw_laser folder contains a las1.3 folder but there are no fw files? Same for TRJ files, I'm assuming they just weren't copied during the delivery creation procedure, these need to be classified and copied in.

Proj tidy is complaining about the naming of sol file and lidar intensity screenshot but I can't see why (they look right to me)

[asm]

Lidar Delivery check

I believe that for proj tidy the sol file should be called:
MA14_08-2014_317.sol versus the previous MA14_08-2014-317.sol
Renamed it just to check if I am right. Not a clue about the intensity screenshot.

-Data quality remarks: Corrected (Thanks stgo).
-New readme created (link to aster policies should have been solved, as far as I know it seems that way)
-las1.0 renamed to las1.2
-las1.3 has now the fw.
-trj files looked good to me.

[stgo]

Lidar
Last comment didn't post.

FW lidar is classifying on asms machine, I have updated the readme quality remarks to read a bit nicer.

[asm]

Lidar Delivery Check

Readme file and everything looking good.

[stgo]

Lidar Delivery Check

asm has fixed the readme and the full waveform files are now classified. Ready for delivery.

[gej]

Lidar Delivered 18 August Via FTP

[asm]

Lidar Delivered
Problems reported downloading the data. Sent a hard drive to Dr. Doreen S. Boyd as requested (15th September 2015)