Some Hawk bands are noisy to the point of uselessness. For example band 71 (1403nm), raw data from Nigg Bay line 3 (attached)

Also see over-water spectrum produced in level 3 image:

Spectrum cannot really be used for anything much - there is no means of quality controlling the data

Data issue occurs over more than one flight, possibly there are sensor problems with some Hawk bands. See eg. Latera band 71, similar to Nigg Bay:

It would be useful if azgcorr could output some extra information on the mapping of points.

Peter Land was interested in level 1 ground coordinates per pixel.

Chris Hecker (#108) has requested per-pixel geocoordinates or per pixel view vector info for feeding into ATCOR, also presumably at level 1. He said ATCOR needed, as an input parameters for the atmospheric correction model, the viewing geometry and distance between plane and each pixel. This can be supplied either as:

• a geo lookup table (GLT) that defines a map coordinate of each pixel while still in image coordinates
• a scan angle file with the viewing vector for each pixel (azimuth angle, zenith, angle, height of plane).

Peter contacted Bill about it, who replied (1/May/2007) with:

The option to 3D output pixel coordinates, solar and sensor view
vector details and time are on the cards for Andrew's group to use
with Modtran, so in the not too distant future will be available.

Split off from ticket #113.

Hawk data processed with Azspec and Caligeo shows a gap between the two, particularly at the short-wave end of the spectrum. Over land the two are very close at the longer-wave end, over water Caligeo is consistently higher than Azspec (though the gap is larger at the short-wave end). Azspec data looks more plausible but Hawk needs calibrating to check which (if either) is correct.

Over water:

Over land: