Template talk:Coord

Coords smashing into hatnotes

On pages with long hatnotes, the coordinates overlays the other text. The screenshot is from Special:Permalink/1300395254. My CSS is really weak, but maybe this is related to the issue above? RoySmith (talk) 13:04, 14 July 2025 (UTC)

They should be shown as true indicators (what they are), and not artificially lowered, like in MediaWiki:Vector.css#L-13: #coordinates {position: absolute; top: 3.5em; Ponor (talk) 14:21, 14 July 2025 (UTC)

@RoySmith: It's not a hatnote, it's the tagline. By default, it reads "From Wikipedia, the free encyclopedia". I guess you have some script or gadget installed that overrides this, making it somewhat longer. This might possibly be "Display an assessment of an article's quality in its page header (documentation)".

Anyway, the tagline and coords have a similar vertical position only in certain skins, and your screenshot is of Vector (legacy) skin, in a non-maximised window, thus constraining the usable width. If you look at the page in e.g. Timeless skin, you'll see that the coords are higher up. --Redrose64 🌹 (talk) 19:14, 14 July 2025 (UTC)

Interesting, thanks. And just because I can't remember the last time I switched skins, I'm switching to Timeless to see how that works. RoySmith (talk) 22:12, 14 July 2025 (UTC)

Very wide images

On top (right) of the page Askja I see:

Coordinates: 65°01′59″N 16°46′59″W

Clicking results in a map that has a very wide oval shape of the lake, while clicking 65°01′59″N 16°46′59″W results in a more round shaped lake on the map. FredTC (talk) 05:32, 18 November 2025 (UTC)

This looks like it might be a projection-related issue. I see the same problem at Imuruk Lake, which is similarly far north. If you zoom all the way out from that lake, you'll see Lake&lang=en a projection instead of a globe. I don't know where to report this bug, but it is real. – Jonesey95 (talk) 23:20, 18 November 2025 (UTC)

I can confirm the issue. These maps seem to be stretched out along the east-west axis.

I think the issue should be reported on m:Talk:WikiMiniAtlas and/or on the GitHub issue tracker. The developer of WikiMiniAtlas, User:Dschwen, does not appear to very active on Wikimedia projects but may still receive ping notifications. ~2025-32085-07 (talk) 22:46, 21 November 2025 (UTC)

At 65.0304 latitude Δ 1° is 111,533 meter, but Δ 1° longitude is 13,718 meter. So Δ 1° latitude there is 8.13 times bigger than Δ 1° longitude. However that is not the factor that is used on this map (I estimate it to be 2 -2.5 times too wide). (something went wrong while measuring) --FredTC (talk) 01:52, 22 November 2025 (UTC)

Coord vs WikidataCoord

Can someone help me understand this? I have found that {{Coord|display=it}} seems to produce the same result as {{WikidataCoords|display=it}} on multiple different pages... Is this template now pulling from wikidata when no coords are supplied? Zackmann (^{Talk to me}/_{What I been doing}) 16:44, 11 December 2025 (UTC)

@Zackmann08: since 2014, no? That's Special:Diff/624928514 Ponor (talk) 16:53, 11 December 2025 (UTC)

@Ponor: appreciate you finding a specific diff for me. I guess what I'm confused about is why was {{WikidataCoords}} even made then? It looks like it was created in 2016. IF the same can be achieved here, can the 2 safely be merged or am I missing something... Zackmann (^{Talk to me}/_{What I been doing}) 16:55, 11 December 2025 (UTC)

I hatted the duplicate discussion that you started at Template talk:WikidataCoord § Coord vs WikidataCoord. One discussion in one place please. See WP:MULTI. And you then immediately reverted the hat because I didn't give you an answer there. Have you no patience?

I wrote Module:WikidataCoord but I no longer remember exactly why I wrote it. But, a few minutes of poking about seems to indicate that I wrote it because {{coord}} doesn't support fetching coordinates from wikidata for an arbitrary qid. This works:

{{WikidataCoord|Q90}} → {{WikidataCoord|Q90|display=inline}}

but this doesn't:

{{Coord|Q90}} →

—Trappist the monk (talk) 00:40, 13 December 2025 (UTC)

Felt it was appropriate to discuss on both templates since I didn't get any good responses in the other location. Appreciate you taking the time to explain the difference. That is very helpful. Zackmann (^{Talk to me}/_{What I been doing}) 00:43, 13 December 2025 (UTC)

Trappist the monk given that the following DOES work, is there a reason not to merge these templates. I understand a straight redirect won't work, but a systematic merge...

{{Coord|qid=Q90}} → 48.8567°N 2.3522°E / 48.8567; 2.3522

--Zackmann (^{Talk to me}/_{What I been doing}) 00:46, 13 December 2025 (UTC)

