| 16 | |
| 17 | == Processing == |
| 18 | |
| 19 | === 2011 onwards === |
| 20 | |
| 21 | The FODIS data processing (2011 onwards) is much the same as for the Eagle data except that each scan line of FODIS data (4 pixels) is averaged together to reduce noise. The resulting processed data will consist of 1 data value per scan line of imagery. |
| 22 | |
| 23 | === pre-2011 === |
| 24 | |
| 25 | Details on processing the pre-2011 ILS/FODIS data are in the azgcorr manual (to a limited extent - we'll improve this as soon as we get the manual text..). Basically it's an extra data vector in the HDF files, called CAils, with one pixel of upwards-looking data per downwards-looking scanline. |
| 26 | |
| 27 | The vector should be present in all CASI and Eagle HDFs, but will be garbage in any flight where the sensor wasn't connected (fibre optic cable from the CCD to the roof-mounted collector). If the data are correct, they should resemble the solar spectrum. |
| 28 | |
| 29 | It will also be garbage in any Eagle HDFs preceding mid 2008 as the cable wasn't connected (may be present in some Ethiopia flights) and the processing wasn't working (fixed as of June/08, backprocessing available on request). |
| 30 | |
| 31 | Note that due to a bug in ENVI (?), it appears that one gets odd spiky results from directly viewing the HDF vector. You must extract it first with: |
| 32 | {{{ |
| 33 | azexhdf -Be fodis.bil -d CAils youreagle.hdf |
| 34 | }}} |