Template talk:Coord/Archive 1

message: I believe this template will be difficult to maintain because the meanings of positional parameters change from one "overload" to the next. --Kevinkor2 18:12, 31 March 2007 (UTC)
replies: text: Please can you explain your concerns in more detail and - if possible - suggest solutions? Thank you. Andy Mabbett 18:31, 31 March 2007 (UTC)
replies: text: Sorry about that. I was trying to debug  and I thought part of the problem was positional arguments with #if. --Kevinkor2 12:55, 6 April 2007 (UTC)

text: OK, no worries. Thank you. Andy Mabbett 13:24, 6 April 2007 (UTC)
thread_title: Maintainability

message: The page Great Barr uses decimal values, to three decimal places:  - an accuracy of ~100m. However, the page displays 52°32′52.8″ N 1°55′55.2″ W - accuracy to ~3m. Whatever is doing the calculating (is it this template, or somewhere else?) needs to do some rounding. Andy Mabbett 17:12, 3 April 2007 (UTC)
replies: text: Thanks, addressed below. —Quarl (talk) 2007-04-04 11:41Z
* Why does the coord template assume that all coordinates should be converted to Degrees/Minutes/Seconds? The coor templates allowed users to decide how they wanted to display the coordinates, according to what was appropriate to the article: articles documenting a region may want to just display an integer degree value, with no minutes or seconds displayed, which appears to be impossible with the coord template. --Ozhiker 17:20, 3 April 2007 (UTC)
thread_title: Inappropriate precision and Coordinate Display/Conversion

message: In coord, the decimal values are hidden by ; if we also wrap the DMS values in a class, say , then, by tweaking their local style sheets, users could choose to display or hide either or both. Andy Mabbett 20:36, 3 April 2007 (UTC)
thread_title: Display preferences

message: I created a copy of List of impact craters on Earth, at User:Pigsonthewing/scratchpad, using coord. It breaks halfway down the second table. Perhaps the cause is the total number of template calls. I've sub-divided the original page and substituted coord;  I'll leave the long, broken version on my user page. Andy Mabbett 14:11, 6 April 2007 (UTC)
thread_title: Bug: breaks with many instances 

message: How will parsers deal with pages which have more then one ? For example, Ridge Route, List of impact craters on Earth. Andy Mabbett 11:41, 6 April 2007 (UTC)
replies: text: So do we know if Google Earth understands coord yet? Amake 07:37, 16 April 2007 (UTC)
replies: text: No - I've been waiting on Gmaxwell. Andy Mabbett 11:36, 16 April 2007 (UTC)
replies: text: Could someone also tell the Google people to enable parsing of Infobox templates? Currently GoogleEarth doesn't seem to capture coordinates from them (e.g. Infobox Town). This leads to the somewhat absurd situation that in some cases stubs (suburbs) show up and fully fleshed out articles (main city) don't. 80.129.120.188 21:52, 11 May 2007 (UTC)
replies: text: Actually according to this site, Google does parse Infobox templates, but only if the coordinate info is labeled with the keywords "coordinates" or "coords".  I was encountering the same problem as you with the :Template:Infobox City Japan, but we (hopefully) solved it by changing the "coord" keyword to "coords".  Unfortunately Google hasn't updated the Wikipedia layer lately, so I don't know if it's actually fixed.  Amake 12:29, 23 May 2007 (UTC)
replies: text: I don't think Google does anything with Infobox templates themselves, they just search the wikitext for coor title d[ms], coor at d[ms] and coor d[ms]. The first two are special because the given coordinate applies to the whole article, which is why we place it at the top as well. A lonely inline coor d[ms] is not important and isn't visualized, unless it's used with a coordinate parameter in an infobox, which in turn makes it apply to the whole article. Note that currently coordinates given with the coord template are not shown at all. Google's updates follow the database dumps, which unfortunately with the English Wikipedia don't happen very ofen. And yes, the Infobox City Japan change looks fine. --Para 23:34, 23 May 2007 (UTC)

text: Couldn't the information in the infoboxes be entered in the format given by the Manual of Style? I don't see much reason in having to give each number in a separate variable, as the information is mostly static anyway. Perhaps I'm overlooking something? --Para 09:51, 23 May 2007 (UTC)
thread_title: Wikicode parsers

