Currently obtained via requests to Andrew Wilson.

We may be able to gain access via the Pan-Government Agreement, according to Tony Clifton @ BGS. We need to sign up at ​http://www.iggi.gov.uk/signUp.php to see if we're eligible.

Steve is doing this.

Just a tracker ticket for an issue found in #2. azgcorr wasn't handling the SCbedit vector correctly when BSEQ/BIL files were used.

Reported to Bill 18/May and fixed over the weekend in release 106. Some notes from Bill's email:

Updated azgcorr.481 by separate email.

SCbedit now works as advertised with the limitation that it only works for the first 16 bands of a data set (because it uses an unsigned int). It was originally only put in for the ATM anyway.

The "distortion" was because I had forgotten for BIL/BSEQ input to move the file when a line was skipped, so after each skipped line the image would shuffle up.

So now for CASI and Specim data the only option is the whole frame is skipped if it is flagged. This makes sense because with a CCD sensor it would be pretty unlikely to have a whole row dead, columns maybe but not rows.

The default in azgcorr.48* is if there is NO -be  the SCbedit vector is used;  if there is a -be then SCbedit is not used and no lines/scans are ignored. 

This needs testing

ATM data could not be processed due to some error in the navigation timing

azimport -- ver: 2.2.10 May 7 2007 (C) Azimuth Systems UK 1996, 2007

Applanix sbet file: ./app/app/Proc/apa06158.sbt Site time limits - day: 158 start: 92559 end: 92801 date: 07 06 2006 jday: 158 utc2gps: 14.0 NAV vgroup exists - updating

Nav records per second from Applanix sbet file: 200.00 Using: 0.01 seconds for gap check site time limits: 33959.00 to: 34081.00 day starts at secs: 259200.0

no SBET epochs in the site time limits - NO navigation saved FILE time limits - start: 78034.01 end: 83945.01 check SBET file used

Run terminated due to data or parameter errors or program failure