-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
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
Samsung versus Exif location #5081
Comments
Could you please upload an original JPEG taken by your camera having text EXIF location to http://exif-viewer.com/ and copy/paste the full result here? Please also share the JPG before sneding to Commons, as a shared Google Drive link for instance. Also, could you please create a separate issue for HEIC, including a link to a HEIC file produced by your camera, shared like above. Thanks! |
First, that site raises a browser error even before you get to it ... you have to push advanced settings to proceed to it anyway. Second when I paste https://upload.wikimedia.org/wikipedia/commons/6/65/International_boundary_line_plaque_Rainbow_Bridge_Niagara_Falls.jpg in to it even more SSL errors occur... |
OK, https://jimpl.com/results/mQGrqQF6vib8h6iNAUB97aUD?target=exif says
|
Anyway, users would be expected to always choose .heic mode because it saves half the disk space, and will not be taking pictures in .jpg mode just to support some legacy apps... |
I can reproduce the problem with pictures taken with a Samsung S9 or S22. E.g. the following JPEG: https://cloud.linux4tw.de/index.php/s/BZXKECKDiqfyMJP Exif Result is:
|
Stock Android 12. |
This happens with the custom picker, the normal picker, as well as sharing from gallery? Actually on a recent Android version the only way I have found to get the location recognized is to first look at the picture's location in Google Photos' details, then share to Commons. |
Yes, i tried it directly with the picker from the app as well as sharing from gallery. Both ways do not recognize the location.
I cannot test this due to not having Google Photos available. But this reads like GPhotos is changing some location exif data at the file. |
Observation: reboot the Samsung phone, totally in airplane mode. Looking in the Samsung Gallery app, in the Details page of each photograph, we see each picture has gone back to latitude and longitude. This gives us a glimmer of cheer. So those geocoded street addresses, are just a temporary phenomenon... |
Hmmm, maybe Samsung is not to blame, and something else zapped the GPS stuff.
(exif:GPSInfo is what isn't clear.) |
It worked with an older version of the app, which i had installed via F-Droid back then, e.g. with Android-App Commons 2.11.0~93b948d20 (info from this picture: https://commons.wikimedia.org/wiki/File:Rathaus_Stralsund_3.8.2019.jpg) It might already have stopped working with with version 3.1.1~1c9267ca0. |
Very interesting! If someone could post the F-Droid links to the last working version and the first broken version, that would be super useful. 🙂 |
Unfortunately, this is not possible anymore. The version 3.1.1~1c9267ca0 was installed from Gplay, because the latest available version on F-Droid is 2.6.0. I installed this 2.6.0, but it crashes directly after logging in. |
By the way, https://play.google.com/store/apps/details?id=com.aminbeheshti.exifviewer is a fine Exif analyzer. |
Using the upload wizard in https://commons.wikimedia.org/w/index.php?title=Special:UploadWizard with a Desktop PC detects the location. Using the same wizard with Firefox on Android does not work to detect the location. |
Samsung Galaxy users often find they are not able to transmit location data in the Exif headers so the Commons App can deal with it properly.
For example: https://commons.m.wikimedia.org/wiki/File%3AInternational_boundary_line_plaque_Rainbow_Bridge_Niagara_Falls.jpg
Samsung's Gallery app certainly knows where it is:
So perhaps maybe indeed it is stuffing actual ASCII text of the street address, where latitude and longitude was supposed to be, there in Exif... https://us.community.samsung.com/t5/Galaxy-S22/GPS-location-coordinates-not-entered-into-photo-Exif-file/td-p/2248843
Anyway perhaps the Commons error message should give more guidance, seeing as Samsung is a heavy player in the cell phone market.
Oh and by the way many Samsung users choose the .heic format to save space. But that proprietary format cannot be uploaded to Wikimedia. So we first do this conversion, to .jpg.
(One must select 80%, or else no conversion will occur.)
Anyway I'm sure many of the staff reading this bug report have Android 12 and Samsung Galaxy and have the same problem.
So perhaps some official guidance could be created. "Do not use the Samsung camera app", or "only take pictures directly via the MediaWiki app", etc. etc.
The text was updated successfully, but these errors were encountered: