Template talk:Coord

Placement of the center of a location?

Greetings and felicitations. The section title is awkward, but I can't think of a better way to phrase it. In particular with cities (and other larger areas), what coordinates should I use—the geographic center of the area in question, or the business district/center of activity? —DocWatson42 (talk) 04:06, 29 October 2023 (UTC)

Edit: An example: North Haven, Maine. One set of coordinates was in the infobox, and another at the bottom of the article (as is often the case with American municipalities and counties), which I moved to the infobox, to aid in comparing the two. The first points to the northern part of the island, near the (possible) geographic center of the island, while the second appears to point to the business district. —DocWatson42 (talk) 04:14, 29 October 2023 (UTC)

Bumping. —DocWatson42 (talk) 08:58, 17 May 2024 (UTC)

Bumping again, in part to avoid the archiving of this topic. —DocWatson42 (talk) 18:07, 10 September 2024 (UTC)

@DocWatson42: Many settlements grew up around the place where two transport routes met, such as a crossroads, or a bridge over a river. I would pick that point, if it can be identified. --Redrose64 🌹 (talk) 22:13, 10 September 2024 (UTC)

Okay—so the human, rather than the geographic, center (assuming there is one, and it can be identified)? —DocWatson42 (talk) 22:23, 10 September 2024 (UTC)

Bumping. —DocWatson42 (talk) 01:28, 24 December 2024 (UTC)

GeoGroup

Since we are encouraging people to use GeoGroup, can we get it fixed as it is not working at all, just hangs when you try to display all the coords. Kerry (talk) 23:23, 22 February 2024 (UTC)

But if you wait long enough, it will display a map of the world with an error message saying "No data to display". Kerry (talk) 23:33, 22 February 2024 (UTC)

Template is not compatible with night mode

The coordinates icon is not displaying very well in the new upcoming night theme: https://phabricator.wikimedia.org/F54691215 Example: https://en.wikipedia.org/wiki/Phoenix,_Arizona?vectornightmode=1&useskin=vector-2022

Is it perhaps time to update this icon, perhaps to one of the map icons in https://doc.wikimedia.org/codex/latest/icons/all-icons.html ? 🐸 Jdlrobson (talk) 04:55, 31 May 2024 (UTC)

@Jdlrobson The icon is provided by the wikiminiatlas gadget, and I believe hosted on meta, or toolforge. It is managed by User:Dschwen. —TheDJ (talk • contribs) 16:37, 31 May 2024 (UTC)

Question about the "city" parameter (repost)

At what point does the size of the population stop mattering? I have been generally ignoring populations smaller than 10,000 and just entering the unmodified "city" parameter—is this correct? (Reposted from 27 May 2023.) —DocWatson42 (talk) 21:02, 10 September 2024 (UTC)

Bumping. —DocWatson42 (talk) 01:29, 24 December 2024 (UTC)

Consequences of placing the template at the top of articles?

Greetings and felicitations. Are there any consequences to placing this template at the top of articles—will it foul anything up? (I have a vague recollection of seeing a mention that it does, but would like specific and concrete information.) —DocWatson42 (talk) 01:34, 24 December 2024 (UTC)

MOS:ORDER says to put it between the navboxes and categories; but if it has |display=title (without inline) it could, in theory, be placed almost anywhere (like categories). It's conventional to put it at the bottom. --Redrose64 🌹 (talk) 23:10, 24 December 2024 (UTC)

I know the convention—I'm just wondering about the consequences of an alternative, mostly because this would put it where it displays, and make it easier to find. —DocWatson42 (talk) 23:37, 24 December 2024 (UTC)

You run the risk of wikignomes (some armed with scripts and bots) moving it to the bottom again. --Redrose64 🦌 (talk) 14:01, 25 December 2024 (UTC)

Help needed with "Script error: The function "coordinsert" does not exist."

Hi, all! Can anyone help us over at cy:Nodyn:Coord, please? We're getting the following when we use Coord template within the Infobox historic site template. Coord works outside of the Infobox historic site template, and we've gotten around it by putting the Coord template at the beginning and hidden the paramater |coordinates for now within the Infobox (see cy:Venta Silurum for an example of all of this in action). Cheers! Xxglennxx (talk) 14:38, 1 January 2025 (UTC)

@Xxglennxx: The English Module:Coordinates has a coordinsert function, which is not present in cy:Modiwl:Coordinates. --Redrose64 🦌 (talk) 16:54, 1 January 2025 (UTC)

Thank you, @Redrose64. Where can I find coordinsert? Cheers! Xxglennxx (talk) 19:17, 1 January 2025 (UTC)

@Redrose64 Not to worry now - I just recopied from en to cy and it seems to have fixed it! Why I didn't do that hours ago is beyond me! Thank you again! :D Xxglennxx (talk) 19:31, 1 January 2025 (UTC)

Broken!

https://geohack.toolforge.org now gives 404. Jidanni (talk) 11:21, 18 January 2025 (UTC)

Seems to work now. — hike395 (talk) 12:54, 18 January 2025 (UTC)

Yes - raised issue on the Help Desk and it started working again soon after, though maybe coincidence. Rupples (talk) 13:04, 18 January 2025 (UTC)

Broken - Feb 2025

Getting a 502 when clicking on a coord link.

Steps to reproduce

1. Click on a coordinates link, for example

{{coord|48|30|N|144|39|E|region:RU_type:isle_source:GNS-enwiki}}

48°30′N 144°39′E

Expected

Navigate to mapping page

Actual

502 error with text:

Webservice is unreachable

The tool responsible for the URL you have requested, https://geohack.toolforge.org/geohack.php?..., is not currently responding.

— Safety Cap (talk) 18:55, 21 February 2025 (UTC)

Test for valid format= parameter value may be needed

Using |format=degrees by mistake results in blank template output: {{Coord|51|26|0|N|19|55|25|E|format=degrees|display=inline}} → . It would be helpful to test for valid parameter values and output an error message and category.

Note that this is not a hypothetical problem: you can see it at Mount Baker Wilderness, where the coordinates are supposed to display in the text "Mount Baker (10,420 feet (3,180 m))," but |format=DMS is suppressing the template's output entirely. – Jonesey95 (talk) 17:43, 5 May 2025 (UTC)

Coordinates displaying inline despite display=title

At this article, the coordinates are displaying inline (and in the title) despite display=title being set. – Jonesey95 (talk) 13:44, 14 May 2025 (UTC)

@Jonesey95: I see coords in the title only. --Redrose64 🌹 (talk) 20:31, 14 May 2025 (UTC)

I see them displayed at the bottom, below the authority control template. I don't see them when I am logged out, though. Oh dear, I may have messed up something in my CSS. I haven't changed it in months, though. Hmm. – Jonesey95 (talk) 23:19, 14 May 2025 (UTC)

When using my nrowser's "view page source" feature to show the HTML that has been served, I find that after the authority control box (a div element) there is a p element as follows:

<p>
<span class="geo-inline-hidden noexcerpt"><style data-mw-deduplicate="TemplateStyles:r1156832818">
.mw-parser-output .geo-default,
.mw-parser-output .geo-dms,
.mw-parser-output .geo-dec{
display:inline
}
.mw-parser-output .geo-nondefault,
.mw-parser-output .geo-multi-punct,
.mw-parser-output .geo-inline-hidden{
display:none
}
.mw-parser-output .longitude,
.mw-parser-output .latitude{
white-space:nowrap
}
</style><span class="plainlinks nourlexpansion"><a class="external text" href="https://geohack.toolforge.org/geohack.php?pagename=Tata_Steel_Netherlands&amp;params=52.47839_N_4.59212_E_type:landmark"><span class="geo-nondefault"><span class="geo-dms" title="Maps, aerial photos, and other data for this location"><span class="latitude">52°28′42″N</span> <span class="longitude">4°35′32″E</span></span></span><span class="geo-multi-punct">&#xfeff; / &#xfeff;</span><span class="geo-default"><span class="geo-dec" title="Maps, aerial photos, and other data for this location">52.47839°N 4.59212°E</span><span style="display:none">&#xfeff; / <span class="geo">52.47839; 4.59212</span></span></span></a></span></span>
</p>

to which I've added some newlines for clarity. Something in your settings must be matching that .mw-parser-output .geo-inline-hidden selector, possibly with a higher specificity, and applying the declaration display:inline causing it to become unhidden. It doesn't have to be a CSS file, although that's the usual place to start - it could be a Javascript file, and the problem there is that many people (myself included) import scripts from other people's user space, over which we have no control. If somebody out there has written a neat script to aid their work, and you have seen the benefits and decided to import it yourself, that's nice until the original author amends the script, at which point you also get the amendments, desirable or otherwise.

Perhaps the script author was working in fixing coords, maybe to trim down excessive decimals and so wanted to find them easily so they could edit the correct section, without opening each section in turn. So they decided to enhance the script so that coords show up inline even for |display=title. You will have inadvertently inherited that new feature.

If you can't trace the script that is doung this, you may need to write a CSS rule to restore that display:none declaration. --Redrose64 🌹 (talk) 10:32, 15 May 2025 (UTC)

I still can't believe we have all this in here, for the 5 users who want to customize this. We should really see about getting rid of it, it makes no sense. —TheDJ (talk • contribs) 11:36, 15 May 2025 (UTC)

Thanks for the above. I blanked my vector-2022.js file, and the coordinates went away, so it looks like one of the .js scripts I am importing has been modified. FWIW, with scripts enabled, I see the above code, but with a closing /p and an additional <div>...</div> pair before the coordinates link, so it appears that the actual text of the coords don't get all that styling applied to them. Here's mine:

<p>
<span class="geo-inline-hidden noexcerpt">
<style data-mw-deduplicate="TemplateStyles:r1156832818">.mw-parser-output .geo-default,.mw-parser-output .geo-dms,.mw-parser-output .geo-dec{display:inline}.mw-parser-output .geo-nondefault,.mw-parser-output .geo-multi-punct,.mw-parser-output .geo-inline-hidden{display:none}.mw-parser-output .longitude,.mw-parser-output .latitude{white-space:nowrap}</style>
<span class="plainlinks nourlexpansion"><span style="position: relative; white-space: nowrap;"></span></span></span>
</p>
<div style="background-color: rgb(255, 255, 255); padding: 0.2em; border: 1px solid black; position: absolute; top: 1em; left: 0em; display: none; z-index: 15;"><span style="cursor: pointer;"><img src="//upload.wikimedia.org/wikipedia/commons/thumb/5/55/WMA_button2b.png/17px-WMA_button2b.png" srcset="//upload.wikimedia.org/wikipedia/commons/thumb/5/55/WMA_button2b.png/17px-WMA_button2b.png 1x, //upload.wikimedia.org/wikipedia/commons/thumb/5/55/WMA_button2b.png/34px-WMA_button2b.png 2x" class="wmamapbutton noprint" title="Show location on an interactive map" alt="" style="padding: 0px 3px 0px 0px; cursor: pointer;">&nbsp;WikiMiniAtlas</span></div>
<a class="external text" href="https://geohack.toolforge.org/geohack.php?pagename=Tata_Steel_Netherlands&amp;params=52.47839_N_4.59212_E_type:landmark"><span class="geo-nondefault"><span class="geo-dms" title="Maps, aerial photos, and other data for this location"><span class="latitude">52°28′42″N</span> <span class="longitude">4°35′32″E</span></span></span><span class="geo-multi-punct"> / </span><span class="geo-default"><span class="geo-dec" title="Maps, aerial photos, and other data for this location">52.47839°N 4.59212°E</span><span style="display:none"> / <span class="geo">52.47839; 4.59212</span></span></span></a>

I guess I could wolf-fence it, but I'll live with it for now unless one of you has additional insight. I scrolled through my .js script list, and I use a lot of them. – Jonesey95 (talk) 13:47, 15 May 2025 (UTC)