Hi Detlev, Is this a new process that has been recently implemented? I am still experiencing a similar problem as described on.... http://groups.google.com/group/google-picasa-data-api/browse_thread/thread/922de11a55e66847?hl=en
Also, do you know if this caching process applies when images that have been previously uploaded to PWA via Picasa Desktop, and then are updated on the desktop, and then updated image is resent to PWA via Picasa Desktop? Would the new image be referenced immediately via the regular Picasaweb.google.com interface or is there a waiting/ processing period until the new image is available? Thanks Lee On Jul 2, 9:30 am, Detlev Schwabe <[email protected]> wrote: > When you update the image bytes (including the EXIF data) of an > existing photo entry, the version of that photo changes as well as the > media:content and media:thumbnail image URLs. > However, you will still be accessing the previous photo version for up > to 24hrs from our image caches if you continue to use the image URLs > from the old photo version. > However, if you downloaded your updated photo through the new image > URLs, you will receive the modified version, also reflecting your > modified EXIF data. > After 24 hrs, the old URLs will also point to the updated content. > > On Jun 30, 12:15 pm, Ed Lebert <[email protected]> wrote: > > > > > This is very strange. Maybe someone can shed some light on this for > > me. Basically exif data on the photo (such as keywords, caption, etc) > > isn't updated on picasaweb when you provide an updated file. > > > 1. Create a new photo on picasaweb that contains a bunch of exif data. > > 2. download the photo and view the exif data using exiftool. > > Everything is correct. > > 3. change some of the values in the exif data using exiftool. > > 4. send your updated file to picasaweb using the API or Picasa desktop > > client. > > 5. download the photo again and view the exif data. The exif data > > wasn't updated! > > > I noticed this at first using the normal Picasa client doing the > > "update" command on individual photos. But then I starting using the > > normal HTTP API manually and witnessed the same behavior. I'd expect > > that when I send picasaweb an updated binary file, it then uses that > > binary file including it's exif data. That doesn't appear to be > > happening. It looks like it strips the image out of the updated jpeg > > file and merges it in with the old exif data from the original photo. > > > I've even gone so far as to delete the file on picasaweb and then re- > > create the new file. After downloading ... still the same old exif > > data from the original file which was deleted. This is super strange. -- You received this message because you are subscribed to the Google Groups "Google Picasa Web Albums API" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-picasa-data-api?hl=en.