message: See: Google_Earth#Wikipedia_and_Panoramio_mashup and Google's documentation. Andy Mabbett 13:02, 5 April 2007 (UTC)
replies: text: So do we know if Google Earth understands coord yet? Amake 07:37, 16 April 2007 (UTC)
replies: text: No - I've been waiting on Gmaxwell. Andy Mabbett 11:36, 16 April 2007 (UTC)
replies: text: Could someone also tell the Google people to enable parsing of Infobox templates? Currently GoogleEarth doesn't seem to capture coordinates from them (e.g. Infobox Town). This leads to the somewhat absurd situation that in some cases stubs (suburbs) show up and fully fleshed out articles (main city) don't. 80.129.120.188 21:52, 11 May 2007 (UTC)
replies: text: Actually according to this site, Google does parse Infobox templates, but only if the coordinate info is labeled with the keywords "coordinates" or "coords".  I was encountering the same problem as you with the :Template:Infobox City Japan, but we (hopefully) solved it by changing the "coord" keyword to "coords".  Unfortunately Google hasn't updated the Wikipedia layer lately, so I don't know if it's actually fixed.  Amake 12:29, 23 May 2007 (UTC)
replies: text: I don't think Google does anything with Infobox templates themselves, they just search the wikitext for coor title d[ms], coor at d[ms] and coor d[ms]. The first two are special because the given coordinate applies to the whole article, which is why we place it at the top as well. A lonely inline coor d[ms] is not important and isn't visualized, unless it's used with a coordinate parameter in an infobox, which in turn makes it apply to the whole article. Note that currently coordinates given with the coord template are not shown at all. Google's updates follow the database dumps, which unfortunately with the English Wikipedia don't happen very ofen. And yes, the Infobox City Japan change looks fine. --Para 23:34, 23 May 2007 (UTC)

text: Couldn't the information in the infoboxes be entered in the format given by the Manual of Style? I don't see much reason in having to give each number in a separate variable, as the information is mostly static anyway. Perhaps I'm overlooking something? --Para 09:51, 23 May 2007 (UTC)
thread_title: Google Earth mashup

message: The new display named parameter adds  and  functionality. display can be inline (default, same as before), title, and inline,title.
Examples:
Replaces 
Replaces 
 or Replaces 
—Quarl (talk) 2007-04-07 07:09Z
:Quarl, thanks again for some superb work! My test page now has 200 working examples. Andy Mabbett 07:21, 7 April 2007 (UTC)
thread_title:  New ''display'' parameter 

message: I've just done a big archive. Some of the material was fairly recent, but superseded by Quarl's latest edits. Andy Mabbett 07:21, 7 April 2007 (UTC)
thread_title: Archive

message:  (DM;DMS) gives: 
Unknown format in . Parameters:
1=36
2=46
3=N
4=118
5=49
6=20
7=W
8=
9=Invalid arguments have been passed to the  function
Andy Mabbett 20:46, 7 April 2007 (UTC)
replies: text: Interesting case.  When would one want to use mixed precision, and what behavior would we want? —Quarl (talk) 2007-04-08 04:33Z
On the page where I found that, I added a "0 seconds", since that was what I thought was implied. Perhasp a job for the conversion bot? Andy Mabbett 08:17, 8 April 2007 (UTC)
thread_title: Bug: poor handling of mis-matched lat/long precision

message: Changing the "display both" output (for example):
:32°18′19″S 115°41′28″E (-32.30528, 115.69111)
to:
:32°18′19″S 115°41′28″E / -32.30528, 115.69111
would mean that there was one less span in the mark-up (reducing file sizes for long lists of coordinates, some of which have over 200 entries) and would look better when the template is already in brackets, like:
:()
::Andy Mabbett 18:51, 8 April 2007 (UTC)
replies: text: Thank you. That looks much better. Andy Mabbett 08:22, 12 April 2007 (UTC)
thread_title:  Suggested improvement 

message: I've been contemplating different possibilities for "wrapping" the output of coord in an hCard microformat. One would be to have a "scope-page" attribute:
:
which included  in the output, hidden by CSS by default.
Another would be a separate hCard template, which called coord if coordinates were present.
Thoughts? Andy Mabbett 13:27, 18 April 2007 (UTC)
replies: text: Is an hCard really appropriate for every instance of coordinates? If not, suresly a separate template would be most appropriate. JPD (talk) 14:20, 18 April 2007 (UTC)
replies: text: No, though most do; especially those which apply the subject of an article page. I don't see how your latter point follows from that, though. Andy Mabbett 14:27, 18 April 2007 (UTC)
replies: text: I'm not sure if I understand completely what it is Andy is contemplating but I'll describe a situation which I believe could be related to this discussion. I've recently added the coord template to Template:Infobox UK station within "fn org" classes. Using the Operator add on for Firefox, this shows up in the drop down "Find with Google Maps" list as , e.g. Huddersfield. I think it would be more desirable to use the  variable to display the page name in the list, e.g. Huddersfield railway station. However, the pagename would want to be hidden of course. I think this is what Andy is discussing and would like to find a way to do it. Adambro 14:41, 18 April 2007 (UTC)
replies: text: That would indeed be good - but hadn't occurred to me! I was thinking, for example, of  yoru recent addition of coord to Huddersfield New College, where the extra parameter would have generated an hCard, with the page name as the "fn org" (i.e. name) attribute, not just a Geo. Andy Mabbett 14:49, 18 April 2007 (UTC)