Module:WikidataCoord came into being 8 May 2016 as a result of discussion at Template talk:Coord/Archive 11 § Using coord to inherit co-ordinates from wikidata. Support for |qid= in {{coord}} was added 16 November 2018 at this edit to Module:Coordinates. So the apparent purpose of {{WikidataCoord}} was support of arbitrary qids.

—Trappist the monk (talk) 02:02, 13 December 2025 (UTC)

Edit request to complete TfD nomination

Template:Coord has been listed at Templates for discussion (nomination), but it was protected, so it could not be tagged. Please add:

<noinclude>{{subst:tfm|help=off|1=WikidataCoord}}</noinclude>

to the top of the page to complete the nomination. Thank you. Zackmann (^{Talk to me}/_{What I been doing}) 04:49, 13 December 2025 (UTC)

Note this was an automated (WP:TWINKLE) comment. I do think the template should be tagged, but I have intentionally wrapped it in <noinclude>...</noinclude> as I do NOT think this needs to show up on well over a million pages. If an admin disagrees, feel free to overrule me! Zackmann (^{Talk to me}/_{What I been doing}) 04:51, 13 December 2025 (UTC)

Yeah, I'm inclined to agree. And I'm the guy who got in trouble over edit warring to un-noinclude TfD tags back when I started editing, and wrote WP:Templates for discussion/Noincluded tags... Anyway,  Done * Pppery * _{it has begun...} 04:50, 15 December 2025 (UTC)

Thanks!!! Zackmann (^{Talk to me}/_{What I been doing}) 05:08, 15 December 2025 (UTC)

Multiple titles on page

Does anyone know where the text cannot have more than one primary tag per page comes from? I can't find it anywhere in the code and am very confused.... Zackmann (^{Talk to me}/_{What I been doing}) 03:38, 26 December 2025 (UTC)

I don't know if this helps, but do a find on this page. I found it linked from this Help page. – Jonesey95 (talk) 16:18, 27 December 2025 (UTC)

Interesting. Thanks Jonesey95! I'm trying to figure out if we can add a tracking category... Category:Pages with multiple primary coordinate tags or something... Zackmann (^{Talk to me}/_{What I been doing}) 16:25, 27 December 2025 (UTC)

@Jonesey95: that got me what I needed!! Edit requested. THANKS! Zackmann (^{Talk to me}/_{What I been doing}) 16:32, 27 December 2025 (UTC)

Take a look at User:Jonesey95/sandbox, where Category:Pages with malformed coordinate tags is already applied. Maybe the thing you want already exists? – Jonesey95 (talk) 16:54, 27 December 2025 (UTC)

Hey look at that! IT DOES!! Thank you! Zackmann (^{Talk to me}/_{What I been doing}) 16:57, 27 December 2025 (UTC)

No references option when retrieved from WikiData

Why is there no option to generate a reference for coordinates pulled from WD? RedWolf (talk) 15:47, 2 January 2026 (UTC)

Because the refs belong on the Wikidata page. --Redrose64 🦌 (talk) 17:12, 2 January 2026 (UTC)

So when users see the coordinates and wonder where they came from but there's no footnote for it, how are they going to know they came from WikiData? The Coordinates page makes no mention of information being pulled from there. If I click the Coordinates link, I don't see a note that these coordinates came from WD. RedWolf (talk) 23:27, 2 January 2026 (UTC)

It is technically feasible to generate a reference from Wikidata, see Module:Settlement Wikidata#L-80. — hike395 (talk) 23:40, 2 January 2026 (UTC)

While I'd rather not be the one to implement this, I do support making this possible. Seems reasonable to add the ability to pull the reference... Zackmann (^{Talk to me}/_{What I been doing}) 03:58, 3 January 2026 (UTC)

Broken

Error message

Not found

The URL you have requested, https://geohack.toolforge.org/geohack.php?pagename=Reshma_(air_base)&params=57_25_36_N_042_25_48_E_type:airport, doesn't seem to actually exist.

If you have reached this page by following a link

This URL is managed by the geohack tool, maintained by Dispenser, Kolossos, Magnus Manske.

On ruwiki coordinates work (e.g. ru:Дьячево) --Altenmann >talk 14:59, 4 January 2026 (UTC)

Works for me --Redrose64 🦌 (talk) 17:48, 4 January 2026 (UTC)

Overprecision when pulling from Wikidata

I've edited Altshallan to test out the pulling of coordinates from Wikidata. It works, but the coordinates are given to six decimal places (as 54.170108°N 7.915984°W), which is far too much precision for the purpose.

For uniformity with other articles, I suggest that coordinates pulled from Wikidata only be shown to four decimal places by default, that is, as 54.1701°N 7.9160°W. If we have consensus on this, I can't see any reason why it shouldn't be rolled out straight away once a limited trial has been made using the test template. — The Anome (talk) 16:29, 7 January 2026 (UTC)

