You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps will reproduce the problem?
1. Installed 0.84 then 0.81.1 then 0.70
2. Geocoded the same photos and view them in Picasa
3.
What is the expected output? What do you see instead?
What version of the product are you using? On what operating system?
Please provide any additional information below.
I am really excited with the program and thank you so much. One of the
reasons why I am using this program over WWMX from Microsoft was that this
one works perfect with Picasa. Photos that are geocoded with WWMX were not
shown correctly in Picasa where this program supported it wonderfully.
But after I upgraded to 0.84, I realized that EXIF data in Picasa was
wrong. Picasa showed the photo's langitude correctly but showed latitude
as 000000...
I cannot wait to see this fixed in the next version. Thank you very much~
Original issue reported on code.google.com by pastor...@gmail.com on 10 Apr 2007 at 5:24
The text was updated successfully, but these errors were encountered:
Hello pastorsoh and thanks for your feedback !
I've just uploaded a test version 0.85 which writes the EXIF in a
slightly different way.
Can you and others try it and tell me if it works for your ?
If it doesn't work as expected can you send me an original
non geocoded picture for testing ? (and eventually a gpx file)
With my Canon Cybershot A620 it works fine.
Thanks in advance for your feedback which is very valuable for me and future
users.
If you can or wish, please answer in the dedicated Google Group so I have right
away
a mail notification.
http://groups.google.com/group/gpicsync
Thanks in advance.
(make backup of your pictures before testing)
francois
Original comment by francois...@gmail.com on 10 Apr 2007 at 7:36
Original issue reported on code.google.com by
pastor...@gmail.com
on 10 Apr 2007 at 5:24The text was updated successfully, but these errors were encountered: