View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000322 | GeoSetter | Image Data | public | 2008-05-05 23:41 | 2008-05-05 23:45 |
| Reporter | Friedemann | Assigned To | Friedemann | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Product Version | 2.4.3 release | ||||
| Target Version | Fixed in Version | 2.4.21 beta | |||
| Summary | 0000322: Coordinates sometimes wrong | ||||
| Description | Sometimes a coordinate will be read wrong by GeoSetter. | ||||
| Tags | No tags attached. | ||||
|
|
For example the longitude 3.1063 has been read as 3.0944 by GeoSetter. A coordinate is stored as three unsigned rational values (degrees, minutes and seconds). In the example above the longitude has been read as 3/1 (=3), 6/1 (=6) and -2029368517/100000000 (=-20.29368517). This is wrong because the values have to be handled as unsigned values, which is the same result for degrees and minutes. But a 32 bit signed value -2029368517 in unsigned format is 2265598779. So the result for the seconds should be 2265598779/100000000 which is 22.65598779. With this value, the coordinate will be 3.10629333 (3 + 6/60 + 22.65598779/3600), which is correct. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2008-05-05 23:41 | Friedemann | New Issue | |
| 2008-05-05 23:41 | Friedemann | Status | new => assigned |
| 2008-05-05 23:41 | Friedemann | Assigned To | => Friedemann |
| 2008-05-05 23:45 | Friedemann | Status | assigned => resolved |
| 2008-05-05 23:45 | Friedemann | Fixed in Version | => 3.4.51 beta |
| 2008-05-05 23:45 | Friedemann | Resolution | open => fixed |
| 2008-05-05 23:45 | Friedemann | Note Added: 0000679 |
