Opened 15 years ago

Last modified 8 years ago

#333 closed flight processing

CEH07/04, flight day 102b/2010, Moorhouse — at Version 5

Reported by: benj Owned by:
Priority: alpha 4 low Milestone: 2010 data processing completion
Component: Archiving Keywords:
Cc: Other processors:

Description (last modified by jb362)

Data location: ~arsf/arsf_data/2010/flight_data/uk/CEH07_04-2010_102b_Moorhouse

Data arrived from ARSF via network transfer on 12th April 2010.

Scientific objective: Unknown (can't find application)

Priority: a4l, process hyperspectral as a3

PI: Andrew Wilson (& CEH Lancaster)

Collected as a single collection with day 102a (Hellifield, #332) - information on the same logsheet, combined nav data, etc. Have split into two separate collections for processing.

Sensors:

  • Eagle
  • Hawk
  • Leica LIDAR
  • Camera

Change History (5)

comment:1 Changed 15 years ago by benj

  • Description modified (diff)

Gary says priority is a4 from before they were recorded as high/med/low. Process as a4l for now, since original PI has retired, we've had no other contacts chasing this and that way it won't push our processing schedule back.

comment:2 Changed 15 years ago by benj

  • Description modified (diff)

Andrew has asked that we send him the raw hyperspectral data for this flight and he'll process them. We just need to do the applanix and the Lidar.

Andrew should send us back a copy of the data for archiving when he's done, but in case he doesn't I'm leaving it in the processing queue, it'll just stay at the bottom. If/when Andrew does return the processed data to us it can come off the queue.

comment:3 Changed 14 years ago by pmlvis12

IPAS navigation processing done.

comment:4 Changed 14 years ago by ella

POSProc failed to make an Sbet file for this project during applanix processing, when attempt was made error message read too many consecutive IIN measurment rejections. Needs someone to take a look.

comment:5 Changed 14 years ago by jb362

  • Description modified (diff)

Started camera processing

Note: See TracTickets for help on using tickets.