Wikipedia talk:WikiProject Trains

This is the talk page for discussing WikiProject Trains and anything related to its purposes and tasks.

Put new text under old text. Click here to start a new topic.
New to Wikipedia? Welcome! Learn to edit; get help.

WikiProject Trains was featured in a WikiProject Report in the Signpost on 20 September 2010.

This page has archives. Topics inactive for 30 days are automatically archived by .

The Trains WikiProject
General information
Main project page	(WP:TWP)	talk
Portal	(P:Trains)	talk
Project navigation bar		talk
Project participants		talk
Project banner (doc)	{{TWP}}	talk
Project category		talk
Manual of style	(WP:TWP/MOS)	talk
Welcome message		talk
Departments
Assessments	(WP:TWP/A)	talk
Peer review	(WP:TWP/PR)	talk
To do list		talk
Daily new article search	search criteria	talk
Task forces
Article maintenance		talk
Assessment backlog elim. drive		talk
By country series		talk
Categories		talk
Images		talk
Locomotives		talk
Maps		talk
Rail transport in Germany		talk
Monorails		talk
Operations		talk
Passenger trains		talk
Portal		talk
Rail transport modelling		talk
Timelines		talk
This box: view talk edit

LNWR 2-2-2-0 no. 189

Which class is this 2-2-2-0 loco? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 21:13, 12 December 2025 (UTC)[reply]

The folks at WT:UKRAIL could probably tell you more, but based on the source website it's possible this was a one-off order. In the early days of steam locomotive manufacturing there was a lot less standardization as manufacturers were still experimenting with what designs were effective, and for what roles. Trainsandotherthings (talk) 16:48, 13 December 2025 (UTC)[reply]

@Pigsonthewing: It's described, with exactly the same photo, in

Jack, Harry (2001). Greenwood, William (ed.). Locomotives of the LNWR Southern Division. Sawtry: RCTS. pp. 141, 144–6. ISBN 0-901115-89-4.

It's one of a class of ten supplied to the LNWR (Southern Division) by Jones and Potts in 1847-48: one (no. 175) bought by the LNWR (S. Div.) ready-made, possibly built 1846, and nine ordered by the Chester and Holyhead Railway, but delivered to the LNWR (S. Div.) in 1847-48 as nos. 182-190. Jack describes them as 4-2-0, not 2-2-2-0. The disc wheels on the leading axle are not original. --Redrose64 🌹 (talk) 10:36, 14 December 2025 (UTC)[reply]

Also listed in Baxter, Bertram (1978). Baxter, David (ed.). British Locomotive Catalogue 1825-1923, volume 2A: London and North Western Railway and its constituent companies. Ashbourne: Moorland Publishing. p. 79. ISBN 0-903485-51-6. OCLC 60034556. OL 25663325M. --Redrose64 🌹 (talk) 10:40, 14 December 2025 (UTC)[reply]

Excellent, thank you. Does either book name the designer?

They should probably be added to Locomotives of the London and North Western Railway. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:37, 14 December 2025 (UTC)[reply]

Page 55 of this 1927 book has a drawing of the locomotive and suggests it was a Stephenson design. Black Kite (talk) 21:40, 14 December 2025 (UTC)[reply]

That drawing in Ahrons depicts a locomotive built by Stephensons, not Jones & Potts; it is of similar basic type (4-2-0 with the cylinders between the carrying axles and the firebox behind the driving axle), but differs in several details. Consider, for instance, the shape of the footplate adjacent to the cab; the driving wheel splashers; the springing to the second axle; the firebox top; the safety valves; the shape of the dome cover. --Redrose64 🌹 (talk) 23:12, 14 December 2025 (UTC)[reply]

My mistake, I read "as built by Stephenson, Jones and Potts" as meaning it was a Stephenson design built by Jones and Potts. Black Kite (talk) 11:19, 15 December 2025 (UTC)[reply]

