Uh oh!
There was an error while loading. Please reload this page.
Extract GPS data from EXIF - #33511
Conversation
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
b4da031 to
c096b1dCompareUh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
come-nc
left a comment
There was a problem hiding this comment.
A few remarks.
Regarding copying the stream to a temp one, I have no idea if this is avoidable.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
c096b1d to
458a373Comparefelhe
commented
Aug 25, 2022
Just adding my two cents, but the recent changes by @CarlSchwan also made the size property from the EXIF metadata available as a DAV property (see here). Wouldn't it be useful to expose the GPS coordinates to the WebDAV PROPFIND as well? @CarlSchwan@icewind1991 |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
PVince81
commented
Aug 25, 2022
that's the plan already, it should be automatically exposed once it exists in the database |
Uh oh!
There was an error while loading. Please reload this page.
c47d652 to
02a6676CompareUh oh!
There was an error while loading. Please reload this page.
Possible performance regression detected Show Output |
02a6676 to
6527080ComparePossible performance regression detected Show Output |
6527080 to
dad7296ComparePossible performance regression detected Show Output |
Uh oh!
There was an error while loading. Please reload this page.
PVince81
left a comment
There was a problem hiding this comment.
👍 please double check the perf bot
come-nc
left a comment
There was a problem hiding this comment.
Apart from small change on logger, approved
Uh oh!
There was an error while loading. Please reload this page.
dad7296 to
f1ad019CompareSigned-off-by: Louis Chemineau <louis@chmn.me>
Signed-off-by: Carl Schwan <carl@carlschwan.eu> Signed-off-by: Louis Chemineau <louis@chmn.me>
f1ad019 to
54b6d07ComparePVince81
commented
Oct 11, 2022
@artonge please also make sure the new CLI args are present in the documentation |
We want to use this on iOS and Android clients to fetch location data without downloading the full res image + exif. To me it looks like this code only does the process of obtaining the info but we can't request it from client. Is this added somewhere else? |
I had to do a workaround to read EXIF data properly:
Some work has been done by @CarlSchwanhere.But theexif_read_datacall does not work, and probably never worked. One possible explanation is that the resource is wrapped. From the README:> Note: due to php's internal stream buffering the $count passed to the read callback will be equal to php's internal buffer size (8192 on default) an not the number of bytes requested by fopen()As it works when the stream is not wrapped, it might be an explanation for why theexif_read_datacall fails.To make it work, I copy the stream into a tmp stream without wrappers before passing it to exif_read_data.✔️ I found a workaround by calling
stream_set_chunk_size($fileDescriptor, 1);before we read the stream. No idea why it works, but it does, and I am reverting it right after to prevent any side effect outside our use case.I also cherry-picked @CarlSchwan PR that adds a CLI command to extract metadata #32309