Status Update
Comments
jf...@google.com <jf...@google.com> #2
We'll take a closer look at the behavior of the 'd' parameter.
pa...@gmail.com <pa...@gmail.com> #3
Can the Google Photos API be used as anything except a write-only API?
ds...@gmail.com <ds...@gmail.com> #4
gi...@gmail.com <gi...@gmail.com> #5
giles@gklinux:~$ idiff -v /media/Data/gphotos-tests/giles-photos/photos/2019/01/IMG_20190111_140358.jpg /home/giles/Downloads/IMG_20190111_140358.jpg
Comparing "/media/Data/gphotos-tests/giles-photos/photos/2019/01/IMG_20190111_140358.jpg" and "/home/giles/Downloads/IMG_20190111_140358.jpg"
didn't know how to process Exif:BitsPerSample, type 3 x 3
Found APP1 XMP! length 288
didn't know how to process Exif:BitsPerSample, type 3 x 3
Mean error = 0
RMS error = 0
Peak SNR = inf
Max error = 0
0 pixels (0%) over 1e-06
0 pixels (0%) over 1e-06
PASS
The vd parameter on videos is a different story, videos are always transcoded (and some older types of video blow up and cause 500 response).
gi...@gmail.com <gi...@gmail.com> #6
Thus I was comparing two images that have already been modified by Googe Photos.
Google Photos has a setting that defines if your photos are "Original" or "High Quality". The latter does not count against disk quota but is compressed. I always use "High Quality" so should expect the image data to look different on anything stored in Google Photos. (Note that I find the difference visually indistinguishable even at high zoom)
The original poster does not specify if he is using "Original" mode. If not then the results are expected.
This does not alter the fact that "=d" does not work as expected since it messes with the metadata, in particular, GPS info is missing.
I think it is reasonable for us to expect to be able to extract our own data. Thus the original wording of this bug report title stands true.
th...@gmail.com <th...@gmail.com> #7
Example use cases:
* Accessing the RAW photo would allow using RAW image editing tools.
* Accessing to original file would allow using the API to "backup"/"archive" media items.
Simple test case:
* Upload any non-lossless file format (e.g. any RAW camera file)
* Download with the "d" parameter
- Expected
* Sample file (potentially with edited/filtered metadata)
- Actual
* A high quality JPEG image
Note: This seems to also be true for any high quality video file.
gi...@gmail.com <gi...@gmail.com> #8
If you are using 'Original' then the behaviour you describe is incorrect. Otherwise, it is expected.
th...@gmail.com <th...@gmail.com> #9
fi...@gmail.com <fi...@gmail.com> #10
Having access to my original photos is important to me, and I'd expect the API to allow this.
Steps to reproduce
* Upload a .jpg photo
* Download the photo from the
* Download using the Photos API with the "d" parameter
Expected:
All three files should be the same
Actual:
The file downloaded using the web interface is identical to the original.
The file downloaded with the API is much more heavily compressed (about half the size).
ds...@gmail.com <ds...@gmail.com> #11
ni...@gmail.com <ni...@gmail.com> #12
Unless rclone can download the original file (unchanged image with all EXIF data) then it is going to be pretty useless as a backup which is very disappointing.
Please provide a download option which does allow fetching the original unmodified photo in the same way that downloading manually from
gi...@gmail.com <gi...@gmail.com> #13
I'm currently looking into an issue where a portion of my approx 100,000 photo library has been altered in subtle ways, such that the backup service I have been developing (
Google has created a very compelling and free photos service. However, if they created the perfect API that allowed us to extract all of the data then we could walk away if they decided to make it less compelling (like charging for it). I can think of no other reason for some of the limitations of the API which you rightly raise.
Hopefully, I'm incorrect and there will be fixes to API coming soon.
bb...@equalos.org <bb...@equalos.org> #14
ma...@gmail.com <ma...@gmail.com> #15
I am starting to get very uncomfortable having my photos on Google Photos now that the sync to Drive feature stopped working (and therefore my backup method).
ha...@gmail.com <ha...@gmail.com> #16
ju...@gmail.com <ju...@gmail.com> #17
cj...@gmail.com <cj...@gmail.com> #18
What gives?? Do you guys have any information at all about when we can expect a usable API for Google Photos? I don't hardly understand how you can publish an API for Google Photos that will not allow you to access the original photos and videos in there. What a dumpster fire
va...@gmail.com <va...@gmail.com> #19
Would appreciate at least a check-in from Google on this even if this isn't a high priority issue. Would be great to understand if this is simply a limitation we need to learn to live with, or if this is considered a real bug that Google intends to eventually address.
bc...@gmail.com <bc...@gmail.com> #20
Considering unlimited storage of raw images on Google Photos was the main reason I went with the Pixel line of smartphones, I am very disappointed in this limitation and will be looking at other options the next time around.
da...@guzik.com.ar <da...@guzik.com.ar> #21
cc...@derago.com <cc...@derago.com> #22
sa...@gmail.com <sa...@gmail.com> #23
rd...@gmail.com <rd...@gmail.com> #24
ta...@gmail.com <ta...@gmail.com> #25
ti...@kingston.gov.uk <ti...@kingston.gov.uk> #26
I don't know how seriously Google takes Google Photos. There seems to be a lot of things wrong with it, considering how big Google is as a company.
The search facility, for example, isn't great and that doesn't even involve people taking stuff out of the Google ecosystem but searching within it.
Large companies are supposed to give us easy access to take our data and move it elsewhere. I guess take out does that.
However, in my case, I am just wanting to move Google Photos to Google Drive so that I can store the photos alongside other documents that Google Photos doesn't support. Alas as Gooogle Photos isn't a supported product, not much I can do. I'm not a sole trader but working for a larger company, so I can't go elsewhere.
I guess I shall just have to do the less efficient manual download and upload. Nice to know Google is helping me to work efficiently and collaborate... not. At least they haven't yet removed the option to share photos between accounts at high quality. I hope they don't ever feel the need to remove that.
ti...@kingston.gov.uk <ti...@kingston.gov.uk> #27
gr...@poudrel.net <gr...@poudrel.net> #28
can you take a moment to fix this bug please ?
I tested today, the issue is still here...
pp...@gmail.com <pp...@gmail.com> #29
su...@gmail.com <su...@gmail.com> #30
on...@gmail.com <on...@gmail.com> #31
da...@gmail.com <da...@gmail.com> #32
om...@gmail.com <om...@gmail.com> #33
st...@erayd.net <st...@erayd.net> #34
il...@gmail.com <il...@gmail.com> #35
ad...@bullserve.co.uk <ad...@bullserve.co.uk> #36
be...@gmail.com <be...@gmail.com> #37
st...@erayd.net <st...@erayd.net> #38
Just star it, and refrain from commenting unless you are adding something of substance.
mt...@gmail.com <mt...@gmail.com> #39
om...@gmail.com <om...@gmail.com> #40
ni...@gmail.com <ni...@gmail.com> #41
pe...@gmail.com <pe...@gmail.com> #42
lc...@gmail.com <lc...@gmail.com> #43
None of these solution is acceptable if for example you want to put back an automatic backup of your pictures from Photos to Drive.
And I don't think Google will change this or even care about this issue ...
Sad but true. @Google, if you won't do anything about this issue, be honest and just close it.
de...@gmail.com <de...@gmail.com> #44
That's the main issue. Lack of information. Given fact, that now a lot of cool features are simply unusable (auto creation — very low quality of results, not predictable and no any answer why after my vacation it is not created automatically), I decided to switch to Adobe Lightroom.
pu...@gmail.com <pu...@gmail.com> #45
This issue will never be fixed. Google just do not want the original photo to be downloadable via API, likely for bandwidth reasons.
go...@jakewharton.com <go...@jakewharton.com> #46
Bandwidth is not a concern. People watch multiple billion hours of YouTube every day. Incremental photo backup at original quality would likely reduce reliance on Takeout so bandwidth usage would likely be a wash (and it's basically a rounding error when viewed in the context of their global network). It's far more likely semi-intentional vendor lock-in.
gi...@gmail.com <gi...@gmail.com> #47
These are fully intentional, and this BaseUrl one is the killer.
cc...@derago.com <cc...@derago.com> #48
ti...@timdickson.com <ti...@timdickson.com> #49
Getting that much data out takes time and I'd love to get this started before the end of time - come on Google
la...@gmail.com <la...@gmail.com> #50
manually export my photos on the website and find a different service for
photo storage. A shame because there are so many features that I do like
about Google Photos
On Fri, Nov 13, 2020, 4:11 PM <buganizer-system@google.com> wrote:
cl...@gmail.com <cl...@gmail.com> #51
ma...@gmail.com <ma...@gmail.com> #52
go...@purple.dropbear.id.au <go...@purple.dropbear.id.au> #53
jb...@gmail.com <jb...@gmail.com> #54
ma...@gmail.com <ma...@gmail.com> #55
[Deleted User] <[Deleted User]> #56
st...@erayd.net <st...@erayd.net> #57
I just want to move my personal photos out of gsuite into an @gmail account without losing all of the location meta data.
If that is all you need, Takeout should be sufficient to complete that task. The lack of a complete API is frustrating, but luckily it's not something that impedes your particular use-case too badly.
wa...@gmail.com <wa...@gmail.com> #58
si...@gmail.com <si...@gmail.com> #59
Google, people are paying for this storage and expecting to get back the same file that they uploaded. Not good enough!
pl...@meta.com <pl...@meta.com> #60
be...@gmail.com <be...@gmail.com> #61
rd...@gmail.com <rd...@gmail.com> #62
pa...@fletch.cx <pa...@fletch.cx> #63
I would also like an answer to this question! Please help with this!
ph...@gmail.com <ph...@gmail.com> #64
lg...@gmail.com <lg...@gmail.com> #65
ro...@catfood.net <ro...@catfood.net> #66
jo...@felixideas.ch <jo...@felixideas.ch> #67
jo...@gmail.com <jo...@gmail.com> #68
yo...@gmail.com <yo...@gmail.com> #69
When will this be fixed? Having GPS-data for all my photos. Why is this striped from the api is beyond my knowledge.
du...@gmail.com <du...@gmail.com> #70
ku...@gmail.com <ku...@gmail.com> #71
lu...@gmail.com <lu...@gmail.com> #72
Only reason for this to be still open almost 3.5 years after is to lock down users. Same reason for new services (like Keep) not having an open API.
Shame on you, "don't be evil" company.
nd...@gmail.com <nd...@gmail.com> #73
cr...@gmail.com <cr...@gmail.com> #74
Shame... ** Rings Bell **
83...@gmail.com <83...@gmail.com> #75
se...@gmail.com <se...@gmail.com> #76
wh...@gmail.com <wh...@gmail.com> #77
or...@gmail.com <or...@gmail.com> #78
jo...@gmail.com <jo...@gmail.com> #79
hu...@gmail.com <hu...@gmail.com> #81
en...@gmail.com <en...@gmail.com> #82
gi...@gmail.com <gi...@gmail.com> #83
mt...@gmail.com <mt...@gmail.com> #84
to...@gmail.com <to...@gmail.com> #85
du...@gmail.com <du...@gmail.com> #86
> Well, this sucks. 2,5 years after my previous comment about it beeing 2
years since first reported this bug is still not fixed!
+1: it's been 6 years since my original post and absolutely no action from
Google. Shameful.
> Already switched browser and mail away from Google's claws, I've been
hoping I didn't have to move away from Photos as well. Sigh
You're in for a nasty surprise when you try to move away from Google
Photos: besides being impossible to download your original photos
programmatically (and having to do it by hand), you can't save albums nor
the other elements (eg interspersed text boxes) inside albums and have to
back them up one by one.
And Google's so-called "takeout" purges all photo metadata from the photo
files themselves and puts them inside a "magic" file which makes it a b*tch
to get them back inside the photo files...
Despite all that, I'm moving away from Google (Photos and other products),
and the greatest benefit is not having to suffer Google's incompetency,
neglect and bad technical decisions anymore.
On Fri, Dec 23, 2022, 19:26 <buganizer-system@google.com> wrote:
al...@gmail.com <al...@gmail.com> #87
va...@gmail.com <va...@gmail.com> #88
mu...@gmail.com <mu...@gmail.com> #89
Who has the best iPhone auto-sync app?
Anything self-hosted? How to auto sync from mobiles on self-hosted?
na...@odinseye.org <na...@odinseye.org> #90
PhotoSync is great:
- Shares purchase with Apple family, so buy once and everyone can use it
- Easily set up custom file names like "YYYY/MM/DD/<original file name>" etc. so you can organize files sanely and not use Apple's "IMG_1234" bullshit
- Supports a TON of back ends (FTP/SSH/etc.)
- Can be set to work based on getting home or a time at night
be...@gmail.com <be...@gmail.com> #91
ni...@nickme.com <ni...@nickme.com> #92
ge...@gmail.com <ge...@gmail.com> #93
xd...@gmail.com <xd...@gmail.com> #94
zh...@gmail.com <zh...@gmail.com> #95
zh...@gmail.com <zh...@gmail.com> #96
na...@odinseye.org <na...@odinseye.org> #97
If you want to download the image retaining all the Exif metadata except the location metadata, concatenate the base URL with the d parameter.
I haven't tested it but retaining Exif metadata does not mean that it is the original image. I'd love for this to work though, it would make rclone
much nicer.
an...@paglusch.com <an...@paglusch.com> #98
ap...@gmail.com <ap...@gmail.com> #99
hu...@gmail.com <hu...@gmail.com> #100
jj...@sigi.icu <jj...@sigi.icu> #101
cr...@gmail.com <cr...@gmail.com> #102
th...@gmail.com <th...@gmail.com> #103
Maybe they just threw away the original pictures and just kept the lossily compressed version. That would explain why they are entirely silent about this issue...
es...@minols.com <es...@minols.com> #104
"Keep original quality"
On Wed, 27 Sept 2023 at 09:11, <buganizer-system@google.com> wrote:
pr...@gmail.com <pr...@gmail.com> #105
The photo downloaded via API using "=d" is less than half the size of photo downloaded from web GUI.
Is anybody working on this!!
I rely on the file size, in addition to the filename, for synchronization with my central backup for various purposes. It's crucial for me to ensure the correct file size is obtained through the API, even if I'm unable to download the file itself.
sh...@deridder.org <sh...@deridder.org> #106
le...@gmail.com <le...@gmail.com> #107
gu...@gmail.com <gu...@gmail.com> #108
ry...@rcchan.com <ry...@rcchan.com> #109
unzip/tar-ing all the photos data every month will probably cost me more in
HDD wear than any amount Google will care about on its infrastructure
On Sun, Oct 15, 2023, 05:00 <buganizer-system@google.com> wrote:
jo...@gmail.com <jo...@gmail.com> #110
As takeout has a different UseCase, I rely on gphotos-sync to get the original data via the api.
Starting this year, I'm happy to pay Google One, but I keep weekly backups on my own server.
Apparently they are lower quality, because this bug.
Would you please be so kind, to fix this?
Thanks!
ni...@nickme.com <ni...@nickme.com> #111
al...@gmail.com <al...@gmail.com> #112
na...@gmail.com <na...@gmail.com> #113
ri...@gmail.com <ri...@gmail.com> #114
Also, if takeout strips metadata from the uploaded images, isnt that a GDPR offence?
gi...@gmail.com <gi...@gmail.com> #115
re...@gmail.com <re...@gmail.com> #116
ry...@rcchan.com <ry...@rcchan.com> #117
no...@gmail.com <no...@gmail.com> #118
na...@odinseye.org <na...@odinseye.org> #119
Unfortunately I can't make our
ho...@gmail.com <ho...@gmail.com> #120
te...@gmail.com <te...@gmail.com> #121
gi...@gmail.com <gi...@gmail.com> #122
gi...@gmail.com <gi...@gmail.com> #123
br...@gmail.com <br...@gmail.com> #124
ro...@gmail.com <ro...@gmail.com> #125
[Deleted User] <[Deleted User]> #126
pr...@gmail.com <pr...@gmail.com> #127
ro...@gmail.com <ro...@gmail.com> #128
kh...@gmail.com <kh...@gmail.com> #129
ed...@gmail.com <ed...@gmail.com> #130
br...@gmail.com <br...@gmail.com> #131
jo...@gmail.com <jo...@gmail.com> #132
Any news?
si...@gmail.com <si...@gmail.com> #133
sm...@gmail.com <sm...@gmail.com> #134
ja...@gmail.com <ja...@gmail.com> #135
mg...@gmail.com <mg...@gmail.com> #136
me...@rafal.io <me...@rafal.io> #137
ap...@gmail.com <ap...@gmail.com> #138
to...@gmail.com <to...@gmail.com> #139
ne...@gmail.com <ne...@gmail.com> #140
dr...@gmail.com <dr...@gmail.com> #141
wa...@gmail.com <wa...@gmail.com> #142
ju...@gmail.com <ju...@gmail.com> #143
ki...@gmail.com <ki...@gmail.com> #144
We'll take a closer look at the behavior of the 'd' parameter. <-----6 years ago
th...@e-x-e.dk <th...@e-x-e.dk> #145
ma...@gmail.com <ma...@gmail.com> #146
da...@gmail.com <da...@gmail.com> #147
ph...@gmail.com <ph...@gmail.com> #148
li...@google.com
Clearly this isn't a priority...but SIX years and nothing??? I l discovered this bug literally right AFTER signing up with the 5tb plan under my developer account. Didn't even think about checking beforehand since it's such a basic feature. Well...just cancelled that account, my wife and son are also cancelling their separate accounts, and moving to another provider.
by...@gmail.com <by...@gmail.com> #149
Google, at least have the decency to Close this bug as either Won't Fix or more honestly, Working As Intended.
ma...@gmail.com <ma...@gmail.com> #150
Hey Google do you need an API engineer to come take a look at this issue, as it seems like there may just be a vacancy. I'll do it just to have this issue fixed once and for all. I'd give you my contact info, but look who I'm talking to 🙃
ge...@googlemail.com <ge...@googlemail.com> #151
I encountered this issue while downloading photos with rclone, which uses this API.
These were the results:
Photos seem to be downloaded in their original size, but the location metadata is stripped entirely.
Videos are still only downloaded with a compressed file size.
da...@stanley.ie <da...@stanley.ie> #152
ja...@ridyard.com <ja...@ridyard.com> #153
ed...@gmail.com <ed...@gmail.com> #154
cr...@gmail.com <cr...@gmail.com> #155
Could you please provide an update here?
xi...@gmail.com <xi...@gmail.com> #156
da...@googlemail.com <da...@googlemail.com> #157
ni...@gmail.com <ni...@gmail.com> #158
al...@gmail.com <al...@gmail.com> #159
no...@gmail.com <no...@gmail.com> #160
tr...@gmail.com <tr...@gmail.com> #161
da...@gmail.com <da...@gmail.com> #162
am...@gmail.com <am...@gmail.com> #163
vi...@gmail.com <vi...@gmail.com> #164
ro...@gmail.com <ro...@gmail.com> #165
al...@nizoux.fr <al...@nizoux.fr> #166
ja...@gmail.com <ja...@gmail.com> #167
ni...@gmail.com <ni...@gmail.com> #168
bi...@gmail.com <bi...@gmail.com> #169
This saves me the hassle of a deliberately mutilated API and I have everything safely in a second location.
Description
In this issue
What steps will reproduce the problem?
1. Download Original Photo in web gui
2. Download the same photo using the <baseUrl>=d
3. idiff web.jpg api.jpg
Comparing "web.jpg" and "api.jpg"
Mean error = 0.203714
RMS error = 0.260547
Peak SNR = 11.6823
Max error = 0.996078 @ (517, 1357, R)
2985188 pixels (100%) over 1e-06
2985188 pixels (100%) over 1e-06
FAILURE
du -sh web.jpg api.jpg
2.4M web.jpg
616K api.jpg
What is the expected output? What do you see instead? If you see error messages, please provide them.
a) idiff to return PASS
b) du to show they have the same file size.