Custom Query (419 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (106 - 108 of 419)

Ticket Resolution Summary Owner Reporter
#359 fixed EU10/03 & EUFAR10/01 (AIMWETLAB), flight day 232b/2010, Aimwetlab (Kis Balaton) knpa iopa
Description

Data location: ~arsf/arsf_data/2010/flight_data/hungary/EU10_03-2010_232b_Aimwetlab_Kis_Balaton

Data arrived from ARSF via SATA disk Q on 15/09/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.

Sensors:

  • Eagle (27/10/2010 & 28/10/2010)
  • Hawk (28/01/2011)
  • Leica LIDAR (28/02/2011)
  • Digital Photography (27/10/2010 & 28/10/2010)
#373 fixed EU10/03 & EUFAR10/01 (AIMWETLAB), flight day 238c/2010, Kis Balaton knpa iopa
Description

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

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 (27/10/2010 & 28/10/2010)
  • Hawk (28/01/2011)
  • Leica LIDAR (19/04/2011 & 20/04/2011)
  • Digital Photography (27/10/2010 & 28/10/2010)
#370 fixed EU10/03, flight day 233a/2010, Lake Balaton East Area D emca knpa
Description

Data location: ~arsf/arsf_data/2010/flight_data/archive-overflow/EU10_03-2010_233a_Lake_Balaton_East_Area_D

Data arrived from ARSF via SATA disk Q on 15/09/10.

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 *note: lidar is low priority for this project*

PI: A. Tyler

Sensors:

  • Eagle (20/10/2010)
  • Hawk (28/01/2011)
  • Leica LIDAR (Requested but low priority)
  • RCD (20/10/2010)
Note: See TracQuery for help on using queries.