Select Page

Template talk:Coord: Difference between revisions

Content deleted Content added
Mandruss (talk | contribs)
Line 171: Line 171:
*::Reducing barriers to entry is never "trivial", although it seems so when one looks only at individual isolated cases like this one. That's in fact the problem: For 19 years editors have seen no problem with adding thousands of bits of unnecessary complexity, one bit at a time, without considering the cumulative effect. If anybody was thinking long-term or "big picture", they were in a small minority and easily outvoted. &#8213;[[User:Mandruss|<span style="color:#775C57;">'''''Mandruss'''''</span>]]&nbsp;[[User talk:Mandruss|<span style="color:#888;">&#9742;</span>]] 17:25, 23 September 2020 (UTC)
*::Reducing barriers to entry is never "trivial", although it seems so when one looks only at individual isolated cases like this one. That's in fact the problem: For 19 years editors have seen no problem with adding thousands of bits of unnecessary complexity, one bit at a time, without considering the cumulative effect. If anybody was thinking long-term or "big picture", they were in a small minority and easily outvoted. &#8213;[[User:Mandruss|<span style="color:#775C57;">'''''Mandruss'''''</span>]]&nbsp;[[User talk:Mandruss|<span style="color:#888;">&#9742;</span>]] 17:25, 23 September 2020 (UTC)
*:This isn't adding any more redirects than already exist, {{tl|coordinates}} is currently redirecting to {{tl|coord}}. --[[User:Lord Belbury|Lord Belbury]] ([[User talk:Lord Belbury|talk]]) 17:44, 23 September 2020 (UTC)
*:This isn't adding any more redirects than already exist, {{tl|coordinates}} is currently redirecting to {{tl|coord}}. --[[User:Lord Belbury|Lord Belbury]] ([[User talk:Lord Belbury|talk]]) 17:44, 23 September 2020 (UTC)
*::Despite working with coordinates frequently for seven years, I wasn't aware of that redirect because (1) I have never seen it used and (2) being quite happy using template names in my coding, I don't bother investigating available redirects. If we perform this move, many average editors will prefer the longer name because that's the template name. After some passage of time, we will have a significant mix of the two names in coding, and new editors seeing that mix will have to learn that "coord" is merely an "alias" for "coordinates". That, combined with the thousands of cases like it, is neither a good use of editors' finite time and brain power nor conducive to editor retention. The project should not only stop this trend but start working to reverse it; in the meantime I will continue to oppose things like this when I see them. &#8213;[[User:Mandruss|<span style="color:#775C57;">'''''Mandruss'''''</span>]]&nbsp;[[User talk:Mandruss|<span style="color:#888;">&#9742;</span>]] 18:50, 23 September 2020 (UTC)
*'''Support''' per above. But I would like to echo Mandruss. It would be really great if [the more active] bots could be programmed to make this change together with another edit (I wouldn't really support a mass bot sweep simply to make this change alone). It is annoying for both versions to be in use for years to come. [[User:Rehman|<span style="font-variant:small-caps; font-weight:bold; color:darkblue">Reh</span>]][[User talk:Rehman|<span style="color:green">man</span>]] 15:40, 23 September 2020 (UTC)
*'''Support''' per above. But I would like to echo Mandruss. It would be really great if [the more active] bots could be programmed to make this change together with another edit (I wouldn't really support a mass bot sweep simply to make this change alone). It is annoying for both versions to be in use for years to come. [[User:Rehman|<span style="font-variant:small-caps; font-weight:bold; color:darkblue">Reh</span>]][[User talk:Rehman|<span style="color:green">man</span>]] 15:40, 23 September 2020 (UTC)
*'''Support''' as making wiki source more human readable. --[[User:Lord Belbury|Lord Belbury]] ([[User talk:Lord Belbury|talk]]) 17:44, 23 September 2020 (UTC)
*'''Support''' as making wiki source more human readable. --[[User:Lord Belbury|Lord Belbury]] ([[User talk:Lord Belbury|talk]]) 17:44, 23 September 2020 (UTC)

Revision as of 18:51, 23 September 2020

Inconsistent behavior?

At Pacific DC Intertie, the first {{coord}} reference doesn't have a globe; it offers a WikiMiniAtlas button when you hover over it. Other apparently identical references on the same page have a globe. Huh? Jordan Brown (talk) 18:07, 15 October 2019 (UTC)[reply]

coord Doesn't Match Markup Between format=dms and format=dec

When a coordinate is entered as dms the outputted different compared to the outputted markup for decimal.

{{coord|41.9925|-70.7265|region:US-MA_type:city|display=inline,title|format=dms}}

produces

<span class="geo-default"><span class="geo-dms" title="Maps, aerial photos, and other data for this location"><span class="latitude">41ยฐ59โ€ฒ33โ€ณN</span> <span class="longitude">70ยฐ43โ€ฒ35โ€ณW</span></span></span>

{{coord|41.9925|-70.7265|region:US-MA_type:city|display=inline,title|format=dec}}

produces

<span class="geo-default"><span class="geo-dec" title="Maps, aerial photos, and other data for this location">41.9925ยฐN 70.7265ยฐW</span><span style="display:none"> / <span class="geo">41.9925; -70.7265</span></span></span>

you can see that the decimal format doesn't split the lat/lng into separate spans and doesn't have class names to specify latitude and longitude. Is there a reason latitude/longitude in the dms format is marked up but not for the dec format? And if there is/isn't should the output match for both formats?

Vermiceli (talk) 18:49, 22 December 2019 (UTC)[reply]

Coordinates not displayed on mobile page

I went to edit a page that seemed to be missing coordinates (Bermeja), but I see that it already has {{coord|22|33|N|91|22|W|display=title}}. The coordinates are displayed as expected on a desktop browser, but not on a mobile browser (see [1]). โ€”AlanBarrett (talk) 10:56, 18 January 2020 (UTC)[reply]

This is the code for coordinates in the title area:
<span id="coordinates">[[Geographic coordinate system|Coordinates]]: <span class="plainlinks nourlexpansion">[//tools.wmflabs.org/geohack/geohack.php?pagename=Special:ExpandTemplates&params=22_33_N_91_22_W_ <span class="geo-default"><span class="geo-dms" title="Maps, aerial photos, and other data for this location"><span class="latitude">22ยฐ33โ€ฒN</span> <span class="longitude">91ยฐ22โ€ฒW</span></span></span>
I am guessing that one of those CSS classes is not displayed on mobile, but I have been unable to find documentation with an explanation. โ€“ Jonesey95 (talk) 15:40, 18 January 2020 (UTC)[reply]

Zoom and translation

What controls initial zoom when map is opened on Wikipedia article? --5.43.82.5 (talk) 23:26, 29 February 2020 (UTC)[reply]

See mw:GeoHack for details. โ€“ Jonesey95 (talk) 01:39, 1 March 2020 (UTC)[reply]
Thanks. --5.43.82.5 (talk) 22:50, 3 March 2020 (UTC)[reply]

Why is not translation of the map textual notes such as "Hold Ctrl or ? and hover over a link to read an article summary" applied for sr.wikipedia? I guess translations have been already entered at the proper place. --5.43.82.5 (talk) 22:50, 3 March 2020 (UTC)[reply]

You should probably ask at the Discussion page for the page linked above. โ€“ Jonesey95 (talk) 23:46, 3 March 2020 (UTC)[reply]
Done. --5.43.82.5 (talk) 01:45, 4 March 2020 (UTC)[reply]

Migrate from WikiMiniAtlas to Kartographer

@Xaosflux, Mike Peel, and TheDJ: It's been two years since the last discussion about migrating the coord template from WikiMiniAtlas to Kartographer. Is there anything standing in the way of this happening other than just someone taking the time to implement it? The community is pretty familiar with Kartographer at this point, and WMA feels like an anachronism (not to mention the privacy and uptime issues). Kaldari (talk) 00:45, 6 March 2020 (UTC)[reply]

Also, I just noticed that all 3 of you have been editing Wikipedia for 14 years! Weird. Kaldari (talk) 01:09, 6 March 2020 (UTC)[reply]
@Kaldari: I suspect that just getting implementation ready, announcing it for feedback, and doing it is needed. Not sure how many odd edge cases may be impacted (Well my MSIE 4.0 browser worked before!, This doesn't work on my 1999 Blackberry now!, etc). โ€” xaosflux Talk 01:18, 6 March 2020 (UTC)[reply]
Kaldari, i personally think we can switch tomorrow, but I also think the community will find 10 things they don't like about the change and I don't want to be having that debate. Last time (somewhere on VPT/T, can't find it atm) some of the objections raised were:
  1. No support for object highlighting (see New_York_City with WMA). (should be doable with qid, but existing uses often don't pass qid, while WMA does auto lookup based on article title against WIWOSM)
  2. Its slower
  3. It takes me longer to open google maps this way
  4. We lose the link to geohack (some people don't want the link to open the map directly). I think we since added it to External maps section because of that.. .
  5. We lose the flexibility of geohack, because external maps in Kartographer are in the source repo instead of on {{GeoTemplate}}. See also: phab:T152971 โ€”TheDJ (talk โ€ข contribs) 09:49, 6 March 2020 (UTC)[reply]
"object highlighting" i think this actually is sort of supported, it's just untested and only works for display title transclusions of it. โ€”TheDJ (talk โ€ข contribs) 10:45, 6 March 2020 (UTC)[reply]
I think I fixed this. Check Template:Coord/testcases#Tests_of_qid. Would be nice if we did auto marker symbol matching for QID instance of. โ€”TheDJ (talk โ€ข contribs) 13:43, 9 March 2020 (UTC)[reply]
Very nice! Kaldari (talk) 15:16, 9 March 2020 (UTC)[reply]
@Kaldari: Also added support for "format" param now, which I just realised was missing before. โ€”TheDJ (talk โ€ข contribs) 15:51, 10 March 2020 (UTC)[reply]
And there isn't client-nojs fallback yet. โ€”TheDJ (talk โ€ข contribs) 12:38, 6 March 2020 (UTC)[reply]
Thanks Derk-Jan, that's a very helpful list! Kaldari (talk) 18:09, 6 March 2020 (UTC)[reply]

So as some might have noticed, I invested some more time in this possible transition. I think biggest open question left from the template point of view (aside from some potential issues in Kartographer) are the microformat and the CSS support to always show Decimal or always show DMS. We have had discussions before about getting rid of the latter as very few people seem to be using it and it adds quite some bytes and complexity. The microformat however... not so much.. but do will still want it ? I feel microformat has been losing ground considerably... I'm also not even sure what a 'valid' format is supposed to look like these days. Ours seems to be the 'pre-standardization' one and well.. even in 2009 people said it wasn't valid geo microformat... โ€”TheDJ (talk โ€ข contribs) 00:19, 11 March 2020 (UTC)[reply]

@TheDJ: In case it wasn't noticed, if the module is transitioned to Kartographer then the coordinsert and coord2text functions will have to be dealt with. I don't really know how these functions should be handled post-transition, especially since both of them rely heavily on the format of {{Coord}} output strings. Particularly since Kartographer only handles Earth coordinates, I suspect both of them might actually have to be retained to avoid breaking things. Jc86035 (talk) 13:26, 12 March 2020 (UTC)[reply]
Jc86035, yeah still trying to figure out how that works. But it's part of why I said people shouldn't do that kind of 'trickery' in the first place. โ€”TheDJ (talk โ€ข contribs) 15:53, 12 March 2020 (UTC)[reply]
Checked it out, as predicted not doable to support that hack. rewriting geojson etc, i'm not implementing that.. Why don't we run a bot to make sure the content has the right parameters (like it should in the first place), instead of rewriting it ? โ€”TheDJ (talk โ€ข contribs) 16:31, 12 March 2020 (UTC)[reply]
@TheDJ: I think it would be a good approach (both for the Kartographer coordinates and the remaining celestial coordinates using GeoHack). It should have been done to begin with, but I think at the time WP:COSMETICBOT was the main factor in the injection being implemented instead (though the bot ultimately ended up making hundreds of thousands of edits anyway). Alternatively, injection could be allowed for simple cases like a single marker. I think what happens could depend on how much of the current metadata gets kept โ€“ considering that it predates Wikidata and no one really seems to care about it all that much, it could potentially be eliminated entirely following community consensus.
In retrospect it would probably have made more sense to implement a coordinates format that could be easily entered in one template parameter, e.g. DD.xx/DD.xx or DD/MM/SS.xx/DD/MM/SS.xx. I think if a lot of pages are going to have to be modified anyway it could potentially make sense to further reduce the amount of complexity by invoking Module:Coordinates directly from the infobox templates without going through {{Coord}}, but this would be a lot of additional work and it would probably be rendered moot in some years anyway. Jc86035 (talk) 17:40, 12 March 2020 (UTC)[reply]
I think we need to output a geohacks link somewhere, because otherwise all kinds of geo tools break because they in turn depend on Wikipedia-World, which apparently uses gehack links to built its database (can't that thing be rewritten to use the GeoData tables) ? โ€”TheDJ (talk โ€ข contribs) 12:01, 13 March 2020 (UTC)[reply]

I have a dumb question: why does replacing WMA with Kartographer get rid of geohack? I thought WMA was accessed by clicking on the little globe, while geohack was accessed by clicking on the coordinate string itself. What am I missing? โ€” hike395 (talk) 14:18, 14 March 2020 (UTC)[reply]

Hike395, the little globe will not be present on kartographer links, as Kartographer already presents its own map and already has an icon. Personally I really don't see the need to confuse people with a gazillion options and i'd like people to put more effort in the core software so that EVERYONE can benefit, not just the few privileged language versions that had a few volunteers that built something 10 years ago. And it would require adaptations to WMA to make it work. I don't think it is needed. โ€”TheDJ (talk โ€ข contribs) 11:23, 23 March 2020 (UTC)[reply]
TheDJ --- speaking as an avid reader of geographic articles, I never click through on the WMA globe, so if that goes away, I won't care. However, I would be unhappy if the geohack links go away. For US Mountain articles, I often look at the CalTopo links, e.g., [2]. I've recently spent many happy hours exploring Wales clicking through to the Bing Ordnance Survey maps, e.g., [3]. The large number of options in geohack serve a lot of different information needs --- I would be careful of deactivating that without understanding its broad usage. โ€” hike395 (talk) 15:41, 23 March 2020 (UTC)[reply]
Hike395, you can reach geohack from the "External services" menu of Kartographer. And we can always make a gadget for 'the select few' who need it at their fingertips. don't you think? โ€”TheDJ (talk โ€ข contribs) 16:22, 23 March 2020 (UTC)[reply]
Personally I'd hate to loose the options provided by GeoHack. More importantly the new system doesn't seem to handle decimal minutes. I've added the official position of the Old Head of Kinsale lighthouse, 51ยฐ36.287โ€ฒN 8ยฐ32.018โ€ฒW (as tested on Template:Coord/doc) and get sent to 1ยฐ60'S 2ยฐ3'W. Martin of Sheffield (talk) 16:45, 23 March 2020 (UTC)[reply]
Martin of Sheffield, you are not losing them, they would move.. I'll give you a gadget with a nice big "Take me to geohack button" right in the page if you want. โ€”TheDJ (talk โ€ข contribs) 19:51, 23 March 2020 (UTC)[reply]
Martin of Sheffield, "More importantly the new system doesn't seem to handle decimal minutes." I didn't even know the format existed. Thanks for adding it to the testcases.. It seems to work fine for me however... is this only in the kartographer dialog that it is sending you to the wrong place, or with a particular external service ? โ€”TheDJ (talk โ€ข contribs) 19:58, 23 March 2020 (UTC)[reply]
FYI decimal minutes are standard for navigation. 1 minute of latitude is one nautical mile (let's not go down the BIPM vs sailors argument) so a tenth of a minute is one cable. Charts have the latitude scale on the sides in degrees and decimal minutes which makes both plotting and measuring simple. Even the French use the system, and they're home to the BIPM! I've just retested the Old Head and it now seems to be working, strange. I've also added the other decimal minute example which is in the eastern hemisphere and was sent to 1ยฐ-1'S 2ยฐ3'W. However, that was in preview, once submitted it seems to be OK. Martin of Sheffield (talk) 20:28, 23 March 2020 (UTC)[reply]

Spaces between measurements

When formatting the coordinates, there should be (non-breaking) spaces between the measurements, as per the SI and even the website/tool the coordinates link to. For example, {{coord|41|17|20|S|174|46|38|E}} produces 41ยฐ17โ€ฒ20โ€ณS 174ยฐ46โ€ฒ38โ€ณE instead of 41ยฐ 17โ€ฒ 20โ€ณ S 174ยฐ 46โ€ฒ 38โ€ณ E or 41ยฐ 17โ€ฒ 20โ€ณ S, 174ยฐ 46โ€ฒ 38โ€ณ E. Getsnoopy (talk) 00:06, 20 March 2020 (UTC)[reply]

The format is determined by Wikipedia's Manual of Style. See MOS:COORDS. The right place for a discussion about spacing is the talk page for that MOS page. โ€“ Jonesey95 (talk) 03:24, 20 March 2020 (UTC)[reply]
@Jonesey95: Interesting. It seems like the MoS text itself is following the format correct (e.g., For the city of Oslo, located at 59ยฐ 55โ€ฒ N, 10ยฐ 44โ€ฒ E), but most of the rest of the text just refers editors to the template to do it "automatically". So this should be fixed in this template then. Getsnoopy (talk) 06:13, 28 March 2020 (UTC)[reply]
That is one occurrence where ordinary spaces are used, possibly to emphasize the separate components to show how they correspond to the template parameters. At any rate, further discussion should be at MOS talk. Johnuniq (talk) 06:46, 28 March 2020 (UTC)[reply]
Sounds good, I've moved the discussion here. โ€” Preceding unsigned comment added by Getsnoopy (talk โ€ข contribs) 20:37, 4 April 2020 (UTC)[reply]
@Jonesey95 and Johnuniq: I should have seen this before, but MOS actually uses spaces (in the "Numeric values" section of the table). It seems like the discussion didn't yield any objections either. Could this be updated? Getsnoopy (talk) 18:00, 4 June 2020 (UTC)[reply]
It's OK with me to experiment with adding non-breaking spaces between the numbers. The place to do it is Module:Coordinates/sandbox, which is beyond my skills. โ€“ Jonesey95 (talk) 18:49, 4 June 2020 (UTC)[reply]
{{coord}} has 1,221,808 transclusions and a change to how it works needs positive assent, not an absence of discussion. Johnuniq (talk) 23:21, 4 June 2020 (UTC)[reply]
I agree strongly. The discussion will go nowhere without examples of the current and proposed format. โ€“ Jonesey95 (talk) 01:46, 5 June 2020 (UTC)[reply]
I specified the current and proposed formats in the OP already: 41ยฐ17โ€ฒ20โ€ณS 174ยฐ46โ€ฒ38โ€ณE is the current one, and 41ยฐ 17โ€ฒ 20โ€ณ S, 174ยฐ 46โ€ฒ 38โ€ณ E is the proposed. Basically, add (non-breaking) spaces after the unit symbols, and a comma to separate latitude and longitude coordinates. Getsnoopy (talk) 22:34, 15 June 2020 (UTC)[reply]

 You are invited to join the discussion at Wikipedia talk:Manual of Style/Layout#Nothing should go between navboxes and authority control. โ€”โ andrybak (talk) 22:40, 1 April 2020 (UTC)[reply]

Expansion of type parameter

Any room for expansion of the type parameter? Could 'port' be added as a type?Fob.schools (talk) 14:37, 27 April 2020 (UTC)[reply]

Port would fall under landmark, as far as I can tell. Rehman 07:15, 27 May 2020 (UTC)[reply]

Malformed coordinates

Hello. Could someone assist me in figuring out why this edit adds articles to Category:Pages with malformed coordinate tags? Is it because those articles (examples: 1, 2) have a separate {{Coord}} parameter outside the infobox? And if so, any suggestions on how I could go about fixing this? AWB them inside the infobox? Courtesy ping to User:Deor (thanks for reverting that edit!) Rehman 07:19, 27 May 2020 (UTC)[reply]

I looked at a couple of the articles before reverting your edit. Yes, some of them already had {{coord}} templates outside the infobox. In the examples you've linked, I assume that the infobox coords are coming from Wikidata, since they're certainly not there in the infobox parameters here, and I'm frankly not sure why your edit should have caused multiple title displays in the articles. (I know nothing about template coding, but the expression "If first display both" looks possibly problematic.) I'm in general very leery of importing Wikidata coords into en.wp; and I don't see why your edit was desirable to begin with, since I'll bet that there are very few articles using {{Infobox power station}} that have coords in Wikidata but lack coords in our articles. I'll leave the technicalities to people familiar with the niceties of templates. Deor (talk) 08:31, 27 May 2020 (UTC)[reply]
Wd coords are only shown if local values are missing. After a deeper look, it seems like that is indeed the cause. Those separate parameters should in fact be within the infobox's coord parameter, with display=inline,title. I will start making those fixes, but I may have to redo my edit so I can track those particular occurrences and fix. Unless anyone knows another way how I could find articles that uses {{Infobox power station}} but also has a separate {{Coord}} template outside the infobox. Rehman 10:14, 27 May 2020 (UTC)[reply]
I'm going ahead with redoing that edit. Will start fixing those occurrences through articles that show up on Category:Pages with malformed coordinate tags. Hence please don't revert the template edit. Thanks! Rehman 03:46, 29 May 2020 (UTC)[reply]
All fixed. Rehman 06:37, 29 May 2020 (UTC)[reply]

The template seems broken.

Clicking on a generated link on any page where this template is used brings up a 404 error. Tested on East Wing. WikiMaster111 (talk) 14:29, 6 June 2020 (UTC)[reply]

Think there is a problem wider than just the template as you get the same from Commons coordinate links. Keith D (talk) 15:56, 6 June 2020 (UTC)[reply]
How do I go about reporting this issue? WikiMaster111 (talk) 15:59, 6 June 2020 (UTC)[reply]
First port of call would be village pump. Keith D (talk) 16:19, 6 June 2020 (UTC)[reply]
Actually, the issue seems to be resolved. WikiMaster111 (talk) 16:25, 6 June 2020 (UTC)[reply]
This was reported more than an hour earlier at Wikipedia:Village pump (technical)#Coordinates. --Redrose64 ๐ŸŒน (talk) 07:19, 7 June 2020 (UTC)[reply]

div inside span

On Camp Atlanta, this template is used inline. Looking at the generated HTML, the WikiMiniAtlas button is a <div> inside the template's <span>. However, this is improper HTML, as divs are block elements while spans are inline elements. Opencooper (talk) 10:00, 11 July 2020 (UTC)[reply]

Is this the coordinates top right? There is no <div>...</div> that I can find. --Redrose64 ๐ŸŒน (talk) 10:11, 11 July 2020 (UTC)[reply]
No, it's the one in parenthesis right after the title in the lead. Here's the corresponding HTML (simplified):
<p><b>Camp Atlanta</b> (<span class="plainlinks"><span><div style="background-color: white...><span style="cursor: pointer;"><img>...
It's the code for the button that shows up when you hover over the coordinates. Opencooper (talk) 10:48, 11 July 2020 (UTC)[reply]
D'oh, I think I just answered my own question. The div is there for the popup... Not sure if it can be done with a span, but I see why it was done that way, even if it's kinda wonky HTML-wise. Opencooper (talk) 10:54, 11 July 2020 (UTC)[reply]
fwiw, you can make pretty much any HTML element behave like a div by manipulating its display property, either through CSS or JavaScript, depending on context. Given WikiMiniAtlas (aiui) requires JS anyway, that's probably the easiest way to do it. Notionally block elements inside inline elements cause wonky behaviour in some contexts (despite html5's attempt to nullify the difference) and in MediaWiki even the instances that don't cause direct problems cause noise in the linter lists that makes other issues (that do cause direct problems) harder to find and fix. --Xover (talk) 11:37, 11 July 2020 (UTC)[reply]

Visual clash with Template:Attached KML

When {{Attached KML}} is called with "display=title" it adds a "Route map" dropdown link to the top right of the article, but passes nothing to the API (eg. https://en.wikipedia.org/w/api.php?action=query&prop=coordinates&titles=Wall%20Street shows that Wikipedia's API can't say where Wall Street is). Adding a display-title {{coord}} to the same article will help the API out, but the coordinate display will overlap the dropdown link, and seems enough reason not to do it.

Is there a way around this? Is there a method of including a {{coord}} template so that it passes the coordinates to the API but doesn't attempt to display coordinates in the title strip? Could {{Attached KML}} include an additional parameter of a single coordinate point that it can pass to the API as the article's single-point location? --Lord Belbury (talk) 15:37, 27 August 2020 (UTC)[reply]

Requested move 18 September 2020

Template:Coord โ†’ Template:Coordinates โ€“ Expand name, match name with module. * Pppery * it has begun... 15:09, 18 September 2020 (UTC)[reply]

  • Comment: I guess this makes sense, as long as we keep "Coord" as a redirect and as long as the new name does not break anything. It seems like a risk for limited benefit. Having a shorthand redirect that is easier for editors to spell is always helpful. I wonder, since this template is so widespread, if there is code that depends on its current name and will break if {{Coordinates}} (currently only 371 transclusions) is used as the default. โ€“ Jonesey95 (talk) 15:53, 18 September 2020 (UTC)[reply]
    Bots and scripts, usually. --Redrose64 ๐ŸŒน (talk) 19:24, 18 September 2020 (UTC)[reply]
  • Support change to match the module. I'm pretty sure most usages of this template are directly via the infoboxes. Since it's a static usage I'd support changing those usages to the new title, which would then also allow finding any problematic usages, if any, that Jonesey95 was concerned about. --Gonnym (talk) 07:50, 19 September 2020 (UTC)[reply]
There are a huge number of direct calls to the {{coord}} template still out there. Sure, a lot of it is bound up in Infoboxes, but even in those, the {{coord}} is called inline. Fob.schools (talk) 10:10, 23 September 2020 (UTC)[reply]
  • Support the current title is an abbreviation, although the article is at Coordinate system, "Coordinates" seems appropriate for an individual place though maybe it should be singular, namely Template:Coordinate? Crouch, Swale (talk) 10:00, 19 September 2020 (UTC)[reply]
  • Weak oppose Seems like a needless change and yet more typing for no good purpose. It's common enough in speech and writing (though probably not publishing) to just call them "coords". BTW, you can have one ordinate (eg a x-axis y-axis position), but two or more coordinates (x/y or lat/long). Martin of Sheffield (talk) 14:29, 19 September 2020 (UTC)[reply]
    When I was at school doing my maths A-level, we were taught that the ordinate is the position along the y-axis; the corresponding position along the x-axis being the abscissa. See Abscissa and ordinate. --Redrose64 ๐ŸŒน (talk) 20:32, 19 September 2020 (UTC)[reply]
    I stand corrected. I was thinking just about the singular/plural and not the ordinate/mantissa. Mea culpa. Martin of Sheffield (talk) 20:41, 19 September 2020 (UTC)[reply]
  • Happy to support any proposal which makes template names clearer โ€” Martin (MSGJ ยท talk) 08:17, 23 September 2020 (UTC)[reply]
  • Oppose unless a bot is created to convert all usage throughout the site to the new name in a matter of hours. What we do not need is yet another instance of multiple names for the same thing, continuing for the life of the project, with new editors required to learn that they are in fact the same thing. This adds unnecessary complexity, raising the barriers to entry. While there is no way to prevent the creation and use of template redirects (unfortunately), we needn't create them without better reasons than those presented here. If it's important for the template and the module to have the same name, rename the module, not the template. โ€•Mandruss โ˜Ž 14:18, 23 September 2020 (UTC)[reply]
    Why is a bot needed, see Wikipedia:Bot requests/Frequently denied bots#Bots to make trivial wikicode improvements. Crouch, Swale (talk) 16:32, 23 September 2020 (UTC)[reply]
    Reducing barriers to entry is never "trivial", although it seems so when one looks only at individual isolated cases like this one. That's in fact the problem: For 19 years editors have seen no problem with adding thousands of bits of unnecessary complexity, one bit at a time, without considering the cumulative effect. If anybody was thinking long-term or "big picture", they were in a small minority and easily outvoted. โ€•Mandruss โ˜Ž 17:25, 23 September 2020 (UTC)[reply]
    This isn't adding any more redirects than already exist, {{coordinates}} is currently redirecting to {{coord}}. --Lord Belbury (talk) 17:44, 23 September 2020 (UTC)[reply]
    Despite working with coordinates frequently for seven years, I wasn't aware of that redirect because (1) I have never seen it used and (2) being quite happy using template names in my coding, I don't bother investigating available redirects. If we perform this move, many average editors will prefer the longer name because that's the template name. After some passage of time, we will have a significant mix of the two names in coding, and new editors seeing that mix will have to learn that "coord" is merely an "alias" for "coordinates". That, combined with the thousands of cases like it, is neither a good use of editors' finite time and brain power nor conducive to editor retention. The project should not only stop this trend but start working to reverse it; in the meantime I will continue to oppose things like this when I see them. โ€•Mandruss โ˜Ž 18:50, 23 September 2020 (UTC)[reply]
  • Support per above. But I would like to echo Mandruss. It would be really great if [the more active] bots could be programmed to make this change together with another edit (I wouldn't really support a mass bot sweep simply to make this change alone). It is annoying for both versions to be in use for years to come. Rehman 15:40, 23 September 2020 (UTC)[reply]
  • Support as making wiki source more human readable. --Lord Belbury (talk) 17:44, 23 September 2020 (UTC)[reply]

Questions