Merger proposal

edit

I propose to merge Infobox London Station into Infobox station. I think that the content in the London station template can easily be replicated in infobox station just like the move of Infobox GB station into Infobox station. Smithr32 (talk) 20:33, 26 September 2020 (UTC)Reply

I'm not sure it should be merged. The biggest difference is the multiple sets of passenger figures under different headings. I am not sure how to smoothly implement that, whilst retaining generality for use in other stations, and also preventing misuse of the generality. Unless a good proposal to get around that is found, I do not think it's likely to be a good merge. ProcrastinatingReader (talk) 21:26, 26 September 2020 (UTC)Reply
We should still hold on with London station, it is a situation similar to New York City Subway station. Both should be scrutinized before any mergers are put forward. Cards84664 23:45, 26 September 2020 (UTC)Reply
It would have been better to merge {{Infobox GB station}} into {{Infobox London station}} because the latter is, by and large, a superset of the former - only a few features of GB station are not provided by London station. --Redrose64 🌹 (talk) 20:55, 27 September 2020 (UTC)Reply
@Smithr32: looked into this more recently, this is probably more feasible than I originally imagined above. Played around with a few demo conversions in my sandbox (the first two), very roughly. I think the key here is on presentation of the passenger information. The data can be carried over given |system= in {{Rail pass box}}, but not sure on the presentation of that data atm. ProcrastinatingReader (talk) 08:48, 28 November 2020 (UTC)Reply

Add tram station capability into infobox

edit
Moonee Ponds Junction
PTV tram and bus interchange
General information
LocationCorner Ascot Vale, Mount Alexander & Pascoe Vale Roads, Moonee Ponds
Australia
Coordinates37°46′02″S 144°55′30″E / 37.76715°S 144.92488°E / -37.76715; 144.92488
Owned byVicTrack
Platforms2 side
Tram routes   
Tram operatorsYarra Trams
Bus routes404, 469, 472, 476, 477, 483, 504, 505, 506, 508
Bus stands9
Bus operatorsCDC Melbourne
Dysons
Kastoria Bus Lines
Moonee Valley Coaches
Transit Systems
Connections
Other information
Stop number12
Fare zoneMyki zone 1
History
Opened24 July 2002
Services
Preceding station   Yarra Trams Following station
Moonee Valley Civic Centre
towards Airport West
Route 59 Montgomery Street
Terminus Route 82 Chaucer Street
towards Footscray
Location
 

I am testing the use of this infobox for major tram stations/stops and bus interchanges. I have added |number for station number (not code), |tram_routes and |tram_operators for display of both bus and tram routes/operators. Example as on the right:

Difference in source code please see: [1]

Is this a good idea? I have made my edit in the sandbox to show how it works. Purin128AL (talk) 06:58, 12 June 2023 (UTC)Reply

I think Yarra Trams call them by “stop numbers”, Adelaide Metro and Transperth do the same for their 5 digit stop numbers for buses, trams, trains, ferries, whatever. Fork99 (talk) 09:32, 12 June 2023 (UTC)Reply
Changed from station number to stop number in sandbox. Purin128AL (talk) 05:13, 13 June 2023 (UTC)Reply
Looks good. I've added the autoheaders feature in the sandbox. — Martin (MSGJ · talk) 11:43, 13 June 2023 (UTC)Reply
  Done Izno (talk) 20:00, 20 June 2023 (UTC)Reply
Using the Tram routes and Tram operators parameters will now trigger the using unknown parameter warning. How can that be fixed? Purin128AL (talk) 18:12, 22 July 2023 (UTC)Reply
The parameters needed to be added to the /doc subpage as well: [2] @Izno for next time. Mackensen (talk) 19:25, 22 July 2023 (UTC)Reply
Can you give an example, because I don't know how the /doc page could affect that? — Martin (MSGJ · talk) 17:45, 23 July 2023 (UTC)Reply
If they are using VE, it depends upon the TemplateData for which parameters to suggest. --Redrose64 🌹 (talk) 18:39, 23 July 2023 (UTC)Reply

Template-protected edit request on 30 April 2024

edit

Regarding the Location and Notes headers, I would like to add the option of having these headers be collapsible, using these edits. This will be useful for keeping infobox height consistent between articles that have location maps and articles that do not use route_map. This will not collapse the headers by default. Cards84664 18:13, 30 April 2024 (UTC)Reply

  Done I made some tweaks to the code your proposed. The new parameters are: |location_state= -> collapse "Location" header, |map_state= -> collapse "Route map" header, |footnotes_state= -> collapse "Footnotes" header. |map_state= is badly named (should be "route_map_state"), but should be kept for backwards compatibility. * Pppery * it has begun... 20:52, 10 May 2024 (UTC)Reply

Documentation section on External style template may need updating

edit

The page Oakland Coliseum station has a station infobox in which titles have insufficient contrast with their background. But if I look at the infobox code on that page, I only find the parameter:

style = BART

and no color coding. If I read the {{Infobox station/doc#External_style_template}} documentation, it says that the above code should correspond to an existing {{BART style}} template. But that template doesn't exist. It appears instead that the color is coming from Module:Adjacent stations/BART.

The section on External style template may need updating from:

The |style= parameter is used to specify the name of the template where the styling is defined; the template's name must end with the word "style", but this word must be omitted from the |style= parameter. For example, |style=DB-IC will use the {{DB-IC style}} template.

to:

The |style= parameter is used to specify the name of the template or module where the styling is defined. If a template, the template's name must end with the word "style", but this word must be omitted from the |style= parameter. If a module, the module's name would be preceded by "Adjacent stations". For example, |style=DB-IC would use either the {{DB-IC style}} template or Module:Adjacent stations/DB-IC.

I realize there is the note:

For systems which have an Adjacent stations module defined the |style2= parameter may be used to specify a sub-style within that system. For example, |style2=Amtrak old used with |style=Amtrak will return the pre-Acela Amtrak heritage colors from Module:Adjacent stations/Amtrak.

but that doesn't make it clear that the module can take the place of the style template as well.

I would make the edit but I'm not sure I understand all the nuances.

Thisisnotatest (talk) 03:23, 5 October 2024 (UTC)Reply