Opened 9 years ago

Last modified 9 years ago

#587 new flight processing

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

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

Description (last modified by stgo)

Data location: ~/arsf_data/2015/flight_data/france/EUFAR15_28-2015_175b_Mont_Blanc

Data arrived from ARSF via SATA disk on 09/07/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)

Change History (26)

comment:1 Changed 9 years ago by stgo

  • Description modified (diff)

comment:2 Changed 9 years ago by asm

Navigation processing
Started.
Needed to use teqc. Done basestation verification.

lat 45 44 21.34921
long 7 21 53.26501
Ellipsoidal height 598.474 m
Antenna height 0.085 m
Last edited 9 years ago by asm (previous) (diff)

comment:3 Changed 9 years ago by asm

Navigation processing

Navigation finished.

Best solution we could get was on Ipas Tc with an ambiguity of 40 cm
for the position separation on the first 3 flightlines and smaller than
10 cm for the rest.

comment:4 Changed 9 years ago by asm

Fenix hyperspectral processing
Started.

There was a problem generating config file due to wrong values on FENIX175b-15-3.hdr
GPS Start Time = UTC TIME: 13:35:53.0000
GPS Stop Time = UTC TIME: 13:35:53.0000
GPS Starting point = {46.014683, 6.837837}
GPS Ending point = {46.014683, 6.837837}

Original header moved to processing/old_fenix_line3_hdr folder and header on fenix folder replaced for:
GPS Stop Time = UTC TIME: 13:40:01.0000

comment:5 Changed 9 years ago by asm

Fenix hyperspectral processing

Error form navigation:
Requested sync time index is out of bounds in GetSyncDelay()

needed to set on config file:
use_nav = false

comment:6 Changed 9 years ago by gej

Lidar Processing Started

comment:7 Changed 9 years ago by gej

Lidar Processing
Found pitch and roll. Some variation.

LineRollPitch
04 243-0.00065-0.00226
06 442-0.00065-0.00226
08 555-0.00065-0.00226

Rest of lines:

RollPitch
-0.00101-0.00226

comment:8 Changed 9 years ago by gej

Lidar Processing
Classification of discrete data finished.
Doesn't appear to be any Full wave form data so will make discrete delivery.

comment:9 Changed 9 years ago by asm

Fenix hyperspectral processing
Found SCT values.

Flightline FENIX
1 30.39
2 3.79
3 51.85
4 2.29
5 4.13
6 3.04
7 6.53
8 3.24
9 34.22
10 2.67
11 2.82
12 3.62
13 3.32
14 1.72
15 4.11
16 2.10
17 1.72
18 2.87

Waiting new calibration for Fenix.

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

comment:10 Changed 9 years ago by gej

Lidar Processing

Logsheet now generated

Discrete Delivery Created,

Ready for Delivery Check

comment:11 Changed 9 years ago by asm

Lidar Delivery Check
Started.

-Readme file has some errors. Digital elevation has wrong format for elevation difference should be the same that the line_numbering in the lidar-config file. It needs to be changed in the config file as well (also the quality remarks).

comment:12 Changed 9 years ago by asm

Lidar Delivery Check

-Demcompare masked mean -4.7874952691507
-Pitch and roll look fine.
-Demcompare masked mean
-Screenshots look OK
-Classification is correct.

Will be ready to delivery once the changes to the readme has been made.

comment:13 Changed 9 years ago by gej

Lidar Delivery

Changed Read-me to use line-numbering.

Ready for DC

comment:14 Changed 9 years ago by asm

Lidar Delivery
All changes has been made. Ready to delivery.

comment:15 Changed 9 years ago by asm

Lidar Delivery
Mail sent to PI and waiting in order to let him select delivery method.

comment:16 Changed 9 years ago by asm

Lidar Delivery
Lidar delivered via FTP. Notification has been sent. Finished.

comment:17 Changed 9 years ago by asm

Fenix Hyperspectral Processing
Delivery created with the new calibration. Readme file generated. Ready for Delivery Check.

comment:18 Changed 9 years ago by gej

Fenix delivery check

Screenshots need renaming, everything else looks okay.
Spectra still needs checking. before delivery.

comment:19 Changed 9 years ago by asm

Fenix Processing

Screenshots have been renamed.
Running Py6S to compare predefined vegetation against Fenix spectra. Output is on airborne's tmp directory as suggested. Some flightlines does not have vegetation and will not compare them using Py6S.

comment:20 Changed 9 years ago by dac

Fenix spectra check

Spectra looks fine - once mapped files have been zipped can be delivered.

comment:21 Changed 9 years ago by asm

Fenix Delivery

Mapped files has been zipped. Fenix delivery is ready to go.

comment:22 Changed 9 years ago by asm

Hyperspectral Data Delivered to PI on 12th November 2015 via FTP (arsf20). A notification mail has been sent.

comment:23 Changed 9 years ago by dac

Archiving

Started archiving

comment:24 Changed 9 years ago by dac

Archiving

  • Navigation data needs tidying up - not sure if the 'basestation_need_teqc' folder in processing is needed.
  • Two of the Owl lines have been renamed but not the rest - need to fix before sending to NEODC.

comment:25 Changed 9 years ago by dac

Archiving

Owl data renamed and navigation tidied by asm. Uploading to NEODC.

comment:26 Changed 9 years ago by dac

Archiving

Data now available from NEODC.

Note: See TracTickets for help on using tickets.