View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000760 | GeoSetter | Image Data | public | 2011-02-07 20:32 | 2011-04-24 02:06 |
| Reporter | mp | Assigned To | Friedemann | ||
| Priority | normal | Severity | major | Reproducibility | N/A |
| Status | resolved | Resolution | fixed | ||
| Product Version | 3.4.12 Release | ||||
| Target Version | Fixed in Version | 3.2.0 release | |||
| Summary | 0000760: Does Geosetter fail to import the existing metadata to XMP? | ||||
| Description | Hert (from Idimager) states: "In general I would advise *not* to use GeoSetter before IDimager. Reason is that GeoSetter writes its GEO location to Exif and XMP, but when it creates its first XMP block, it fails to import the existing metadata to XMP, leaving you with a half baked XMP block that only contains the GEO coordinates. When you have first used IDimager on these images then IDI will create the full XMP block and GeoSetter will *add* the GEO coordinates to that XMP block." Is this true? Has it been fixed? Are you gonna fix it? ... | ||||
| Additional Information | http://forum.idimager.com/viewtopic.php?f=13&t=13037&p=74347&hilit=geosetter#p74347 | ||||
| Tags | No tags attached. | ||||
|
|
This should be fixed since version 3.1.0 - see here: http://www.geosetter.de/en/changes/ ("When adding XMP data to image initially, all existing data from Exif and IPTC will be synchronized") |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2011-02-07 20:32 | mp | New Issue | |
| 2011-04-24 01:12 | Friedemann | Status | new => assigned |
| 2011-04-24 01:12 | Friedemann | Assigned To | => Friedemann |
| 2011-04-24 02:06 | Friedemann | Note Added: 0001554 | |
| 2011-04-24 02:06 | Friedemann | Status | assigned => resolved |
| 2011-04-24 02:06 | Friedemann | Fixed in Version | => 3.2.0 release |
| 2011-04-24 02:06 | Friedemann | Resolution | open => fixed |
