Casi line 3 have alot of chequers and nav problems as in below image

Two issues:

• Amer checking on LIDAR.
• Use of bsq with azgcorr
  • mggr suspects perhaps the missing scans are throwing off the navigation?

Rachel's initial contact email:

I am trying to process ATM and CASI data flown last summer over my two
sites in Wales (GB06/05, PI - Tim Malthus). Unfortunately we are
having a few problems with AZGCORR and I wanted to check whether you
had encountered them before and had any idea what might be wrong (or
who else might have).

As we are carrying out atmospheric correction before geometrically
correcting the swaths in AZGCORR, so we are using the resulting .bsq
image in conjunction with the original .hdf (and a DTM) as inputs to
AZGCORR, as recommended in the user guide. With the CASI data and most
of the ATM swaths this appears to work ok (at least as far as can be
determined by visual inspection of the results), however with certain
swaths the geometric correction is not successful. These seem to be
swaths with considerable numbers of missing pixels / scan lines.  When
the raw .hdf data is geometrically corrected directly, the problems do
not appear and AZGCORR  works correctly (attached jpeg1), but when the
image is first converted to .bsq and atmospherically corrected the
image seems to be corrected up until the point of the missing scan
lines, but after that appears to be just 'stretched' to fit the
correct outline (jpeg2). The same problem is also being encountered by
John Dowens in correcting strips from GB06/07.

Do you have any ideas what may be causing this problem? Any
suggestions very much appreciated.  I was also wondering if you know
when I might be likely to receive the remaining LIDAR data from this
acquisition (I have the lidar from my Glasfynydd site but not from
Clocaenog)?

Currently, the batch files output a fixed set of bands (2, 3, 5). This won't work for the dynamic bands in CASI. We need a small utility to pick out the 3 bands closest to RGB from an HDF file.