Template_talk:Coord

Template talk:Coord

Template talk:Coord


More information WikiProject Geography To-do list: ...
More information Date, Process ...

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)

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 (talkcontribs) 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)

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)

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 (talkdgaf)  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 (talkdgaf)  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 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 (talkdgaf)  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 (talkcontribs) 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)

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 (talkdgaf)  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.0367TheDJ (talkcontribs) 09:22, 8 February 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)

Share this article:

This article uses material from the Wikipedia article Template_talk:Coord, and is written by contributors. Text is available under a CC BY-SA 4.0 International License; additional terms may apply. Images, videos and audio are available under their respective licenses.