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.