Template talk:Coord/Archive 14

Archive 10

←

Archive 12

Archive 13

Archive 14

Having dedicated decimal degree and DMS templates

I work with new users through training and occasional users through programs like 1Lib1Ref and other GLAM outreach. They are all using Visual Editor. They find the coord template baffling beause of its use of positional parameters which don't play nicely with the Visual Editor. And people can't get their heads around the bundling of some parameters e.g. "type:city_region:AU-QLD" etc. So it occurred to me that the main reason for the use of positional parameters in the template is simply because some coords are in decimal degrees and others using DMS. Could we have some convenience templates with named parameters e.g.

{{coordDD|lat=-27.34167|long=153.04611|type=city|region=AU-QLD| etc }} {{coordDMS|latD=27|latM=20|latS=30|latDir=S|longD=153|longM=02|longS=46|longDir=E|type=city|region=AU-QLD| etc }}

which just map onto the coord template. While there might not be great benefit to the wikitext user who uses coord regularly, it would be huge benefit for the Visual Editor user as they will see a form for coordDD and coordDMS with a meaningfully named box for each value (with the usual help info, default values, whether something is mandatory or not etc). Easy-peasy for people to fill in. It would also benefit the occasional wikitext user, who finds the positional parameters hard to remember and how to construct type:city_region:AU-QLD etc. I note nothing in this proposal stops anyone continuing to use coord, these are additional for those who would benefit from them. What do you all think? Kerry (talk) 08:41, 12 January 2022 (UTC)

I'm not opposed to that. I also think we should seriously consider splitting out the geohack info into separate parameters. Or you know, just switch to the new Kartographer based version and get rid of geohack. —TheDJ (talk • contribs) 10:15, 12 January 2022 (UTC)

Hang on, it looks like such templates have existed since 2013 and with the same motivation I had (make it easier for Visual Editor users) Template:CoordDec and Template:CoordDMS and Template:coordDM. They got taken to TfD with the usual anti-VE vitriol, which ended with no consensus. No idea if they are actively maintained or how well they work, but I guess I need to explore that. Kerry (talk) 10:47, 12 January 2022 (UTC)

Coordinates bad positioning

Moved from WP:VPT

Tracked in Phabricator
Task T281974

Am I the only one bothered by seeing the top page coordinate location overlapping on the languages drop down menu?

I've noticed it since I started using the new Vector last year and it never changed. I thought I need patience for the newly tested skin to be set, but so far nothing has been touched.

• Legacy Vector view: no overlapping
• New Vector: annoyingly overlapping with the languages drop down menu.

Thanks all. --Mahmudmasri (talk) 01:49, 25 February 2022 (UTC)

@Mahmudmasri: I've moved this report to the template page that makes the coord's, this page is fairly well attended by people that know about it. — xaosflux ^Talk 02:03, 25 February 2022 (UTC)

Thanks. I just think it is related to the Vector skin, not the coordinates template itself:

.skin-vector-2022 #coordinates
{
  top: -3em;
}

I could fix this for me alone by changing the value of -3 to -1.6. --Mahmudmasri (talk) 02:47, 25 February 2022 (UTC)

This is bug T281974. This is also discussed above. It is not clear to me if anything was actually implemented. – Jonesey95 (talk) 14:06, 25 February 2022 (UTC)

@Izno think you were looking in to this, is this something that can be dealt with in Module:Coordinates/styles.css? — xaosflux ^Talk 14:11, 25 February 2022 (UTC)

As discussed above and at Module talk:Coordinates#coordinsert feature broken and at MediaWiki talk:Vector-2022.css#Interface-protected edit request on 5 February 2022, there are two ways forward: Either we move this to a page indicator +- attendant grief, or we use a default-on JS gadget to position coordinates, which is, well, suck. The former requires additional fixing per the module talk page. I dropped it after that self-reverting that attempt for other priorities (which ended up being procrastinating on reading for an ArbCom case). I do not know how best to move forward. A headsup in a public place that it's moving to an indicator if we go that way (I see the JavaScript solution as a non-starter, not least because it will make Google sad for reflow, never mind the bad performance for users). The last solution would be to remove title-placed page coordinates entirely. It's probably a last choice for most people. Izno (talk) 23:05, 25 February 2022 (UTC)

