Using the -mTMS flag in azgcorr to denote southern-hemisphere processing causes either a segfault or north-south inverted results. Have had a couple of potential fixes exchanged with Bill (not quite right yet though), raising this mostly to go with the work order.

this is a request for the ability to click on a point in the main window or in the profile window and a pop up box to appear listing all the recorded data. this will allow the user to see the exact values rather than the slightly fuzzier graphically interpretations of these values.

the feature will display the closet point when several fall in the same location (so from the top down view this is the highest point)

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