| Version 484 (modified by anch, 14 years ago) (diff) |
|---|
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 |
| EUFAR10-01 | 238b/2010 | Lake Balaton Peninsula | Hyperspectral | a4h | #371 |
| EUFAR10-01 | 238d/2010 | Lake Balaton Peninsula | Hyperspectral | a4h | #374 |
| GB07/09 | 212a/2010 | Alps | Hyperspectral | a4m | #352 |
| EU09/02 | 212b/2010 | Alps | Hyperspectral | a4m | #353 |
| CEH07/04 | 102a/2010 | Hellifield | Hyperspectral | a4l- | #332 |
| CEH07/04 | 102b/2010 | Moorhouse | Hyperspectral | a4l- | #333 |
| EM10/07 | 143/2010 | Trapani | Hyperspectral | a4l- | #338 |
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 | 233a/2010 | Lake Balaton (East, Area D) | LiDAR | a5 | #370 |
| 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, Camera | 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 |
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 |
| EUFAR10/01 | 233b/2010 | Lake Balaton Peninsula | Hyperspectral | a4h | #363 |
| EUFAR10/08 | 301/2010 | ValCalHyp | Hyperspectral | a4h | #384 |