Custom Query (432 matches)
Results (331 - 333 of 432)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#114 | fixed | Az* lever arm better with offsets | mggr | benj |
Description |
The az* lever arm format is currently gam/del/dst (two angles and a distance) for legacy reasons. These reasons are now irrelevant, so for clarity and ease of calculation it would be better if az* used x/y/z offsets (three distances) instead. |
|||
#112 | wontfix | Add BigTIFF support to azexhdf | mggr | mggr |
Description |
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. |
|||
#110 | fixed | Azspec processed Hawk data has spectral spikes | mggr | benj |
Description |
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: Compared to Caligeo spectrum from same pixel: 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 |