It seems, by a reading of Ahrons, and other pages in Jack, that the long-boiler 4-2-0, with outside cylinders between the two carrying axles, was a patent of Robert Stephenson & Co. but not necessarily designed by Stephenson himself. Several manufacturers produced locomotives to this general design, including: Robt Stephenson & Co; Jones & Potts; Charles Tayleur & Co, and they were supplied to several railways. BTW a "long-boiler" engine is one where the firebox is entirely behind the rearmost axle. The consequential short wheelbase can cause instability problems, both pitching and yawing. --Redrose64 🌹 (talk) 20:54, 17 December 2025 (UTC)[reply]

Finding a source about local French rail lines/tramways around Le Touquet

As part of GA review, I was questioned about the authenticity of sources cited in the rail section of the article. I posted a resource request to find the book. Any help from you would be welcome, not limited to the book request but also to the whole rail section. Szmenderowiecki (talk · contribs) 17:38, 26 December 2025 (UTC)[reply]

@Szmenderowiecki: I have the book Tortillards of Artois which covers the various tramways in and around Le Touquet amongst other narrow gauge railways in the area. Is this likely to be useful to you? Mjroots (talk) 13:32, 2 January 2026 (UTC)[reply]

Artois is more inland, but if it has stuff about Le Touquet, absolutely. Send me a wikimail with the file sharing link. Many thanks. Szmenderowiecki (talk · contribs) 13:50, 2 January 2026 (UTC)[reply]

@Szmenderowiecki: it's an actual book. Not sure it is available in digital form. Mjroots (talk) 14:05, 2 January 2026 (UTC)[reply]

