Template talk:Location/2018

From Wikimedia Commons, the free media repository
Jump to navigation Jump to search

Object location as secondary coordinate

Hi all, hi @Jarekt: Is there a reason why this template does not pass the secondary coordinate parameter to mw:Extension:GeoData (via Module:Coordinates) by default? This would allow to obtain the object location using the geosearch API or from the geo_tags SQL table. Related Phabricator task: T135686. – Simon04 (talk) 14:20, 20 May 2017 (UTC)

Simon04, I am not sure what are you asking about. I wrote all the code for this template but I do not have deep understanding of tags needed for communication with tools that might use the data. The way it works is that if someone asks for additional tagging I add it or help with adding it and I try not to loose it as the code changes. So if some passing mechanism is not there, propose to add it, and if no one objects, I will work with you to add it. As I recall, {{Object location}} is much less interesting to mapping tools as it does not say anything about camera location, and depicted object could be meters or kilometers away. Only Proximityrama tool seems to be using that information and they can get coordinates they need somehow. --Jarekt (talk) 14:51, 20 May 2017 (UTC)
@Jarekt: @Kolossos: I would like to see the parameter secondary=1 to be passed for every {{#invoke:Coordinates}} invocation (unless an other value is specified for this parameter). This would greatly ease extracting the object location in my Commons:Locator-tool (currently I fetch the coordinates from Template:Location from the API, but need to fetch and parse the wikitext for extracting the Template:Object location). Would the change be feasible or is there anything objecting this? – Simon04 (talk) 17:44, 21 May 2017 (UTC)

@Jarekt: Hi! Finally I found time to investigate this issue again. I simulated an invocation of mw:Extension:GeoData for the {{Object location}} of one picture: Special:Diff/284920290 (not marking it as primary). The API calls nicely distinguish between returning the primary coordinate only (by default) and returning all coordinates. Maybe we could think of an adequate type for the object location (e.g., landmark?). This would definitively help my Commons:Locator-tool to deal with {{Location}} and {{Object location}} in the same way. Thanks! – Simon04 (talk) 20:23, 2 February 2018 (UTC)

Simon04, Sorry I have seen this post but forgot about it before I replied. I do not know much about who and what tools use the locations. However if you propose specific change, We can post it here and on com:Geo. We can ping other people that might know if the change would break anything and if there are no objections than I would deploy it. --Jarekt (talk) 02:58, 26 February 2018 (UTC)

Commons talk:Geocoding#Pass object location to Extension:GeoData (Special:Diff/289289242) –Simon04 (talk) 21:19, 26 February 2018 (UTC)

Longitude sign

@The RedBurn: it looks like your edit of the documentation is wrong: it says "Degrees of Longitude. The sign indicates hemisphere: +(West) and -(East)", while the template works in the opposite way: