Opened 4 years ago

Closed 4 years ago

Last modified 3 years ago

#584 closed flight processing (fixed)

EUFAR15/38 , flight day 170/2015, Mallorca

Reported by: lah Owned by:
Priority: immediate Milestone: 2015 data processing completion
Component: Processing: general Keywords:
Cc: Other processors:

Description

Data location: ~arsf/arsf_data/2015/flight_data/spain/EUFAR15_38-2015_170_Mallorca

Data arrived from ARSF via SATA disk on 09/07/2015

Scientific objective: Use airborne hyperspectral, LiDAR and SfM to improve process understanding by monitoring and modelling changing patterns of ecogeomorphological connectivity in Mediterranean insular catchments.

Priority: Unknown

PI: Joan Estrany
EUFAR Project ID: MEDhy2CON

Sensors:

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

Change History (30)

comment:1 Changed 4 years ago by lah

unpacking
Have moved fenix lines 17 and 18 to ~arsf/2015/flight_data/arsf_internal/dark_frames_2014_075 as the log sheet states that these are the dark current data files that we have been waiting for.

Fenix line 1 has been moved from the 169b data folders as it is time stamped as day 170. It is not in either logsheet so may not need to be processed.

comment:2 Changed 4 years ago by gej

Navigation Processing Complete

Had to use teqc for basestation.

Bad results using IPAS TC so have used IPAS Pro

Latitude : 39 32 26.26607
Longitude : 2 43 19.99703
Height : 53.679m

comment:3 Changed 4 years ago by gej

Started Hyperspectral Fenix Processing

comment:4 Changed 4 years ago by gej

Fenix Processing

Flightline 1 is skipped.
Fenix missed flightline 6.

therefore, flightlines are : 2,3,4,5,7,8,9,10,11,12,13,14,15,16

use_nav = false

comment:5 Changed 4 years ago by gej

Fenix Processing

Found SCT values

Flightline FENIX
1 ?
2 3.60
3 4.30
4 1.90
5 3.95
6 ?
7 1.40
8 2.60
9 2.50
10 3.95
11 1.70
12 2.60
13 18.5
14 3.40
15 1.60
16 7.30

Flightline 1 has bad data, and flightline 6 fenix missed.

Status: Waiting on Fenix Calibration files

comment:6 Changed 4 years ago by gej

Started Lidar Processing

comment:7 Changed 4 years ago by gej

Lidar processing

Got pitch and roll values.
Not many overlap regions on flightlines.
pitch and roll vary throughout

linerollpitch
1 020-0.001225-0.00230
2 709-0.001225-0.00230
3 252-0.000725-0.00218
4 910-0.00120-0.00230
5 529-0.00065-0.00180
6 222-0.00110-0.00230
7 834-0.00095-0.00230
8 428-0.00120-0.00184
9 137-0.00120-0.00180
10 744-0.0006-0.0020
11 336-0.0005-0.0025
12 023-0.0010-0.0022
13 644-0.0007-0.0020
14 251-0.0015-0.0022 cross section

comment:8 Changed 4 years ago by gej

Lidar Processing

Classification complete,

Starting full waveform processing

comment:9 Changed 4 years ago by gej

Lidar Processing

Full waveform processing complete
Creating Delivery

comment:10 Changed 4 years ago by gej

Lidar Processing

Delivery created
Ready for DC

comment:11 Changed 4 years ago by asm

Lidar Delivery Check
-Data quality remarks need more precise information.
-Screenshots look fine.
-Pitch and roll look perfect.
-Demcompare masked mean ~4.28
-Some point clouds (on low terrain) have been incorrectly classified as noise. Need to run again the classification algorithm with different values and check them manually afterwards.

comment:12 Changed 4 years ago by gej

Lidar Processing
Have added a bit more detail into data quality remarks.
Re-done classification and checked all flightlines manually. All looks okay to me now.

Re-made delivery,
Ready for DC

comment:13 Changed 4 years ago by asm

Lidar Delivery Check
-Previous comments has been solved: classification and readme are now OK. New ascii files has been created in accordance.
-Lidar full wave form also look fine.

Ready for delivery.

comment:14 Changed 4 years ago by asm

Lidar Data Delivery
Delivered on FTP server. Sent notification to PI.

comment:15 Changed 4 years ago by gej

Fenix Processing
Currently generating mapped files with new calibration.

comment:16 Changed 4 years ago by gej

Fenix Processing

Read me Generated Ready for Delivery Check

comment:17 Changed 4 years ago by asm

Fenix Delivery Check
Started.
Data quality remarks on readme file need to specify some details about fligthlines not included (lines 01 and 06). Moreover, please re-check sentence on cloud coverage and also add some specific words for clouds on flightline 15.

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

comment:18 Changed 4 years ago by asm

Fenix Delivery Check

-All data is correct.
-Spectra looks fine, good match to 6S simulated spectra.
-Creating zipped files.
Will be ready to delivery once readme has been updated and zip flies created

comment:19 Changed 4 years ago by lah

Fenix DC
Have double checked some spectra. Spike in overlap region, but this is in mask region, so ok to deliver.

comment:20 Changed 4 years ago by asm

Fenix Delivery Check
Done. Zipped files created. Ready to delivery.

comment:21 Changed 4 years ago by gej

Hyperspectral Data Delivered to PI on 20th October 2015 via FTP

comment:22 Changed 4 years ago by gej

PI had problems with download data via FTP so has now been delivered via HDD to University of Balearic Islands, 18th November 2015

comment:23 Changed 4 years ago by dac

Archiving

Started archiving

comment:24 Changed 4 years ago by dac

  • Resolution set to fixed
  • Status changed from new to closed

Archiving

Data now available via NEODC.

comment:25 Changed 4 years ago by dac

There is a letter which needs to go in with the hard drive - speak to Dan.

comment:26 Changed 3 years ago by stgo

Lidar reprocessing

Created new delivery

comment:27 Changed 3 years ago by dac

  • las1.0 -> las1.2
  • demcompare reports difference with ASTER as 4 m.
  • Corrected DEM name in header file
  • The offsets between lines are larger than normal - suggest putting something to indicate this in readme. Previous delivery had "These flightlines have a limited overlap region and are in mountainous regions, this means that the data may be less accurate due to the difficulty of calculating pitch and roll errors where the flight-lines do not overlap or are in a mountainous region where the altitude of the terrain is constantly changing."

Once readme has been updated ready to deliver.

comment:28 Changed 3 years ago by dac

Added the following to readme:

"The mountainous terrain and lack of buildings meant correcting for errors in pitch and roll was difficult for this flight, resulting in larger than normal elevation differences between lines"

Started copying to hard drive.

comment:29 Changed 3 years ago by dac

LiDAR Delivery

Reprocessed LiDAR delivered on hard drive (13/04/2016) and uploaded to NEODC.

comment:30 Changed 3 years ago by dac

Archiving

Reprocessed LiDAR now available from NEODC.

Note: See TracTickets for help on using tickets.