We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi,
This issue was first opened on the piwigo-openstreetmap github page : https://github.com/xbgmsharp/piwigo-openstreetmap/issues/109#
It was confirmed by xbgmsharp unfortunately no solution was found.
Some of my photos EXIF GPS data are not read on my Piwigo installation (Ubuntu 16.04 server with latest PWG package).
I have attached 2 photos as an example : photo.zip
For both the photos :
But on my PWG server, only EXIF GPS data of photo2.jpg are retrieved correctly :-(
The text was updated successfully, but these errors were encountered:
Hello,
I had the same issue and debugged it to a problem in parsing some images which have makernotes in exif. See : http://piwigo.org/forum/viewtopic.php?pid=164428.
I found a bug in PHP bug tracker which seems to be the cause of the issue : https://bugs.php.net/bug.php?id=72682
I was using php 7.0.8. An upgrade to php 7.0.10 fixed the problem for me.
For ubuntu 16.04 I used this PPA : https://launchpad.net/~ondrej/+archive/ubuntu/php
Hope it helps !
Sorry, something went wrong.
Thansk a lot : I upgraded to PHP 7.0.10 and it indeed fixed the problem.
No branches or pull requests
Hi,
This issue was first opened on the piwigo-openstreetmap github page :
https://github.com/xbgmsharp/piwigo-openstreetmap/issues/109#
It was confirmed by xbgmsharp unfortunately no solution was found.
Some of my photos EXIF GPS data are not read on my Piwigo installation (Ubuntu 16.04 server with latest PWG package).
I have attached 2 photos as an example :
photo.zip
For both the photos :
But on my PWG server, only EXIF GPS data of photo2.jpg are retrieved correctly :-(
The text was updated successfully, but these errors were encountered: