Custom Query (419 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (82 - 84 of 419)

Ticket Resolution Summary Owner Reporter
#524 fixed RG12/09, flight day 159/2014, Wessex knpa
Description

Data location: /users/rsg/arsf/arsf_data/2014/flight_data/uk/RG12_09-2014_159_Wessex/

Data arrived from ARSF via network transfer on 09/06/2014 Data archived on 13/01/2014

RG12/09 Scientific objective: Biodiversity and the provision of multiple ecosystem services in current and future lowland multifunctional landscapes

RG12/09 Priority: 10

PI: France Gerard

Sensors:

Camera (Requested), delivered 14/08/2014 Fenix (Requested) LiDAR (Requested), delivered 14/08/2014 FW LiDAR OWL

#520 fixed RG12/09, flight day 088/2014, Wessex dap stgo
Description

Data location: /users/rsg/arsf/arsf_data/2014/flight_data/uk/RG12_09-2014_088_Wessex

Data arrived from ARSF via network transfer on 31/03/2014

Scientific objective: Unknown

Priority: Alpha 5 - high

PI: France Gerrard

Sensors:

  • Fenix (requested), Delivered 08/10/2014, Submitted to NEODC 21/04/2015
  • Leica LIDAR (requested), Delivered 08/10/2014, Submitted to NEODC 21/04/2015
  • RCD (requested), Delivered 08/10/2014, Submitted to NEODC 21/04/2015
#88 fixed Restricting level 1 processing by scan line causes error mggr anee
Description

The use of -l in azspec produces a blank image if anything than a start line of 0 is used. The end line number does seem to produce the correct effect however.

Same problem also occurs in azatm (causes errors saying "scan jump from: 0 to 191119 scan : 191119 rejected"). Same option in azcas2 seems to work correctly.

Note: See TracQuery for help on using queries.