Processing Order

This page gives the provisional order in which ARSF-DAN will process the data for each project (2009 data onwards). As standard we choose the order in which to process data first by project alpha grading and second by date flown, but we may make exceptions to this - names in italics have been moved from where they would be in the standard order. Please note that this order is subject to change without notice. If your project is not on this page, or it is but not all the sensors you expect are listed, then it is probably being processed, see the relevant project ticket for more information. If we are processing several flight days from the same project code close together in time then we may wait until processing for all flight days has been completed before dispatching data - please contact us if you would like us not to do this.

See also the Processing status page

Primary sensors

This list is for sensors specifically requested in the ARSF application (i.e. required for the science case). If a sensor was not requested but was flown anyway, it will still be processed after all primary sensors have been processed.

Project code Flight day/year Site name Sensors Priority Ticket
EM10/07 143/2010 Trapani Hyperspectral a4l-' #338
EUFAR11/03 092/2011 HYMEDECOS (Erosion) Hyperspectral a4h #390
EUFAR11/03 092/2011 HYMEDECOS (Erosion) LiDAR a4h #390
EUFAR11/03 095/2011 HYMEDECOS (Erosion) LiDAR a4h #391
EUFAR11_04 097/2011 HYMEDECOS (Gradients) Hyperspectral a4h #392
EUFAR11_04 097/2011 HYMEDECOS (Gradients) LiDAR a4h #392
EUFAR11_06 098/2011 DELNVADER Hyperspectral a4h #393
EUFAR11_06 098/2011 DELNVADER LiDAR a4h #393
EUFAR11_06 098/2011 DELNVADER RCD a4h #393
EU11_03 100/2011 Alcornocales (South) Hyperspectral a4l #394
EU11_03 100/2011 Alcornocales (South) LiDAR a4l #394
EU11_03 100/2011 Alcornocales (South) RCD a4l #394
EU11_03 102/2011 Alcornocales (Mid) Hyperspectral a4l #395
EU11_03 102/2011 Alcornocales (Mid) LiDAR a4l #395
EU11_03 102/2011 Alcornocales (Mid) RCD a4l #395
GB11_00 83/2011 Chopwell LiDAR last #396

Secondary sensors

This list is for sensors flown but not specifically requested in the ARSF application (i.e. not required for the science case). If a sensor was not requested but was flown anyway, it will still be processed after all primary sensors have been processed.

Project code Flight day/year Site name Sensors Priority Ticket
EU10-03 234a/2010 Lake Balaton (East, Area A) LiDAR a5 #360
EU10-03 234c/2010 Lake Balaton (East, Area A) LiDAR a5 #364
EU10-03 235a/2010 Lake Balaton (East, Area) LiDAR a5 #365
EU10-03 238a/2010 Lake Balaton (East, Area) LiDAR a5 #366
EUFAR10/08 301/2010 ValCalHyp LiDAR a4h #384
EM10/07 145a/2010 Trapani LiDAR a4l #385
EM10/07 145b/2010 Trapani LiDAR a4l #386
EM10/07 143/2010 Trapani LiDAR a4l- #338
EUFAR11-03 092/2011 HYMEDECOS (Erosion) RCD a4h #390
EUFAR11-04 097/2010 HYMEDECOS (Gradients) RCD a4h #392

Delivery checking

This list shows projects for which processing has been completed and they are awaiting final QC checking prior to delivery to the PI. When the project is removed from this list it is being checked and should be ready for dispatch shortly, unless problems are found during final QC. Note that because some sensors are processed separately for each flight, the fact that a project is on this list means only that at least one category of sensor has completed processing, not necessarily all that were flown.

Project code Flight day/year Site name Sensors Priority Ticket
EU09_02 212b Alps HS a4m 353
Last modified 13 years ago Last modified on May 20, 2011, 3:24:06 PM