text: (edit conflict)That could be a good thing to do with , but I don't really see why it should be part of this template. As I understand it, what you have done is not so much "added the coord template to Template:Infobox UK station within "fn org" classes", as added both the coord template and "fn org" classes, wrapped in an hCard microformat. As the coords are just part of an hCard (perhaps more relevant than the fact that they don't always belong in one), it seems logical to call coord from an hCard template, rather than incorporate the hCard in the coord template, whether or not  is used. JPD (talk) 15:07, 18 April 2007 (UTC)
thread_title: Adding hCard wrapper

message: could we add an additional optional parameter specifying altitude? do we have any "4d" geo-template where you could also encode speed, heading and datestamps, and possibly define "polygons", e.g. to trace roads, rivers or historical voyages? dab (𒁳) 13:16, 20 April 2007 (UTC)
thread_title: altitude

message: In the help:

it would be: "  Toronto - decimal with Northing & Westing"
but the output is:
43.651234, -79.383333
without N W --WISo 12:18, 26 April 2007 (UTC)
replies: text: The "help" is correct - it describes the input, and demonstrates the output. Andy Mabbett 13:21, 26 April 2007 (UTC)
replies: text:  The help page says: "parameters, which are optional, can be any type:, region:, or scale: setting which is recognised by the map server, such as the popular type:city and type:landmark options..." but doesn't say nothing about the format parameters, there are only two example. --WISo 14:44, 26 April 2007 (UTC)
thread_title:  Bug: display N/W/E/S 

message: The logic is that: ±½' of latitude (±½ Nautical Miles exactly) is approx ±1013 yards (exactly ±926m ≈ ±1km)
Traditionally Ship/Aircraft navigators used their divider's distance between the latitude lines as their unit of measure, i.e. 1 Nautical Mile.
Given the size of Barents Sea, ±1km seems reasonable. :-)
Could we also have a note somewhere extolling the virtues of using the Degree/Minute format (d°m′N d°m′W) for anything bigger then a ship?
(This - as a consequence - becomes a great aid in mentally estimating distances between two objects.)
Is there a best location for such a note?
(OT: another useful conversion is: 2 knots ≈ 1.03m/s, esp for estimating wind speed)
NevilleDNZ 01:12, 29 April 2007 (UTC)
replies: text: Precision is discussed at WP:GEO. Andy Mabbett 05:09, 29 April 2007 (UTC)
replies: text: ThanX NevilleDNZ 06:06, 29 April 2007 (UTC)
thread_title:  Changed location of Barents Sea from (71°55′49″N, 41°20′49″E) to (71°56′N, 41°21′E) 

message: Please add :Category:Templates generating Geo. Thank you. Andy Mabbett 22:30, 10 May 2007 (UTC)
replies: text: You can put that in the doc page inside <includeonly>. CMummert · talk 01:06, 11 May 2007 (UTC)
replies: text:  I already tried to edit the doc, but it says "This page is currently protected from editing because it is transcluded in the following pages, which are protected with the "cascading" option enabled: Template:Coord".  I'm not sure why the cascading option needs to be enabled here . . .   --Seattle Skier (talk) 01:25, 11 May 2007 (UTC)
replies: text: You should have let me know. I went through and protected all the subpages individually as appropriate, so now the docs should be unprotected. CMummert · talk 02:09, 11 May 2007 (UTC)
replies: text:  OK.  I just saw this page on my watchlist and tried to help out, but couldn't.  I've added :Category:Templates generating Geo to /doc now.  --Seattle Skier (talk) 02:18, 11 May 2007 (UTC)
replies: text:  Thanks. I thought you were Andy Mabbett when I said you should have let me know about the protection. Sorry about the confusion. CMummert · talk 02:59, 11 May 2007 (UTC)
thread_title:  New category