Custom Query (432 matches)
Results (154 - 156 of 432)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #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. |
|||
| #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. |
|||
| #115 | fixed | ATM bands marked bad suspiciously | mggr | benj |
| Description |
Some ATM lines for IPY have bad bands marked for some lines. However, the bad parts seem to correlate with areas where there is bright sunshine shining on white snow - in other words where the value is going to be pretty close to max. It's possible either this is incorrectly causing it to be classified as bad, or else that the max value is itself being used to mark bad data. Eg. Green Box line 1:
|
|||