If you feel comfortable making photos of relevant pages (basically if it's legal), I would very much appreciate it. Szmenderowiecki (talk · contribs) 21:37, 2 January 2026 (UTC)[reply]

@Szmenderowiecki: I've added to the Le Touquet article from Tortillards of Artois. Mjroots (talk) 12:07, 6 January 2026 (UTC)[reply]

Thank you very much for your effort.

I'd just like you to know that I'm being grilled at GA review page for overextending with the article and trying to cram too much detail, and the rail section did become excessively long. Maybe spin some of it to Étaples-Paris-Plage train line and maybe Trams in Le Touquet? I just need an overview of the infrastructure development, not all details about its operations. Szmenderowiecki (talk · contribs) 13:03, 6 January 2026 (UTC)[reply]

@Szmenderowiecki: Feel free to trim. The "Étaples-Paris Plage train line" is more correctly the Tramway d'Étaples à Paris-Plage. Mjroots (talk) 16:48, 6 January 2026 (UTC)[reply]

Requested move at Talk:Sukhumvit Line#Requested move 21 December 2025

There is a requested move discussion at Talk:Sukhumvit Line#Requested move 21 December 2025 that may be of interest to members of this WikiProject. Vestrian24Bio 04:41, 28 December 2025 (UTC)[reply]

Requested move at Talk:Britomart Station#Requested move 24 December 2025

There is a requested move discussion at Talk:Britomart Station#Requested move 24 December 2025 that may be of interest to members of this WikiProject. TarnishedPath^talk 08:31, 1 January 2026 (UTC)[reply]

Re: Infobox rail service

Anyone noticed in {{Infobox rail service}} setting |map_state= as collapsed isn't working. it's always expanded.––KEmel49(📝,📋) 18:32, 1 January 2026 (UTC)[reply]

@KEmel49:

Works for me. Please always give an example of where you are seeing the problem. --Redrose64 🦌 (talk) 20:22, 1 January 2026 (UTC)[reply]

@Redrose64, Let's say the documentation of that template. The Example section - TranzAlpine infobox.––KEmel49(📝,📋) 11:39, 2 January 2026 (UTC)[reply]

Again,

Works for me. It's collapsed, and the "[show]" link uncollapses it. --Redrose64 🦌 (talk) 17:14, 2 January 2026 (UTC)[reply]

It's still same for me, i have taken a screenshot, how can i show that––KEmel49(📝,📋) 10:04, 3 January 2026 (UTC)[reply]

WP:WPSHOT. --Redrose64 🦌 (talk) 10:10, 3 January 2026 (UTC)[reply]

Good article reassessment for Pakenham line

Pakenham line has been nominated for a good article reassessment. If you are interested in the discussion, please participate by adding your comments to the reassessment page. If concerns are not addressed during the review period, the good article status may be removed from the article. Z1720 (talk) 15:27, 3 January 2026 (UTC)[reply]

Requested move at Talk:Main North railway line, New South Wales § Requested move 4 January 2026

An editor has requested that Main North railway line, New South Wales be moved to Main north railway line, which may be of interest to this WikiProject. You are invited to participate in the move discussion. Qwerty123M (talk) 10:23, 4 January 2026 (UTC) I have also proposed that the pages for the Main Western and Main Southern railway lines be moved to a different title.[reply]

Top and tail

Hi, there has recently been a big addition to the Top and tail article without a checkable reference. Can someone please check the Two locomotives powering section is correct, regards Atlantic306 (talk) 22:20, 5 January 2026 (UTC)[reply]

To put this into context, the material (or something very like it) has been removed and re-added at both Top and tail and Push–pull train. It's a case of "should we have two articles, or one", or if you prefer, an undiscussed split/merge dispute. --Redrose64 🦌 (talk) 22:28, 5 January 2026 (UTC)[reply]

Thanks, i'll leave it to the project members to decide on that, regards Atlantic306 (talk) 21:24, 7 January 2026 (UTC)[reply]

Requested move at Talk:Main North railway line, New South Wales#Requested move 4 January 2026

There is a requested move discussion at Talk:Main North railway line, New South Wales#Requested move 4 January 2026 that may be of interest to members of this WikiProject. TarnishedPath^talk 06:43, 6 January 2026 (UTC)[reply]

Maybach diesels, and an English Electric loco

Hi all. Part 1: As far as I can work out, the following BR locos were (possibly) powered by Maybach diesel engines:

British Rail Class 35
British Rail Class 42
BR Class 50 ? [1]
British Rail Class 52
British Rail Class 53 (single prototype)
See also [2]

Does anyone know of any others?

Part 2: I started User:MinorProphet/Draft subpages/English Electric Type 3B several years ago and ran out of refs. Does anyone know any more about this tiny shunter, with sources, so I can publish the article? Happy New Year, :> MinorProphet (talk) 22:10, 7 January 2026 (UTC)[reply]

Definitely not Class 50; they had English Electric engines. --Redrose64 🌹 (talk) 19:11, 8 January 2026 (UTC)[reply]

Thanks. MinorProphet (talk) 15:26, 9 January 2026 (UTC)[reply]

Requested move at Talk:Ginza line#Requested move 2 January 2026

There is a requested move discussion at Talk:Ginza line#Requested move 2 January 2026 that may be of interest to members of this WikiProject. TarnishedPath^talk 11:26, 9 January 2026 (UTC)[reply]

Discussion at Wikipedia talk:WikiProject UK Railways § LB&SCR E2 class

You are invited to join the discussion at Wikipedia talk:WikiProject UK Railways § LB&SCR E2 class. Redrose64 🌹 (talk) 22:30, 9 January 2026 (UTC)[reply]

Category:Electric multiple units by number of cars has been nominated for discussion

Category:Electric multiple units by number of cars has been nominated for possible deletion, merging, or renaming. A discussion is taking place to decide whether it complies with the categorization guidelines. If you would like to participate in the discussion, you are invited to add your comments at the category's entry on the categories for discussion page. Thank you. XtraJovial (talk • contribs) 19:12, 10 January 2026 (UTC)[reply]

Category:Diesel multiple units by number of cars has been nominated for discussion

Category:Diesel multiple units by number of cars has been nominated for possible deletion, merging, or renaming. A discussion is taking place to decide whether it complies with the categorization guidelines. If you would like to participate in the discussion, you are invited to add your comments at the category's entry on the categories for discussion page. Thank you. XtraJovial (talk • contribs) 19:12, 10 January 2026 (UTC)[reply]

Requested move at Talk:Orbirail

An editor has requested that Orbirail be moved to Orbital railways in London, which may be of interest to this WikiProject. You are invited to participate in the move discussion. ~2026-17719-5 (talk) 14:45, 13 January 2026 (UTC)[reply]

Gradient template?

Is there a function in convert for gradients, e.g. 1-in-X = y degrees or z%? I thought something like this might be useful for the article I'm currently working on, a narrow-gauge railway in Victoria, Australia - Walhalla railway line, to make the article more compatible with international readers who might be more used to expressions of slope in, say, percentage values whereas locally we almost always use "1 in X".
At the moment my edit of the article has a mix of "1:30", "1-in-30" and "1 in 30" formats; I'll do a final sweep and standardise those before I finish, but the template could deal with all those at the same time as a side-benefit. This 1927 diagram [3] shows the gradients of the railway line expressed as 1 in X, e.g. a slope marked "30" is 1 in 30.
For inputs, I think a code chain of {{convert|30|x|%dr}} might work, where the user inputs any one value, x for 1 in X, % (or pc?) for percentage, d for degrees or r for radians, and it provides outputs for all other terms, in this case %, d, and r, but fewer if not all three are specified in the final convert term. There'd also need to be something for rounding, e.g. maximum 2 decimals on percentage. A more complicated version might want to account for swapping from downhill to uphill, e.g. downhill 1 in 30 changes to uphill 1 in 30, net difference 1 in 60.
I originally asked this in the page for the {Convert}} template page, @Johnuniq (talk · contribs) recommended that I bring it over here. Anothersignalman (talk) 19:28, 13 January 2026 (UTC)[reply]

