Opened 12 years ago

Last modified 4 years ago

#373 closed flight processing

EU10/03 & EUFAR10/01, flight day 238c/2010, Lake Balaton Peninsula — at Version 4

Reported by: iopa Owned by:
Priority: alpha 5 Milestone: 2010 data processing completion
Component: Archiving Keywords:
Cc: Other processors:

Description (last modified by iopa)

Data location: ~arsf/workspace/EU10_03-2010_238c_Lake_Balaton_Peninsula

Data arrived from ARSF via SATA disk Q on 15/09/2010.
However missing IPAS and LiDAR data on disk Q and on thelma delayed unpacking until 06/10/2010.

Scientific objective: Lake Balaton provides an ideal area for testing emerging algorithms on retrieval of in-water constituents and on mapping bloom-forming cyanobacteria using in-situ radiometric, airborne and satellite data.

Priority: a5 - the data set as a whole is listed as a5 due to it being part of EU10/03, however the PI of EU10/03 has lowered the LiDAR priority to a4m, and therefore LiDAR stands with a priority of a4h due to being part of EUFAR10/01.

PI: A. Tyler (EU10/03) & A. Zlinszky (EUFAR10/01)

When data is processed it should be dispatched to both PIs individually for their respective projects.

This data needed to be split into 238c and 238d, there was already a logsheet for each distinct set of data. The reason they needed splitting was that the first set of data (238c) is part of 2 projects (EU10-03), whereas the second (238d) only of 1 (EUFAR10-01). Originally they were both came from ARSF Ops as 238c.

Note: Data is currently symlinked from ~arsf/arsf_data/2010/flight_data/archive_overflow and when this is resolved the symlinks will need to be re-directed.

Sensors:

  • Eagle
  • Hawk
  • Leica LIDAR
  • Digital Photography

Change History (4)

comment:1 Changed 12 years ago by iopa

  • Description modified (diff)

comment:2 Changed 12 years ago by iopa

Applanix and IPAS is common with 238d and need only be processed once.

comment:3 Changed 12 years ago by iopa

  • Description modified (diff)

comment:4 Changed 12 years ago by iopa

  • Description modified (diff)
Note: See TracTickets for help on using tickets.