Geotagging data not showing up in Picasa for windows

[berend]

I don't have the tools or software to EDIT EXIF data.... But I'm willing to put money on the idea if the Eye-fi to windows photo had it's "missing" Geo data edtited back in from the PicasaWEB .jpg I bet the now edited photo would properly show it's Geo location in Picasa for windows.

How much?

I haven't checked - let me know how Picasa the desktop application does with this edited version of the photo delivered to the desktop with GPS coordinates to match the fractional part of the photo downloaded from Picasa Web Albums.

Berend

[Sardog]

Well I was able to add the missing "seconds" .52 (LAT) and .64(LONG) in GeoSetter and low and behold IT WORKS!!!! http://dl.dropbox.com/u/5415621/IMG_356 ... sec%29.JPG

Berend....I don't know what you changed to your attached file but your version did not post Geo data on Picasa (for windows)...Thanks though

So it looks like we have a solution.... Eye-Fi just needs to add the last part of the LAT & Long "seconds" to its "Eye-Fi to computer" transfer and the problem will be solved!

[berend]

I don't know what you changed to your attached file but your version did not post Geo data on Picasa (for windows)...Thanks though

As expected. Here's the decode showing you that the edited matches the Picasa Web Albums version exactly, without any other changes to the EXIF data:

Code: Select all

berend-macbookpro:~ berend$ exiftool -v "IMG_3567 fro Eye-fi software edited.JPG"
  ExifToolVersion = 6.90
  FileName = IMG_3567 fro Eye-fi software edited.JPG
...
  | 10) GPSInfo (SubDirectory) -->
  | + [GPS directory with 5 entries]
  | | 0)  GPSVersionID = 2 2 0 0
  | | 1)  GPSLatitudeRef = N
  | | 2)  GPSLatitude = 28 8 53.52
  | | 3)  GPSLongitudeRef = W
  | | 4)  GPSLongitude = 82 19 11.64
...

So it looks like we have a solution.... Eye-Fi just needs to add the last part of the LAT & Long "seconds" to its "Eye-Fi to computer" transfer and the problem will be solved!

Sigh. No, sardog. All that you did is to get GeoSetter to read in the EXIF header, reformat it and write it out again, which is what seems to have made Picasa happier. As I said before, it is simply sensitive to the formatting of the EXIF header, as written by different cameras and software packages. You are more than welcome to reopen this file in GeoSetter, remove the fractional parts of the latitude and longitude seconds, save it, and observe (I expect) that Picasa still displays it fine. The issue is not the fractional part of the seconds in the latitude and longitude values.

Berend

[Sardog]

If it's not the fractional parts...What is it then? I only added the fractional parts to the Lat & Long and that made Picasa happy.... Whats wrong for asking Eye-Fi for the exact same file that they upload to Picasa web(with the fractional parts included) to also transfer to our local machine?

Makes perfect sense to me and this solves the issue entirely.

[berend]

If it's not the fractional parts...What is it then?

sardog,

As I described a number of times now, it is the specific formatting of the EXIF headers and something about Picasa not liking one kind of formatting. Did you try my suggested experiment of loading the photo into GeoSetter and removing the fractional part? I guarantee that Picasa will still display the geo-tagging information after you save it from GeoSetter after editing because it is being helped by the fact that GeoSetter is rewriting the EXIF headers, as it happens in a format that it is able to deal with.

Think of it this way - what if the location that the photo was taken happened to line up to a location on an exact seconds in either the longitude or latitude, or both. There would naturally not be any fractional part to the numbers. It simply does not follow that the presence of the fractional part (which really is present in both formats, but simply zeros in one of them) is the significant factor. Please try the experiment that I suggested.

Makes perfect sense to me and this solves the issue entirely.

Unfortunately not. I'm sorry, I'm running out of ideas to convince you. We are still looking to see if we can identify Picasa's problem or if we can work around it, but the problem has nothing to do with the fractions and is squarely in Picasa's court, as demonstrated by the presence of numerous other applications, including GeoSetter, which can deal with the geo-tagging information just fine as written by Eye-Fi Center.

Berend

[Sardog]

Berend,
I did your suggested test and you're right it does still display geo info in Picasa for windows

So do you think the PicasaWEB app is re-writing the EXIF data causing it to display Geo info?

So where do we go from here? I have yet to see any acknowledgment of a software issue on Google's forums from an employee.....Just more finger pointing Canon<----->Picasa<----->Eye-Fi

I'm over all the finger pointing ...lets just get this issue fixed.

Thanks again Berend for helping me understand (some) of this stuff

[Sardog]

Someone has an issue with a Nikon D90 & and missing Geo data with Picasa. http://www.google.com/support/forum/p/P ... 177d&hl=en

