Template talk:Infobox station

Merger proposal
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)
 * 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)
 * 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.  Cards   84664   23:45, 26 September 2020 (UTC)
 * It would have been better to merge into  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. -- Red rose64 &#x1f339; (talk) 20:55, 27 September 2020 (UTC)
 * 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)

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

Difference in source code please see:

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)


 * 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)
 * Changed from station number to stop number in sandbox. Purin128AL (talk) 05:13, 13 June 2023 (UTC)
 * Looks good. I've added the autoheaders feature in the sandbox. &mdash; Martin (MSGJ · talk) 11:43, 13 June 2023 (UTC)
 * ✅ Izno (talk) 20:00, 20 June 2023 (UTC)
 * 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)
 * The parameters needed to be added to the /doc subpage as well: @Izno for next time. Mackensen (talk) 19:25, 22 July 2023 (UTC)
 * Can you give an example, because I don't know how the /doc page could affect that? &mdash; Martin (MSGJ · talk) 17:45, 23 July 2023 (UTC)
 * If they are using VE, it depends upon the TemplateData for which parameters to suggest. -- Red rose64 &#x1f339; (talk) 18:39, 23 July 2023 (UTC)

Template-protected edit request on 30 April 2024
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.  Cards   84664   18:13, 30 April 2024 (UTC)
 * ✅ 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)