[ubuntu-mono] [Bug 277594] [NEW] F-Spot modifies GPS, altitude, and original time/date exif fields on import

[Adam Fryska]

Public bug reported:

Binary package hint: f-spot

There are a number of bug reports about F-Spot issues concerning changes
to the time/date exif data when importing, but I couldn't find anything
that sounds like what I dealt with.  This is on Ubuntu Hardy.

I had about 200 photos on my computer which had been previously copied
from my digital camera and which had been  tagged with additional
lat/long/altitude exif data using the package 'gpscorrelate'.  After
importing the photos into F-Spot, a number of changes were made to the
exif data:

- Every few photos had their timestamp moved back two hours (this sounds similar to some of the other bug reports, except that not all photos were affected).
- All photos which had identical lat/long/altitude data (meaning, they were taken in the same place) had their original date/time exif field changed to that of the earliest timestamp.  In other words, photos that were taken in one place over the course of an hour all had their timestamp changed to the timestamp of the very first photo taken in that location.
- Some of the gps and altitude data was wiped or garbled.  Again, this didn't happen to all the photos and there didn't seem to be a pattern, but some photos altitude was set to '0', decimal points went missing in lat/long coordinates, or the values were simply changed.

Net result, one big mess and several hours of using jhead and
gpscorrelate to fix everything.  I suppose I brought this on myself by
checking the "write metadata to disk" option, but persistent tagging of
photos was the whole reason I wanted to try F-Spot.

Let me know if I can clarify anything else or provide more information.

Cheers,
Adam

** Affects: f-spot (Ubuntu)
     Importance: Undecided
         Status: New

** Description changed:

  Binary package hint: f-spot
  
  There are a number of bug reports about F-Spot issues concerning changes
- to the time/date exif data when when importing, but I couldn't find
- anything that sounds like what I dealt with.  This is on Ubuntu Hardy.
+ to the time/date exif data when importing, but I couldn't find anything
+ that sounds like what I dealt with.  This is on Ubuntu Hardy.
  
  I had about 200 photos on my computer which had been previously copied
  from my digital camera and which had been  tagged with additional
  lat/long/altitude exif data using the package 'gpscorrelate'.  After
  importing the photos into F-Spot, a number of changes were made to the
  exif data:
  
  - Every few photos had their timestamp moved back two hours (this sounds similar to some of the other bug reports, except that not all photos were affected).
  - All photos which had identical lat/long/altitude data (meaning, they were taken in the same place) had their original date/time exif field changed to that of the earliest timestamp.  In other words, photos that were taken in one place over the course of an hour all had their timestamp changed to the timestamp of the very first photo taken in that location.
  - Some of the gps and altitude was wiped or garbled.  Again, this didn't happen to all the photos and there didn't seem to be a pattern, but some photos altitude was set to '0', decimal points went missing in lat/long coordinates, or the values were simply changed.
  
  Net result, one big mess and several hours of using jhead and
  gpscorrelate to fix everything.  I suppose I brought this on myself by
  checking the "write metadata to disk" option, but persistent tagging of
  photos was the whole reason I wanted to try F-Spot.
  
  Let me know if I can clarify anything else or provide more information.
  
  Cheers,
  Adam

** Description changed:

  Binary package hint: f-spot
  
  There are a number of bug reports about F-Spot issues concerning changes
  to the time/date exif data when importing, but I couldn't find anything
  that sounds like what I dealt with.  This is on Ubuntu Hardy.
  
  I had about 200 photos on my computer which had been previously copied
  from my digital camera and which had been  tagged with additional
  lat/long/altitude exif data using the package 'gpscorrelate'.  After
  importing the photos into F-Spot, a number of changes were made to the
  exif data:
  
  - Every few photos had their timestamp moved back two hours (this sounds similar to some of the other bug reports, except that not all photos were affected).
  - All photos which had identical lat/long/altitude data (meaning, they were taken in the same place) had their original date/time exif field changed to that of the earliest timestamp.  In other words, photos that were taken in one place over the course of an hour all had their timestamp changed to the timestamp of the very first photo taken in that location.
- - Some of the gps and altitude was wiped or garbled.  Again, this didn't happen to all the photos and there didn't seem to be a pattern, but some photos altitude was set to '0', decimal points went missing in lat/long coordinates, or the values were simply changed.
+ - Some of the gps and altitude data was wiped or garbled.  Again, this didn't happen to all the photos and there didn't seem to be a pattern, but some photos altitude was set to '0', decimal points went missing in lat/long coordinates, or the values were simply changed.
  
  Net result, one big mess and several hours of using jhead and
  gpscorrelate to fix everything.  I suppose I brought this on myself by
  checking the "write metadata to disk" option, but persistent tagging of
  photos was the whole reason I wanted to try F-Spot.
  
  Let me know if I can clarify anything else or provide more information.
  
  Cheers,
  Adam

-- 
F-Spot modifies GPS, altitude, and original time/date exif fields on import
https://bugs.launchpad.net/bugs/277594
You received this bug notification because you are a member of MOTU Mono
Team, which is subscribed to f-spot in ubuntu.