This is an archive of past discussions about Template:Track gauge. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page.
I propose to remove the 783 mm gauge from the definitons list. As the sourcing article HOn30_gauge explains, this is just a theoretical (prototype) gauge. Such a theoretical gauge is the reaul of a calculation of model gauge ⁄ model scale (the reversed way). -DePiep (talk) 19:45, 16 August 2017 (UTC)
"theoretical prototype gauge" explained
1. Regular determination of a model gauge is as follows (prototype gauge = real life gauge):
With OO scale being 1:76, we find prototype gauge:
4 ft 1+1⁄2 in (1,257 mm) × 1:76.2 = 16.5 mm model gauge
Since the 4 ft 1 1⁄2 in gauge exists in RL, this is OK. (so the modeling uses two scales, which both result in gauge-fitting rolling stock, but they'll look unnaturally different when riding with each other on the same model track).
3. However, the reverse-calculation can also lead to a non-existing gauge:
H0e scale is 1:87, defined as 9 mm model gauge (from prototype 760 mm, rounded toward the definition).
Actual prototype would be:
? prototype × 1:87 = 9 mm
783 mm × 1:87 = 9 mm
That prototype does not exist in real life, so it is theoretical only. Therefor it should be deleted from the list of definitions. (There are dozens of model gauges & scales to combine that would lead to multiple dozens of such theoretical gauges). -DePiep (talk) 09:20, 19 August 2017 (UTC)
Even better would be to move the four foot coverage from "narrow gauge" to standard gauge. The early 4' and 4'6" railways weren't a "narrow gauge", they were simply a lack of agreement this early as to what the "standard" would become. Their history is more closely related to early railways than to the two-decade-later beginnings of a deliberately-narrowed loco-hauled edge-railway. Andy Dingley (talk) 08:01, 19 August 201
I can understand this moving it out of 'narrow gauge'. However, I don't think it should be in standard gauge, because it is not related to it (unlike, for example, near-s.g. tracks that are actually connected to true s.g. somehow). New grouping article like "Non-narrow-gauge narrow gauges" needed? (well, something more serious then but you get the idea). -DePiep (talk) 08:45, 19 August 2017 (UTC)
BTW, {{Track gauge}} itself does not use the "narrow gauge", "s.g.", "broad gauge" classifications at all. (The documentation only has rough assumption, internally). So if the 1200 mm sourced definition is moved to an other article, {{Track gauge}} will follow by changing the link. The move Andy mentiones (out of "narrow gauge" class) is relevant for content articles & categories. Better discuss there, or at WT:TRAINS? -DePiep (talk) 08:50, 19 August 2017 (UTC)
Yes, Peter Horn. The template is complicated & sensitive (for wrong data), so it is protected. But as you know from this talkpage, all proposals are discussed very seriously. When a discussion concludes, the template will be changed (by me, often). Peter, this is why this enwiki list of well-defined track gauges is so very great & stable & trustworthy & well-sourced. And of course, you are one of those who contributed heavily to that greatness. -DePiep (talk) 20:42, 19 August 2017 (UTC)
I don't know. Never in Wikipedia we say: "the author must have read it somewhere" as a WP:RELYABLESOURCE. It is simple: someone could make a talkpage request at that dewiki talkpage. Must say: I am only maintaining {{Track gauge}}, not providing all its 250+ sources. -DePiep (talk) 22:46, 19 August 2017 (UTC)
Defined in source: Johnson, Peter (2011). An Illustrated History of the Great Western Narrow Gauge. Oxford Publishing Co.
Currently in sandbox: 2 ft 2.5 in
Conclusion:
References
This gauge seems to be sourced (cannot check), but by saying it was proposed, not build. No need to add to the list then, just use {{Convert}}. -DePiep (talk) 13:59, 8 September 2017 (UTC)
Following on to this, it's quite right that this was a proposed gauge for the Corris Railway which was actually built to 2 ft 3 in (686 mm) gauge. But I think there were a small number of industrial railways n the UK that did use this gauge - particularly underground in coal mines. Let me see if I can confirm and source that. If my recollection is correct, then it might be worth adding this gauge to the template. Railfan23 (talk) 22:50, 9 September 2017 (UTC)
Yes, when sourced there sure will be an article that should have that gauge + source (maybe a list), and then it can be added to the template. -DePiep (talk) 15:50, 22 September 2017 (UTC)
1065 mm in South Africa (not 1067 mm, from 3 1/2 ft)
Note: Rounded from 3 ft 6 in (1,067 mm). Formal in South Africa. Output|allk=on will yield gauge name Cape gauge. However, input {{track gauge|Cape gauge}} will yield the original imperial definition: 3 ft 6 in (1,067 mm) Cape gauge.
It appears that "1065 mm" (in metric) is the formal gauge in South Africa. So Cape Gauge has two sizes (like Russian gauge). -DePiep (talk) 19:52, 9 December 2017 (UTC)
We want to link to an article that has the source (reference) for a gauge definition. When multiple articles apply, of course we use the first/original/institutional definition article.
wrt changing to Killingworth Colliery railway: that link has some issues. The section it Redirects to has one dead link, and the actual source for this gauge is a book (I can not check). IMO this is a bit below standard ;-). If someone could shape it up, check & fix sources, use {{Cite}} nicely, replace "world famous" with the reason of this being famous, maybe make it a stand-alone article (stub), wouldn't that be inviting? Of course the essence (being the origin of s.g.) is huge. - DePiep (talk) 10:09, 15 April 2018 (UTC)
I was recently browsing some pages on rolling stock in New South Wales, Australia when I noticed that the decimal place indicator was a comma in the Guage field of the train Infobox, while length, width, and height use a dot. This struck me as inconsistent.
Is there any reason why this is so? Could this be made more consistent?
JonsterMonster (talk) 22:23, 9 July 2018 (UTC)
You mean like in 1,000 mm (3 ft 3+3⁄8 in)? This is the thousands-separator, described in MOS:DIGITS. A decimal point is used in 0.256 in (6.5 mm). Which article(s) were you looking at?
I don't know. Never in Wikipedia we say: "the author must have read it somewhere" as a WP:RELYABLESOURCE. It is simple: someone could make a talkpage request at that dewiki talkpage. Must say: I am only maintaining {{Track gauge}}, not providing all its 250+ sources. -DePiep (talk) 22:46, 19 August 2017 (UTC)
Note: Unique gauge (so far); see comment on source quelity
Conclusion:
References
Source does mention it, but why would a company start a new gauge (*next to existing, common gauges)? Could it nbbe the source was sloppy? See also 12+5⁄8 in (321 mm) - DePiep (talk) 10:38, 15 April 2018 (UTC)
This is an unique gauge (nowhere else used or mentioned). The source here is The Railway Age, July 1, 1898., which indeed mentions that gauge. However, it is strange that for this one track (6 locomotives) the company would create a new gauge, while they also build the common 12+5⁄8 in (321 mm) (of 1⁄8 inch difference). In other words, it may very well be that the 12+1⁄2 in the source is a miswriting.
Looking at {{Convert}}. The / slash is not available by default, but can be used:
{{convert|5|ft|6|in|mm|abbr=on|disp=x|/}} → 5 ft 6 in/1,680 mm
However, you may have a point. Would thin space help?
5 ft 6 in/1,676 mm
5 ft 6 in / 1,676 mm
5 ft 6 in / 1,676 mm
(not the best way to compare, better inline. Anyway, I'd definitiely make the first space NBSP, so that a linebreakl may occur after the slash). -DePiep (talk) 16:22, 9 January 2019 (UTC)
{{Track gauge}} does not use Convert internally, all gauge values are hardcoded in the list (the ~275 gauges × 2 metric/imperial), and internally formatted stealing from Convert. I'm looking at Convert because it is good to keep similar formatting &tc.
Asking Johnuniq for input here, especially for the visual/typographical aspect you mention. (There might be older considerations I'm not aware of). -DePiep (talk) 16:46, 9 January 2019 (UTC)
In convert, |disp=slash was removed in November 2014. That link shows an example of how it looked before removal: "55 miles / 89 kilometres" with a non-breaking space before the slash. Convert still allows a slash in a range as requested for high/low temperature ranges which is apparently standard for weather reports (September 2016). In case it's of interest, following is an example showing the exact wikitext output by convert for 83 / 63 °F (28 / 17 °C):
That no-slash discussion is here in the Convert Archives. Problematic situation is "570 mph/917 km/h; 495 kn". In track gauge, the "km/h" does not occur, but double-meaning of slash does: "2 ft 1⁄8 in/613 mm".
While we allow the slash value-separator in {{Track gauge}}, we better add spaces to strengthen the right visual grouping:
Please find articles that actually use these gauges, and sources with them. We do not add rare gagues to the list that are not sourced. -DePiep (talk) 04:36, 6 February 2019 (UTC)
Peter Horn, these are all redlinks or unspecified. You just dumped a mess and walked away. What do you expect from others? Cooperation? Improvement? Clean up your chaos? I've had enough of this commanding attitide.
Let me tell you how to use this talkpage. The point of a talkpage, any talkpage, is that you can ask a question or propose something. On this very talkpage, that would be a sentence like: "I propose to add gauge xyz, as used in article [[Pqr]] and sourced as a defined track gauge in [...]. That is how it works, that's how wikipedia works, and that's what I've asked you here for years. Still you come here dumping loads of work for others to research & check & cleanup without the least care or info or behaviour input. I strongly suggest you rewrite your post into something constructive. -DePiep (talk) 06:25, 6 February 2019 (UTC)
As for the "red links", may be we could invite NE2 to research and write the pertinent articles, since he appears to be the one who has access to all those reference volumes. I don't have access to them. Peter HornUser talk14:37, 6 February 2019 (UTC)
What's your point here? Two of these are hugely well known gauges. The others (in the main) are already in the template. So what are you asking to be changed in this template? 5'9" is the only one I can see that isn't. Most of the others, they're a recognised gauge already but you've added some unlinked changed version of it - what's that about? Andy Dingley (talk) 14:59, 6 February 2019 (UTC)
Thanks Peter. Will take a look later on. Let's add a gauge per source (which track gauge is in which source?). -DePiep (talk) 15:02, 6 February 2019 (UTC)
To be clear: we are looking for the combination: gauge -- article -- source. (de:Liste_der_Spurweiten might help, but note dewiki does convert to mm always while we keep the original unit being imperial or metric). -DePiep (talk) 10:30, 7 February 2019 (UTC)
At least one UK quarry used 2 ft 3+1⁄2 in (699 mm). This was Boon's Granite Quarries near Nuneaton.[12] I know nothing of the quarry, but they were the first customer, in 1929, for Kerr Stuart's widely-used DX-1 contractor's loco. These had a 30 hp McLaren petrol engine and the first had a Robertson CVT. They're in Webb's book, Webb, Brian (1973). The British Internal Combustion Locomotive, 1894-1940. David & Charles. p. 62. ISBN0715361155. {{cite book}}: Invalid |ref=harv (help) User:Andy Dingley 12:29, 16 September 2019 (UTC)
According to Frank Jux's KS Locomotive Works List (Industrial Locomotive Society 1991) this would be KS4422 of 9/1929 "Basset Green" User:RGCorris 13:26, 16 September 2019 (UTC)
Probably because making a change to a subpage of a module, where you can't see the effect without taking a leap in the dark, isn't an easy or comfortable choice.
No re 'probably becasue'. TE editors did not work following the queu, they obviosly skipped the easy ones. Is what I asked about. -DePiep (talk) 00:42, 8 October 2019 (UTC)
Obviously your perception of what is easy differs from the perception of the TEs who skipped your request. Your expectation that requests will be handled in a specific order is not realistic and, as far as I'm aware, doesn't apply to any queue on the wiki. Cabayi (talk) 09:55, 8 October 2019 (UTC)
I wrote "easy" because the requested edit did not invoke further questions or research by any TE. As for "leap in the dark": it was tested. wrt the order: except that one could expect older requests may be looked at first. All in all this is what caused my question. -DePiep (talk) 10:12, 8 October 2019 (UTC)
I think we've had this discussion before. I accept you've tested it to your satisfaction, that you're a competent template editor. BUT... Where could I see the effect tested? Where in your request did you point to any testing for me to validate the change for myself before making it? Cabayi (talk) 10:51, 8 October 2019 (UTC)
The consensus section I linked to has a box saying "Currently in sandbox: 2 ft 3 1⁄2 in (699 mm)". Anyway, if such testing were an issue for TE's passing by, why not simply ask for it? The primary requirementrs are: showing consensus, and be clear about the change— both were served here IMO. wrt your reference to an earlier discussion we had: that was about a different issue in an edit request. No reason and even not helping cxlarification to turn to that full stop. -DePiep (talk) 11:06, 8 October 2019 (UTC)
The engineering-timelines.com source, from the article, says: "The tracks are of bullhead rails set at 1.14m (3ft 9in) gauge, ...". -DePiep (talk) 08:22, 8 October 2019 (UTC)
I have copies of several Cassier's Magazines myself, but after some searching I found the article online as well. You can read it here. It says "the rails are laid to a gauge of 3 feet 8 inches, and the larch sleepers are placed at about 6 feet pitch..." starting at the bottom of the right-hand column on page 68. The Mirror Cracked (talk) 13:52, 8 October 2019 (UTC)
@DePiep: A note on the engineering-timelines.com source. It is not entirely reliable. While it has a lot of good information, it doesn't fully source its information, and it is user-generated content - I don't think there is any editorial control. I've found several instances of factual errors on it, and I treat it with caution. That said sources do disagree about the track gauge of the Cliff Railway. The Cassier's article could be a typo - though you would think the chief engineer of the line would be keen to get that sort of detail right. It is even possible that it was originally 3ft 8in and was slightly gauge widened when the modern concrete sleepers were put in. The Mirror Cracked (talk) 19:28, 8 October 2019 (UTC)
Interestingly, Martin Easdown's 2018 book give 3ft 8in as the gauge for the Clifton Rocks Railway, not 3ft 2.5in: Easdown, Martin (15 July 2018). Cliff Railways, Lifts and Funiculars. Amberley Publishing. pp. 34–35. ISBN978-1-4456-8004-0.. I've also found another paper by Marks given to the Institute of Civil Engineers which again quotees 3ft 8in for the gauge of the Lynton Cliff Railway.Institution of Civil Engineers (Great Britain) (1894). Minutes of Proceedings of the Institution of Civil Engineers. The Institution. p. 318. This to me makes it less likely that the 3ft 8in is a typo. It would appear that Marks at least thought it was a 3ft 8in gauge line. The Mirror Cracked (talk) 02:01, 9 October 2019 (UTC)
Please help me out. Do we understand that both "58.875 in" (4 ft 10+7⁄8 in) and "Toronto gauge" (4 ft 10+7⁄8 in) refer to the same, physical gauge width? Also, that they are mutually excluding (i.e., no other gauges by name of width), refer to this one?
Toronto-gauge railways For historical reasons could {{Track gauge|59in}} or {{Track gauge|4ft11in}} 4 ft 11 in (1,499 mm) or 4 ft 11 in (1,499 mm) be added? {{cvt|4|ft|11|in|mm|0}} 4 ft 11 in (1,499 mm) It has already {{Track gauge|58.75in}} 4 ft 10+3⁄4 in (1,492 mm) Peter HornUser talk12:02, 16 June 2020 (UTC)
Actually, Peter Horn, these days I do not have much editing time to spend on Track Gauges. Have a nice edit. -DePiep (talk) 22:37, 22 January 2021 (UTC)
In {{Track gauge}}, a target link is to a gauge-specific article, which has sources for that gauge. That is, defining sources, proving actual usage of the definition. For example: "5 ft (1,524 mm)". For the 20-inch gauge, that could be one of the articles Category:20_in_gauge_railways_in_England (3) (only 2 are categorised). Quite often I see articles that use this setup: "20 in (508 mm) (minimum gauge)". -DePiep (talk) 17:34, 29 December 2020 (UTC)
To be clear: I can only respond to clear questions. Your first, 17:10 question I have answered. Waiting for more proposals/requests. -DePiep (talk) 23:14, 29 December 2020 (UTC)
Won't redirect the 20in track gauge to that one, then. Will remove that one from 500mm even. For principle explained above. -DePiep (talk) 01:15, 30 December 2020 (UTC)
General requirement for any wikilink in this form: the target article must have a RS for the actual gauge being defined (by actual usage/ordering). In order of preference: gauge-dedicated article, gauge-defining installation(s) (railroad build), generic article ("gauges in country XX", "gauges overview"). RS required always. -DePiep (talk) 13:31, 31 December 2020 (UTC)
Reason for changing "Victorian broad gauge" to "Australian broad gauge"
1600 mm (5ft 3in) gauge exists in the Australian states of Victoria and South Australia (and, now trivially, existed in Tasmania in the 19th century). Australia-wide, the broad gauge is not known as "Victorian broad gauge" but simply "broad gauge". Victoria has no special claim to the "Victorian" nomenclature on the basis of history or any other reason. Changing the term to "Australian broad gauge" would recognise the common usage and the fact that it does not exist solely in Victoria.
Consequent suggested changes
In the "List of defined track gauges" table, in the 1,600 mm row:
column 3: change "Victorian broad gauge" to "Australian broad gauge".
Similarly, in the "Named gauges" table:
column 1: change {{Track gauge|Victorian|al=on}} to {{Track gauge|Australian|al=on}}
It sure would help to have some citations at the linked page. Do you know of any? Also, why not just call it "broad gauge", as indicated in the target article, to be inclusive of Brazilian usage as well? – Jonesey95 (talk) 05:42, 23 February 2021 (UTC)
(ec) We should only use names that are actually used as such, not descriptive terms. Despite "Victorian" being a misnomer, as you say, is it not used? And "Australian broad gauge", is that used in sources? -DePiep (talk) 05:45, 23 February 2021 (UTC)
Jonesey95, I have added a citation to the bullet point relating to Australia on the linked page. Re your question, "why not just call it "broad gauge?", I guess it's simply that it's a relative term: unless a context is put on it, the term would mean different things to different people – e.g. 5ft 6in on the Indian subcontinent and 1668mm in Spain – hence ambiguous. That said (and the following also addresses DePiep's comment), I can say very confidently that someone in Australia with an interest in railways, when asked, say, "What gauge was the line from Melbourne to Albury before it was standardised?", would reply, "It was broad gauge". And similarly, "Were the railways in the Adelaide suburban area standardised when the interstate routes were?", the reply would be, "No, it's still broad gauge." The terms "Victorian broad gauge" (as currently in the article) and "South Australian broad gauge" would simply never be used. And "Irish gauge" is not used in Australia either. To explicitly answer your 2nd question, De Piep, you would only find the term "Australian broad gauge" used by Australians in a discussion of multi-national gauges, so a published source would be as rare as hen's teeth. I'll browse some old magazines and books and ask my mates to look for one, but I won't hold my breath. ;-) It makes sense to me, as mentioned at the beginning, to add "Australian" solely to establish context among other nation's alternative understandings for the term. Cheers, Simon – SCHolar44 🇦🇺💬 at 12:43, 23 February 2021 (UTC)
PS: Almost forgot, De Piep – with regard to "comma=off" and your 12 January comment: "will dive into this", have you had any luck yet? SCHolar44 (talk) 12:43, 23 February 2021 (UTC)
Current working: {{Track gauge|Victorian|allk=on}} → 1,600 mm (5 ft 3 in) Victorian broad gauge
Request (demo): {{Track gauge|Australian|allk=on}} → 1,600 mm (5 ft 3 in) Australian broad gauge
About "Victorian": So actual uasage (as a track gauge name) is disputed in OP. If no sources are found that supports this name (today or historically), it must be deprecated & removed indeed. Of course it might be regional, pertaining to Australia and in now way in Ireland for example. (I recall, from initial days of {{Track gauge}}, this 'source' requirement was not this hard, so Victorian might have entered from habit).
About "broad gauge": Not useful havng this as input option: it contains dozens of gauges (all >1,435 mm (4 ft 8+1⁄2 in) standard gauge). However, in an article section it is usable, to make nice sentences: "AU has 1,600 mm (5 ft 3 in), a broad gauge. The broad gauge was introduced ... etc.".
About "Australian gauge": To make this a recognised name in {{Track gauge}} (as are, nowadays: Victorian, Iberian, Ohio, Russian, etc.), we need sources RS that use this as a name (not as a description). It could be historical (only used in certain era). Best would be, like, an order of a rail road company: "We order this rolling stock with Australian gauge" :-) If these sources can not be found, this signals that "Australian" has not been used as such, and so is not acceptable here. (I understand here in current ref#6, R. Fitch, might be helpful but does not use it; I cannot access the book). In this case too, I note that a colloquial name as "Australian gauge" can be introduced in text, with less sourcing requirements, and improve the article's info & legibility.
Hello DePiep, I laughed out loud at the notion of a colloquial name of "Australian gauge" -- not in any way at you, I assure you, just at how it shows up Australia's tragic railway history. The logical concept of one Australian gauge is the very antithesis of what happened with three main gauges that persist today, ignoring the minor ones – which people overseas can barely conceive of. Here's a comment by a former railways commissioner (=president or CEO):
Australia’s rail gauge mess has been nothing short of disgraceful, and it is to the everlasting discredit of those responsible. It has been a farrago of procrastination, parochialism, interstate jealousies and political bloody-mindedness. All this capped off by hindrance on the part of Canberra-insulated public servants whose function appeared, for the most part, to be confined to paper shuffling but who, despite their remoteness from the action, sought to impose their obstructive philosophies on the states. And, finally, when at last something was done, we were still left with three gauges, a dozen breaks of gauge — which, at one stage, included two three-gauge stations only a few kilometres apart — and a half-baked standard gauge system that one could be pardoned for suggesting had been designed specifically to ensure that complete unification could never be achieved.
... Today, after more than 100 years of Federation, we are left with 33,500 route kilometres of public railways on the mainland, still of three gauges — 4000 broad, 15,100 standard, 14,100 narrow and 300 dual — together with ten operative breaks of gauge and three inactive ones on account of the cancellation of services.
That should demonstrate why the term "Australian gauge" doesn't have traction anywhere in Australia, and why it hasn't been used historically -- it simply wouldn't make sense. If used overseas it would be erroneous through being a meaningless term. It won't therefore be found in a published source. (I'm confident on this subject because I've been involved professionally with the Australian railway industry for a long time.)
So, unless you disagree, could you clarify what sort of citations you think are needed now? I'll try to help.
I see! As for {{Track gauge}}, there is no use in adding any "Australian gauge" ID. It's as wide as "broad gauge" is: not specific. So, we'll remove Victorian (b/c unsourced), and not add anything. -DePiep (talk) 20:44, 3 March 2021 (UTC)
PrimeHunter: MOS:DIGITS, in saying "Numbers with exactly four digits left of the decimal point may optionally be grouped (either 1,250 or 1250) ...", overlooks the formal SI preference for a space: "Spaces should be used as a thousands separator (1 000 000) in contrast to commas or periods (1,000,000 or 1.000.000) to reduce confusion resulting from the variation between these forms in different countries", and perhaps that's what Peter Horn had in mind (or maybe not) in asking for a space instead of the comma. My experience has been that the space is used much less often than when the SI convention was instigated -- it seems to me that people are now pretty well aware of the convention in the "other" jurisdiction.
In the event, provision could be made for three options: default comma, space, no comma until there are 5 or more numerals. ("Comma=5", as already provided in Template:Convert, is better than "comma=off", because once you get to millions the comma is inserted at position 3 in addition to position 6.)
We should not support an option that is not supported by the MOS, regardless, which would appear to dis-include the ISO's preference. --Izno (talk) 07:15, 19 February 2021 (UTC)
If you believe SI having a specific preference is sufficient to see something added to the MOS, you will be quite surprised. Regardless, adding it to the MOS is blocking to adding it here. --Izno (talk) 08:04, 19 February 2021 (UTC)
Sorry, Izno, I don't understand "is blocking to adding it here" in your 2nd sentence. Could you please clarify? Thank you. Come to think of it, a bit of background about being surprised about adding to the MOS would also be appreciated -- I'm keen to benefit from your experience. SCHolar44 (talk) 08:11, 19 February 2021 (UTC)
"blocking" in a development process usually refers to "you need to sort the blocking thing out before doing the blocked thing". In context, adding to MoS is blocking adding it here means "you must have it added to MOS before adding it here".
As for surprise, the MOS is its own MoS. While we may take into consideration some particular style, we often need to make other concessions or actively reject other style points. For example, regarding the symbol of a byte or its multiples, I do not think we follow SI. (Why is left to the curious reader.) The case of a space separator is a case where I believe our desire to have a consistent numerical representation for both technical (for SI's primary concern is technical for the majority of its recommendations) and non-technical readers (the majority of ours are undoubtedly the latter) would likely have us reject a change to include spaces as a permissible 10^3n separator (and/or 10^-3n). But, if you should feel obliged on the point, start by reviewing the talk archives there (WT:MOSNUM) to ensure it has not been discussed, and then start a new discussion with your understanding of previous discussion laying out why you think the MOS should change. --Izno (talk) 08:25, 19 February 2021 (UTC)
Per current data, only applies to metric not ft,in values (IOW, no comma present in current ft,in output so not applied on ft,in in the module at all).
PrimeHunter. I noticed a bug in my sandbox, so I had to pause my request.
Issue (pls take a look PH, maybe you can help): #comma_=_off_bad_input tests, with "ugly input", showed bugs. In short: when input is like |comma= (<blank>), |comma=foo, the 'remove comma' still fires. I cannot get it right somehow. If you could take a look & edit fix it, would be great. -DePiep (talk) 23:12, 3 March 2021 (UTC)
Unclear report. About which gauge are you talking? I see both 3ft6in, 4ft6in, 1372mm; and a chaotic bug report (not "is ...; should be ...; see also ..."). -DePiep (talk) 13:59, 1 March 2021 (UTC)
@DePiep: At the current version of this template, {{Track gauge|4ft6in|lk=on}} and {{Track gauge|54in|lk=on}} both generate a link to 4 ft 6 in gauge railway. When using millimeters instead of inches, {{Track gauge|1372mm|lk=on}} generates a link to Toden Arakawa Line, which is inappropriate as I mentioned above. Likewise the cases with "4ft6in" and "54in", {{Track gauge|1372mm|lk=on}} should be linked to 4 ft 6 in gauge railway.--侵入者ウィリアム (talk) 14:43, 1 March 2021 (UTC)
Interesting note: The "Toden_Arakawa_Line" is linked because it is defined metric not ft/in, with source! So: for consistency :-). Here at {{Track gauge}}, we adhere to defined tracks, even per unit (ft/in or metric). So this is why the 1372mm link is as it is.
(Probably used because article says 'define in metric', initially. But we can not confirm such a source today.)
All in all, there is no sourcing article (found yet) to claim an "1372 mm gauge" article. So nor change existing ft/in article into "4 ft 6 in and 1372 mm gauge railway".
I add: base of the {{Track gauge}} is that it encourages sourced track gauges. That is: gauges that are sourced, including their unit. e.g., "metre gauge " was never defined or ordered in ft/in units :-)
To editor 侵入者ウィリアム: Thanks. This was elaborate talks. The enwiki track gauge set is well-based (sourced) and we prefer that. Maybe, in the future, I might ask more questions about 1372mm & Japan ;-) Have a nice edit. -DePiep (talk) 22:31, 10 March 2021 (UTC)
If the article is stable, and has sources for the gauge, it can be used as target. IMO, if it only has list of usage it might not be viable (then categorise the list). But feel free. -DePiep (talk) 14:40, 18 March 2021 (UTC)
@Ost316: Your edit looks OK. I have removed the "1422 mm" (metric) definition because no source available (see #1422 mm below). I leave the honour of the EditRequest (../data/sandbox) to you :-) -DePiep (talk) 12:29, 6 April 2021 (UTC)
Interesting case. Is 1145 mm original (=thought of locally), or a rounded conversion of the imperial size? After all, rounding is just 2 millimetres (0.079 in). The (modern) source only mentions metric, but possibly the contemporary source (=design) *might* mention the imperial one as origin.
For the moment, I am thinking: "1145 mm is the metrical equivalent of 3 ft 9 in (1,143 mm), rounded". Needs some more research. -DePiep (talk) 12:40, 5 July 2021 (UTC)
Seems to have been an error introduced in a change to the Toronto gauge entry.
Basically, when the article was moved from Toronto gauge to Toronto-gauge railways, the entry in the data here was changed such that {{Track gauge|Toronto|first=met|allk=on}} (basically the |allk=on version) lists "Toronto-gauge railways" instead of what it should list, which is "Toronto gauge" (i.e. list the name of the gauge as the link text, not the name of the article it links to).
This can be seen in the second paragraph of this, where the sentence reads:
The trains are powered by linear induction motors and operate on 1,435 mm (4 ft 8+1⁄2 in) standard gauge tracks, unlike the city's subway lines and the Toronto streetcar system, which use the unique 1,495 mm (4 ft 10+7⁄8 in) Toronto gauge.
You can see the usage expects the template to generate something like "standard gauge", not "standard-gauge railway". You can see how Toronto sticks out currently as wrong in the table of gauges, where all the other "Alt Name" entries are in the form "[location name] gauge" (e.g. "Ohio gauge", "Russian gauge") whereas Toronto's entry is "Toronto-gauge railways".
I think I've fixed this in the sandbox here but to be honest I couldn't quite figure out how to test changes made to the sandbox version of /data.
Anyway, can someone either make the change as per the link I've provided or, if it's incorrect, fix it so that when |allk= is set to "on" for "Toronto", it lists "Toronto gauge" as the link text and not "Toronto-gauge railways"? Joeyconnick (talk) 19:10, 2 August 2021 (UTC)
The track has never been build, so inclusion not applicable. Also, there is no RS source in the link for this design. Policy is that unsourced traks are not added. -DePiep (talk) 13:48, 27 September 2021 (UTC)
My first impression is that "0.65 m" is a typo or a data mistake. Would be very peculiar if for this 32 km of rails rolling stock with such an unique gauge would have been created. -DePiep (talk) 15:26, 13 October 2021 (UTC)
Sorry, not is not "Ctrl f". When the reference opens, there are instructions in German to the left. There is a search window and to the right of that "Los gehts". That allows me to find 0.65 m gauge. Peter HornUser talk19:17, 14 October 2021 (UTC)
The source is a US government department publication which has been used as a source for most of the railways mentioned in the article, there are for me "no obvious reasons" why it should be unreliable. As for "not plausible", a number streetcar systems in the US had unusual, if not unique, track gauges. To this day the Toronto Transit Commission is hobbled by the Toronto gaugePeter HornUser talk18:13, 15 October 2021 (UTC)
The "author" is not disputed. I wrote that the unique gauge is probably a typo or data mistake, because it is not plausible that a 32-km track in Tucuman Argentine would order an worldwide unique rolling stock with that gauge. About the "0.51 m", I suggested you took a little reasonability-research. Well this is what I though you could have found in a whimp: 0.51 metres (20.079 in) is quite likely a regular "20-inch" gauge, rounded in metrification somewhere in the reporting route. (If not a rounding difference, then the same unlikeliness occurs: why order an unique gauge?).
Since this is a talkpage, I have some talking notes to make. First, all the links you added are all to a single source. Doubling a link does not add quality for the claim. Also, it would be helpful if you tried to grasp my remarks & questions, and then build unpon those. For now, it looks like if you missed most of my points. -DePiep (talk) 18:43, 15 October 2021 (UTC)
Good action. And indeed, although it says "commercial", the military goal is quite clear. Nowadays, CIA maintains such lists. -DePiep (talk) 06:16, 16 October 2021 (UTC)
^3 ft 6 in (1,067 mm) is given throughout Pope et al., and Paar. Casserley, page 121, gives 3 ft 8 in (1,118 mm) , as does MacDermot, volume II, page 402.
I don't think we need to. {{Convert}} is handling precision & uncertainty in the generic way, bases on common measurement & precision theories in science. It's about scientists expressing uncertainty in the measurement (with original unit); convert then should try to reproduce that uncertainty as good as possible (but not suggesting more precision than the source says).
Track gauges, OTOH, are a defined size (length), and by unit so (defined in a certain unit). The definition size itself does not imply uncertainty/precision. Because: it is defined, not measured. Possibly the definition has specifications on tolerance in RL constructing, all right. We don't know them, we don't need to report them: for these specifications, go to the definition page (say, Standard gauge § precision). On top of this, the defined precision (tolerance) varies: for a TGV the SG tolerance is much smaller than for an underused fright track. So far for the defined size in a unit.
Then, when we (enwiki) convert to a non-defined unit, we should not imply or suggest precision in the new value. {{Track gauge}} does consistently:
In the conversion, round to nearest 1 mm or 1⁄32 in. [1 mm (0.039 in), 1⁄32 in (0.794 mm)]
In practice, this conversion is hardcoded into {{Track gauge}}. For the model gauges, those under 89 mm or 3+1⁄2 in, this guideline is not applicable.
This looks like a most understandable representation, not-impractically precise and expressed in commonl;y recognisable units. -DePiep (talk) 09:14, 27 November 2021 (UTC)
Conclusion: Done, added 2023-01-01 [15]. Todo, separately: formally merge 1 ft 11 in (584 mm) and 1 ft 10+3⁄4 in (578 mm) as similar, for example in categorisation. 08:05, 2 January 2023 (UTC)
References
^Quine, Dan (December 2022). The Hendre Ddu Tramway: Blue Stones and Green Trees. Lightmoor Press. ISBN9781915069153.
What we want to have is the definition of a gauge, say: the size as ordered. So when in practice, when it is ~1⁄4 inch off, it might be the same gauge (but source is imprecize).
Then, when these are the same, that explains why you were surprised: they are present under a different size.
OTOH, if these are not the same (i.e., they are absolutely defined to be different by original order), this is an unique gauge railway.
Hi @DePiep:. The source gives the gauge of the tramway as 1ft 11in, as distinct to other close variants, so I believe it is the definition of the gauge. I'm surprised this gauge isn't used more, since it would be an obvious variant of "near-2ft" gauges. Anyway, I do believe this is a unique (or at least rare) gauge that should be separately defined in the template. Thanks, Grachester (talk) 02:17, 28 December 2022 (UTC)
OK, thanks, yes that is plausible. Now the other part of my (confusing) question is:
Are the other, nearby gauge sizes possibly the same as this 1 ft 11 in, but only more sloppy researched/documented?
Because, it is very likely that these are originally defined the same. Why would there be such small variations? Why would the Hendre-Ddu Tramway have an unique gauge by itself? (surprising indeed, as you said yourself). So the 2nd question is: could you take a look at the other lines, whether their gauge is well-sourced to be different? DePiep (talk) 21:08, 28 December 2022 (UTC)
@DePiep:it's entirely possible that there are other railways at 1ft 11in. Those listed above as 1 ft 10¾ in gauge are correct. There are a lot of tramways and railways in Wales that served mines and quarries that were "around" 2ft gauge. Most of these are either undocumented, and/or were roughly laid and their gauge varied by +/- an inch or even two. So stating a precise gauge for them is difficult. I don't have a list of other known 1ft 11in gauge railways, but there certainly would have been some. These small differences didn't matter for horse/human worked tramways, but did make a difference once the railways were locomotive-worked, as the Hendre Ddu was from 1921 onwards. So I do think it is meaningful to list this specific version of "2ft gauge" even if the Hendre Ddu is the only (so far) documented example. Grachester (talk) 00:21, 29 December 2022 (UTC)
I'm not that interested where an error comes from ;-), which answers nothing. I'd like to see a confirming source :-).
At first, a new metro way in the 1960s(!) in France(!) would hardly have a non-standard gauge. However, since the city has a history in fr:Tramway de Rennes from 19th century, a distinct gauge could be plausible. That is, the new metro would have chosen the same gauge as their old tramways...
For now, finding a source is best, probably frwiki is better positioned. If in say a few months a source is not found, we'll have to remove any gauge number as not-verifiable. DePiep (talk) 12:15, 4 February 2023 (UTC)
OK then. Don't think we should list this in/as {{Track gauge}}. I propose you use simple {{Convert}} in the infobox (here, enwiki), and maybe note this detail with it. DePiep (talk) 05:39, 8 February 2023 (UTC)
This template admits a parameter comma which is described almost nowhere in the description. By "almost nowhere", I mean that the only place where I found it mentioned is at the bottom of the TemplateData rollout, as "Parameter: comma; Description: no description; Type: Unknown; Status: optional". That's rather uninformative, don't you think ? After having seen that parameter in use in several places in the article Dual gauge, I wanted to know what it did, and after reading the above, I still didn't know. Then I guessed that comma=no suppressed the thousands comma in the gauge widths, but after trying to add an example as part of this comment, the preview still separated the thousands with a comma. So please, someone, complete the description of the comma parameter at the bottom of the TemplateData rollout, and also add some examples of its use here and there in the rest of the description.
— Tonymec (talk) 15:37, 21 September 2023 (UTC)