Nomination for merger of Template:Coord-doc-dim

Template:Coord-doc-dim has been nominated for merging with Wikipedia:WikiProject Geographical coordinates/dim:. You are invited to comment on the discussion at the template's entry on the Templates for discussion page. Thank you. 65.92.246.142 (talk) 15:38, 3 March 2022 (UTC)

Template:WikidataCoord and Category:Coordinates_on_Wikidata‎

Please check Wikipedia:Village_pump_(technical)#Template:WikidataCoord_and_Category:Coordinates_on_Wikidata. --Tim Wu (talk) 15:49, 14 May 2022 (UTC)

Decimal degree rounding

The United States Geological Survey provides coordinate position data in decimal degrees to seven places. This far exceeds the actual precision of the location, but the seven decimal places are very useful for reviewing data accuracy. It would be very useful if Template:Coord could provide a decimal degree rounding capability. This way coordinates could be entered to seven decimal places but the template would only display the coordinates to (for example) four decimal places. Yours aye,  Buaidh  talk e-mail 14:32, 14 June 2022 (UTC)

Can someone please make a sandbox version of Template:Coord to accommodate this extension? Thanks,  Buaidh  talk e-mail 23:51, 30 June 2022 (UTC)

city() is broken

The city(9,999) parameter seems to be broken now, currently rendering everything after the "(" inline; e.g., as "7,456)_dim:3875&title=Mount+Pleasant 32°01′42″S 115°50′56″E" instead of just "32°01′42″S 115°50′56″E". Betterkeks (talk) 03:16, 3 July 2022 (UTC)

@Betterkeks: This sounds like an issue for Module talk:Coordinates. When you report it, make sure that you include a link to the actual article where the problem occurs. --Redrose64 🌹 (talk) 07:46, 3 July 2022 (UTC)

"More than one primary tag"

Could anybody tell me what is the cause of the error at Whitehouse, Milton Keynes, please? The problem arises because I have added a second infobox (for the school). I have tried removing display=inline,title from the coord invocation in mapframe-custom but to no avail. 𝕁𝕄𝔽 (talk) 21:17, 9 October 2022 (UTC)

Deor has fixed it. (Thank you). Too difficult to see on mobile what the magic formula was, will look later in big screen. --𝕁𝕄𝔽 (talk) 22:24, 9 October 2022 (UTC)

The {{coord}} templates in both infoboxes (and the one in the mapframe template as well) had display=inline,title parameters. An article can contain only one title display of coordinates without throwing up an error message and being listed in Category:Pages with malformed coordinate tags, which is where I saw it. Deor (talk) 22:43, 9 October 2022 (UTC)

