Module talk:Coordinates

Archives

Examples

//tools.wmflabs.org/geohack/geohack.php?pagename=Module_talk:Coordinates&params=

adding a place name through coordinsert

I have added an additional feature to coordinsert in Module:Coordinates/sandbox to allow for |name= to add a place name. with this addition, {{coord|0.3|0.4|region:US|name=foobar}} is equivalent to {{#invoke:coordinates/sandbox|coordinsert|{{coord|0.3|0.4|region:US}}|name=foobar}}. you can verify this through Special:ExpandTemplates. this feature is only activated when |name= is specified, so it should have zero impact on existing uses. if there are no objections or concerns, I plan to eventually update the live module. this will help migrate Template:Mountain index row to use fully use {{coord}} without having to duplicate the name information in the coordinates call. Frietjes (talk) 13:48, 7 June 2017 (UTC)

no objections after 4 weeks, so now added. Frietjes (talk) 14:16, 5 July 2017 (UTC)

Negative E and negative N coordinates

TheDJ posted a note on my talk page: "

I think there is a bug: with {{coord|45.5039|-73.5876|region:CA|display=inline,title}}: 45°30′14″N 73°35′15″W / 45.5039°N 73.5876°WCoordinates: 45°30′14″N 73°35′15″W / 45.5039°N 73.5876°W

Fatal error: The format of the coordinate could not be determined. Parsing failed.

. This creates a link with -73 East, which is incorrect of course. I also suspect it will call out to the parser function this way and I think that's why coordinates in this format are not in the location database...

" as far as I can tell, the only place where it is incorrect is in the url. I made this change to the sandbox, which appears to fix the problem: 45°30′14″N 73°35′15″W / 45.5039°N 73.5876°W / 45.5039; -73.5876

Fatal error: The format of the coordinate could not be determined. Parsing failed.

. would there be a problem if I were to make the same change to the live template? is there something that I am missing? thank you. Frietjes (talk) 13:59, 19 December 2017 (UTC)

@Frietjes: looks good to me. —TheDJ (talk • contribs) 21:39, 19 December 2017 (UTC)

To summarise:

{{coord|45.5039|-73.5876}} is currently passed to geohack as params=45.5039_N_-73.5876_E
This is odd, as decimal notation usually doesn't specify N/S/W/E unless the values are positive
It also turns out that the parserfunction #coordinates from the GeoData extension doesn't support this format
Geohack however doesn't support passing: params=45.5039_-73.5876
Geohack in this case expects params=45.5039;-73.5876
wikiminiatlas doesn't seem to support params=45.5039;-73.5876

Sigh... so the change Frietjes proposes seems to be the best we can get right now :( —TheDJ (talk • contribs) 15:35, 27 December 2017 (UTC)

Sharing from Open Street Map

I have just been retrospectively trying to find some coords for en: and commons. I can find the building- there is a tab called share- and the side panel tells me that the centre point (my building) is/has geo:51.50161,-0.04668?z=17. Going back to the days of the manframe we were taught to make it simple for the user who is by definition simple- computer power is cheap. So how about letting me paste the text geo:51.50161,-0.04668?z=17 into the first field and let the server translate it into {{coord|51.50161|-0.04668}}. I assume the pseudo code for {{{1}}}} would be on the lines of if {{{1}}}!= text| {{{1}}}}| toreal({{{1:char(5)..char(13)}}}) with a cleanup for the position of the comma. The {{{2}}} field would need to come from {{{1}}} too. This would also allow for the named fields to be added too.ClemRutter (talk) 01:22, 10 January 2018 (UTC)

Convert to indicator

@Dragons flight, Frietjes, Jc86035, TheDJ, and MaxSem: I've implemented <indicator name="coordinates">...</indicator> in this change for phab:T67648. I don't know Lua, so please review. — JJMC89 (T·C) 21:13, 24 March 2018 (UTC)

We will have to prepare new CSS for all skins for this indicator. Not too much of a problem, though sizing is a bit like playing with fire here as it wasn't particularly consistent in the old template (depended on where in the document you added it, and often it was inside font-small markers in the infobox). I have prepped something for Vector.css and monobook.css. It's a little bit bigger this way in almost any instance. However it is more consistent with the font size of the tagline ("From Wikipedia, the free encyclopedia"). opinions. Note that the css has to account for the old styling rules, as due to parser caching both the old and the new will need to live side by side for a while.. (prefix the old with .mw-parser-output class ?) —TheDJ (talk • contribs) 15:34, 26 March 2018 (UTC)