Template talk:Location

Info non-talk.svg Template:Location has been protected indefinitely because it is a highly-used or visible template. Use {{Edit request}} on this page to request an edit.
Please test any changes in the template's /sandbox or /testcases subpages, or in a user subpage, and consider discussing changes at the talk page before implementing them.

This Template is intended to complement Template:Information.

Example for useEdit

See: Image:Hildesheim-Hoher.Weg.Huckup.01.JPG

Syntax {{Location|Degree|Minute|Second|Latitude|Degree|Minute|Second|Longitude|Information attributes}}
Example {{Location|52|09|03.70|N|9|57|02.79|E|type:landmark_region:DE-NI_scale:5000}}


The example is for a landmark in the region Germany (DE), Lower Saxony (Niedersachsen NI). By scale you request the mapping program to render the map in a scale of 1/5000.) Information attributes on landmark and region should always be added. Scale is an optional parameter and is not necessarily required. To find adequate parameters for other regions of the Earth, please look at the project pages in the English Wikipedia (w:en:Wikipedia:WikiProject Geographical coordinates or in the German Wikipedia (w:de:Wikipedia:WikiProjekt Georeferenzierung).

Location of measurementEdit

VLF 18.1 kHz spectrogram

I have a figure of a radio measurement taken at a particular location. The template says "Camera location", but there was no camera. Also the source of the transmission is at a distance, so what I have is the measurement location, not the "object" location. What to do? Olli Niemitalo (talk) 07:19, 5 May 2015 (UTC)

Is the location really relevant? At any rate I don’t think it’s a great stretch to expand the definition of camera, for the purpose, to something like recording device for electromagnetic radiation—thereby including the receiver-spectrograph apparatus used; I don’t think anyone would be confused or misled by that. I‘m not sure what you mean by “measurement location”, but if the source is ill-defined (or multiple), I‘d just leave the object location out. If the source has directional coordinates (RA & Dec or similar), I guess those should be provided in the description, as I don’t think the location templates can be used for anything but geographic (or selenographic &c.) latitude & longitude.—Odysseus1479 (talk) 01:28, 6 May 2015 (UTC)
I've used {{object location}} (same syntax, but not about a camera location) on a similar file, because the location is relevant for the observation, i.e., Hamburg is no rural area.:-)Be..anyone (talk) 10:20, 7 May 2015 (UTC)

Geocoding page linkEdit

Currently Circle-information.svg icon links to Commons:Geocoding page. How I can direct that link to geocoding page translated to Malayalam (Commons:ജിയോകോഡിങ്)? Pls help--Praveen:talk 13:43, 28 June 2015 (UTC)

On top of Commons:Geocoding there is a link to Commons:ജിയോകോഡിങ്. Otherwise the best option would be to translate Commons:Geocoding using translation tool. --Jarekt (talk) 14:26, 28 June 2015 (UTC)
I know that. I translated that page before translation tool (The page is not added to translation tool yet). There is also a redirect from "Commons:Geocoding/ml". Actual problem is that if someone click the link from Malayalam Wikipedia, it lands in the English page. Is there any option to link respective languages from the script itself?--Praveen:talk 17:42, 28 June 2015 (UTC)
Pictogram voting keep.svg Fixed --Jarekt (talk) 17:13, 30 June 2015 (UTC)
Thank you Jarekt :)--Praveen:talk 14:44, 9 January 2016 (UTC)

headings for {{Object location}}Edit

The definition says: In case of {{Object location}} template that might mean that we are looking at a South wall/side of the structure/object. I don't like the soft formulation that might mean. Prefer the straight that means. But, looking at a South wall/side means heading North with the camera ({{location}}), more or less. This is disturbing and confusing. My proposal is to disallow headings for {{Object location}}. Even more as there are actually only few uses. And even less with individual values. --Herzi Pinki (talk) 22:35, 29 June 2015 (UTC)

  • Symbol keep vote.svg Agree: headings for {{Object location}} don’t make enough immediate sense to be of any use. Any particular situations (like the inherent heading of some “aiming” items like windows or canons, or of linear structures) are more clearly covered by using text. -- Tuválkin 04:47, 30 June 2015 (UTC)
  • I agree they should be deprecated, or at least that the documentation should clearly describe any use-cases considered worth keeping. And some wording that advises use of the description field for other possible meanings would also be helpful. See my postings here a few months ago. Is there any way we can tell how many instances there are ‘in the wild‘ of this template with a heading parameter?—Odysseus1479 (talk) 06:30, 1 July 2015 (UTC)
