Cannabis Ruderalis

Content deleted Content added
Redrose64 (talk | contribs)
Johnuniq (talk | contribs)
→‎South pole coords: want to NOT show "0°E"
Line 137: Line 137:
Is there a way to make this template display 90°0′S without the E/W component? Listing an ice core drilled at the S pole in [[list of ice cores]] seems to require me to add 0°0′W, though in the sources it's usual to omit the longitude component, for obvious reasons. [[User:Mike Christie|Mike Christie]] ([[User_talk:Mike Christie|talk]] - [[Special:Contributions/Mike_Christie|contribs]] - [[User:Mike Christie/Reference library|library]]) 01:38, 25 April 2017 (UTC)
Is there a way to make this template display 90°0′S without the E/W component? Listing an ice core drilled at the S pole in [[list of ice cores]] seems to require me to add 0°0′W, though in the sources it's usual to omit the longitude component, for obvious reasons. [[User:Mike Christie|Mike Christie]] ([[User_talk:Mike Christie|talk]] - [[Special:Contributions/Mike_Christie|contribs]] - [[User:Mike Christie/Reference library|library]]) 01:38, 25 April 2017 (UTC)
:{{tlx|coord|-90|0}} → {{coord|-90|0}} --[[User:Redrose64|<span style="color:#a80000; background:#ffeeee; text-decoration:inherit">Red</span>rose64]] &#x1f339; ([[User talk:Redrose64|talk]]) 11:07, 25 April 2017 (UTC)
:{{tlx|coord|-90|0}} → {{coord|-90|0}} --[[User:Redrose64|<span style="color:#a80000; background:#ffeeee; text-decoration:inherit">Red</span>rose64]] &#x1f339; ([[User talk:Redrose64|talk]]) 11:07, 25 April 2017 (UTC)
::The request is to ''not'' show "0°E" which does not make sense at a pole. I doubt it can be done, and it may break various processes that scrape coordinates from articles, or may break the link that coord can produce. [[User:Johnuniq|Johnuniq]] ([[User talk:Johnuniq|talk]]) 11:33, 25 April 2017 (UTC)

Revision as of 11:33, 25 April 2017

How to extract longitude degrees from a Coord template?

If you know how to extract the longitude degrees from a {{Coord}} template, please offer some assistance at this discussion. Thanks. – Jonesey95 (talk) 05:33, 24 January 2017 (UTC)[reply]

