Template talk:Rail line
Script error: No such module "Banner shell".
Documentation
Is this template documented anywhere? --Concrete Cowboy 14:40, 27 May 2005 (UTC)
- Not that I can find. I am particularly wondering about the coloured bars - I think they're being used to distinguish railway companies, but I haven't found a key. --ColinFine 17:25, 7 January 2006 (UTC)
Colour-coding for rail operators
As far as I can tell, from existing articles:
- █ #FF0000 – First ScotRail and Virgin Trains
- █ #FFFF00 – Merseyrail
- █ #8B00FF – Northern Rail
- █ #800000 – Wessex Trains
- █ #010385 – First Great Western, GNER and First TransPennine Express
- █ #30C5B8 – Arriva Trains Wales and Heathrow Express
- █ #00BB00 – Central Trains and First Great Western Link
- █ #FF9999 – Heathrow Connect
- █ #008080 – Midland Mainline
- █ #2E8B57 – Hull Trains
- █ #C80051 – CrossCountry (Kevin Steinhardt 00:20, 28 October 2007 (UTC))
- █ #FF7518 – London Overground (Kevin Steinhardt 00:20, 28 October 2007 (UTC))
- █ #FA0000 – National Express East Coast (Kevin Steinhardt 03:12, 30 October 2007 (UTC))
- █ #0D2A72 – Crossrail (Kevin Steinhardt 09:54, 30 October 2007 (UTC))
I'm not sure why several operators have to share the same colour in some cases. In the absence of anything else, I guess this can be used as a quick-reference -- Gurch 22:30, 8 March 2006 (UTC)
- Some time recently, it seems to have been decided to go pink with First ScotRail, primarily to keep with First ScotRail's colours. Some of the big ones have already been changed, here, for example, on the 28th April. Some work has already been done on this, and as I've gone through, I've changed with this move. Can we reach quick concensus that oweing to First ScotRail's new colours, and that Virgin Trains serve some routes that First ScotRail do, we can move to
- █ #FF80C0 - First ScotRail
Cheers. M0RHI | Talk to me 23:45, 28 August 2006 (UTC)
Colour-coding for Historical Scottish Routes
- █ #66ba5a G&SWR: A light olive green
- █ #496799 Caledonian: 'Caledonian Blue'
- █ #517a6a Joint Caledonian and G&SWR: an aqua colour as a result of mixing the two colours together for G&SWR and Caledonian
- █ #8f691e North British: 'French mustard'
- █ #556920 Joint NBR and Caledonian: A mixture of the colours for NBR and Caledonian
(from WPTIS Talk) Stewart 18:28, 18 February 2007 (UTC)
Users of this template may be interested in Template:Rail station, being developed by User:Captain scarlet as a possible alternative or replacement. Warofdreams talk 23:46, 16 March 2006 (UTC)
Auto-terminus
I've changed the template so that when "previous" and/or "next" are not defined, Terminus will automatically show up in the respective column. I hope this saves some space in the articles about termini. - Tangotango 18:03, 7 June 2006 (UTC)
colours - update
I've done a load of "research" on colour used by each different TOC and put the results up at Wikipedia talk:WikiProject UK Railways#colours (I'll copy the raw data over here later as an index). I'm asking some pretty key question that affect the use of colours relating to this template, all variants of it (heritage, disused, etc) and well as the "infamous" "s-rail". any comments, thoughts, agreement, disagreement would be welcome - before i do something drastic and upset someone! Pickle 08:52, 13 September 2007 (UTC)
"Next" and "Previous" Flexibility
Is it possible to have some flexibility in the "next" and "previous" settings, so that you can have more than one station as the next/preivous on the line? At present it seems that you can only have one, and this is not much use for stations before or after a junction. If there was some way of putting "Previous Stations: X or Y" that would be great. If there is already, please correct me and show me how!! Thank you. Chrisfow (talk) 00:24, 17 December 2008 (UTC)
Border widths
For a long time, I've noticed that if Template:Tlc is used inside route boxes commenced using Template:Tlx, some of the borders will appear double-width, because of a differing method in border specification, as seen at Shildon railway station.
In technical terms, Template:Tlx applies the border-collapse: separate; property to the table, and expects the cells in each row to have the bottom cell borders always suppressed, also selectively suppressing the left or right borders, so that only one border is drawn between any two adjacent cells. Template:Tlx does not apply border-collapse: separate;, and does not expect the row templates to specify any border suppression. This means that should a cell have its bottom border set, and the cell directly beneath have it top border set, two adjacent borders are drawn, which has the appearance of a double-width border. Similarly for the right and left borders of cells side by side. Less obviously, but equally visible, this causes the doubling of the width of the outer edges of the table - it gets one border from the table itself, and one from the cell inside.
We might be able to fix this by adding selective border suppression to Template:Tlx: I have created a prototype at Template:Rail line/sandbox, and set up some testcases. --Redrose64 (talk) 16:14, 11 November 2012 (UTC)
- Further: Template:Tlx also applies
style="border-top: 0px none; "where Template:Tlx etc. do not. --Redrose64 (talk) 14:08, 15 November 2012 (UTC)
Collapse functionality
There really needs to be a way to collapse all these services. At present, look at the article Haymarket railway station. The services chart takes up way too much space. I'm not sure what to do about this, but I'll leave this here in case anyone cares to do anything about it. RGloucester — ☎ 17:13, 24 February 2014 (UTC)
- This came up about a month ago on Talk:Filton Abbey Wood railway station/GA1. Template:Trim&oldid=Template:Trim Here's my response. --Redrose64 (talk) 17:27, 24 February 2014 (UTC)
What should go in the 'Route' box?
I'm not clear what should go in the route box. Is it just (a) the name of the TOC and then (b) the name of the railway? In the absence of template documentation, 'custom and practice' seems to say yes, that's all.
Except when it isn't: sometimes we also have a (c) Terminus-1 Template:Spaced ndash Terminus 2. Whether or not item c appears seems to be at the whim of editors, so some add it and others delete it. But sometimes it seems indispensable, especially when cross-country services are involved (see Template:Rws or Template:Rws for example) or for 'n-furcated' lines like the West Coast Main Line. Comments? — Preceding unsigned comment added by John Maynard Friedman (talk • contribs) 11:33, 15 September 2014
- As I understand it, for routes with a current service, the
|route=parameter holds the name of the TOC on the upper line, in normal size text; and the name of the route, line or service on the lower, in<small>...</small>tags. - The Reading/Oxford problem is one of a complicated service pattern. There are two main traffic flows for XC services to the north: those that at Birmingham go straight on towards Stafford, and those that back out again and head for Derby. Similarly, to the south, there are those which go no further than Reading, and those which back out again and head for Southampton. But there are many different origins, and destinations also: Bournenouth, Southampton C, Reading, Birmingham NS, Manchester Picc, York, Newcastle, Edinburgh (I may have missed some).
- We have differing editor attitudes: on the one hand there are people (like me) who would have the routebox show only the principal services - most trains at off-peak times are either Manchester-Bournemouth, or Newcastle-Reading, so those are the only two services that I would include. But there are some people who wish to sqeeze in every possible origin and destination, even for once-a-day services (like the last train of the day which only runs part of the route). This in my view is unnecessary overcomplication. --Redrose64 (talk) 14:55, 15 September 2014 (UTC)
- So you are saying that item c, the [primary] service being run, should always be shown? But surely that just duplicates the 'Service pattern' which has already been given under each TOC above? (and, as you say, it invites people to put in every destination).
- You do many more of these than I do: what is your sense of the consensus 'custom and practice'? My objective in this discussion is to create a proper 'template documentation' that is much needed for this template. --John Maynard Friedman (talk) 14:08, 16 September 2014 (UTC)
- As I see it, (c) has crept in over recent years based on the parameter in Template:Tlx. It used to be limited to routeboxes appearing in Metro station articles but then popped up in Crossrail stations. At best, it tells the reader what they already know. At worst, it adds another layer of complication as service patterns don't always allow for neat distinctions (e.g. Reading/Oxford), meaning that several rows would be needed to accurately reflect the situation. However, we're now straying into WP:NOTTIMETABLE territory. Surely the most simple solution is to follow the standard approach that routeboxes run from north to south, west to east. That way, we're only interested in the preceding and following stations without having to check TOC timetables to see if Bournemouth or Crinkley Bottom is actually the terminus for the service in question. Lamberhurst (talk) 16:22, 16 September 2014 (UTC)
- Template:Replyto I don't think that John Maynard Friedman is referring to the "towards" items in the left/right columns of routeboxes like this, but to the station pairs in the central column of routeboxes like this. --Redrose64 (talk) 19:19, 16 September 2014 (UTC)
- I see...I hadn't come across that before. Although I can understand how such an addition can be useful, adding such a level of detail poses difficulties in terms of keeping the routes indicated up-to-date for complex service patterns. The point is well-illustrated by the situation at Oxford. Today's timetable between 1128 and 1243 reveals three different XC services: Newcastle/Southampton, Reading/Newcastle and Manchester/Bournemouth. Only the third service is correctly referred to in the Oxford routebox with the first omitted entirely and the second inaccurately mentioned. And I haven't even checked the rest of the day's XC services. Lamberhurst (talk) 20:58, 16 September 2014 (UTC)
- The problem is particularly evident/severe in places like Oxford and Reading because the lines used by the XC services don't have pretty names like WCML or even EWRL, more a bit of this bit of that. As the template stands, this central box assumes that there will be such a nice name. Where it doesn't exist, people make something up like the Terminus-1 - Terminus-2 notation. Unfortunately that in turn becomes problematic if there are in fact no services from this station to one or other of those terminuses.
- We also have to think of the 'world-wide perspective' in proposing rules for the template: just taking two places at random - Gare de Lyon-Perrache and Bologna Centrale railway station - in all cases the middle box is used simply for the type of service (TGV, intercity, sleeper, regional) [which, IMHO, would be an improvement on the mess we have here]. Maybe it is just too late to stuff the cat back in the bag? --John Maynard Friedman (talk) 15:25, 17 September 2014 (UTC)
- If such detail is not given either at Perrache or Bologna, that gives further support to the notion that it is not needed here. As far as I can see, it appears to be the action of a minority of editors, and I would therefore suggest not continuing it. This Template:Trim&oldid=Template:Trim recent edit to Bletchley highlights the difficulties involved: the Southern service to MK from Croydon runs over the WCML, the Dudding Hill line, the WLL and the BML. Furthermore, the service has been known to start from South Croydon. The information there about the service is therefore inaccurate (but understandably so as the route is not well-known); why create a rod for our backs? Lamberhurst (talk) 11:15, 18 September 2014 (UTC)
- I see...I hadn't come across that before. Although I can understand how such an addition can be useful, adding such a level of detail poses difficulties in terms of keeping the routes indicated up-to-date for complex service patterns. The point is well-illustrated by the situation at Oxford. Today's timetable between 1128 and 1243 reveals three different XC services: Newcastle/Southampton, Reading/Newcastle and Manchester/Bournemouth. Only the third service is correctly referred to in the Oxford routebox with the first omitted entirely and the second inaccurately mentioned. And I haven't even checked the rest of the day's XC services. Lamberhurst (talk) 20:58, 16 September 2014 (UTC)
- Template:Replyto I don't think that John Maynard Friedman is referring to the "towards" items in the left/right columns of routeboxes like this, but to the station pairs in the central column of routeboxes like this. --Redrose64 (talk) 19:19, 16 September 2014 (UTC)
- As I see it, (c) has crept in over recent years based on the parameter in Template:Tlx. It used to be limited to routeboxes appearing in Metro station articles but then popped up in Crossrail stations. At best, it tells the reader what they already know. At worst, it adds another layer of complication as service patterns don't always allow for neat distinctions (e.g. Reading/Oxford), meaning that several rows would be needed to accurately reflect the situation. However, we're now straying into WP:NOTTIMETABLE territory. Surely the most simple solution is to follow the standard approach that routeboxes run from north to south, west to east. That way, we're only interested in the preceding and following stations without having to check TOC timetables to see if Bournemouth or Crinkley Bottom is actually the terminus for the service in question. Lamberhurst (talk) 16:22, 16 September 2014 (UTC)
Consistency in route (succession) boxes
I've used these (as a reader), and also edited a few. I've noticed that they often contain a number or errors and inconsistencies. At the very least, I would expect that if you started at the first station on a line and selected the "following station", and repeated this you would eventually get to the last station... (More difficult if you're dealing with an unused or historic railway where maybe not all stations have an associated article).
I recently tried to "virtually travel" from Birmingham (New Street) to Liverpool Lime Street (with intermediate stations Cosely, Wolverhampton, Penkridge, Stafford, Crewe, Runcorn, Liverpool Parkway). Also, for simplicity, I've not included visiting the smaller stations of Winsford, Hartford, and Acton Bridge (and striked them out in the following table).
The following table shows the route boxes in the order of travel:
| Preceding station | National Rail National Rail | Following station | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Terminus | style="background:#Template:LM colour; color:inherit; border-left: 0px none; border-right: 0px none; border-top:1px #aaa solid; border-bottom:0px none;" | | London Midland (Birmingham-Liverpool) (No. 1 - as shown at Birmingham New Street) |
style="background:#Template:LM colour; color:inherit; border-left: 0px none; border-right: 0px none; border-top:1px #aaa solid; border-bottom:0px none;" | | Coseley | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Birmingham New Street | style="background:#Template:LM colour; color:inherit; border-left: 0px none; border-right: 0px none; border-top:1px #aaa solid; border-bottom:0px none;" | | London Midland Birmingham-Liverpool (No. 2 - as shown at Cosely) |
style="background:#Template:LM colour; color:inherit; border-left: 0px none; border-right: 0px none; border-top:1px #aaa solid; border-bottom:0px none;" | | Wolverhampton | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Coseley | style="background:#Template:LM colour; color:inherit; border-left: 0px none; border-right: 0px none; border-top:1px #aaa solid; border-bottom:0px none;" | | London Midland Birmingham-Liverpool (No. 3 - as shown at Wolverhampton) |
style="background:#Template:LM colour; color:inherit; border-left: 0px none; border-right: 0px none; border-top:1px #aaa solid; border-bottom:0px none;" | | Penkridge | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Wolverhampton | style="background:#Template:LM colour; color:inherit; border-left: 0px none; border-right: 0px none; border-top:1px #aaa solid; border-bottom:0px none;" | | London Midland Rugby-Birmingham-Stafford Line (No. 4 - as shown at Penkridge) |
style="background:#Template:LM colour; color:inherit; border-left: 0px none; border-right: 0px none; border-top:1px #aaa solid; border-bottom:0px none;" | | Stafford | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| London Midland Liverpool-Birmingham (No. 5 - as shown at Stafford) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Stafford | style="background:#Template:LM colour; color:inherit; border-left: 0px none; border-right: 0px none; border-top:1px #aaa solid; border-bottom:0px none;" | | London Midland Birmingham - Liverpool (No. 6 - as shown at Crewe) |
style="background:#Template:LM colour; color:inherit; border-left: 0px none; border-right: 0px none; border-top:1px #aaa solid; border-bottom:0px none;" | | or Hartford or | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Liverpool South Parkway | style="background:#Template:LM colour; color:inherit; border-left: 0px none; border-right: 0px none; border-top:1px #aaa solid; border-bottom:0px none;" | | London Midland Liverpool-Birmingham (No. 7 - as shown at Runcorn) |
style="background:#Template:LM colour; color:inherit; border-left: 0px none; border-right: 0px none; border-top:1px #aaa solid; border-bottom:0px none;" | | or Hartford or | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Runcorn | style="background:#Template:LM colour; color:inherit; border-left: 0px none; border-right: 0px none; border-top:1px #aaa solid; border-bottom:0px none;" | | London Midland Birmingham New Street - Liverpool Lime Street (No. 8 - as shown at Liverpool Parkway) |
style="background:#Template:LM colour; color:inherit; border-left: 0px none; border-right: 0px none; border-top:1px #aaa solid; border-bottom:0px none;" | | Liverpool Lime Street | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Liverpool South Parkway | style="background:#Template:LM colour; color:inherit; border-left: 0px none; border-right: 0px none; border-top:1px #aaa solid; border-bottom:0px none;" | | London Midland Liverpool - Birmingham (No. 9 - as shown at Liverpool Lime Street) |
style="background:#Template:LM colour; color:inherit; border-left: 0px none; border-right: 0px none; border-top:1px #aaa solid; border-bottom:0px none;" | | Terminus
It goes reasonably well until you get the Runcorn, where (clicking on "following station") you get to Crewe - to go to Runcorn (Oh! Mr Porter). It begins to sort itself out after that but there are some other inconsistencies:
I've seen these sorts of errors/inconsistencies when following through different succession boxes (try the South Wales valley lines or the lines passing through Bristol Temple Meads). I'm quite happy to have a go at tidying this up, but have some questions:
Robevans123 (talk) 00:17, 26 February 2015 (UTC)
Script error: No such module "outdent". So here's what the stations on the Liverpool-Birmingham route should look like (I've left the station names in for now for ease of editing):
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||