Custom Query (432 matches)
Results (28 - 30 of 432)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #116 | wontfix | azgcorr seg fault | mggr | mark1 |
| Description |
azgcorr ver 4.8.9, causes segmentation fault when processing the full data and also when processing certain "chunks" of data, defined by a number of lines. For example using a chunk of lines 1-5000 works ok, but 1-5200 fails. 1-12402 works ok, 1-12403 fails. This is using the Eagle data from IPY07-06. |
|||
| #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. |
|||
| #87 | fixed | Aznav omits initial 0 on grid references starting with 0 | benj | benj |
| Description |
As title - if aznav processes a line that starts or ends on a grid reference where one component starts with 0 (eg NZ 0429 9739 - Harwood line 6 end), on display it omits the initial zero and displays a three-digit number instead of a four-digit number (eg NZ 429 9739). This can be confusing, though it appears to process correctly. |
|||