Custom Query (432 matches)


Show under each result:

Results (298 - 300 of 432)

Ticket Resolution Summary Owner Reporter
#109 fixed Output of ground coordinates in azgcorr mggr mggr

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.
#110 fixed Azspec processed Hawk data has spectral spikes mggr benj

Azspec-processed level 1b hawk data does not appear to be correct - it contains large anomalous spikes in some bands, seemingly correlated to very low data values. Eg from Nigg Bay line 3:

Hawk spectrum from azspec-processed level 1b file over water (8px average)

Compared to Caligeo spectrum from same pixel:

Hawk spectrum from caligeo-processed level 1b file over water (8px average), same place as azspec example

Could be underflowing, but would expect a much higher value for the spikes (~65k) in this case. Might still be underflowing and then changed by maths in azspec though.

Note extended from ticket #106, but separate to Hawk noise issue

#112 wontfix Add BigTIFF support to azexhdf mggr mggr

Current TIFF formats are limited to 2GB, which is an issue with the Eagle & Hawk - large numbers of bands can easily exceed this limit.

Bill says that ERDAS 9.2 supports BigTIFF (and perhaps big geotiffs as a result?). It'd be good to find out the extent of the support and perhaps implement BigTIFF support in azexhdf.

This ticket is to track the issue for now. At some point we may want to take action on it.

Note: See TracQuery for help on using queries.