• I concur. Abductive (reasoning) 21:23, 15 February 2026 (UTC)

Handling preferred / unknown values

I was chatting to @Phuzion earlier today trying to debug a problem on Dooley's Ferry Fortifications Historic District.

• The Wikidata item here (d:Q18149965) has two P625 statements, one unknown and one with a coordinate value; the second one 33N-93W is marked as preferred.
• {{wikidatacoord}} works as expected (returns 33N-93W)
• {{coord}} breaks and gives "Coordinates: Missing latitude", but does correctly produce Category:Coordinates on Wikidata. It works correctly if given qid=... for a different item with simpler P625 values.

I think what is going on here is that {{coord}} is pulling both values (unknown and normal) from the item, then trying to interpret unknown, failing, and providing an error. The section that produces the category, meanwhile, uses "mw.wikibase.getBestStatements" - which presumably only finds the preferred value and so works fine. However, I'm not sure how best to change the module code to look for only the best value - is that possible, or have I completely misdiagnosed the problem? Andrew Gray (talk) 18:37, 19 January 2026 (UTC)

Wanted to chime in and thank you for the troubleshooting earlier today! I'll be keeping a close eye on this thread. phuzion (talk) 18:43, 19 January 2026 (UTC)

The Bakery

I know this is very small and silly, but I would like to know if there's a way to modify the "Interactive map of [article name]" caption on the Bakery's article, since the rest of the page follows MOS:THECAPS. GustavoCza (talk • contribs) 03:52, 23 January 2026 (UTC)

User:GustavoCza you can modify the caption with |mapframe-caption= in the infobox. Zackmann (^{Talk to me}/_{What I been doing}) 14:58, 23 January 2026 (UTC)

It didn't worked, unfortunately! GustavoCza (talk • contribs) 19:52, 23 January 2026 (UTC)

You didn't do what I suggested... What are you trying to make the caption? I'll do it... Zackmann (^{Talk to me}/_{What I been doing}) 04:49, 24 January 2026 (UTC)

I read too quickly and thought I had to put the command on "Coord" instead of the Infobox, all good now. Sorry about that! GustavoCza (talk • contribs) 20:42, 24 January 2026 (UTC)

Overlink?

The text added to the top right of an article with this template contains the text "Coordinates", which links to Geographic coordinate system. Is this really a helpful link? I feel like there's a chance readers will click the "Coordinates" text thinking it'll show the coordinates on a map; then, after being unexpectedly directed to the GCS article, they'll assume the rest of the text will also link to that same page and that there is no map.

Not sure if this would be a particularly common occurrence, but I do wonder if the link is necessary to begin with. asex twin^{talk · contribs.} 03:17, 25 January 2026 (UTC)

Initial zoom scale

I'd like to display a closer initial zoom in the infobox of Daylit Gallery. Just the V&A museum and perhaps its immediate environs would be ideal. Any help figuring this out would be appreciated. Cheers, Cl3phact0 (talk) 08:36, 15 April 2026 (UTC)

This is nothing to do with Template:Coord. --Redrose64 🌹 (talk) 16:07, 15 April 2026 (UTC)

Sorry, perhaps the correct term is "scale" or "map scale" (using the type:, dim:, or scale: parameters mentioned in the template's doc) rather than "initial zoom". My mistake. -- Cl3phact0 (talk) 16:16, 15 April 2026 (UTC)

These options - described at Template:Coord#Coordinate parameters - are for configuring outside mapping services, such as those reached by clicking this link: 51°29′48″N 00°10′15″W. They are nothing to do with infoboxes. --Redrose64 🌹 (talk) 18:29, 15 April 2026 (UTC)

For instance, if one compares this or this to the Daylit Gallery's infobox map initial zoom (i.e., "map scale"), the former two display a 1km resolution, whereas the latter displays at 5km. This is what I'm trying to adjust. -- Cl3phact0 (talk) 20:04, 15 April 2026 (UTC)
PS: If the map in the article's infobox displayed per the example you've linked above (51°29′48″N 00°10′15″W), that would be fine. -- Cl3phact0 (talk) 20:09, 15 April 2026 (UTC)

Daylit Gallery uses Template:Infobox room; Museum of Applied Arts, Vienna and Art, Design and Architecture Museum both use Template:Infobox museum. In each case, the maps in the infobox are configured by the mapframe parameters, of which there is a comprehensive set - about thirty in all. All that the infobox maps obtain from {{coord}} are the latitude and longitude. Nothing else. --Redrose64 🌹 (talk) 21:33, 15 April 2026 (UTC)

Bullseye! Thanks, just what I needed (adding the mapframe-zoom = 12 parameter works). There may be a way to refine this further, but you've solved my immediate quandary. "From its fruit the tree is known" (and it seems that I was simply shaking the wrong tree). Cheers, Cl3phact0 (talk) 08:52, 16 April 2026 (UTC)