Template talk:F1 Drivers Standings
Formula One Template‑class | |||||||
|
Semi-protected edit request on 29 May 2016
This edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
14 | Nico Hülkenberg | 7 | 15 | 15 | Ret | Ret | 6 |
---|
Maxjaja (talk) 16:37, 29 May 2016 (UTC) Please change Rank of Nico Hulkenberg from 7 to 6 for Monaco Grand Prix
Proposed change
I added a section to the talk page of the 2016 season related to this table Talk:2016_Formula_One_season#Results_and_standings. I don't want to create parallel discussions, so I am adding just a link to it here. Rks13 (talk) 15:59, 10 July 2016 (UTC)
Edit request
The standings read 1-2-3-5-4. Vettel and Kimi are correctly visually placed at 4th and 5th in the standings, respectively, but Vettel's position is still listed as "5" with Kimi's as "4". These numbers should be swapped.
Current
5 | Sebastian Vettel | 3 | DNS | 2 | Ret | 3 | 4 | 2 | 2 | Ret | 9 | 4 | 5 | 6 | 128 | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
4 | Kimi Räikkönen | Ret | 2 | 5 | 3 | 2 | Ret | 6 | 4 | 3 | 5 | 6 | 6 | 9 | 124 |
Proposed change
4 | Sebastian Vettel | 3 | DNS | 2 | Ret | 3 | 4 | 2 | 2 | Ret | 9 | 4 | 5 | 6 | 128 | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
5 | Kimi Räikkönen | Ret | 2 | 5 | 3 | 2 | Ret | 6 | 4 | 3 | 5 | 6 | 6 | 9 | 124 |
71.212.127.93 (talk) 01:55, 30 August 2016 (UTC)
- Done. Thanks. DH85868993 (talk) 02:07, 30 August 2016 (UTC)
Wrong total
Ricciardo's total points should be 161, not 151. 118.209.15.7 (talk) 00:16, 5 September 2016 (UTC)
- Thanks, his total had not been updated after Sunday. I have fixed it. PrimeHunter (talk) 00:35, 5 September 2016 (UTC)
Semi-protected edit request on 27 August 2018
This edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Danniel ricciardo standing should be 6th and not 5th there is two 5th and no one in 6th place 62.28.72.93 (talk) 08:29, 27 August 2018 (UTC)
- Done Fixed. Thanks. DH85868993 (talk) 09:18, 27 August 2018 (UTC)
Fastest lap
it would be nice to mark the driver that has the fastest lap. A way to do this is to add an "asterisk" next to the points received by the driver and add a note at the bottom that indicates its meaning. Otherwise there is no information on the table on why some drivers have more points than others with the same results. — Preceding unsigned comment added by 24.69.190.94 (talk) 18:52, 1 April 2019 (UTC)
- The driver who set fastest lap is already indicated by their result being in italics. DH85868993 (talk) 19:56, 1 April 2019 (UTC)
Fastest Lap Indicator
Any interest in changing the fastest lap indicator to something besides italic? Italic numbers are quite hard to differentiate. Perhaps underlining would be better? Krea (talk) 23:40, 14 July 2019 (UTC)
|
Above compares italic, asterisk and underlining for displaying fastest lap. AUS to GER (first 12 races) is a straight comparison, BEL to SIN (next 3 races) has 3 random drivers given the fastest lap using italics, RUS to MEX (next 3 races) has 3 random drivers given the fastest lap using asterisks, USA to ABU (final 3 races) has 3 random drivers given the fastest lap using underlining.
For me, italics is far too difficult to spot (BEL to SIN), and underlining is also not as clear as I hoped (USA to ABU). Using asterisks is the clearest, but it would look more ungainly where a dagger is also present; however, since it's pretty unlikely the two would ever be present together, and even if it did it wouldn't be the end of the world, then I think it should be the identifier used. Krea (talk) 00:56, 13 August 2019 (UTC)
Alternative ideas:
- using an overdot (<math>\dot{N}</math>):
- using an overbar (<math>\bar{N}</math>):
- formatting of the box (colour or border)
These alternatives are probably not a good idea. Alternatives 1 and 2 will need <math>...</math> tags. Alternative 3: if using a background colour, it would confuse the currently very nice colour usage. Colouring the numbers (especially with the coloured backgrounds) would probably not be very clear. If changing the border, it would be inconsistent with the current styling and would probably look really ugly. Krea (talk) 01:17, 13 August 2019 (UTC)
|
Comparison with italics (Driver_A), asterisk (Driver_B), addition symbol (Driver_C), and bullet (Driver_D). Comparing asterisk and the addition symbol, actually I think the latter is clearer. Likewise for using an addition symbol over a bullet. (There's also a nice consonance between the use of an addition symbol to mark the addition of a bonus point for fastest lap.) I will change the table to use the addition symbol on Monza qualifying Saturday (4 days' time). No doubt it will be reverted by someone, so I welcome objections, comments or suggestions below. Krea (talk) 20:04, 3 September 2019 (UTC)
Semi-protected edit request on 17 November 2019
This edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
update the template P1909 (talk) 20:46, 17 November 2019 (UTC)
- Edit requests are requests to make specific, precise edits, not general pleas for improvement. –Deacon Vorbis (carbon • videos) 21:17, 17 November 2019 (UTC)
- Done but @P1909: you are welcome to be bold and do it yourself.
SSSB (talk) 11:27, 18 November 2019 (UTC)
Semi-protected edit request on 8 December 2019
This edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Hello,
I have noticed that for the 2019 F1 drivers and constructors standings tables that poles and fastest laps are displayed using letters next to the position that the driver finished the race in. In my opinion the F1 2019 standings should revert to the old format of bold for pole position and italics for Fastest lap. It was a neat and simple way of displaying pole positions and fastest laps. There was no clutter in the small boxes given for finishing positions. It is like how the IndyCar standings are done which I have always disliked for the same reason as here. The normal format is simple, clean, easy to see (have had no issues seeing on computer or tablet) And do not see why it should change. This is just my opinion and I hope that F1 drivers and constructors standing can be kept to the way normally used.
Thanks,
Passionate F1 fan. 2407:7000:8747:6724:8109:41F7:77F5:86D0 (talk) 11:14, 8 December 2019 (UTC)
- Hi,
These changes were made after a long discussion at Wikipedia talk:WikiProject Formula One#Fastest Lap Indicator (and Table Key) - to cut a long story short, this change has been made to imporve accessability. You are of course welcome to discuss these changes at the afore linked centralised discussion if you think they can be imporved or to otherwise throw your opinion in to the ring. Thanks,
SSSB (talk) 11:37, 8 December 2019 (UTC)
Remove semi-protection
Is anyone able to do that?--95.251.49.173 (talk) 15:50, 27 April 2020 (UTC)
- You can place a request at WP:RPP.
SSSB (talk) 16:00, 27 April 2020 (UTC)- In which section do I have to ask correctly it? Thanks @SSSB:--95.251.49.173 (talk) 11:03, 28 April 2020 (UTC)
- WP:RPP#Current requests for reduction in protection level. But as that section suggests you should first ask the admin who added the protection User:HJ Mitchell.
SSSB (talk) 11:37, 28 April 2020 (UTC)- Thanks anyway. I've changed my mind. I will not do that.--95.251.49.173 (talk) 11:50, 28 April 2020 (UTC)
- WP:RPP#Current requests for reduction in protection level. But as that section suggests you should first ask the admin who added the protection User:HJ Mitchell.
- In which section do I have to ask correctly it? Thanks @SSSB:--95.251.49.173 (talk) 11:03, 28 April 2020 (UTC)
Semi-protected edit request on 20 July 2020
This edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Hello, I am an established Formula 1 fan and started editing the pages and driver stats after the most recent Grand Prix and I believe I earned the right to be able to edit this but if you feel otherwise, That is completely fine with me. Farrisd (talk) 23:16, 20 July 2020 (UTC)
- You will be able to edit this template and other protected pages when you become autoconfirmed.
5225C (talk • contributions) 23:19, 20 July 2020 (UTC) - Not done: this is not the right page to request additional user rights. You may reopen this request with the specific changes to be made and someone will add them for you, or if you have an account, you can wait until you are autoconfirmed and edit the page yourself. Jack Frost (talk) 01:07, 21 July 2020 (UTC)
Change
Pérez Withdrawn from the 2020 British Grand Prix Formula Uuno (talk) 19:50, 30 July 2020 (UTC)
Semi-protected edit request on 1 August 2020: Change WD for Sergio Perez
This edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
For the British Grand Prix, Sergio Perez' result should be changed from WD (Withdrawn) to DNP (Did not participate) as he was entered into the weekend but did not take part in any session. Withdrawn (WD) is used for drivers who were entered for the race, but were replaced before qualifying and after taking part in practice (an example would be Felipe Massa in the 2017 Hungarian Grand Prix). Mark John Mallia (talk) 10:32, 1 August 2020 (UTC)
- He shouldn't have anything at all next to his name for this race, as he was replaced prior to the first session, with a new entry list being drawn up, voiding the previous entry list. Bretonbanquet (talk) 11:08, 1 August 2020 (UTC)
- Good point, I'll keep this unanswered until someone changes the result to a blank cell then. Mark John Mallia (talk) 13:35, 1 August 2020 (UTC)
- @Mark John Mallia: this is currently being discussed at Talk:2020 Formula One World Championship where you are welcome to contribute. Until then it would be undue to make this blank.
SSSB (talk) 08:52, 2 August 2020 (UTC) - Your description does not match with how use the WD code in the past. That has simply been applied to entrants who appeared on a entry list and later officially withdrew their entry without having qualified (otherwise it would be DNS), regardless of whether they actually drove in a session.Tvx1 21:12, 6 August 2020 (UTC)
- @Mark John Mallia: this is currently being discussed at Talk:2020 Formula One World Championship where you are welcome to contribute. Until then it would be undue to make this blank.
- Good point, I'll keep this unanswered until someone changes the result to a blank cell then. Mark John Mallia (talk) 13:35, 1 August 2020 (UTC)
Qualifying classification link
It might be convenient for the readers to have the pole position ("P") indicator in the table linked to the corresponding GP qualifying classification. Now that classification is hidden behind the "Report" link, and you have to dig further to figure out how the session went. Ximaera (talk) 22:39, 3 August 2020 (UTC)
- Adding such a link would only save readers one click and frankly it wouldn't be easy to insert. It don't think the benefit would be that great. Also how the session "went" isn't really relevant to the standings.
SSSB (talk) 07:49, 4 August 2020 (UTC) - I agree with SSSB. I don't see how this link would be useful.
5225C (talk • contributions) 08:13, 4 August 2020 (UTC)
Stroll as Did Not Practice: Eifel Grand Prix
I think Lance Stroll should be DNP on the standings For EIF JamesVilla44 (talk) 17:51, 11 October 2020 (UTC)
- Based on other keys (e.g. {{Template:Motorsport driver results legend}}, I believe DNP is meant to stand for "Did Not Participate" (as in, the competitor was present at the track and chose not to be involved) rather than "Did Not Practice" (Hülkenberg could be DNP then). Regardless, because Stroll was replaced on the entry list, withdrawn is the most appropriate result to record.
5225C (talk • contributions) 23:13, 11 October 2020 (UTC)
Sainz Broke
Sainz is showing results for the three GPs that haven't happened, but it looks like they aren't included in the total. This should leave a notification for whoever can edit, right? — Preceding unsigned comment added by MJCato (talk • contribs) 03:16, 19 November 2020 (UTC)
- This was vandalism of {{F1R2020}} and has been reverted.
5225C (talk • contributions) 03:54, 19 November 2020 (UTC)
Sprint Qualifying at the British Grand Prix
Since Sprint Qualifying has been confirmed for the British GP, shouldn't we add a second column below the British Grand Prix? It would look like this:
|
|
Notes:
- † – Driver did not finish the Grand Prix, but was classified as he completed more than 90% of the race distance.
Poklane 23:45, 5 June 2021 (UTC)
- @Poklane: Please see the discussion at Talk:2021_Formula_One_World_Championship#Splitting_British_GP_Column_on_Race_results_for_SR. DH85868993 (talk) 06:57, 6 June 2021 (UTC)
- No, we shouldn’t. Sprint qualifying positions do not count towards the championship. There are only some bonus points for the top three. Adding all positions would be confusing in case drivers are tied on points.Tvx1 17:41, 10 June 2021 (UTC)
Use of Template:F1R2021 for 2021 season?
I'm just curious: why aren't we using Template:F1R2021 for this year's season? It's currently the data source for the Constructor's Championship template and the results on individual driver's pages. Would the community be open to changing this template to use Template:F1R2021 ? — Preceding unsigned comment added by Cin316 (talk • contribs) 19:31, 6 June 2021 (UTC)
- We tried to do that but we hit the WP:transclusion limit for 2021 Formula One World Championship.
SSSB (talk) 19:52, 6 June 2021 (UTC)- Ahhh, that makes sense. I'm taking a stab at converting Template:F1R2021 to a Lua module. You can see my progress here. I'll certainly bring this up to the community for feedback if my experimentation makes it look like we should switch.
– Cin316 (talk) 03:52, 10 June 2021 (UTC)- @Cin316: Thanks for having a go at converting Template:F1R2021 to a Lua module. Something to consider when designing the module is that on rare occasions, we need the background colour to not "match" the result, e.g. where a driver finishes in the top 10 but no points are awarded (see the McLaren row of 2007_Formula_One_World_Championship#World_Constructors'_Championship_standings as an example). So (on the assumption that we'll eventually adopt your module, and that it will be used as a model for future years) if you're tossing up between two ways of doing something and one would make non-standard background colours harder and one would make them easier, then I'd suggest going for the one that makes them easier. But it's not something we definitely need for 2021 so don't worry about it too much. (Off the top of my head, I can imagine something like the module supporting an optional extra parameter which lets the caller specify the background colour - for the majority of cases, the caller would not specify the parameter and the module would determine the colour, but the caller could specify the parameter and hence override the default colour if required, e.g. the 2007 WCC table). DH85868993 (talk) 05:10, 10 June 2021 (UTC)
- @Tvx1: pinging Tvx1, who I seem to recall suggested this in the past.
SSSB (talk) 10:28, 10 June 2021 (UTC) - Hi, Cin316. I'm very happy to read that you are willing to create a lua module for us. I had indeed suggested that our wikiproject started using lua modules some time ago. I'm not familiar enough with lua myself though to create an entire module myself. However, I think we would be more helped with a general module for creating our results tables rather than a module that is only intended for one specific season.Tvx1 16:27, 11 June 2021 (UTC)
- Ahhh, that makes sense. I'm taking a stab at converting Template:F1R2021 to a Lua module. You can see my progress here. I'll certainly bring this up to the community for feedback if my experimentation makes it look like we should switch.
- @Cin316: just curious, has this been frozen for now? cherkash (talk) 22:35, 15 September 2021 (UTC)
- @Cherkash: Yeah, unfortunately I haven't had time to work on it lately. It shouldn't be too difficult, but I'm busy at the moment. If anyone else wants to take a stab at it, the code is on that template page for anyone to edit. Cin316 (talk) 03:22, 20 September 2021 (UTC)
Google sheets to automate standings tables
(Also cross-posted to Constructors as an example, and to the wikiproject talk page)
I've put together a google sheets to fill in the race results which will automatically generate this table: 2023 Formula 1-2-3-E wiki tables. It's currently set to comment-only to avoid disruptive editing, might be worth a discussion as to how editing permissions on this should work going forward.
In lieu of having any actual results to load into it for now, I've put in some sample data (mostly the first few races of 2022, including a sprint) to test:
|
Things the sheet CAN do:
- Fill in the correct background colour for the position
- Add superscript pole / sprint position / fastest lap
- Calculate points for the race, sprint, and fastest lap (and if you get a point for fastest lap at all)
- Sort the table, including up to two iterations of countback
- Generate and sort the Constructors' table as well
Things I'll have to do manually:
- Deal with mid-season driver changes (e.g. if Lance Stroll can't drive in Bahrain, or if Red Bull swaps their second driver, etc.)
- Remake the table for 2024
Things the sheet CAN'T do:
- Handle unexpected formatting, e.g. in 2007 when McLaren were disqualified mid-season so all their results from then on were technically non-points-scoring positions (i.e. blue)
- Apply countback more than twice (see P16 in the example)
- Put a single P in pole position in the one day between qualifying and the race
How the sheet will be used:
Race positions are added into the top-left table (F3:AH22). Pole position and fastest lap are added as driver numbers in rows 24 and 25.
Columns DG-EG on rows 3-22 produce the sorted Drivers' Championship table. You copy/paste the cells into a simple text editor (I use Notepad++) and replace all instances of a tab with a new line (in Notepad++ this is \t → \n with "Extended" search mode on). Then, just copy/paste that into the main body of the table here.
If something strange happens track-side (e.g. McLaren's 2007 DSQ), manual adjustment may be needed. I'll aim to hardcode any one-off weirdness into the sheet by the next race.
Please let me know what you think! AsmodeanUnderscore (talk) 15:00, 2 March 2023 (UTC)
- Please make any comments at the WP:CENTRALised discussion at Wikipedia talk:WikiProject Formula One#Google sheets to automate standings tables. SSSB (talk) 16:35, 2 March 2023 (UTC)
Adding "Team" to Driver Standings table
I tried to add a team column to this table and BryOn2205U reverted it. I think this is a useful addition to the chart. The fact that team information has been missing from the chart has always bothered me. Confirming a driver's team requires checking their page, a time-consuming process.
This was a good-faith edit that improves the table without, to my knowledge, exceeding the transclusion limit, and it is in line with F1's practices. I also noticed that BryOn2205U has been warned about unnecessary reversion before.
I am reverting BryOn2205U's reversion and would remind them that an edit war is against Wiki policy: Revert Only When Necessary. Please change or edit the additions to improve them, but please do not just destroy them wholesale. Wikipedia belongs to everyone. Knowledgeispow333r (talk) 22:12, 28 May 2023 (UTC)
- This is the drivers' standings, so teams aren't relevant here. We've discussed this before, and consensus has never developed for them to be included. It's not the purpose of the WDC table to show the WCC as well, nor is it the purpose of the WCC table to show the WDC results. It gets unwieldy and overcomplicated the second a driver changes team mid-season. 5225C (talk • contributions) 02:31, 29 May 2023 (UTC)
- Changes midseason are simple: Team listed is current team. It certainly works for the F1's official standings, which I linked to above.
- How do we determine consensus?
- Wikipedia is supposed to be nimble and open to all. A Knowledgeispow333r (talk) 04:42, 29 May 2023 (UTC)