No doubt you are correct but I had assumed that to be the most likely reason and, as I said, tried removing it without effect. (There were only two real instances, the one in the civil parish infobox and the other in the mapframe. The "standard" one in the school infobox was commented out. Or at least so I believed but evidently I missed something. We live and learn. --𝕁𝕄𝔽 (talk) 23:33, 9 October 2022 (UTC)

multiple display=title items

some pages cover a small number of locations and would benefit from this. instead of 1 coordinate in the title, there would be a small list of named coordinates. it would also help as a quick indicator that a page is about separate locations, if it were to be used regularly.

but it might interfere with other stuff like (what comes to my mind just now): GeoGroup. Nowakki (talk) 13:13, 28 October 2022 (UTC)

Template:Coord pulling from Wikidata on its own?

So I'm helping with the backlog of articles with coordinates in wikidata but not here. Normally, I will open the wikidata listing and copy-paste the coordinates into the Template, but I noticed recently that several articles just do {{coord|display=title}} and it will pull the coordinates from wikidata already. Is this a new feature? Bkissin (talk) 17:32, 8 December 2022 (UTC)

See the documentation: "You can get coordinates from Wikidata by transcluding this template without any numbered arguments." – Jonesey95 (talk) 18:03, 8 December 2022 (UTC)

OK thanks. Wanted to make sure I wasn't missing something or messing anything up. Bkissin (talk) 19:04, 8 December 2022 (UTC)

Reg. region:

The doc says If no region: parameter is provided, GeoHack attempts to determine the region from the coordinates. Take for eg:Anand Vihar metro station, The template didn't do so. {{Infobox station}} adds a Region: from the value in |country= but shouldn't it work without that? REEDriler (talk) 18:03, 16 April 2023 (UTC)

messed up display when using display=title

I have noticed that on many articles that use this template (template:coord) w/ the parameter 'display=title' the resulting coordinates text appears in the upper right corner of the article (OK, as expected so far) but the text is all messed up by the fact that the coordinates-text is overwriting the title-text for an info-box placed under the coordinates. Some articles that show this problem are: Claremont Institute, Acton Institute, Leadership Institute. The problem seems to only happen when an info-box is present. Also, this appears to happen on at least three different web browsers I have tested with; namely: Firefox, Safari, and Chrome. Is there some solution to this? Why has this bug lasted so long? Thanks for any information. L.Smithfield (talk) 12:15, 29 April 2023 (UTC)

• I see a number of pages with other issues of coords showing up over infoboxes and other templates at the top of the page. Ex: Adelaide, Bundestag, Suez Canal, any page that doesn't have one of the other page indicators in the space b/t coords and title [which would push the whole page down]. – SJ + 13:43, 29 April 2023 (UTC)

  Thanks that someone besides myself has noticed this. I noticed this problem quite some time ago (maybe more than one or two years ago?) but for some reason I ignored it, thinking that it might not be something that is systematic (like a rare bug of some sort rather than a bug that is exhibited very often). But for some reason, I now realize that this bug is quite widespread (as you also have noticed). For a moment I was sort of hoping that it was a bug just exhibited by a single browser, but as I mentioned above, I have confirmed this bug on at least three different browsers already (Chrome, Safari, and Firefox). It is strange that this bug has gone unaddressed for so long. What would be the next step towards bringing this to the attention of someone who can fix this? Thanks. L.Smithfield (talk) 14:02, 29 April 2023 (UTC)

The practical discussion seems to be here - with a checklist for resolving this. Stalled, and not an obvious candidate for {{sofixit}}, but commenting there would be useful. – SJ + 14:25, 29 April 2023 (UTC)

Thanks for the pointer. I am glad to know that this was under investigation. Thanks again. L.Smithfield (talk) 18:12, 29 April 2023 (UTC)

Switching to Kartographer

Looks like the last discussion Template_talk:Coord/Archive_13#Migrate_from_WikiMiniAtlas_to_Kartographer stalled despite the technical issues seemingly being resolved. The last Kartographer version of the module would have to be synced (I can probably do that) but after that I wonder if the RfC/discussion Kaldari suggested can be run. The current WikiMiniAtlas is embarrassingly out of date and it would be good to replace it. Pinging everyone from the last discussion: @Xaosflux, TheDJ, Jc86035, Hike395, Martin of Sheffield, Evad37, and Jackmcbarn. Galobtter (talk) 07:45, 30 April 2023 (UTC)

I made Module:Coordinates/sandbox the Kartographer version including the updates done to Module:Coordinates in the meantime. Galobtter (talk) 07:58, 30 April 2023 (UTC)

I'm not opposed to getting rid of WikiMiniAtlas in favor of Kartographer: it's clearly better. However, the proposal is to get rid of both WikiMiniAtlas and the link to GeoHack. I just tested it --- Kartographer doesn't fulfill my mapping needs, because it doesn't appear to have regional mapping services. Two years ago, TheDJ said there would be a link to GeoHack -- that's now true, but the regional parameters from Template:Coord are not being passed to GeoHack, so my mapping experience is now badly degraded -- what was one click is now "go to Kartographer, click on GeoHack, scroll down to correct region". Would it be possible to pass the parameters from Template:Coord through Kartographer over to GeoHack? Or (better yet) to have Kartographer offer regional mapping services itself, depending on region code?

Another question --- there's some process/CSS somewhere in WP that detects links to GeoHack and prepends a WMA globe link. Is that going to go away?

Thanks in advance! — hike395 (talk) 10:36, 30 April 2023 (UTC)

That globe icon, c:File:WMA button2b.png, is displayed for title coords, but seems to be suppressed for some inline coords, I've not worked out the circumstances. I think that it and the associated link are added by JavaScript, it's certainly not possible in CSS alone. --Redrose64 🌹 (talk) 11:55, 30 April 2023 (UTC)

If there was a user script that restored a geohack link for those who wanted it, would that address your needs?

(re your question, yes, see the section on WikiMiniAtlas at MediaWiki:Common.js) Galobtter (talk) 17:34, 30 April 2023 (UTC)

fwiw, I wouldn't mind if the WMA globe links went away for all geohack links.

Re: user script --- do you mean some JS I could put in my own common.js file and coord links would act as they would today? That would be suboptimal, but acceptable. I would be sad to miss out on the new Kartographer features (e.g., outlines), but if no one is going to fix Kartographer to allow reasonable access to regional mapping services, I would probably use such a thing.

I experimented with the sandbox version of {{coord}}, and I notice that the dim parameter would now be non-functional under Kartographer? @Galobtter: would it be ok with you if I modify Module:Coordinates/sandbox to attempt a fix? I'm only a templateeditor, so this is my chance to help make the outcome better. — hike395 (talk) 20:54, 30 April 2023 (UTC)

Sure you can try. The user script would probably add an additional link to geohack adjacent to the Kartographer link. Galobtter (talk) 21:43, 30 April 2023 (UTC)

Actually, all you need to do is add this piece of css in your common.css:

.coord-geohack { display: inline !important;}

and that restores the geohack link next to the Kartographer link that is already emitted by the sandbox version for compatibility reasons (add the css and go to Module talk:Coordinates/testcases). So we can just probably the emitted version slightly prettier and that should be good. Galobtter (talk) 21:53, 30 April 2023 (UTC)

Thanks for the CSS tip -- it worked like a charm. I was WP:BOLD and made the emitted HTML slightly prettier. I also got dim and city population to work at Module:Coordinates/sandbox. Everything seems to work nicely. — hike395 (talk) 01:42, 1 May 2023 (UTC)

It’s gonna be an endless train of minor/niche grievances blocking the obvious way forward. I don’t want any part of it. Please stop pinging me on this topic. —TheDJ (talk • contribs) 12:01, 30 April 2023 (UTC)

Kartographer has some really nice features and would be an substantial improvement. But if you're going to deprecate an old system, you should not seriously degrade the old experience. I'm not even asking for parity --- I'm willing to spend more user actions to get my tasks done. I will follow your wishes and not ping you again on this matter. — hike395 (talk) 15:59, 30 April 2023 (UTC)

As far as I can see, the only issue remaining is slight output differences with coord2text as can be seen at Module talk:Coordinates/testcases. I'll try to fix that soon. Galobtter (talk) 02:19, 1 May 2023 (UTC)

I used the same method of extracting coordinates as Module:Location map, and everything seems to work well now. I honestly don't see any blockers, so I'll put a proposal out soon. Galobtter (talk) 02:53, 2 May 2023 (UTC)

Proposal

Please see Wikipedia:Village pump (proposals)#RfC: Updating Template:Coord to use Kartographer. Galobtter (talk) 06:24, 10 May 2023 (UTC)

Preview page broken

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

Tracked in Phabricator
Task T338204

Hello people,

I just wanted to add that previews of pages with this template show the coordinates as the preview as opposed to the introduction of the article. I've had to remove the template from a few articles in order to resolve this issue, however a more permanent fix would be more ideal. Could the developers of this template look into this issue further?

Thanks. Aydenholtonvlogs (talk) 02:37, 6 June 2023 (UTC)

Always provide links to example pages when reporting a problem. It looks like you removed the coordinates from Regional Representative Council, where they are working fine for me. Please let us know what skin you are using (you can see it in your Preferences) and, ideally, provide a screen shot of the problem. – Jonesey95 (talk) 02:48, 6 June 2023 (UTC)

@Aydenholtonvlogs: Please stop removing the template which is used in 1.3 million pages without any problems reported apart from the above. You have removed coord from Australia (continent) and United Arab Emirates—they need to be restored. Also, this edit removed coord and pp-move-indef. Please do not remove stuff unless you understand its purpose and have good reason to believe that removal is necessary (pp-move-indef is needed in that article). A screenshot of the problem would be desirable but as a first step, please describe what you see with the exact text of whatever the problem is. Johnuniq (talk) 03:13, 6 June 2023 (UTC)

There is an explanation at Module talk:Coordinates#Protected edit request on 29 May 2023. Further discussion should occur there. The problem is that (with scripting enabled and "Enable page previews" selected in Preferences > Appearance), hovering the mouse over a blue link should show a preview of the start of the article, but the text is now showing just the coordinates. Documentation is at mw:Page previews. The problem will be fixed but not by removing the template from 1.3 million articles. Johnuniq (talk) 03:43, 6 June 2023 (UTC)

Sorry. Aydenholtonvlogs (talk) 10:09, 6 June 2023 (UTC)

Previews are broken for me for ITER. I can't find any vandalism. Sungodtemple (talk • contribs) 12:02, 6 June 2023 (UTC)

Discussion at Wikipedia:Village pump (technical) § Page previews (popups) broken

—Trappist the monk (talk) 12:17, 6 June 2023 (UTC)

The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Display coordinates in title without Wikidata

I'm using the template for a fictional place that (obviously) doesn't exist on Wikidata, on my own private MediaWiki installation. How can I get coordinates to display in the title without depending on Wikidata? A diehard editor (talk | edits) 20:37, 27 July 2023 (UTC)

P.S. I've since solved the problem by commenting out the call to makeWikidataCategories() and it works now. A diehard editor (talk | edits) 20:44, 27 July 2023 (UTC)

Coordinates duplicated in the lead (both inside and outside infobox)

Please discuss at Wikipedia_talk:Manual_of_Style/Dates_and_numbers#Coordinates_duplicated_in_the_lead_(both_inside_and_outside_infobox). fgnievinski (talk) 03:16, 13 August 2023 (UTC)

Always show on mobile

Some users want to see it all the time on mobile!

Somebody made a value judgment, that the most important part of a page in my opinion was the least important part of a page in their opinion.

Now mobile users, have to in their browsers, switch to desktop mode, just to get a link to the coordinates, if indeed they can still find it, on the microscopic pages seen in browsers' desktop modes.

And... they also need to dig the "m."out of the URL to get off the mobile site.

All in an effort by the designers to save one line of the users' screens. But that assumes that there's something more valuable on all the other lines of an article, requiring this one line to get sacrificed, for some reason. Jidanni (talk) 17:29, 6 October 2023 (UTC)

"just to get a link to the coordinates" what do you mean ? The only coordinates hidden on mobile are the ones as the page indicator (title mode). Generally however people should be using |display=inline,title exactly for this reason. There isn't enough place to put all information that people might potentially be interested in at the top of an article. It's better to bring examples and then study them to see how the articles can be improved.

"need to dig the "m."out of the URL to get off the mobile site" No they don't, they simply choose the "Desktop view" link at the very bottom of every single page. —TheDJ (talk • contribs) 18:45, 6 October 2023 (UTC)

Date parameters

Since adding OpenHistoricalMap to {{GeoTemplate}} back in 2021, I've found this link to be helpful for navigating to the relevant location in OHM, just as with the OSM link below it, but it would be a lot more useful if it could automatically set the date according some date specified by this template. For example, if a reader follows the {{coord}} link in Heinlenville, then follows the "OpenHistoricalMap" link, OHM should be set to the former neighborhood's coordinates and a time period during which it flourished. This way the reader can see the place in context, rather than merely the memorials to it that exist today.

OHM supports the following URL query parameters, which {{coord}} and {{GeoTemplate}} could plumb through:

date

The map depicts the state of the world as of this date in ISO 8601 format (allowing a missing day or month if unknown), for example, 1903-12-12.

daterange

The time slider's start and end dates separated by a comma, for example, 1887-05-04,1949-05. The reader can click a button to animate the map from the start date to the end date.

{{GeoTemplate}} lists one other map provider that supports date filtering, Old Maps Online:

date_from

Earliest year of results, for example, 1887.

date_to

Latest year of results, for example, 1949.

and one other tool, SunriseSunset.com:

month

Month of the calendar, for example, 5.

year

Year of the calendar, for example, 1949.

There are some additional minor date-sensitive sites if you follow the "more maps" link in the OpenStreetMap row.

Would there be interest in adding date:, start_date:, and end_date: coordinate parameters to this template? I realize it's a bit of an unusual request, since neither WikiMiniAtlas nor any of the other GeoHack-listed map providers is date-sensitive. But Template:Coord#Coordinate parameters cites Wikimaps as the reason for coordinate parameters in the first place, and OHM is the main outcome of the Wikimaps initiative all these years later.

 – Minh Nguyễn ^💬 22:02, 24 October 2023 (UTC)

Question about the "city" parameter

Greetings and felicitations. 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? —DocWatson42 (talk) 07:01, 27 May 2023 (UTC)

Bumping. DocWatson42 (talk) 04:01, 29 October 2023 (UTC)

Page wikidata data used instead of Coord template parameters upon multiple usages in one page

So hard to believe this has been broken, and not fixed, but perhaps this is a new symptom?

In page Tenagra Observatories the infobox mentions two *different* physical locations within the 'same' observatory organization. The infobox uses the {{Coord}} template twice to show the two different locations on maps. Two maps are displayed, but the location red dots are in the same location in both maps.

The parameters in the second {{Coord}} invocation are ignored. It is very suspicious that the wikidata item for the page Q115907980 Tenagra Observatories duplicates the parameters of the first {{Coord}} invocation, and seems to be substituted for the parameters of the second / both {{Coord}} invocations? That is, wikidata parameters are overriding all {{Coord}} invocations in a page.

Mentions of wikidata within Template:Coord documentation include:

• If the coordinates were transcluded from Wikidata, use {{WikidataCoord}}.
• You can get coordinates from Wikidata by transcluding this template without any numbered arguments.
• qid= specify Q item to display the coordinates of. Used primarily by Wikidata powered infoboxes.

But none of these should apply as location arguments are given, qid= is not, and the invocation is {{Coord}}.

Is there an easy way to search for more article pages that use {{Coord}} multiply? To discover whether the problem is uniquely seen in this page?

Is this another instance of wikidata and "two steps forward, one step backward"? Shenme (talk) 03:25, 14 November 2023 (UTC)

I don't think this is a problem with {{coord}}. You might want to post this at the talk page for {{Infobox observatory}}. I believe that I have fixed this problem in {{Infobox observatory/sandbox}}. If you preview Tenagra Observatories using the sandbox version of the template, you should see accurate map pins. – Jonesey95 (talk) 18:25, 14 November 2023 (UTC)

Should this template mark itself with noexcerpt?

Hi there we got a bug report phab:T352706 about page previews not showing for links like Arkansas.

Generally we recommend moving such meta data below the lead section/bottom of the article but another approach would be to add the noexcerpt class to the element per mw:Extension:Popups#How_can_I_remove_content_from_a_page_preview?.

Thanks in advance for your help. Jdlrobson (talk) 23:19, 4 December 2023 (UTC)

@Jdlrobson this continues to be an issue because of Module_talk:Coordinates#Protected_edit_request_on_29_May_2023, further discussion above at #Preview page broken. No one tuned in to what I had to say so no one has done anything. I have now merged that task to phab:T338204 of which it is a duplicate now. Izno (talk) 23:44, 4 December 2023 (UTC)

Appears to be fixed now by Jdlrobson identifying a bug here in the service. If you see someone else report this problem, and it appears to be caused by coordinates, send them here and or ping both of us. Izno (talk) 17:53, 7 December 2023 (UTC)

Blank line before coord

I've seen {{coord}} with and without a blank line before it, and came to the doc to see if there was any guidance on that, but didn't find any, nor did I easily find anything in the talk archives.

So out of curiosity, and my own weird version of fun, I decided to see which format is more prevalent. I got as many mainspace-transcluded pages as I could - 1,000,000. Then, I threw away any pages where no {{coord}} started on a new line - i.e. failed to match \n *{{\s*coord\s*[\|}] (after bypassing all redirects), which left 261,175 pages. Of these:

• 73.6% (192,120) had at least 1 blank line before (i.e. matched \n\s*\n\s*{{\s*coord\s*[\|}]), and
• 26.4% (69,055) did not have a blank line before.

To me, this result makes sense, since {{coord}} is usually sandwiched between navs and DEFAULTSORT/cats, so it doesn't belong abutting either.

So, given the clear preference for a blank line before, and to prevent editors from going back and forth between styles (not that I've looked for, nor seen that, but it's plausible), is it worth adding this to the documentation as (lightly?) suggested usage?   ~ Tom.Reding (talk ⋅dgaf)  19:40, 18 January 2024 (UTC)

@Tom.Reding: MOS:ORDER applies. Normally, coord is used at the bottom of an article, where it should be after all navboxes but before the defaultsort (if there is one) or cats (if there isn't). There may be a blank line before it, after it, or both. Sometimes you'll find a coord in between two navboxes, this often causes a visual gap so the coord should be moved below them. If used at the top of an article (and outside the infobox), there should be no blank lines. --Redrose64 🌹 (talk) 20:37, 18 January 2024 (UTC)

@Redrose64: agreed. I'm interested in addressing the "There may be a blank line before it, after it, or both." part (only when at the bottom of the page, and not displayed inline), and changing it to something like "There should usually be a blank line before it and after it", or weaker, since I'm sure there are some exceptions out there. The vast majority of pages I've seen (conservatively, at least 90%) with {{coord}} on the bottom have a blank line after it, and most of the cases where it's missing are due to it being misplaced nearby, like amongst the navs, or between DEFAULTSORT & cats.   ~ Tom.Reding (talk ⋅dgaf)  21:15, 18 January 2024 (UTC)

Coords get used in tables, lists, infoboxes, and in-line text, where blank lines would usually make no sense. But, even at the bottom of an article, what each of us sees is somewhat different as rendering depends on our device, the size of the window, our chosen skin, preferences, gadgets, and whatever else. So being overly concerned about layout is often a waste of time as others are seeing the rendered article differently in any case. Kerry (talk) 22:12, 18 January 2024 (UTC)

Personally I don't like blank lines in wikicode, but I won't get too bothered — Martin (MSGJ · talk) 22:07, 7 February 2024 (UTC)

Extra parameters, part 2: the exciting one

I also propose a qid parameter to allow the specification of a Wikidata QID for a {{coord}} template.

For most pages the Wikidata QID will be that of the linked Wikidata entity for that page and so the qid parameter would be redundant and should be omitted, but there is one very important case where a QID parameter would be very useful, and that is the use of {{coord}} to refer to multiple, identifiable objects that do not by themselves meet the Wikipedia notability threshold, but do meet Wikidata's criteria for inclusion.

A good example are the lists of listed buildings like Grade I listed buildings in Devon. Each entry in that article refers to an individual building that appears in authoritative databases that make it worthy of a Wikidata entry: linking the {{coord}} for that entry to a corresponding QID provides a way to link these between the Wikipedia and Wikidata domains, opening up the way to closer cross-wiki integration at a later date. — The Anome (talk) 19:10, 7 February 2024 (UTC)

• Support for more wikidata usage & integration.   ~ Tom.Reding (talk ⋅dgaf)  19:41, 7 February 2024 (UTC)

Sounds good. Would it be worth disabling the title display version if the qid does not match the current article's qid? This would avoid misleading or incorrect information. — Martin (MSGJ · talk) 22:04, 7 February 2024 (UTC)

There already is one, isn't there ? 38.895°N 77.0367°W / 38.895; -77.0367 —TheDJ (talk • contribs) 09:22, 8 February 2024 (UTC)

Extra parameters, part 1: dull, but utilitarian

I propose the following extra parameters for {{coord}}: dim, region, and type, to replace the existing string representation of "dim:xxx_region:yyy_type:zzz". This would have the advantage of being easier to use using standard template mechanics, making this metadata useful, for example, for assigning pages to categories.

This has the disadvantage that it might break some off-wiki tools that perform analysis on coord metadata, but changing those tools to the new syntax should be trivial: a matter of changing a couple of regular expressions.

As we move toward closer integration with Wikidata, it would also be useful to tag coord templates with a source parameter. Values for this parameter might be "wikidata", "GNS", "GNIS" or possibly other values. This would initially be purely a tracking parameter, and can be ignored by the template logic, but it provides a place to stash away metadata, and provide a hook for future expansion if need be. — The Anome (talk) 19:10, 7 February 2024 (UTC)

• Support - this seems like a long overdue standardization. The current usage looks very out-of-place compared to the rest of a page's wikitext, and like something pulled from the metadata, and not something editors can relatively intuitively interact with.   ~ Tom.Reding (talk ⋅dgaf)  19:41, 7 February 2024 (UTC)
  • Thanks. Implementing it with a bot would be easy, but the bot will take weeks to complete the run, even at one edit per second. I will try to reach out to the operators of the analysis tools, if I can remember who they are. — The Anome (talk) 20:20, 7 February 2024 (UTC)

Please can you explain dim, region and type for those unfamiliar with the template? — Martin (MSGJ · talk) 22:05, 7 February 2024 (UTC)

@MSGJ: See Template:Coord#dim:D, Template:Coord#region:R and Template:Coord#type:T. Generally, dim is redundant if type is specified, and vice versa. region is independent of both of these. So we might have |type:railwaystation_region:GB-OXF. --Redrose64 🌹 (talk) 21:46, 8 February 2024 (UTC)

lets first introduce the new ones, then deprecated the old one. Also, I think... I or someone else might have already did this once in the sandbox version. possibly for the kartographer variant of the template that was never released ? —TheDJ (talk • contribs) 08:37, 8 February 2024 (UTC)

I think we need to understand what exactly "Coordinate parameters are parameters that {{Coord}} passes to the map server" means. There are more than three such parameters, and all this change seems like a lot-of-work-so-nothing-would-change. The last unnamed param can be parsed by the module, where needed, so I question the usefulness of having separate template params. Ponor (talk) 15:12, 8 February 2024 (UTC)