If the folks at convert sent you here I'd it's probably best as a separate template (c.f. {{rail gauge}}, but yes it absolute would be a good idea. For syntax perhaps {{gradient|x|in|y}} to output a percentage and {{gradient|x|%}} to out put 1 in x? I don't have anything approaching the ability to make this myself. Thryduulf (talk) 13:00, 14 January 2026 (UTC)[reply]

I figured no need for x in y because as far as I've seen, it's always 1 in X, not say 3 in 65 or whatever; and that could be allowed for with decimals in any case. I also wanted to cover all the other possible ways someone might try to describe a slope, hence degrees and radians as well. Anothersignalman (talk) 14:48, 14 January 2026 (UTC)[reply]

That's fair. I also now remember discussing this somewhere previously several years ago, I didn't find that in the archives of Template talk:Convert but I did find other relevant discussions of gradients and angles in several different contexts (astronomy, railways, mountaineering, Egyptian pyramids):

Pinging the users involved in those discussions who appear to be still active (in no particular order): @Johnuniq, Hermes Thrice Great, Sauer202, Mike Peel, Mattbuck, UnladenSwallow, Gah4, Praemonitus, RoySmith, Jc3s5h, Ashill, Slawekb, and David Eppstein:. Thryduulf (talk) Thryduulf (talk) 15:06, 14 January 2026 (UTC)[reply]

Re I figured no need for x in y because as far as I've seen, it's always 1 in X, not say 3 in 65 or whatever If you supported the more general case, this might be useful for things like Roof pitch. RoySmith (talk) 15:20, 14 January 2026 (UTC)[reply]

Yeah, OK, roof pitch is a good argument for the more complex x-in-y option. Without knowing anything about programming, I'm guessing that means we can't have a single field each for input-type, number, output types plural as I'd shown above though? Anothersignalman (talk) 16:00, 14 January 2026 (UTC)[reply]

I'm also not a programmer but given convert handles the same parameter doing different things depending on what it contains (e.g. {{convert|4|ft}}, {{convert|4|x|4|ft}}, {{convert|4|±|1|ft}} and {{convert|4|-|8|ft}} all do different things) it might be possible for "in" in the second parameter to trigger different handling. I guess it would make it a lot more complicated though. 16:13, 14 January 2026 (UTC) Thryduulf (talk) 16:13, 14 January 2026 (UTC)[reply]

The next step would be to work out what inputs should be accepted, with any wanted limit checks. Then, determine the exact wikitext wanted for the outputs. The best way to show that would be in a list of examples with actual numbers. I suggest one list which others edit until it's at an agreed state. There are a few coders who would implement it (possibly me) but a specification is needed before thinking about that. Johnuniq (talk) 01:17, 15 January 2026 (UTC)[reply]

This is what I originally envisaged, plus a few ideas from above. Open to other people adding to this list.

Example 01: {{slope|40|x|%dr}} generates 1 in 40 (2.5%, 1.43°, 0.025 radians) - Base case
Example 02: {{slope|40|x|dr%}} generates 1 in 40 (1.43°, 0.025 radians, 2.5%) - Note output order swap
Example 03: {{slope|2.5|%|xdr}} generates 2.5% (1 in 40, 1.43°, 0.025 radians) - Input %, output slope
Example 04: {{slope|40|x|%}} generates 1 in 40 (2.5%) - One calculated value only
Example 05: {{slope|-40|x|%}} generates -1 in 40 (-2.5%) - Support for negative inputs
Example 06: {{slope|3in8|x|%}} generates 3 in 8 (37.5%) - Any letters between two numbers in the lead term would allow a fraction other than 1 in X.
- Auto-add spaces in this example, though per below we might standardise on dashes instead?
Example 07: {{slope|3 i 8|x|%}} generates 3 i 8 (37.5%) - Letters copied verbatim causes this error missing the letter "n". This is intended as support for other languages.
- Units are x, %, d, r. Are there any others we want?

Notes:

Commas inserted between multiple output terms in brackets automatically
Order of terms in brackets as defined by the order of letters to be converted to
Decimal and comma numbers permitted in inputs, e.g. |1.7 or |1,700.
|1in8|x would generate the same output as |8|x
For the full-length gradient expression, do we want "1 in 40" without dashes, or "1-in-40" with dashes? I think I prefer the former, but open to one or the other being default with option to select.

Optional terms after the final convert-to value:

Rounding:

|round=2u - Rounds all numbers to 2 significant digits, explicitly rounding up, e.g. 6.666...% becomes 6.7%
|round=2d - Rounds all numbers to 2 significant digits, explicitly rounding down, e.g. 6.666...% becomes 6.6%
|round=4 - Rounds all numbers to 4 significant digits, rounding off, e.g. 0.14285714285 becomes 0.1426 (regardless of unit). Note an input with insufficient significant digits would be expanded, e.g. 1 in 40 would become 1 in 40.00. Not sure if that's desirable?
|round=2t - Rounds all numbers to 2 significant digits, trimming off any additional digits, e.g. 0.14285714285% becomes 0.14%
|round=-2 - Rounds all numbers to negative 2 significant digits, e.g. 142.85% becomes 140%.
- Round must always have a number; optional letters u, d, t.

Term styles:

|style=: - Swaps in (with spaces) for :, e.g. 1 in 40 becomes 1:40
|abbr=off - Swaps % to percent; ° to degrees; rad to radians - note this is the inverse of {{convert|...}}, where abbr=on has to be specified.
Question whether this and |style=: can/should be merged; and if it should be possible to specify abbreviations for some but not all terms? e.g. |xa, |%a for abbreviated versions of those two in lieu of |abbr=off altogether.
Need to think about how to allow 16.2 in 37.5, for example, in the output side. We'd need to specify rounding (including negative rounding) for each of the numerator and the denominator, though default would be round to integers.

Is that the sort of thing you were after, for an opening spec outline? Anothersignalman (talk) 14:27, 15 January 2026 (UTC)[reply]

A couple of thoughts based on that

I think we should keep parameter names and operation the same as in {{convert}} where they do the same job, for ease of learning syntax and for merging if that were to ever happen in the future. For example:
- abbr= should default to off
- round= should work the same as in {{convert}}.
- style= should be disp=
There should also be support for ranges, e.g. {{slope|20-40|%|x}} → 1 in 5 – 1 in 2.5
- ranges should use "-" (or whatever flavour of short horizontal line MOS prefers) or "to" depending on the input
There should be support "and" and "or" in a similar way to ranges.

Thryduulf (talk) 15:10, 15 January 2026 (UTC)[reply]

Agree on all points. Do you want to edit those into the above specs, or it is fine to have it in this threaded format? Anothersignalman (talk) 15:59, 15 January 2026 (UTC)[reply]

I'm about two days behind on my watchlist, so only just seen this. {{railway gradient|30}} → 1 in 30 (33.3 ‰). --Redrose64 🌹 (talk) 21:11, 15 January 2026 (UTC)[reply]

Is the per mille symbol standard in some other jurisdictions? I've only ever seen gradients expressed as 1 in x or percent e.g. 3.33%, not 33.3‰. Anothersignalman (talk) 09:42, 16 January 2026 (UTC)[reply]

Railway gradients tend to be much easier than road gradients - 1 in 30 is steep for a railway. In the UK, gradients like this are the exception rather than the rule - such as the Lickey Incline. A gradient expressed as a percentage would need to be steeper than 1 in 100 (1.0 %) in order to get a non-zero digit before the decimal point. Since many railways have a gradient easier than this, a per mil figure is used, where any gradient between 1 in 100 and 1 in 1000 (which covers most of them) will have a single non-zero digit before the point. Consider the Great Western Main Line between Paddington and Swindon, which does not exceed 1 in 660 (1.5 ‰) at any point - and that's in a distance of 77 miles. Even on this line, most of the line between Paddington and Reading (36 miles) is significantly easier: long stretches are either level or 1 in 1320 (0.8 ‰). --Redrose64 🌹 (talk) 19:49, 16 January 2026 (UTC)[reply]

Ah, you might not be familiar with Australian railways. We have gradients that have horrified UK engineers. This is the case study I'm working with - [4] - note the 26 mile line has about 16 miles of 1 in 30 to 1 in 40, and from about the 87 mile mark to the end is almost entirely curves - and the standard gauge Main West line from Sydney apparently has a net of about 9 miles of 1 in 33 which forced us to use different gearing for our HST exports. Anothersignalman (talk) 05:56, 17 January 2026 (UTC)[reply]

@Anothersignalman I've just replied in more detail in your crosspost (that I saw before I saw the question here). Per mille seems to be common in German-language sources but as far as I found not (or at least less so) in English ones. Thryduulf (talk) 20:00, 16 January 2026 (UTC)[reply]

2026 Sikhio train disaster

The 2026 Sikhio train disaster article needs a little help. For example, the line on which it occurred needs to be identified. Who is investigating the accident? Mjroots (talk) 13:56, 14 January 2026 (UTC)[reply]

The train involved was an APD.20 diesel multiple unit. Unit 2521 is identifiable from the BBC ref used in the article. The State Railway of Thailand article claims that unit 2515 was also involved, but without a reference. Can we confirm the second unit? Mjroots (talk) 15:43, 15 January 2026 (UTC)[reply]

Help with BSicon map

Hi all,

For this page - Template:Walhalla railway line - I've done the best I can with my existing skill set, but I need help adding a few other symbols including creating some that don't exist (e.g. some of the level crossings and road bridges). I've taken a screenshot and edited it to what I want for the final output here

. Is anyone here able to help out? Once the artwork is done and in place I can go back and link to various references, other articles etc. Anothersignalman (talk) 16:12, 14 January 2026 (UTC)[reply]

Please drop a message below or on my talk page with a description of exactly which icons are required. If there are icons that exist in the default colour scheme that you need in a different colour set I can create them and upload them to Wikimedia Commons ready for use. You can also overlay BSicons by adding the first (bottom layer) BSicon, followed by !~ and then the next BSicon which is drawn over the top of the first.

A handy template for displaying BSicons inline on talk pages is Template:BS-q — use {{BS-q|}} with the BSicon name after the pipe symbol, for example adding {{BS-q|fexWBRÜCKE2}} displays as

(fexWBRÜCKE2)

There are already icon sets for roads and rivers on Commons at Category:BSicon/road and Category:BSicon/water which you can browse, or use the navbox at Template:Bsicon to find gallery subpages. -=# Amos E Wolfe ^talk #=- 02:25, 15 January 2026 (UTC)[reply]

I also have a work-in-progress at Commons:User:AmosWolfe/BSicon which has galleries displaying BSicons in all of the current colour sets, with clickable redlinks to upload a new file in cases where that colour variant does not yet exist. Editing the SVG code of a BSicon to change the line colour is a fairly simple process which I can describe to you if required. -=# Amos E Wolfe ^talk #=- 02:29, 15 January 2026 (UTC)[reply]

Thanks Arnos. I'd prefer not to overlap symbols unless absolutely necessary, because that would be more confusing for anyone who copies from this template for their own future project. These are the ones I need (I think):

(fexSKRZ-G2) - unprotected level crossing, closed green railway, will replace (fexBUE)

Done -=# Amos E Wolfe ^talk #=- 01:22, 16 January 2026 (UTC)[reply]

variant of (RP1uRP2), as road bridge over closed green railway. I'm guessing it would be (fexuRP2) but not certain.

Done — icon already exists as

(fexSKRZ-G2u) -=# Amos E Wolfe ^talk #=- 01:34, 16 January 2026 (UTC)[reply]

Is there a symbol for a water-wheel? That was a significant landmark. Otherwise I'll need a recoloured (uvxWDAMM+LOCKf), with both sides light blue; though I don't actually know whether the wheel was left or right of the stream, and I'm not sure I can find out.
Recolouring of (exSTRo) to create (fexSTRo).

Done -=# Amos E Wolfe ^talk #=- 01:27, 16 January 2026 (UTC)[reply]

There was a spot where the railway passed under a large tree trunk, that had burned through, fallen over and speared into the ground on the other side of a station. Not sure if there is, or should be, a symbol for that? Photo here - [5]

Perhaps consider using

(STR2+4 brown) or

(STR3+1 brown) as an overlay with a text label to explain the meaning? -=# Amos E Wolfe ^talk #=- 01:33, 16 January 2026 (UTC)[reply]

(TREE) and

(TREE brown) have now been added by Useddenim -=# Amos E Wolfe ^talk #=- 08:52, 16 January 2026 (UTC)[reply]

Anothersignalman (talk) 15:58, 15 January 2026 (UTC)[reply]

There are symbols for a watermill

(uWMILL L)

(uWMILL R) etc. Mjroots (talk) 17:43, 15 January 2026 (UTC)[reply]

Thanks for that, I was searching for the wrong thing. Most of the options there are for straight rivers e.g.

(uexWMILL R), not streams e.g.

(WASSER), which is also slightly narrower and a different colour. I considered

(exHELM), but it just so happens that the geometry of

(ueMILL) is perfect in my use case, fitting neatly on top of

(WASSER+l) with the hut and wheel parts correctly placed. Anothersignalman (talk) 18:33, 15 January 2026 (UTC)[reply]

I've copied the request above (other than the water mill) to the BSicon request thread. Anothersignalman (talk) 20:11, 15 January 2026 (UTC)[reply]

Much appreciated, thanks both Useddenim (talk · contribs) and AmosWolfe (talk · contribs) Anothersignalman (talk) 10:28, 16 January 2026 (UTC)[reply]

Requested move at Talk:The Strand Station#Requested move 9 January 2026

There is a requested move discussion at Talk:The Strand Station#Requested move 9 January 2026 that may be of interest to members of this WikiProject. Jeffrey34555 (talk) 01:11, 16 January 2026 (UTC)[reply]

Requested split at Talk:Puffing Billy Railway#Splitting Proposal

There is a requested split discussion at Talk:Puffing Billy Railway#Splitting Proposal that may be of interest to members of this WikiProject. Anothersignalman (talk) 10:26, 16 January 2026 (UTC)[reply]