I just saw the EXIM detail which is kind of a dealbreaker, in conjunction with the fact that google photos is yet another API they will probably keep messing with and changing in the future, and I instead upgraded my Dropbox account to 2TB (which wasn't really an option when I first started with google photos) and am using Autosync https://play.google.com/store/apps/details?id=com.ttxapps.dr... to push my photos out as is (Dropbox's photo sync wants to rename the photos for no good reason). Just pushing out the raw data from the phone directly where I can grab it on my synology on the backend seems like the best approach. But it's only been about 45 minutes and there's plenty of time for something to blow up, maybe I'll be back.
Isn't this embedded with the photo itself, the EXIF data? Or is that what the Google API strips out of the photo?
Also: Thanks for the link to timeliner, looks useful.
Looks like you don't support iCloud, not surprised I'm sure there's no public API and their API would be quite fragile and hostile to use.
I do use google photos on my phone, so everything syncs from iCloud -> Google Photos anyway.
I can take a picture on any device, or copy in a picture or video, or import from my camera SD card on any device, and within a few minutes I have at least 2 backup copies available.
I just wish Nikon, Canon, Sony, or anyone really would be able to integrate a DSLR/mirrorless camera into Dropbox or iCloud Photos so I could take out the manual import process :P
Given that eyefi exists, this is mostly a client-side software issue. We already have the technology, which is awesome.
This announcement breaks that and destroys the easiest option for downloading all photos from Google.
There is also Perkeep which is very interesting as well. https://perkeep.org/
Shouldn't jpegs have this data if geoloc was on at the time of shooting ? Am I right in understanding that you imply that this meta-data is somehow disconnected from the file on Google Photos ?
This is awwwwwwesome!!!
I was just the other night telling somebody I wish I had something like this.
Another feature (do you know anything that does this, or if it could be done in timeliner?) is if it could republish my photos to Facebook if it got them from Google Photos, and vice-versa?
This is indeed extremely sad.
I’m writing from an iPhone/Ubuntu perspective.
There's a setting:
"Remove geo location in items shared by link Affects items shared by link but not by other means"
Edit: I just tried it, I downloaded a photo and double checked, EXIF location data was included.
That should make all the sponsors happy, right?
Joking aside, looks like a good project.
Sucks that EXIF is stripped upon being uploaded into Google.
I think I have enough backups.
Only alternative I can figure is to scrape the actual Google Photos web app.
All photos still exist in the cloud, backed up on a hard drive. Multiple copies are unlikely to fail at the same time.
I run this on a cronjob and it adds all my photos to a timeline in conjunction with my tweets and Facebook posts. It's got a few rough edges but should (mostly) work as advertised.
I would love to have help maintaining it, especially now given this announcement (because Timeliner does not require Google Drive).
One major limitation with the Google Photos API is that it's impossible to get the location data from the photos through it. Timeliner tries to compensate for this by allowing you to import your Google Location History, but this is not ideal either. Edited to add (since there are a lot of the same question in the replies): no, the EXIF metadata does not contain the location because Google Photos API strips it out (it leaves most other metadata intact).