View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000617 | GeoSetter | Image Data | public | 2010-07-27 01:57 | 2010-11-08 00:20 |
| Reporter | ace_dent | Assigned To | Friedemann | ||
| Priority | normal | Severity | major | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Product Version | 3.3.60 Release | ||||
| Target Version | Fixed in Version | 3.3.61 beta | |||
| Summary | 0000617: GPS-Info reported by ExifTool, not visible in Geosetter | ||||
| Description | Attached file exhibits problem. I have a large number of geotagged files, with GPS data visible in Exiftool (e.g. using 'Info' section in Geosetter). However, when using Geosetter to view on the map or update GPS details there are non apparently present. When saving an updated file, the chnages are no longer visisble and the GPS data is not displayed again in Geosetter... | ||||
| Tags | No tags attached. | ||||
|
2010-07-27 01:57
|
20080920T113000.jpg (606,358 bytes) |
|
|
Testing revealed the problem is with a specific incorrectly formed GPS tag, e.g. GPS:ImgDirection = 0 0 2.26939... It seems three rational numbers are stored(?), rather than one Rational64u as specified by exiftool. Also, the exif standard suggests an angle 0 - 360... Regarding 'fixes'- it would be useful if: * exiftool warned the user of the malformed gps tag; * Geosetter forwarded the warning, ignored the direction tag, and used the other correct gps tags (i.e degraded gracefully). Just for info: the file was geocoded back in 2008 using the following process: - From Google Earth, a KML file was created for a location. - Using iTag (with Microsoft's WIC under the hood), the KML location was used to geocode the jpeg. - I suspect the KML camera properties (Tilt Roll Bearing?) may have been used... - Due to software updates, the bug seems to be fixed (/can no longer be recreated). Cheers, Andrew |
|
|
The GPSImageDirection is "0 0 52.5896692". So there are 3 values instead of 1. Do you know which software maybe did write these values? That's why GeoSetter unfortunately crashes when reading it... Of course I can fix it and take the 3rd value. Do you think 52 degress is ok for the direction? |
|
|
Please try http://www.geosetter.de/geosetter_beta.exe |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2010-07-27 01:57 | ace_dent | New Issue | |
| 2010-07-27 01:57 | ace_dent | File Added: 20080920T113000.jpg | |
| 2010-07-30 01:16 | ace_dent | Note Added: 0001209 | |
| 2010-10-03 22:59 | Friedemann | Status | new => assigned |
| 2010-10-03 22:59 | Friedemann | Assigned To | => Friedemann |
| 2010-10-03 23:37 | Friedemann | Note Added: 0001244 | |
| 2010-10-03 23:37 | Friedemann | Status | assigned => feedback |
| 2010-11-08 00:20 | Friedemann | Note Added: 0001333 | |
| 2010-11-08 00:20 | Friedemann | Status | feedback => resolved |
| 2010-11-08 00:20 | Friedemann | Fixed in Version | => 3.3.61 beta |
| 2010-11-08 00:20 | Friedemann | Resolution | open => fixed |
