Last modified: 2012-09-04 21:44:56 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T41745, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 39745 - Location where the photo was taken should be added to the upload if the location is made available
Location where the photo was taken should be added to the upload if the locat...
Status: RESOLVED WONTFIX
Product: WikiLoves Monuments Mobile
Classification: Unclassified
General (Other open bugs)
unspecified
All All
: Low enhancement
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-08-28 19:50 UTC by Maarten Dammers
Modified: 2012-09-04 21:44 UTC (History)
2 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Maarten Dammers 2012-08-28 19:50:14 UTC
See https://commons.wikimedia.org/wiki/File:San_Francisco_Fire_Department_Engine_Co-_Number_2_%28taken_on_27Aug2012_13hrs44mins0secs%29.jpg . We either know the location of the photographer because the camera has a gps or we know the object location because we got that from the api.

Would be nice to add that information (in that order of preference)
Comment 1 Jon 2012-08-28 21:47:09 UTC
Should this be added as EXIF or in the description?
Comment 2 Phil Chang 2012-08-29 18:01:38 UTC
I believe the location is part of the EXIF data if the camera and user has that enabled. If not, we are running into some possible issues regarding privacy.
Comment 3 Jon 2012-08-29 18:59:57 UTC
We are not going to fix this due to privacy concerns. If in the mobile phone camera the user has set 'add my location' the gps coordinates will appear in the EXIF data. I currently am not doing this on my camera so it was not sent. It seems unfair to ask the user before an upload if they want to send their location as well - this would give them 2 places to manage that - and that location is not necessarily correct anyway as the information we do have may be out of date. We can look it up again but that will slow down the upload process.

It's worth noting that we can cross reference the photo with the monument to work out the GPS roughly if need be so we are not necessarily gaining anything by storing it.
Comment 4 Maarten Dammers 2012-08-30 11:41:52 UTC
Jon, if the lat/lon is added to the exif data this is picked up by a bot (https://commons.wikimedia.org/wiki/User:DschwenBot) after upload.

If the exif data doesn't contain lat/lon another bot (erfgoedbot) will add an {{object location}} template. 

This is all afterwards, error prone and shouldn't be too hard to just implement this in the app. It would be much nicer to do it on upload right away.

Logic would be like this:
* Phone adds exif lat/lon : Add {{Location dec|<lat>|<lon>|source:exif_heading:<heading>}} (leave ? for heading if it's not available)
* Phone doesn't add lat/lon : Add {{Object location dec|<lat>|<lon>}}
Comment 5 Jon 2012-08-30 20:05:00 UTC
Marteen sure. It's not a case of being hard - it's a case of privacy.

1) If I have purposely set my camera not to include my location on exif photo - is it right that the photo automatically gets it attached via other means?

2) If we decide to add the user's location to the upload - how do we ensure this is okay? We don't want to just do it without the user's permission - they might see this as us sharing data about them. What if the location is inaccurate and has cached their home location - we would be sharing photos with their home attached.

3) If we need user confirmation on the upload - how does this appear? Is it tucked away in settings or is it per upload. Is it a check box? Do we need to present the information we are sending to the user to inform them better e.g. a map ? If it's in settings is it on by default? If it is how do we ensure that the user is aware of this setting so they don't complain about it later.

Hence I think this needs more thought. :-)

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links