Can the CEO of Eye-Fi have a conference call with the folks at Picasa and FIX THIS ALREADY !!!!

[berend]

I did your suggested test and you're right it does still display geo info in Picasa for windows

Thank you for trying the experiment and confirming the expected result. This proves that Picasa is happy with the EXIF headers as they've been reformatted by GeoSetter, while all other applications and web services are perfectly happy with the original EXIF headers written by Eye-Fi Center.

So do you think the PicasaWEB app is re-writing the EXIF data causing it to display Geo info?

No. I tried to explain earlier in the thread that photos that are uploaded to web sharing servers via the Eye-Fi servers get their geo-tagging data inserted using ExifTool, which is separate from the Adobe XMP library and the libexif library which are used by the Eye-Fi Center. It is just that Picasa Web Albums and Picasa are both happy with the EXIF headers inserted with ExifTool, while Picasa (unlike Picasa Web Albums and many other applications) is not happy with the headers written by the Adobe XMP library and the libexif library.

I'm over all the finger pointing...

I hope you understand that the intent here is not "finger pointing," as between Prabha and myself we've spent hours in both analyzing your case, as well as trying to share information and educate folks on this thread. As programmers ourselves, we wish "standards" were really "standards" and everything interoperated readily, but this is rarely the case and it makes our lives "interesting."

We have a suspicion that Picasa does not like EXIF headers with mixed endianness, unlike other applications that parse EXIF headers, but we haven't fully-baked that theory yet and are continuing to look into it. Depending on how the analysis goes, we may share that information with the folks at Google or simply work around the Picasa bug in our own application, but at this time it is too early to promise anything. I suggest that you (and others) continue to keep the discussion alive on the Picasa forums, too.

Thanks,

Berend

[kriemer]

I'm not sure if this is a new wrinkle or not, but I just realized that NONE of the EXIF information is visible in Picasa. Anyone else notice this?

And noticed another wrinkle, last night uploaded a couple of photos, took longer than usual. The interesting thing is that these pics show correctly as geotagged.

Thanks

k

[Sardog]

Thanks berend .... Will do.

[prabha]

sardog/kriemer,

can you guys try the latest build and let me know if that fixes the problem with picasa.

Download the latest from here:

Windows: http://support.eye.fi/agent/3.1.4/Setup.exe
Mac: http://support.eye.fi/agent/3.1.4/Eye-Fi.dmg

[kriemer]

Tested a couple of uploads, and that appears to do it moving forward (thanks for allowing be to beta test). Any suggestions about fixing the past, I ask because I was on vacation this past week and the data is there, but not there.

I notice that you need to to change version number in Eye-Fi Enter "About" (still shows as version 3.1.2; I know this is a beta release).

Again, thanks for what appears to a fix.

K

[Sardog]

sardog/kriemer,

can you guys try the latest build and let me know if that fixes the problem with picasa.

Download the latest from here:

Windows: http://support.eye.fi/agent/3.1.4/Setup.exe
Mac: http://support.eye.fi/agent/3.1.4/Eye-Fi.dmg

IT WORKS!!! Thanks for building a FIX for this issue

[prabha]

kriemer, to fix the old files, you can use geosetter to open & save them as sardog did here: viewtopic.php?f=3&t=2111&st=0&sk=t&sd=a&start=30#p8791

-prabha

[berend]

Tested a couple of uploads, and that appears to do it moving forward (thanks for allowing be to beta test).

IT WORKS!!! Thanks for building a FIX for this issue

Thanks for confirming the workaround guys - it looks like the Picasa folks owe Prabha a beer or two!

Berend

[kriemer]

Amen to that!!!

[FrankRT]

Hello,

With my new Eye-Fi Pro X2 I just run into a similar problem (I believe). Of course I now have installed the new firmware 3.1.4 - unfortunately only after having transferred (and deleted from the card) some 100 pictures. No exif information is visible in Picasa, only in other programs (IrfanView, GeoSetter).

Is there a to make the exif data on those files readable by Picasa (and btw Windows Explorer, whose thumbnails do not recognize the exif orientation tag either)?

kriemer, to fix the old files, you can use geosetter to open & save them as sardog did here: viewtopic.php?f=3&t=2111&st=0&sk=t&sd=a&start=30#p8791

..I mean - a "faster" way?? I tried a batch rename via IrfanView, but (as one should expect) this does not affect the exif formatting.

Thanks so much in advance.

Frank

[klooth]

I am having this same problem described above as fixed in 3.1.4 of EyeFi Center (photos not showing up as geotagged in Picasa). I have 3.4.23 of Eye-Fi. And my Picasa is up-to-date as well (3.8.0). I don't seem to be making any progress with support. Any ideas?