Opened 5 years ago

Closed 3 years ago

#561 closed flight processing (fixed)

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

Reported by: dap Owned by:
Priority: whenever Milestone:
Component: Processing: general Keywords:
Cc: Other processors:

Description (last modified by dac)

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)

Change History (32)

comment:1 Changed 5 years ago by dap

  • Description modified (diff)

comment:2 Changed 5 years ago by dap

  • Description modified (diff)

comment:3 Changed 5 years ago by 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

comment:4 Changed 4 years ago by asm

Navigation Processing
Started navigation processing

comment:5 Changed 4 years ago by 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

comment:6 Changed 4 years ago by 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.

comment:7 Changed 4 years ago by asm

Hyperspectral Processing
Starting hyperspectral processing.

Last edited 4 years ago by asm (previous) (diff)

comment:8 Changed 4 years ago by 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

comment:9 Changed 4 years ago by asm

Hyperspectral Processing
Awaiting new calibration for fenix

Last edited 4 years ago by asm (previous) (diff)

comment:10 Changed 4 years ago by asm

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

Roll -0.0061
Pitch -0.00055

Starting classification.

comment:11 Changed 4 years ago by 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).

Last edited 4 years ago by asm (previous) (diff)

comment:12 Changed 4 years ago by 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.

comment:13 Changed 4 years ago by asm

LiDAR Processing
Delivery created.

comment:14 Changed 4 years ago by asm

LiDAR Processing
Readme created. Ready for Delivery Check.

comment:15 Changed 4 years ago by stgo

Lidar Delivery check
Beginning Lidar check

comment:16 Changed 4 years ago by 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)

comment:17 Changed 4 years ago by 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.

comment:18 Changed 4 years ago by 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.

Last edited 4 years ago by stgo (previous) (diff)

comment:19 Changed 4 years ago by asm

Lidar Delivery Check

Readme file and everything looking good.

comment:20 Changed 4 years ago by stgo

Lidar Delivery Check

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

comment:21 Changed 4 years ago by gej

Lidar Delivered 18 August Via FTP

Last edited 4 years ago by gej (previous) (diff)

comment:22 Changed 4 years ago by asm

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

comment:23 Changed 4 years ago by dac

  • Description modified (diff)

comment:24 Changed 4 years ago by stgo

Fenix reprocessing

Ready for delivery check.

This delivery needs to be thoroughly checked for:

  • correct lines included
  • correct linenames from logsheet
  • data quality comments
  • spectra shifts

comment:25 Changed 4 years ago by gej

Fenix delivery check
have copied logsheet into directory.

Flightlines 13,14,15 and 20 have high cloud cover in the lower regions. should be mentioned in readme. (20 also has a large blackspot in the screenshots, i think this is because of cloud.)

Screenshots need renaming according to proj tidy.
SRTM dems are in delivery, don't think they are supposed to be.

Data quality report needs updating to 2015 version

checked spectra, looks okay to me.

Last edited 4 years ago by gej (previous) (diff)

comment:26 Changed 4 years ago by stgo

Fenix DC

Updated readme with new comment

screenshots renamed

SRTM removed

data quality updated

comment:27 Changed 4 years ago by gej

Fenix DC

Readme comment is now fine,

Screenshot names are fine,
SRTM dem has been removed,
Data quality report is now fine and proj_xml has been changed to match.

needs spectra checking by dac or lah.

comment:28 Changed 4 years ago by lah

Fenix DC - spectra
Have checked spectra for all lines and no major problems. SWIR shift looks within 5 nm, so no problem there. There is a persistent narrow spike and an occasional hump in the overlap region, both of which are in the mask region. The spike is generally larger for the early lines which have lower signal, probably due to the low sun angle.

Ready to deliver once files have finished zipping.

comment:29 Changed 4 years ago by gej

Fenix Delivered via FTP to Paul Aplin and via Hard drive to Doreen Boyd(University of Nottingham) on 11/11/2015

comment:30 Changed 4 years ago by dac

Sent hard drive to Paul Aplin on 23/11/2015 due to problems downloading data via FTP (slow transfer speed).

comment:31 Changed 3 years ago by dac

Archiving

Tidied up ready for archiving. Renamed owl data. Line 21 had no hdr file so created a dummy one for renaming then removed.

Started uploading to NEODC.

comment:32 Changed 3 years ago by asm

  • Resolution set to fixed
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.