That sounds reasonable for an image file with an obvious individual subject, where there is a single camera–target vector, but that’s not true of categories or gallery pages including multiple angles of view—where I would expect this version of the template to be most often used. (Camera locations wouldn‘t make sense in those contexts either.) Perhaps the documentation should draw this distinction; would you object to deprecating the parameter for the latter applications?—Odysseus1479 (talk) 19:20, 1 July 2015 (UTC)
I am all for depreciating heading info if used in category or gallery namespace. We might have some categories like Category:Stari Most viewed from north there category might have specific heading but that is quite rare. I think we should update documentation and may be run a bot to remove heading from categories like Category:Astronomical Centre Rijeka. --Jarekt (talk) 19:50, 1 July 2015 (UTC)
to disallow/discourage heading on categories and galleries would be an improvement. --Herzi Pinki (talk) 12:51, 9 July 2015 (UTC)
I cannot follow your idea of considering {{location}} and {{object location}} on an image defining a vector AND allowing heading on both. It will overdetermine the system and could help to find geometric errors we would not have without heading. Ok, we could run some plausi to find inconsistencies, if there were enough heading values. In my experience copying of {{location}} or manual determination is error prone, users are even challenged with the difference between {{location}} and {{object location}}. --Herzi Pinki (talk) 12:51, 9 July 2015 (UTC)
  • Disagree Theoretically useful for Ships (Port and starboard), Statues (Forward facing), Theaters (Stage Left/Right), Airport runways (Direction of takeoff), Ski ramps, Waterfalls (presumably the direction of flow, not the staring direction), or the direction of home plate. This directionality is the reason I didn't flag it in my ghel reports. Just because people are unable to document it, doesn't mean its a bad idea. —Dispenser (talk) 02:26, 6 July 2015 (UTC)

I fear there are two contradicting semantics around: the south side of a building has a heading S, while the heading of a runway could have any heading. In case of a statue it could be the statue is heading (facing) S or it is the side of the statue shown on the photo (maybe the back side) heading S. If heading for {{object location}} is kept, documentation should be precise and not encourage both semantics. If I would have to decide, I would prefer to give heading of objects the meaning of the direction the object is moving, or the direction, other objects are moving on the object (planes, cars) (as Dispenser argued) and not the meaning of heading (as Jarekt argued). This will also remove overdetermination. For waterfalls, I would not add heading, because it is always the same: down. :-) --Herzi Pinki (talk) 12:51, 9 July 2015 (UTC)

{{object location}} has been around for a long time and so far the meaning of heading meant only one thing: the heading of the camera, so is a photograph has both {{location}} and {{object location}} than headings are the same. This definition makes little sense for categories unless you have category like Category:Chillon viewed from north which has specific viewing direction. I do not think we should change the current definition written in Template:Location/attribute documentation, but we can clarify it if needed. We can also add something about discouraging usage of "heading" in category namespace. Last week I looked through all usages of "heading" in categories and removed it if it was not valid. --Jarekt (talk) 14:26, 9 July 2015 (UTC)
Thanks, hopefully the default for objects is now "no heading at all". –Be..anyone 💩 02:14, 28 April 2016 (UTC)


Hi all, is there a version of this template that takes the coordinates from Wikidata? --Arnd (talk) 15:37, 17 December 2015 (UTC)

Not at the moment. How would it be used? --Jarekt (talk) 17:12, 17 December 2015 (UTC)

I just think that it would be helpful to have geographical categories with coordinates. When properly linked the Wikidata coordinates could be used as category coordinates. See also Commons:Village pump#Many categories lacking latitude/longitude. --Arnd (talk) 18:20, 17 December 2015 (UTC)

Hi Jarekt and others. Some time ago User:ԱշոտՏՆՂ helped me to create a prototype that shows how a category can be enriched by the coordinates from Wikidata. It should be added to each category with a connected Wikidata item that also contains coordinates. Of course, before the layout must be aligned. Do you think it would make sense to continue this approach? Best regards, --Arnd (talk) 17:16, 27 April 2016 (UTC)

  • There are 135k categories (https://tools.wmflabs.org/autolist/index.php?language=en&project=wikipedia&category=&depth=12&wdq=claim[625]%20AND%20link[commonswiki]&pagepile=&wdqs=&statementlist=&run=Run&mode_manual=or&mode_cat=or&mode_wdq=not&mode_wdqs=or&mode_find=or&chunk_size=10000) that benefit from it. --Arnd (talk) 18:27, 28 April 2016 (UTC)
Arnd, I am working on Category:Wikidata access templates. Now {{Data|item=Q90|property=P17}} gives "France" as "country" of "Paris", but {{Data|item=Q90|property=P625}} which should return geocoordinates of Paris does not work here or on wikidata. I am sure we will be adding Wikidata to many templates including this one, but this seems like it might be more tricky. --Jarekt (talk) 17:42, 27 April 2016 (UTC)
You can get latitude with {{#invoke:Wikidata|formatStatementsE|property=P625|item=Q90|displayformat=latitude}} (same for longitude). I think the most convenient solution is to make use of that in Module:Coordinates. At least it is how I did it in frwiki. --Zolo (talk) 21:34, 27 April 2016 (UTC)
Return to "Location" page.