I responded there, but for anyone who is just reading here we have {{#invoke:coordinates|coord2text|{{Coord|..}}|long}}. Frietjes (talk) 16:01, 24 January 2017 (UTC)[reply]
I have added a section to the documentation too. But having done that it appears the whole /doc is fragile- we have a listing of coordinate parameters but no mention of display parameters. eg |display=inline, title. There seems to be more emphasis on history and deprecated templates than describing usage. I don't like to interfere here- but you know what it is like when you stumble across a page that needs some tender loving care. --ClemRutter (talk) 01:10, 26 January 2017 (UTC)[reply]

Overlay

Hi, It is possible to deactivate the overlay on the WikiMiniAtlas for a specific page. On Ottawa River page the WikiMiniAtlas 100km scale is substituted by the 2km scale of the overlay. thx --YB 15:53, 3 March 2017 (UTC)[reply]

Obviously nobody care about that malfunction ! --YB 20:04, 6 March 2017 (UTC)[reply]
YB, can you not set the scale in the {{coord}}? Frietjes (talk) 23:29, 6 March 2017 (UTC)[reply]
I did but when there is an overlay it is the overlay scale that overwrite. --YB 01:04, 7 March 2017 (UTC)[reply]
YB, try asking at WP:VPT. Frietjes (talk) 13:54, 7 March 2017 (UTC)[reply]

decimal degrees to degrees, minutes, and seconds of arc

I was adding a coord tag to an artical using decimal degrees, however this results in the geohack to linking to the right place on the google map.

I haven't had this issue with degrees, minutes, and seconds of arc, has anyone else had an issue? Back ache (talk) 07:21, 16 March 2017 (UTC)[reply]

@Back ache: I'm guessing that you mean these edits. The main problem is that you have set |W instead of |E - the meridian runs right through Hayes, and positive longitudes are east. But I'm puzzled why you removed the coords from the infobox - in doing so, you have lost several important pieces of information - such as the type, region and scale. You have also gone from four places of decimals to seven, which is very much overprecise - this gives an "accuracy" of just one centimetre. --Redrose64 🌹 (talk) 09:22, 16 March 2017 (UTC)[reply]
@redrose Thanks for looking at that, I agree that the right place should be in the infobox, especially as infobox's are often used by wikidata as a source of scraping.
However, I have been using https://en.m.wikipedia.org/wiki/Special:Nearby and unfortunately unless the CoOrd tage is at the top of the source the geographic information is often ignored by the indexer, with the rise of mobile devices as a way to access wikipedia and microdata as a way to search it, this cannot be ignored Back ache (talk) 11:03, 16 March 2017 (UTC)[reply]
@Back ache: Special:Nearby is something that I've never encountered before. Your comments imply that there is a problem with this utility (if utility it is), and so we should address this by fixing the utility, rather then moving the coordinates out of the infobox. If nothing else, the sheer scale of that task (Wikipedia has over five million articles, over two million of which have infoboxes, although not all of these have coordinates as well) would be prohibitive, and should not be undertaken without discussion. I've started a thread at Wikipedia:Village pump (technical)#Special:Nearby. --Redrose64 🌹 (talk) 11:53, 16 March 2017 (UTC)[reply]
@Redrose64: Our location database (which is feeding the results of Special:Nearby and other forms of our maps), by default only queries the primary coordinates of pages (title coordinates). Title coordinates are usually visible at the top right of a page, and the older revision of Back ache's case already produces them. The solution for an infobox that doesn't produce title coordinates, is to check if that infobox has a parameter like coordinates_display, which {{Infobox UK school}} has, or fix the infobox to support controls like that. There was no need to move the coordinates here. —TheDJ (talk • contribs) 12:28, 16 March 2017 (UTC)[reply]
@TheDJ: That isn't what I've been finding, I've moved to a new job and used Special:Nearby to see whats around, what I have found is pages with coordinates arn't being listed till I move the CoOrd tag to the top of the source.Back ache (talk) 12:33, 16 March 2017 (UTC)[reply]
@Back ache: Then that is a problem that should be reported, not something that the content should be adapted to. (Adapting content to match a software problem should always be the last resort, after having checked that it is in fact the correct solution). —TheDJ (talk • contribs) 12:37, 16 March 2017 (UTC)[reply]
@TheDJ: The version as it stood prior to Back ache's edits did have title coordinates. --Redrose64 🌹 (talk) 12:36, 16 March 2017 (UTC)[reply]

Example for a page with Template:Infobox UK School, which is registered in our coordinates database correctly: Paul's School, London. If that doesn't show up in Special:Nearby, then something else is going wrong. —TheDJ (talk • contribs) 12:44, 16 March 2017 (UTC)[reply]

And this is the query that retrieves all coordinates around the coordinates of Hayes School. link. This matches what Special:Nearby would request. —TheDJ (talk • contribs) 13:07, 16 March 2017 (UTC)[reply]


@TheDJ: and yet, this morning when used special:nearby in Hayes this morning the school wasn't listed, hence my editing. For now I'll only alter articles that have coords tags (and move them to the top) once I can build a good test case I'll raise a bug. I really like the idea of geographically enabling wikipedia.— Preceding unsigned comment added by Back ache (talk • contribs) 14:51, 16 March 2017 (UTC)[reply]

I think this thread has over-complicated things. The problem here is that the only way to tell Template:Coord to mark coordinates through the #coordinate magic word as primary is to position them near the title of the article (e.g. display=title). In my opinion the solution is as easy as just allowing users to specify themselves if the primary tag should be used or not. So, I would like to propose that an new argument is added, called "primary" and if an translusion mentions "primary=yes" then it is marked as primary. I would keep "display=title" being marked as primary, just so that thousands of articles do not need to be edited. The #coordinates magic word itself has an error if there are several primary coordinates on an page and an tracking category, so this template does not need to track that.--Snaevar (talk) 19:54, 18 March 2017 (UTC)[reply]

That sounds like a good idea, special nearby seems to be missing a lot of geocodes in infoboxs just in my local area, so I assume it's a wider issue Back ache (talk) 00:33, 22 March 2017 (UTC)[reply]

Enard Bay

Hi can anybody provide help regarding Enard Bay. I'm having problems with setting the coords in the Infobox:body of water. Any help would be appreciated. It's coming back with the Lua exception error: 58°05′45.0240″N -5°20′11.0688″E Coordinates: longitude degrees < 0 with hemisphere flag Invalid arguments have been passed to the {{#coordinates:}} function: invalid longitude scope_creep (talk) 12:13, 26 March 2017 (UTC)::[reply]

Fixed it. It was the formatting. Copied the infobox from a Russian page and it was set to wrong locale scope_creep (talk) 12:22, 26 March 2017 (UTC)[reply]

Decimal vs. degrees/minutes/seconds

I'm starting to construct a list article, and am finding the coordinates for the locations involved expressed in both decimal form (41.289°S 174.777°E) and degree/minute/second form (57°18′22″N 4°27′32″W). Given that I'm going to have to convert some of them, is there any reason to prefer one form over another? Is there any advantage to a reader, or to other software that might want to make use of the data? Mike Christie (talk - contribs - library) 09:57, 5 April 2017 (UTC)[reply]

One very minor point: a minute of latitude is one nautical mile, so using degrees and minutes makes distance estimation easier. Martin of Sheffield (talk) 11:39, 5 April 2017 (UTC)[reply]
There is a Wikipedia-centric reason to prefer decimal degrees over degrees-minutes-seconds (DMS). Most people would write the first DMS angle Mike Christie wrote as 57°18'22" because it only contains one symbol not found on the typical keyboard. Presumably there is a great deal of software expecting the use of the quote and double quote characters. But strictly speaking it should be written as 57°18′22″ (57°18&prime;22&Prime; in the wikitext editor) because the correct symbols for prime and double prime are different from quote and double quote. The wikitext editor can be configured in various ways; the default configuration provides the ′ and ″ symbols below the edit window, but not all configurations do. Heaven only knows if the visual editor supports those characters.
Then there are lots of gnomes who write bots to "correct" things so whatever minute or second symbol an editor writes is likely to get changed to something "better" by a bot. Jc3s5h (talk) 13:47, 5 April 2017 (UTC)[reply]
If you use the {{coord}} template (e.g. 41°17′20″S 174°46′37″E / 41.289°S 174.777°E / -41.289; 174.777 or 41°17′20″S 174°46′37″E / 41.289°S 174.777°E / -41.289; 174.777), you won't have to worry about the prime symbols or do any math. The template will construct the prime symbols for you and do the conversions. That way, the prime symbols won't get "corrected" to straight quotes by well-meaning gnomes, and it will be easy to change the format with a find and replace if a talk page discussion settles on the other format. – Jonesey95 (talk) 14:39, 5 April 2017 (UTC)[reply]
Just to "throw a spanner in the works", be aware that degrees and decimal minutes are used in some contexts. For instance the following was abstracted from a nautical chart correction notice: "Insert restricted area line joining: 51°28’·11N 1°03’·19E ...". Martin of Sheffield (talk) 14:52, 5 April 2017 (UTC)[reply]
Unless there is some guideline that specifically precludes this, one solution to the problem is to allow both formats in the list. Messy inconsistency may be the lesser of various evils in this case. If we could agree on "any reason to prefer one form over another", we would probably have a house default format. My personal preference is decimal for various reasons, FWIW. ―Mandruss  15:29, 5 April 2017 (UTC)[reply]

Thanks for the various responses. Jc3s5h, the symbols I pasted in were copied from the example under "Quick how to" at Template:Coord, so I'm surprised that they include an apostrophe, and not a prime. Yes, I think VE does include the prime; it seems to include most characters I've ever found a need for, though since I'll be generating these coordinates via the template I won't actually need the prime.

I'll use the dms; as pointed out above, it's an easy search-and-replace change to make it dec if needed. Thanks. Mike Christie (talk - contribs - library) 22:23, 5 April 2017 (UTC)[reply]

Type for 4th-level admin unit

A civil parish in England, such as Allithwaite Upper or Kirklinton Middle, is listed in List of administrative divisions by country as a 4th-level admin unit. So what "Type" do we use for its coords? Does it count as "City"? PamD 06:29, 20 April 2017 (UTC)[reply]

@PamD: It says "cities, towns, villages, hamlets, suburbs, subdivisions, neighborhoods, and other human settlements" so yes. --Redrose64 🌹 (talk) 08:58, 20 April 2017 (UTC)[reply]

Icon position error

 – Jonesey95 (talk) 14:48, 23 April 2017 (UTC)[reply]

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.


I noticed that the position of the airplane icon (the "pushpin_mark" graphic) is misleading in the Joint Base Anacostia–Bolling article. It appears at the tip of Greenleaf Point, even though the coordinates for JBAB appear to be correct in the template. Clicking on the Coordinates text in the article as displayed shows the correct location about a mile south of Greenleaf Point. At first I thought this error was related to the fact that the pushpin label wraps across three lines, but reducing the label to one line doesn't solve the problem. So I don't know how to fix the problem, but it seems to be real enough. 76.22.118.146 (talk) 02:00, 23 April 2017 (UTC)[reply]

JB Anacostia–Bolling is located in the District of Columbia
JB Anacostia–Bolling
JB Anacostia–Bolling
See the pushpin map at right. Is the aeroplane icon displayed in the correct position here? If it is, there is some sort of problem in extracting coordinate values from {{Coord|38|50|34|N|077|00|58|W|name=JB Anacostia–Bolling|display=inline,title}} but if it is also wrong, the problem is nothing to do with {{coord}} but concerns {{Location map}}, and is most likely to be the corner coordinates that are recorded at Template:Location map USA District of Columbia. The best place to discuss that is at Module talk:Location map. --Redrose64 🌹 (talk) 08:53, 23 April 2017 (UTC)[reply]
JB Anacostia–Bolling is located in the District of Columbia
JB Anacostia–Bolling
JB Anacostia–Bolling
Replacing the map name with "Washington, DC" works for some reason, even though the location map in question appears to be a redirect. I must be looking in the wrong place for the map that is used. – Jonesey95 (talk) 14:44, 23 April 2017 (UTC)[reply]
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.

South pole coords

Is there a way to make this template display 90°0′S without the E/W component? Listing an ice core drilled at the S pole in list of ice cores seems to require me to add 0°0′W, though in the sources it's usual to omit the longitude component, for obvious reasons. Mike Christie (talk - contribs - library) 01:38, 25 April 2017 (UTC)[reply]

{{coord|-90|0}}90°S 0°E / 90°S 0°E / -90; 0 --Redrose64 🌹 (talk) 11:07, 25 April 2017 (UTC)[reply]
The request is to not show "0°E" which does not make sense at a pole. I doubt it can be done, and it may break various processes that scrape coordinates from articles, or may break the link that coord can produce. Johnuniq (talk) 11:33, 25 April 2017 (UTC)[reply]

Leave a Reply