Misplaced Pages

talk:WikiProject Weather: Difference between revisions - Misplaced Pages

Article snapshot taken from Wikipedia with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.
Browse history interactively← Previous editContent deleted Content addedVisualWikitext
Revision as of 19:57, 18 April 2022 editLightandDark2000 (talk | contribs)Autopatrolled, Extended confirmed users, Pending changes reviewers, Rollbackers62,349 edits →Bold titles in article leads for events without formal names: We really should be looking at each article individually, instead of imposing a single, general, wide-ranging approach.← Previous edit Latest revision as of 22:32, 15 January 2025 edit undoJotamar (talk | contribs)Extended confirmed users12,309 edits →Cool vs Cold: new sectionTag: New topic 
Line 1: Line 1:
{{talk header|wp=yes|sc1=WT:WEATHER|sc2=WT:WPWX|bot=Lowercase sigmabot III|age=30|minthreadsleft=4}} {{talk header|wp=yes|sc1=WT:WEATHER|sc2=WT:WPWX}}
{{WikiProject banner shell|1= {{WikiProject banner shell|
{{WikiProject Weather {{WikiProject Weather}}
}}
}} }}
{{User:MiszaBot/config {{User:MiszaBot/config
| algo = old(30d) | algo = old(50d)
| archive = Misplaced Pages talk:WikiProject Weather/Archive %(counter)d | archive = Misplaced Pages talk:WikiProject Weather/Archive %(counter)d
| counter = 1 | counter = 5
| maxarchivesize = 150K | maxarchivesize = 150K
| archiveheader = {{Automatic archive navigator}} | archiveheader = {{Automatic archive navigator}}
| minthreadstoarchive = 1 | minthreadstoarchive = 1
| minthreadsleft = 4 | minthreadsleft = 5
}} }}
{{Page views}} {{Page views}}


==2024–25 WikiProject Weather Good Article Reassessment ==
== Space weather task force ==
<!-- ] 15:24, 23 January 2026 (UTC) -->{{User:ClueBot III/DoNotArchiveUntil|1769181847}}
] {{Small|1='''Bumping thread'''&#32;for 180 days days. ]<sup>]</sup> 14:43, 1 July 2021 (UTC)}}<!-- ] 14:43, 29 June 2031 (UTC) -->{{User:ClueBot III/DoNotArchiveUntil|1940510623}}
A few of us decided off wiki to make a space weather task force to cover the branch of meteorology dedicated to space weather. We need to outline every article that should be included here. ]<sup>]</sup> 00:55, 1 July 2021 (UTC) I would like to announce that a new task force has been created to re-examine the status of every GA in the project. Many good articles have not been reviewed in quite a while (15+ years for some) and notability requirements have changed quite a bit over the years. The goal of this task force is to save as many articles as possible. Anyone not reviewing an article may jump in to help get it up to par if it does not meet the GA requirements. The process will start officially on February 1 and will continue until every article has been checked and either kept or delisted. The task force may be found at ]. ], ]<sup>]</sup> 15:22, 26 January 2024 (UTC)
:{{Ping|Hurricanehink}} What thoughts would you have on this? ]<sup>]</sup> 02:00, 1 July 2021 (UTC)
::I love the idea. Misplaced Pages should be thorough and reflect the body of information that is out there. I believe we might need an article for ], if we want to be thorough. I believe our mission should be as thorough as possible, with as much organization as possible, identifying a logical structure to all of the information presented. Some of these redlinks and stubs might one day be the best source of information for researchers who haven't even been born yet. ♫ ] (<small>]</small>) 17:52, 1 July 2021 (UTC)
:{{ping|Ruslik0|Serendipodous|Owllord97}} Hello, I was wondering if you would be interested in having cooperation between our two projects. I would be interested to hear your input on what articles should be included in this taskforce. I have formed a preliminary list below of ones I have seen and feel should be included. ]<sup>]</sup> 00:36, 2 July 2021 (UTC)
], obviously. ] and ] are the mechanisms generating the solar wind. ] and ] if we're restricting ourselves to Earth, ] and ] if we're not. <b>]]<span style="color: #00b;">]</span></b> 16:06, 4 July 2021 (UTC)


;Articles under review
<s>*'''Weak Oppose''' creation. Space weather is distinct from Earthly weather. I guess we could include the climate articles for each planet in WPWeather, but solar storms and the like are quite unrelated to weather. ] (]) 17:51, 4 July 2021 (UTC)</s>
*] (])
**{{ping|Destroyeraa}} I think it's worth including some of the space stuff in the article, as it has a big impact on our weather and the way we forecast it. For example, Katrina was partially attributed to . However, my biggest question with the whole project is how far we should go with things where the weather played an important role and potentially changed history like World War 2 (D-Day or the German invasion of Russia) or the Miami Building Collapse.] (]) 20:10, 4 July 2021 (UTC)
*] (''']''')
** We need to cover all forms of weather as that is what this project is about. We can't pick and choose which ones we do and which we don't. Space storms have had a profound impact on people in the past and should be covered. ]<sup>]</sup> 20:17, 4 July 2021 (UTC)
*] (''']''')
**This isn't really up for a vote. WikiProject Weather was set up to cover all areas of weather in general, and it was already decided that we would have a Space Weather Task Force to address the topic of ] itself. Also, no, space weather is definitely ''still'' ]. The only difference is that it happens in space, rather than on Earth. Why should we exclude space weather from this project? There isn't any good reason for doing so. This is ''WikiProject Weather'', NOT WikiProject Earth Weather. And space weather also constitutes a separate branch of meteorology, so it definitely warrants inclusion in this project. Given the significance and scope of space weather, the only other alternative would be to set up a separate WikiProject for space weather, but that would just result in a mostly-inactive project (like WPNTS) with numerous overlaps with both WikiProject Weather and WikiProject Astronomy, so this option is better. For the record, I '''support''' the creation of the Space Weather Task Force and its proposed organizational structure, as is. This branch of meteorology definitely needs to be covered in a general weather project, and I think that the organizational structure proposed below is an excellent one. ''''']''''' 🌀 (]) 20:58, 4 July 2021 (UTC)


== List of tornadoes in XY trivia concerns ==
===Organization===
*] (top)
:*]
:*]
:*]
:*]
:*]
:*]
::*]
::*]
::*]
::*]
::*]
::*]
::*]
::*]
::*]
::*]
::*]
::*]
::*]
:*]
:*]
::*]
::*]
::*]
::*]
::*]
::*]
::*]
::*]
::*]
::*]
::*]
::*]
::*]
::*]
::*]
::*]
::*]
::*]
::*]
::*]
::*]
::*]
::*]
::*]
::*]
::*]
::*]
::*]
::*]
::*]
:*]
:*]
:*]
:*]
:*]
:*]
:*]
:*]
:*]
:*]
:*]
:*]
:*]
:*]
:*]
:*]
:*]
:*]
:*]
:*]
*]
:* ]
:* ]
:* ]
:* ]
:* ]
::*]
::*]
::*]
:* ]
:* ]
::*]
:* ]
:* ]
:* ]
:* ]
:* ] - Split?
::*]
::*]
::*]
:* ]
:* ]
:* ]
:* ]
:* ] - Split?
::*]
::*]
:* ]
:* ]
:* ]
::* ]
<!--More exo planets with atmosphere details-->
:*]
::*]
:::*]
:::*]
:::*]
:::*]
::*]
:::* ]
:::* ]
:::* ]
::*]
:::* ]
:::* ]
:::* ]
:::* ]
:::* ]
:::* ]
:::* ]
*]
:*]
*] (high)
:*]
:*]
:*]
:*]
:*]
:*]
:*]
::*]
::*]
::*]
::*]
:*]
:*]
:*]


A user recently added tags to a lot of articles including ] stating that the article contained overly trivial content appealing only to a specific audience. I disagree with this assertion, so upon removing these tags and explaining in the edit summary that the article is standard, the user reinstated the tags and stated they're going to stick with this assertion even if it is a project-wide standard. So, I suppose, consider this a heads-up for a future RfC, because I have aspirations of getting the 31 March outbreak to a good / featured topic and these tags are killing those plans in their tracks. ] (]) 20:59, 6 December 2024 (UTC)
== RfC: Changing the color scheme for storm colors to make it more accessible ==
{{User:ClueBot III/DoNotArchiveUntil|1640145680}}
{{anchor|rfc_8CBBD83}}Which color scheme is more accessible?


:It would probably be good to ping this user in the article's talk page and ask for specific details on what they mean before escalating further. <span style="color:#006400">''']''' <sub>''(he/him)''</sub></span> (]) 21:47, 6 December 2024 (UTC)
The current colors have been used across weather for the past decade. I believe these colors are hard to distinguish between on track maps for the dots, particularly between the Category 1-4 range. There simply isn't enough contrast between the colors to tell them apart (C1 and C2, C2 and C3, C3 and C4). This has presented a challenge for me as a reader and editor with normal color vision and decent eyesight with glasses. This issue would be even worse for color-blind editors. On the grounds of ], I am proposing a change to the below SSHWS colors, which increase the contrast between the hurricane colors. To summarize these changes, the Tropical Depression color was lightened ever so slightly, the Tropical Storm and Category 1 colors were left untouched, Category 2 was darkened, the current Category 4 and 5 colors were moved down to 3 and 4, respectively, and a new purple color was introduced to fill the empty Category 5 spot. These changes would apply to track maps and infoboxes for weather articles. I would also propose adjusting the colors used for the infoboxes for other scales to match the changes being proposed here for SSHWS so we maintain a mostly-uniform color scale for the different tropical cyclone and weather scales. Below are tables of the old colors and proposed changes. I have also included a side-by-side comparison between the two color schemes for ]'s track. ]<sup>]</sup> 02:55, 17 November 2021 (UTC)
::The specific diff is ] and the edit summary back-and-forth went as such:
:Some portions of the above are no longer accurate due to changes made to improve the overall scale. ]<sup>]</sup> 03:44, 18 November 2021 (UTC)
::* 2 December: <q><nowiki>Added {{Excessive examples}} and {{Overly detailed}} tags</nowiki></q>
::* 6 December: <q>Undid revision 1260738230 by Fram (talk) remove tags - this is a standard "list of tornadoes in xy outbreak" page and this one shouldn't be singled out, if there's a problem with these page's notability it'd be better to take it to Wikiproject Weather instead of this page</q>
::* 6 December: <q>Undid revision 1261573129 by Departure– (talk) If the issues xith this page are standard with this project, then geel free to alert the project thzt they will have to cleanup the other articles as well. This is a list with way too much trivia</q>
::I understand their assertion and think that it would have been made inevitably. @], could you please clarify your specific concerns regarding the "list of tornadoes in xyz" page format? I understand your position is that these pages consist entirely of trivia outside the scope of Misplaced Pages. I don't agree with that position but if you have any further comments please do share. ] (]) 22:38, 6 December 2024 (UTC)
:::Thank you for raising this and pinging me. I´ll have more time to answer on Monday probably. I don´t consider the whole list to be trivia, but way too many if the minor tornadoes and their (lack of) damage and so on is of no importance at all. ] (]) 22:51, 6 December 2024 (UTC)
::::That's a fair assessment to make, but consider also that the list of tornadoes is usually included in the outbreak's article itself, and is usually only split off once it reaches 100 entries or so. If you want a really extreme example of this, see ] or ] - these both have nearly double what the 31 March outbreak article has, and having them as separate from the outbreak's article seems obvious. I should also state that the list articles can be useful in illustrating the widespread nature of any given tornado outbreak, and remember that even a "weak" EF1 tornado can change lives, as we saw at the ]. Even EF2 / EF3 tornadoes can fail the notability test for article sections, even if they have plenty of coverage and do deserve at least a mention in reference to the outbreak, and the list articles do just that. Once you have those, it's clear that including even the weak tornadoes that caused no human cost should be included. I'll compare it here to ] which has a list and brief description of each episode - as a whole, these episodes have enough information to comprise a list, even those with bare-bones notability and importance. Their absence would be detrimental to the list as a whole. ] (]) 23:03, 6 December 2024 (UTC)
:::::An episode seen by 300,000 people in the US alone, shown in other countries, repeated, perhaps a DVD, ... vs. a tornado which caused little or no damage or is only seen by some security camera or one or two people. More on monday! ] (]) 23:13, 6 December 2024 (UTC)


This list (and many similar ones) want to describe every single tornado, no matter how minor. I see no reason why we would want to have so much unimportant, minute details, taking away the attention of the actual more major tornadoes by putting every little thing down. We don't do this for other events or accidents, we wouldn't list every car accident or building fire because some of them are important, notable, deadly, and we also don't list every damaged property, affected village, uprooted tree in the case of non-tornado storms. ... In the ], we have 146 tornadoes, 12 of them major (EF3/4), 32 average, and 103 minor or unknown. Some of these minor ones are more notable than others, due to where or when they happened, but the vast majority are really of very passing interest only. Briefly mentioning the minor ones as groups (genre "14 EF0 en EF1 tornadoes occurred in Wisconsin, causing damage to properties and uprooting trees") and only giving more attention to the more notable ones would solve ] issues, not inundating the reader in countless details where minor and major stuff is given equal weight. ] (]) 13:34, 9 December 2024 (UTC)
=== Proposed color changes ===
==== Color comparison table ====
<div style="text-align: center">
{| style="display: inline-block"
| style="vertical-align: top" |
{| class="wikitable" style="text-align: center; margin-top: 0"
|+ Saffir-Simpson Hurricane Wind Scale colors
! rowspan="2" | Category !! colspan="2" | Normal !! colspan="2" | Protanopic !! colspan="2" | Deuteranopic !! colspan="2" | Tritanopic
|-
! <abbr title="Current">C</abbr> !! <abbr title="Proposed">P</abbr> !! <abbr title="Current">C</abbr> !! <abbr title="Proposed">P</abbr> !! <abbr title="Current">C</abbr> !! <abbr title="Proposed">P</abbr> !! <abbr title="Current">C</abbr> !! <abbr title="Proposed">P</abbr>
|-
| Tropical Depression
| style="width: 32px; height: 32px; background-color: #5EBAFF" |
| style="width: 32px; height: 32px; background-color: #5ABEF7" |
| style="width: 32px; height: 32px; background-color: #9CAFF6" |
| style="width: 32px; height: 32px; background-color: #a0b1ee" |
| style="width: 32px; height: 32px; background-color: #92B0FF" |
| style="width: 32px; height: 32px; background-color: #97b1fb" |
| style="width: 32px; height: 32px; background-color: #47C2D2" |
| style="width: 32px; height: 32px; background-color: #44c3d3" |
|-
| Tropical Storm
| style="width: 32px; height: 32px; background-color: #00FAF4" |
| style="width: 32px; height: 32px; background-color: #10F9DF" |
| style="width: 32px; height: 32px; background-color: #E1DDE3" |
| style="width: 32px; height: 32px; background-color: #e5dccf" |
| style="width: 32px; height: 32px; background-color: #E7D9FB" |
| style="width: 32px; height: 32px; background-color: #edd7ea" |
| style="width: 32px; height: 32px; background-color: #83F0FF" |
| style="width: 32px; height: 32px; background-color: #78efff" |
|-
| Category 1
| style="width: 32px; height: 32px; background-color: #FFFFCC" |
| style="width: 32px; height: 32px; background-color: #f7eb45" |
| style="width: 32px; height: 32px; background-color: #FFFCF3" |
| style="width: 32px; height: 32px; background-color: #ffe671" |
| style="width: 32px; height: 32px; background-color: #FFE2C1" |
| style="width: 32px; height: 32px; background-color: #ffe2be" |
| style="width: 32px; height: 32px; background-color: #FEFBFF" |
| style="width: 32px; height: 32px; background-color: #feddea" |
|-
| Category 2
| style="width: 32px; height: 32px; background-color: #FFE775" |
| style="width: 32px; height: 32px; background-color: #f9aa01" |
| style="width: 32px; height: 32px; background-color: #FFE775" |
| style="width: 32px; height: 32px; background-color: #d1b90f" |
| style="width: 32px; height: 32px; background-color: #FFC140" |
| style="width: 32px; height: 32px; background-color: #ebaf00" |
| style="width: 32px; height: 32px; background-color: #FFDEEA" |
| style="width: 32px; height: 32px; background-color: #ff9da8" |
|-
| Category 3
| style="width: 32px; height: 32px; background-color: #FFC140" |
| style="width: 32px; height: 32px; background-color: #ec7410" |
| style="width: 32px; height: 32px; background-color: #E4CC43" |
| style="width: 32px; height: 32px; background-color: #a89520" |
| style="width: 32px; height: 32px; background-color: #FFC140" |
| style="width: 32px; height: 32px; background-color: #bd8d00" |
| style="width: 32px; height: 32px; background-color: #FFB8C4" |
| style="width: 32px; height: 32px; background-color: #ef6b73" |
|-
| Category 4
| style="width: 32px; height: 32px; background-color: #FF8F20" |
| style="width: 32px; height: 32px; background-color: #EC3469" |
| style="width: 32px; height: 32px; background-color: #C1AC28" |
| style="width: 32px; height: 32px; background-color: #7e7d88" |
| style="width: 32px; height: 32px; background-color: #D9A30F" |
| style="width: 32px; height: 32px; background-color: #98795d" |
| style="width: 32px; height: 32px; background-color: #FF8891" |
| style="width: 32px; height: 32px; background-color: #e94043" |
|-
| Category 5
| style="width: 32px; height: 32px; background-color: #FF6060" |
| style="width: 32px; height: 32px; background-color: #C06CEC" |
| style="width: 32px; height: 32px; background-color: #A09676" |
| style="width: 32px; height: 32px; background-color: #548bff" |
| style="width: 32px; height: 32px; background-color: #B78F58" |
| style="width: 32px; height: 32px; background-color: #628fdf" |
| style="width: 32px; height: 32px; background-color: #FF5F65" |
| style="width: 32px; height: 32px; background-color: #ad848e" |
|}
| style="vertical-align: top" |
{| class="wikitable" style="text-align: center; margin-top: 0"
|+ North Indian Ocean, Southwest Indian Ocean, Australia/South Pacific
! rowspan="2" | Category !! colspan="2" | Normal !! colspan="2" | Protanopic !! colspan="2" | Deuteranopic !! colspan="2" | Tritanopic
|-
! <abbr title="Current">C</abbr> !! <abbr title="Proposed">P</abbr> !! <abbr title="Current">C</abbr> !! <abbr title="Proposed">P</abbr> !! <abbr title="Current">C</abbr> !! <abbr title="Proposed">P</abbr> !! <abbr title="Current">C</abbr> !! <abbr title="Proposed">P</abbr>
|-
| {{abbr|DD|Deep Depression}}/{{abbr|TD|Tropical Depression}}/{{abbr|TL|Tropical Low}}
| style="width: 32px; height: 32px; background-color: #5EBAFF" |
| style="width: 32px; height: 32px; background-color: #5ABEF7" |
| style="width: 32px; height: 32px; background-color: #9CAFF6" |
| style="width: 32px; height: 32px; background-color: #a0b1ee" |
| style="width: 32px; height: 32px; background-color: #92B0FF" |
| style="width: 32px; height: 32px; background-color: #97b1fb" |
| style="width: 32px; height: 32px; background-color: #47C2D2" |
| style="width: 32px; height: 32px; background-color: #44c3d3" |
|-
| {{abbr|CS|Cyclonic Storm}}/{{abbr|MTS|Moderate Tropical Storm}}/{{abbr|C1|Category 1 (Australia)}}
| style="width: 32px; height: 32px; background-color: #00FAF4" |
| style="width: 32px; height: 32px; background-color: #10F9DF" |
| style="width: 32px; height: 32px; background-color: #E1DDE3" |
| style="width: 32px; height: 32px; background-color: #e5dccf" |
| style="width: 32px; height: 32px; background-color: #E7D9FB" |
| style="width: 32px; height: 32px; background-color: #edd7ea" |
| style="width: 32px; height: 32px; background-color: #83F0FF" |
| style="width: 32px; height: 32px; background-color: #78efff" |
|-
| {{abbr|SCS|Severe Cyclonic Storm}}/{{abbr|STS|Severe Tropical Storm}}/{{abbr|C2|Category 2 (Australia)}}
| style="width: 32px; height: 32px; background-color: #CCFFFF" |
| style="width: 32px; height: 32px; background-color: #CCFFFF" |
| style="width: 32px; height: 32px; background-color: #F8F3F8" |
| style="width: 32px; height: 32px; background-color: #F8F3F8" |
| style="width: 32px; height: 32px; background-color: #FFF1FD" |
| style="width: 32px; height: 32px; background-color: #FFF1FD" |
| style="width: 32px; height: 32px; background-color: #E8F7FF" |
| style="width: 32px; height: 32px; background-color: #E8F7FF" |
|-
| {{abbr|VSCS|Very Severe Cyclonic Storm}}/{{abbr|TC|Tropical Cyclone}}/{{abbr|C3|Category 3 (Australia)}}
| style="width: 32px; height: 32px; background-color: #FFFFCC" |
| style="width: 32px; height: 32px; background-color: #f7eb45" |
| style="width: 32px; height: 32px; background-color: #FFFCF3" |
| style="width: 32px; height: 32px; background-color: #ffe671" |
| style="width: 32px; height: 32px; background-color: #FFE2C1" |
| style="width: 32px; height: 32px; background-color: #ffe2be" |
| style="width: 32px; height: 32px; background-color: #FEFBFF" |
| style="width: 32px; height: 32px; background-color: #feddea" |
|-
| {{abbr|ESCS|Extremely Severe Cyclonic Storm}}/{{abbr|ITC|Intense Tropical Cyclone}}/{{abbr|C4|Category 4 (Australia)}}
| style="width: 32px; height: 32px; background-color: #FFC140" |
| style="width: 32px; height: 32px; background-color: #ec7410" |
| style="width: 32px; height: 32px; background-color: #E4CC43" |
| style="width: 32px; height: 32px; background-color: #a89520" |
| style="width: 32px; height: 32px; background-color: #FFC140" |
| style="width: 32px; height: 32px; background-color: #bd8d00" |
| style="width: 32px; height: 32px; background-color: #FFB8C4" |
| style="width: 32px; height: 32px; background-color: #ef6b73" |
|-
| {{abbr|SuCS|Super Cyclonic Storm}}/{{abbr|VITC|Very Intense Tropical Cyclone}}/{{abbr|C5|Category 5 (Australia)}}
| style="width: 32px; height: 32px; background-color: #FF6060" |
| style="width: 32px; height: 32px; background-color: #C06CEC" |
| style="width: 32px; height: 32px; background-color: #A09676" |
| style="width: 32px; height: 32px; background-color: #548bff" |
| style="width: 32px; height: 32px; background-color: #B78F58" |
| style="width: 32px; height: 32px; background-color: #628fdf" |
| style="width: 32px; height: 32px; background-color: #FF5F65" |
| style="width: 32px; height: 32px; background-color: #ad848e" |
|-
| colspan="999" | ''Tooltips have been added for categories for non-] members.''
|}
|}
</div>


:I get that they may not all be inherently notable, but the main reason I'm willing to die on this hill is I'm trying to get the March 31, 2023 tornado outbreak to featured topic status, which will require to get this article to featured list status. The ] has the following:
==== Track map comparison ====
:*Comprehensiveness.
<div style="text-align: center">
:**(a) It comprehensively covers the defined scope, providing at least all of the major items and, '''where practical, a complete set of items;''' where appropriate, it has annotations that provide useful and appropriate information about the items.
<templatestyles src="Misplaced Pages talk:WikiProject Weather/colorChangeRfC.css"/>
:**(b) statements are sourced where they appear, and they provide inline citations if they contain any of the four kinds of material absolutely required to have citations.
{| class="rfc-tcca-base" style="width: 100%; max-width: 1100px;"
:**(c) In length and/or topic, it meets all of the requirements for stand-alone lists and includes at minimum eight items; does not violate the content-forking guideline, does not largely duplicate material from another article, and could not reasonably be included as part of a related article.
| class="rfc-tcca-typeA rfc-tcca-imageA" colspan="2" |
:There's no reason in my eyes not to list every tornado, but a significant amount of the tornadoes were weak EF0 and EF1 tornadoes and including at the very least a one sentence summary for them would be preferred to increase the quality of the article. I'm not aware of any list where entries deemed minor or unimportant are stripped of their right to a summary, ''especially'' when there are reliable sources to put descriptions of said entries. ] (]) 13:42, 9 December 2024 (UTC)
|-
::I'll also say that this is a much more specific and inclusive page than the parent outbreak's article, ]. That, in fact, does have descriptions of six individual tornadoes that day under the section #Confirmed tornadoes, and each is given around 6000 words of prose. I agree that it would be absurd to give that to each tornado in the outbreak - hence why the list is used for less notable tornadoes. ] (]) 13:45, 9 December 2024 (UTC)
| class="rfc-tcca-typeA rfc-tcca-imageB" colspan="2" |
:::But the same is done when there is no main article, or when the tornadoes are just a more or less random grouping, as in ]. This is not an outbreak but an arbitrary period, with at first glance ''one'' tornado which caused considerable damage plus deaths and will have plenty of sources, but of the 250+ other tornadoes, probably 10 or so will have received local coverage, and the others are just entries in the NCEI database. ] (]) 14:12, 9 December 2024 (UTC)
|-
::::We have been doing monthly tornado lists like this for a while. We usually merge months together unless there are more than about 150 tornadoes in a given month. One thing worth mentioning is that yearly tornado articles keep a tally on the number of tornadoes by rating, which would be quite difficult without some kind of list. ] (]) 02:57, 10 December 2024 (UTC)
| class="rfc-tcca-typeB rfc-tcca-imageA" |
:::::We should hardly keep articles in the mainspace just for the sake of a yearly tally. I see that e.g. 2017 had 1418 tornadoes in the US, so hardly a rare event. Apart from counting them, what is the purpose of listing and describing all of them, no matter how minor? ] (]) 15:43, 10 December 2024 (UTC)
| class="rfc-tcca-typeB rfc-tcca-imageB" |
::::::What would be the appropriate namespace then? ] (]) 18:51, 10 December 2024 (UTC)
|}
:::::::If the project needs this, then projectspace. ] (]) 08:32, 11 December 2024 (UTC)
{{cot|title=Color blindness simulations}}
::::::::I have serious doubts that putting these pages in project space would fix the problem, and also doubt the problem exists nearly to the point of removing a significant amount of projectspace pages. There just aren't many reasons to make an article on, say, Hurricane Milton's tornado outbreak, despite producing multiple significant tornadoes responsible for multiple deaths, when it's summary at ] fits that just fine. A lot of more minor outbreaks aren't good fits for pages but are still clearly fits for Misplaced Pages. It's entirely practical to list every tornado in the country. These articles pass ], as the 2024 tornado season has been discussed independently in reliable sources (a list of tornadoes in 2024 would be too long, so splitting it into smaller articles is practical). It's by no means of little interest to the general public and still gets an average of 89 page views per day over the last month. Even barring that, the fact is that most tornadoes nowadays have their best summaries on Misplaced Pages and choosing to not have these summaries on the grounds of "not being of interest to the general public and being too similar to other outbreaks, and giving too much details to unimportant events" strike me as nonsensical.
{{cot|title=] (red-blind)}}
::::::::Tornadoes, even weak ones, can and do change lives, and enough of them happen each year to establish their notability; we're describing and listing them as a group, whether or not they hit anyone, because we recognize their importance and agree that it is indeed practical to list every tornado in a season / outbreak / part of a year. ] (]) 13:23, 11 December 2024 (UTC)
{| class="rfc-tcca-protan" style="width: 100%; max-width: 1050px;"
:::::::::But the vast majority of these tornadoes ''don't'' change lives, and "enough of them happen each year to establish their notability" doesn't make any sense: the fact that there are notable X doesn't mean that every X is notable. The same arguments can be made about car crashes, house fires, ... some of them are notable, change lives, have lasting importance: but that doesn't mean that we would list every car crash if we had some public database of them. What makes extremely minor tornadoes different from extremely minor car crashes? ] (]) 13:44, 11 December 2024 (UTC)
| class="rfc-tcca-typeA rfc-tcca-imageA" colspan="2" |
::::::::::Your point is understandable and I acknowledge we wouldn't be having this discussion if there was a proper policy setting in stone the procedure for individual weak tornadoes. But I will say that you are the first to state that you believe these pages have notability issues; the consensus in the weatherspace of Misplaced Pages is, from what I can tell, that these articles do belong in mainspace as they are. I don't feel like discussing this further as i believe we've reached deadlock with both sides raising valid objections, so expect an RFC to be opened later today regarding this topic, where you will be welcome to argue your position on this matter in a more formal consensus-building setting. I'll admit I'm not a die-hard on keeping the tornadoes, but the alternative requires changing the status quo and gutting articles that have been untouched for years, including a few featured lists (], ], ], ], ]). Good day to you. ] (]) 13:52, 11 December 2024 (UTC)
|-
::::::::::Just a P.S. for Fram: Referencing car accidents isn't a good argument since , which means more car crashes happen in 1 day in just the U.S. than tornadoes worldwide in just the 21st century (roughly 1,600-ish tornadoes a year worldwide). Honestly, the list of tornadoes is closest to something like the ], where it goes year-by-year, month-by-month, and even in the ], Day-by-day. '''The ]''' (] 14:13, 11 December 2024 (UTC)
| class="rfc-tcca-typeA rfc-tcca-imageB" colspan="2" |
:::::::::::Then replace car crashes with bus crashes. As for the shipwrecks, most of these are at least a lot more substantial than "two storm chasers drove through this short-lived tornado which did no damage" and similar entries. They are also referenced to actual major news sources in many cases, not a government database, so they have clearly received independent attention. ] (]) 14:22, 11 December 2024 (UTC)
|-
::::::::::::rther comments should be discussed in the RFC at the bottom of this page. ] (]) 14:33, 11 December 2024 (UTC)u
| class="rfc-tcca-typeB rfc-tcca-imageA" |
| class="rfc-tcca-typeB rfc-tcca-imageB" |
|}
{{cob}}
{{cot|title=] (green-blind)}}
{| class="rfc-tcca-deuteran" style="width: 100%; max-width: 1050px;"
| class="rfc-tcca-typeA rfc-tcca-imageA" colspan="2" |
|-
| class="rfc-tcca-typeA rfc-tcca-imageB" colspan="2" |
|-
| class="rfc-tcca-typeB rfc-tcca-imageA" |
| class="rfc-tcca-typeB rfc-tcca-imageB" |
|}
{{cob}}
{{cot|title=] (blue-blind)}}
{| class="rfc-tcca-tritan" style="width: 100%; max-width: 1050px;"
| class="rfc-tcca-typeA rfc-tcca-imageA" colspan="2" |
|-
| class="rfc-tcca-typeA rfc-tcca-imageB" colspan="2" |
|-
| class="rfc-tcca-typeB rfc-tcca-imageA" |
| class="rfc-tcca-typeB rfc-tcca-imageB" |
|}
{{cob}}
{{cob}}
</div>


== Requested move 8 December 2024 ==
===Discussion===
{{archive top|'''No consensus''' for any changes. Please see the newer, ongoing discussion below for the later RfC on the new color system proposal. ''''']''''' 🌀 (]) 05:32, 13 February 2022 (UTC) <small>(Non-administrator closure)</small>}}
*'''Support''' As proposer. ]<sup>]</sup> 02:55, 17 November 2021 (UTC)
*'''Support''' per nom, and as the creator of the above comparison maps. <span style="background:#ffff55">''''']'''''</span>&nbsp;<small style="font-size:calc(1em - 2pt)">(])</small> 03:08, 17 November 2021 (UTC)
*'''Strong Support''' per both above, as well as the fact that I have had similar issues in the past distinguishing the different colors, and that each new intensity example is easier to distinguish for me with the better contrast in the colors. <s>The only possible slight hiccup would be that it might take some time for other users, readers and editors to get used to the change if it were to be put in effect, considering the original coloring scheme has been in effect for some time now. Otherwise,</s> this seems like a good idea. 🌀]]]🏈 |''']''' 03:35, 17 November 2021 (UTC)
*:Not much of a hiccup since we already include the storm color key in {{T|storm path}}, so it shouldn't be that hard for newer users to check the new legend. <span style="background:#ffff55">''''']'''''</span>&nbsp;<small style="font-size:calc(1em - 2pt)">(])</small> 03:39, 17 November 2021 (UTC)
*:: Ah, okay, that makes sense. {{Reply to|Chlod}} Thank you for explaining and clarifying that. I have struck corresponding portion of my comment. 🌀]]]🏈 |''']''' 03:43, 17 November 2021 (UTC)
*'''Strong Support''' – Per the proposer. Also, I've noted for years that we've had issues with some of the color contrast, in terms of just how similar they are. This is most obvious in the current SSHWS color system, which uses 5 different shades of red/yellow colors. I've found myself having difficulty distinguishing between the Cat 1 - Cat 4 colors at times, especially when similar shades are right next to each other, such as Cat 1 vs. Cat 2, and Cat 2 vs. Cat 3 (the worst two cases, IMO). I consider myself to have extremely good color sense, BTW. If I'm having trouble distinguishing between these colors, then so are many other readers out there. Also, the orange/yellow shades are too similar to be distinguished by colorblind people. So we have a serious problem here, in terms of accessibility. The current coloring system used for the ] and the ] also use the same colors from the SSHWS system in ], so they have the same issue; by making the changes to the SSHWS system alone, we'll also be fixing this issue in the Fujita and the Enhanced Fujita scale colors. The new colors proposed by Hurricane Noah are mostly similar to the current colors, but have more of a contrast and are much easier to distinguish. Thus, I support this proposal. If this is done, all of the track map images will need to be updated accordingly, and while this would be the most difficult part of implementing the color changes, it is definitely doable. ''''']''''' 🌀 (]) 04:50, 17 November 2021 (UTC)
:*However, in the proposal, I would like to replace the pink C3 "proposed color" for the new NIO/SWIO/Aus/SPAC system with the current dark yellow C4 color in use, in order to provide more of a contrast between C3 and C4 for that part of the new coloring system. ''''']''''' 🌀 (]) 04:50, 17 November 2021 (UTC)
:* Done. ]<sup>]</sup> 12:42, 17 November 2021 (UTC)
* Pinging {{Ping|Meow|Supportstorm|FleurDeOdile|AveryTheComrade|Cyclonebiskit}}, since they are currently the main creators of new track maps for the project. The biggest hurdle in this plan is the fact that all of the old track map images will have to be updated with the new coloring scheme, but I think that this can be done. Some of the older track maps need to be redone, anyway (especially for the older SHEM and NIO seasons). ''''']''''' 🌀 (]) 04:50, 17 November 2021 (UTC)
*'''Oppose''' – We were discussing this change earlier and thought the pink looked good within the scale. However, looking at it in a map I do not feel like it meshes well. The changes don't look much better than the current scale. Our maps are used by many people outside of wikipedia, an I have never seen anyone directly comment on the map colors being hard to see. Not to say some had, but if this color scheme can last +15 years without any major complaints I don't feel like a change is needed. That being said if someone can point me to a previous assessment of an ACCESS issue with the color scale I'd appreciate it. I recall there being one mentioned the last time this was brought up and want to know what was discussed there. ] (]) 05:27, 17 November 2021 (UTC)
*:Reading through previous left about accessibility issues with the color scheme, most seem to boil down to . Nova and AustinMan found the colors to be in compliance to ] standards during the . Not sure if standards have changed or if others want to validate their previous assessments. I'm leaning more towards oppose with these changes. ] (]) 06:02, 17 November 2021 (UTC)
*::I've checked the current color scheme against several color checkers and found no violations to the WCAG standard against the ocean color. For green land we have several fails with both schemes, but the land varies in color so it's hard to gauge. I have not come across of another objective way of determining if the maps comply with colorblindness with either current or proposed color schemes. It's becoming more apparent as this conversation draws out, to me, that this is mostly an argument of subjective aesthetics since both schemes are likely within colorblind standards. ] (]) 15:22, 18 November 2021 (UTC)
*'''Comment''' – I would like to know the impact on colour-blind people first.&nbsp;]] 05:47, 17 November 2021 (UTC)
*'''Comment''' Without a serious consideration of what these changes affect for colorblind people (no mention of them in this proposal beyond "it's probably hard for them"), the amount of work required to generate all new maps would be unjustified and I would oppose. Examples would be appreciated. &ndash; ]<span style="line-height: 1.3em;"><span style="font-size:large">𓅊</span></span>] 05:51, 17 November 2021 (UTC)
*:About the maps: they can be systematically regenerated using a bot since most map uploaders place generation data in the Commons summary (even though it's technically an improper use of the {{para|code}} parameter). It hasn't been tried (since something like this hasn't been proposed before), but it's definitely achievable. <span style="background:#ffff55">''''']'''''</span>&nbsp;<small style="font-size:calc(1em - 2pt)">(])</small> 17:44, 17 November 2021 (UTC)
*::It's certainly achievable, however, I think a great deal of thought and consideration needs to be put into the proposal to go through with all that effort lest we change it only for this problem to come up over and over again in the future (as it has before). I didn't think that the requisite consideration was put into this proposal originally, but I am glad that revisions are being made as concerns arise. &ndash; ]<span style="line-height: 1.3em;"><span style="font-size:large">𓅊</span></span>] 23:57, 17 November 2021 (UTC)
*'''Oppose''', it would take years fr readers to get used to this. The most common color-blindness is red-green, which is not a concern either way. However, purple-red is also a common type of color-blindness, and it would be virtually impossible for people affected by it to distinguish whether a storm was Category 4 or 5. ]&nbsp;]&nbsp;&nbsp;''<sup style="font-family:Times New Roman">]</sup>'' 11:10, 17 November 2021 (UTC)
*:{{re|Chicdat}} I've updated the comparison table above (along with the filtered map images) to disprove this. Perhaps you should take a look. <span style="background:#ffff55">''''']'''''</span>&nbsp;<small style="font-size:calc(1em - 2pt)">(])</small> 17:45, 17 November 2021 (UTC)
*'''Comment:''' {{re|Supportstorm|Meow|Atomic7732|Chicdat}} Checked for color blindness and posted those results above. Overall, I think the new coloring scheme does a better job of providing contrast between colors, especially ones directly next to each other on the scale. ]<sup>]</sup> 13:00, 17 November 2021 (UTC)
*{{icon|commons}} '''Example changed''': Category 5 color switched to {{color box|#A751EF}} #A751EF at 16:42, November 17, 2021 (UTC). <span style="background:#ffff55">''''']'''''</span>&nbsp;<small style="font-size:calc(1em - 2pt)">(])</small> 00:05, 18 November 2021 (UTC)
*<s>'''Comment''' This seems like a good idea, however, the C5 color seems a bit off, and it's hard to distinguish between it and other colors in the tritanopia examples. I also find it hard to distinguish between TS and C1 in the deuteranopia and protanopia examples; the C5 color is also much too similar to the TD color in the same examples. The CS and SCS colors also seem similar, though that probably won't matter since the SCS colors are barely used, though the jump between CS/SCS and VSCS is quite wide. When fixed, I'd be happy to support. <span style="font-family: Bahnschrift"><b>]]</b></span> 14:34, 17 November 2021 (UTC)</s> Changing to '''Support''' since my concerns have been addressed. <span style="font-family: Bahnschrift"><b>]]</b></span> 02:29, 18 November 2021 (UTC)
:* {{re|Akbermamps}} I can't update the tracks to have the same colors since I lack the technical ability to make that happen, but I updated the color schemes for the tables. I believe the new values are better than the old ones and fix the issues. The colors for the others scales outside the SSHWS would solely be for the infobox coloring purposes rather than maps. ]<sup>]</sup> 15:09, 17 November 2021 (UTC)
::*Everything is now updated. ]<sup>]</sup> 17:36, 17 November 2021 (UTC)
::* {{re|Hurricane Noah}} I think something close to {{color box|#D3326D}} #D3326D may be better as a C5 color as the color used is still too similar to the C3 color in the tritanopia example. Looking at the colorblindness simulations, it looks much more pleasant while still remaining distinct. <span style="font-family: Bahnschrift"><b>]]</b></span> 01:26, 18 November 2021 (UTC)
*'''Strong Oppose''' - Simply put, I do not see much of any reason why we need to change the colors out of nowhere. There is plenty of contrast in the current color scheme and, if I'm gonna be completely honest here, the new colors look worse than the old ones - so why should I support a downgrade? ] (]) 21:05, 17 November 2021 (UTC)
*:"Out of nowhere" is incorrect: this was proposed due to ACCESS problems. Reading the initial proposal might help. <span style="background:#ffff55">''''']'''''</span>&nbsp;<small style="font-size:calc(1em - 2pt)">(])</small> 00:29, 18 November 2021 (UTC)
*'''Comment''' - I think the SSHWS colours look mostly fine, but my main concern is the NIO/SWIO/AUS/SPAC colours. I really don't like how it jumps from light blue to dark orange, and it looks extremely ugly to my eyes. I think it might be better if the VSCS/TC/C3 colour was equivalent to the SSHWS C1 colour, and the ESCS/ITC/C4 colour was equivalent to the SSHWS C3 colour, like how it is currently. ] (]) 21:08, 17 November 2021 (UTC)
:*{{re|SolarisPenguin|Lucarius}} Fair point and I will adjust that accordingly. ]<sup>]</sup> 22:18, 17 November 2021 (UTC)
*<strike>'''Strong oppose''' in spite of the fact I recognize my opinion does not matter — No. Just no. Our current color system is fine as-is and the blue to dark orange jump in non-SSHWS scales disturbs me greatly. What was the point of this? This solves nothing major - none of the changes look better than the originals in the colorblindness simulations, and quite frankly it'll look even more ugly there. This is an unneeded choice. I will remain convinced of this until a broad public survey proves me otherwise. (And it will, because weather-wise everyone loves when things get changed.) ~ ]] 21:24, 17 November 2021 (UTC)</strike>
** I am now in '''support''' however I would prefer my idea below. ~ ]] 21:41, 18 November 2021 (UTC)
*'''Comment''' — Interesting proposal, one that’s been well thought out as well. The logistics of it are sound; on the condition that it does make things better on those who are colorblind, and it does increase the contrast of the colors. However I do have one or two concerns. First off, this proposal causes a very non-linear progression of color as the categories advance. This is most apparent in the transition between categories 2-5; where one goes from a gold-yellow to orange to red (a very natural progression) and then immediately goes to a deep purple. A pink color may flow better and is what I would likely suggest but, as previously mentioned, it wouldn’t mesh well with track maps. Secondly, as mentioned by Solaris and others, the proposed changes also create inconsistencies in color progression for scales in foreign basins. While this is a bit less significant as it’s only used for infoboxes, it’s still something of note. With all considered, were I to vote i’d lean towards opposing on this one. ''']''' (''']''') 21:31, November 17 2021 (UTC)
:* Actually, Supportstorm is mistaken. It was a different purple color I had shown him. I can investigate a pink color and report back here. ]<sup>]</sup> 22:18, 17 November 2021 (UTC)
*{{icon|commons}}'''Example changed''': Category 5 color switched to {{color box|#D948D9}} #D948D9 at 23:51, November 17, 2021 (UTC). <span style="background:#ffff55">''''']'''''</span>&nbsp;<small style="font-size:calc(1em - 2pt)">(])</small> 00:05, 18 November 2021 (UTC)
*'''Comment''' — Is there a reason the tropical storm color has been made more similar to the tropical depression color? It is less distinguishable on the maps than before. Additionally, from an aesthetic perspective, the proposed category 5 color stands out like a sore thumb compared to the gradient of the rest of the scale. &ndash; ]<span style="line-height: 1.3em;"><span style="font-size:large">𓅊</span></span>] 23:44, 17 November 2021 (UTC)
:* It was made a tiny bit darker to give a bit more contrast between it and the C1 color for the colorblind folks. ]<sup>]</sup> 01:10, 18 November 2021 (UTC)
*'''''Weak'' Oppose'''. It would be confusing to our readers as the Cat 4 color would be applied to Cat 3 and the Cat 5 color would be applied to Cat 4. Also, I disagree with the Cat 1 color for the SSHWS: Noah stated that {{tqqi|Category 1 colors were left untouched}} but in the proposed color table, Cat 1 was changed from #FFFFCC" to #FFFF80", which is really similar to the current Cat 2 color. Also, the current colors were never confusing to my eyes, and without a wider survey taken, there is not enough evidence to claim the current colors being an ACCESS issue. ] <small>(])</small> 00:03, 18 November 2021 (UTC)
**In fact, the proposed Cat 1 and Cat 2 colors are even more indistinguishable than the current ones. ] <small>(])</small> 00:04, 18 November 2021 (UTC)
***Changing to weak oppose as Noah states that under WMF policy discrimination based on disability is outlawed. Here's my proposal: ] <small>(])</small> 03:00, 18 November 2021 (UTC)
*'''Comment''' It's a bit interesting to see the polarity of this discussion: on one hand there's those like Noah, CF71, L&D, and I who have been having issues with the color contrasts (a few of which have been looking at these maps for years), and then there's other a few other editors who have never had that issue. If there's already at least four non-colorblind people affected by this, then how much more colorblind people are affected? Besides that: this is a friendly reminder that the colors are negotiable &mdash; you can freely recommend other changes you think are better, rather than simply call colors "ugly" (which is both subjective and isn't constructive to the discussion). <span style="background:#ffff55">''''']'''''</span>&nbsp;<small style="font-size:calc(1em - 2pt)">(])</small> 00:16, 18 November 2021 (UTC)
*:It's also worth noting: ACCESS is a guideline. "Ugly" is not. <span style="background:#ffff55">''''']'''''</span>&nbsp;<small style="font-size:calc(1em - 2pt)">(])</small> 00:19, 18 November 2021 (UTC)
*::I'm sure we could look up like, the 7 most scientifically accessible and color-blind-friendly colors, or pick like 7 colors at random as far apart as possible on the color wheel, but they would probably not look very good. And certainly there would be an argument to be made to use them anyway (if they were actually significantly more useful than the current colors), however clearly aesthetics ''are'' part of the consideration here, since that has not been done. Not to mention, looking similar to the previous color scale is also something that people value. &ndash; ]<span style="line-height: 1.3em;"><span style="font-size:large">𓅊</span></span>] 00:50, 18 November 2021 (UTC)
*:::The proposal here isn't to be the most scientifically accessible: that defeats the purpose of creativity. The proposal is to change the colors to make it more distinguishable not only for colorblind people but also for those who aren't. I was suggesting that those leaning oppose would suggest colors that you would agree more to rather than simply call the colors "ugly" in order to have an actually constructive discussion. <span style="background:#ffff55">''''']'''''</span>&nbsp;<small style="font-size:calc(1em - 2pt)">(])</small> 01:03, 18 November 2021 (UTC)
*'''Comment''' - Even in the proposed version, the SCS/STS/C2 and VSCS/TC/C3 colours appear like they could be confused with each other, as they remain very similar. ] (]) 01:22, 18 November 2021 (UTC)
:* hold that thought as there may be a better color scheme even though mine has been thought out. ]<sup>]</sup> 01:34, 18 November 2021 (UTC)
::*{{re|SolarisPenguin}} What do you think of the modified version? ]<sup>]</sup> 03:17, 18 November 2021 (UTC)
*'''Oppose''' Not much to say here, but it's actually a really cool idea to make the SSHWS colors more accessible to colorblind people. I won't give it a strong support as the old colors were so widespread and well known that it would probably take time to adjust everything, but I'm pretty sure we can adjust real smoothly. I really don't care whos proposal gets in as they all are pretty good at their purpose. (Edit, changed to weak support for the points I listed previously. (Edit 2, yes I know I am indisicive but im changing to oppose for basically the same reasons as Mario.)) ] (]) 03:32, 18 November 2021 (UTC)
::Are you another user or something? This account has a total of six edits on Misplaced Pages and frankly the participation here doesn't make too much sense. ] (]) 04:44, 18 November 2021 (UTC)
*'''Weak Oppose''' I generally don't mind changing the colours here, however I'd like to see further tweaking so current readers don't get confused, as the proposed Cat 4 colours are near-identical to the current Cat 5 colours, same thing down to Cat 1. AC's version is somewhat better, but I still do have similar complaints. ] (]) 03:50, 18 November 2021 (UTC)
:*{{re|AveryTheComrade}} The issue is that there are limited number of options for us to use that contrast sufficiently with either the land or the water, has a clear progression of colors, and is good for colorblind issues. This is why many colors are similar to the current ones. This is really unavoidable to be honest due to all the constraints. I think with the map kep included and maybe a note of some kind, readers would be fine. ]<sup>]</sup> 03:56, 18 November 2021 (UTC)
*'''Strong Oppose''' – I really don’t think this is the best idea in the long run as it is far more likely that there is public pushback against this since we have used this for over a decade and I personally see no issue with the coloring we have right now. I should mention that because of this the new colors may give the impression of stronger storms when being recalled with the old color scheme (even with a key in the image box, which is something that I really do not like especially the C3/4/5 debacle. I should also mention that some wikis revolving around such colors for TCs and tornadoes will have to undergo major changes/end up being inaccurate wiki wide and that is something I don’t want to see happen. I know this was made in good faith but I don’t think it’ll work sadly given how long it’s already been in place. --''''']''''' (<sup>]</sup>/<sub>]</sub>) 04:28, 18 November 2021 (UTC)
*:I can't help but point out that just because <em>you</em> {{tq|personally see no issue}}, doesn't mean we're not supposed to push this change. Accessibility has been a longstanding goal not only by Misplaced Pages but by the Wikimedia Foundation itself, as declared in the WMF Board of Trustees ]. Additionally, the reason why we made the proposal here instead of ] is because we wanted the attention of all involved weather projects &mdash; including the opinions of those in WikiProject Severe Weather among others. <span style="background:#ffff55">''''']'''''</span>&nbsp;<small style="font-size:calc(1em - 2pt)">(])</small> 05:44, 18 November 2021 (UTC)
*::If it bothers WPSVR that much, we can simply branch off a different template for the Fujita scale, among others. <span style="background:#ffff55">''''']'''''</span>&nbsp;<small style="font-size:calc(1em - 2pt)">(])</small> 05:54, 18 November 2021 (UTC)
*'''Strong Oppose''' – Like others here, I also don't think changing the color scheme that has been used for over a decade is a good idea. The colors have become commonplace all over wikipedia and it is absolutely pointless to change them now and cause confusion. ] (]) 04:35, 18 November 2021 (UTC)
*:Humans are quick to adapt to anything: even a global pandemic. There is no reason that someone won't be able to adapt to simple color changes on a map with the legend provided to them. ] has had over a thousand revisions since 2010, and ] have been made successively throughout the years. WPTC (and in proxy, WPWX) has simply failed to meet up to those expectations, which is why we're trying to change that before this becomes even more of a long-term pain in the ass that we need to drag around for the next 10, 20, 30 years. Misplaced Pages has always been about changing something if it seems wrong: that's what ] is all about, so I really don't see anything policy-based or guideline-based (or at the very least, "wiki-improving") about "]" <span style="background:#ffff55">''''']'''''</span>&nbsp;<small style="font-size:calc(1em - 2pt)">(])</small> 05:52, 18 November 2021 (UTC)
{{hat}}
::I love when I get so-called “policy” thrown at me. ] (]) 06:01, 18 November 2021 (UTC)
:::] and ] are Misplaced Pages guidelines, the ] is a globally-agreed and recognized reference for accessibility, and ] is a WMF Board of Trustees resolution. They have page notices at the top to clearly illustrate these, but perhaps you missed that. <span style="background:#ffff55">''''']'''''</span>&nbsp;<small style="font-size:calc(1em - 2pt)">(])</small> 06:11, 18 November 2021 (UTC)
::::Hmm... I never actually mentioned this being a policy-based change, but rather a guideline-based one. Perhaps you also misread my message? <span style="background:#ffff55">''''']'''''</span>&nbsp;<small style="font-size:calc(1em - 2pt)">(])</small> 06:14, 18 November 2021 (UTC)
:::::When you act in such a manner as you are now, it really makes you look bad. ] (]) 06:16, 18 November 2021 (UTC)
::::::I'm just trying to point out possible oversights, since I feel like you're missing the point of the proposal, and that's really the last thing that I would want to happen since you wouldn't be able to make an informed decision. <span style="background:#ffff55">''''']'''''</span>&nbsp;<small style="font-size:calc(1em - 2pt)">(])</small> 06:18, 18 November 2021 (UTC)
:::::::I’m not missing anything. I’ve been here for 10 years. You, not even 2 yet. I’ve seen this same discussion before and I didn’t support it then and still don’t now. That’s my opinion on it. I don’t believe the purple is a good idea, and I don’t think using some of those other funky colors will actually make anything better and will probably make it worse. ] (]) 06:21, 18 November 2021 (UTC)
::::::::Well, I guess there's not much ] can do if ]. Still was worth a shot. <span style="background:#ffff55">''''']'''''</span>&nbsp;<small style="font-size:calc(1em - 2pt)">(])</small> 06:27, 18 November 2021 (UTC)
:::::::::I was only pointing out that I’ve been here long enough to have seen this before and know that I don’t support it. It has nothing to do with me being here longer, but go ahead and make another smart comment. ] (]) 06:34, 18 November 2021 (UTC)
{{hab}}


<div class="boilerplate mw-archivedtalk" style="background-color: var(--background-color-success-subtle, #efe); color: var(--color-base, inherit); margin: 0; padding: 0 10px 0 10px; border: 1px dotted var(--border-color-subtle, #AAAAAA);"><!-- Template:RM top -->
{{ping|TornadoLGS|ChessEric|Hurricanehink|Cyclonebiskit|Yellow Evan|Jason Rees}} This may be of interest to you, whether you support, oppose, or are neutral in the matter. ] (]) 06:01, 18 November 2021 (UTC)
:''The following is a closed discussion of a ]. <span style="color: var(--color-error, red);">'''Please do not modify it.'''</span> Subsequent comments should be made in a new section on the talk page. Editors desiring to contest the closing decision should consider a ] '''after''' discussing it on the closer's talk page. No further edits should be made to this discussion.''
*'''Weak Oppose''' - Even with a legend, people might still get confused with the new colours due to their similarities (even if the colours themselves are somewhat different), and it will take a long time to change everything. Many other wikis also use Misplaced Pages-style tracks, and they would have to adapt quickly, which would take a lot of work. However, if a change happens, I believe that we should go with AC's idea. ] (]) 09:24, 18 November 2021 (UTC)
*'''Weak Support''' for changing the color scheme, but '''oppose''' the proposed replacement. I agree that the current colors are too similar. I myself have sometimes had trouble distinguishing C2/3 and C3/4 on the map. However, color scales for ordinal data should be consistent and intuitive (e.g. consistently redder and/or darker with increasing values). Having colors become progressively darker with increasing intensity, and then suddenly lighter for C5 is neither consistent nor intuitive. AC's idea below is a bit better, but assigning the current color scheme's colors to different categories (e.g. the current C5 color going to C4) would be confusing to people accustomed to the color scale we've used for years. ] (]) 17:54, 18 November 2021 (UTC)
**{{ping|TornadoLGS|Hurricane Noah}} This is why I made the C4 color in my proposal lighter than the current magenta shade. I propose changing Cat 4 to {{color box|#E20707}} #E20707. ] <small>(])</small> 21:13, 18 November 2021 (UTC)
*'''Comment''' I still do not understand the change for the Cat 1 color. The current color poses no challenge to color-blind people with the other proposed colors. ] <small>(])</small> 21:13, 18 November 2021 (UTC)
*'''Comment''' Going back to my oppose, I would support if there was a compromise of their being two tracks, the original map and the colorblind friendly map. ] (]) 02:11, 19 November 2021 (UTC)
*'''Netural''' While I can see that updating the colours maybe a good idea for our colour blind users, I am not sure that the benefits outweigh the consequences.] (]) 16:47, 20 November 2021 (UTC)
*'''Neutral''' I like the idea, but the color change seems a bit too drastic for my liking] (] <b>·</b> ]) 19:36, 21 November 2021 (UTC).
*'''Neutral''' Personally, I do like the current color scheme, but I do understand that there are accessibility concerns raised and won't oppose changing to address them. I would prefer, however, that the least changes are done to the color scheme to address the concerns. I can see how the Categories 2, 3 and 4 colors may have issues and can see the need to address them, but I don't know if the Category 1 color needs to be adjusted, for example. &mdash; <span style="font-family:Helvetica;Arial; font-size:12px;">]]</span> 23:39, 27 November 2021 (UTC)
{{Archive bottom}}


The result of the move request was: '''moved''' as proposed. If any of these need further changes, feel free to start a separate RM (or just move them BOLDly). ] (]) 04:08, 15 December 2024 (UTC)
====AC's Idea====
----


* ] → {{no redirect|List of tornadoes in the outbreak sequence of May 7–11, 2008}}
<div style="text-align: center">
* ] → {{no redirect|List of tornadoes in the outbreak of April 15–16, 1998}}
{| class="wikitable" style="text-align: center; margin-top: 0"
* ] → {{no redirect|List of tornadoes in the outbreak of April 6–8, 2006}}
|+ ALL the colors
* ] → {{no redirect|List of tornadoes in the outbreak of May 22–27, 2008}}
! rowspan="2" | Category !! colspan="2" | Normal !! colspan="2" | Protanopic !! colspan="2" | Deuteranopic !! colspan="2" | Tritanopic
* ] → {{no redirect|List of tornadoes in the outbreak sequence of June 3–11, 2008}}
|-
* ] → {{no redirect|List of tornadoes in the outbreak of May 10–13, 2010}}
! <abbr title="Current">C</abbr> !! <abbr title="Proposed">P</abbr> !! <abbr title="Current">C</abbr> !! <abbr title="Proposed">P</abbr> !! <abbr title="Current">C</abbr> !! <abbr title="Proposed">P</abbr> !! <abbr title="Current">C</abbr> !! <abbr title="Proposed">P</abbr>
* ] → {{no redirect|List of tornadoes in the outbreak of May 18–21, 2013}}
|-
* ] → {{no redirect|List of tornadoes in the outbreak of April 27–30, 2014}}
| Potential Tropical Cyclone or Disturbance
* ] → {{no redirect|List of tornadoes in the outbreak of April 22–25, 2010}}
| style="width: 32px; height: 32px; background-color: #80CCFF" |
* ] → {{no redirect|List of tornadoes in the outbreak sequence of May 14–31, 1962}}
| style="width: 32px; height: 32px; background-color: #72A9CD" |
* ] → {{no redirect|List of tornadoes in the outbreak sequence of April 2–5, 1957}}
| style="width: 32px; height: 32px; background-color: #B3C0F8" |
* ] → {{no redirect|List of tornadoes in the outbreak of May 26–31, 2013}}
| style="width: 32px; height: 32px; background-color: #979fc7" |
* ] → {{no redirect|List of tornadoes in the outbreak of May 4–6, 2007}}
| style="width: 32px; height: 32px; background-color: #B2C0FF" |
* ] → {{no redirect|List of tornadoes in the outbreak of April 25–28, 2024}}
| style="width: 32px; height: 32px; background-color: #989ecf" |
* ] → {{no redirect|List of tornadoes in the outbreak of March 31 – April 1, 2023}}
| style="width: 32px; height: 32px; background-color: #73D0E1" |
* ] → {{no redirect|List of tornadoes in the outbreak sequence of May 21–26, 2011}}
| style="width: 32px; height: 32px; background-color: #6babb9" |
* ] → {{no redirect|List of tornadoes in the outbreak of April 14–16, 2011}}
|-
* ] → {{no redirect|List of tornadoes in the outbreak of December 10–11, 2021}}
| Tropical Depression
* ] → {{no redirect|List of tornadoes in the outbreak sequence of May 19–27, 2024}}
| style="width: 32px; height: 32px; background-color: #5EBAFF" |
* ] → {{no redirect|List of tornadoes in the outbreak of May 6–10, 2024}}
| style="width: 32px; height: 32px; background-color: #5EBAFF" |
* ] → {{no redirect|List of tornadoes in the outbreak sequence of May 2019}}
| style="width: 32px; height: 32px; background-color: #9CAFF6" |
– Literally any article entitled "List of tornadoes in the tornado outbreak / tornado outbreak sequence of XY" renamed to drop the second "tornado" in the title. It lets each article have a shorter title, and the fact that it's a tornado outbreak is obvious given that it's a list of tornadoes, established in the title. The only exception is for named outbreaks like the 2011 Super Outbreak - this is for genericly named outbreaks only. ] (]) 03:02, 8 December 2024 (UTC) ] (]) 03:02, 8 December 2024 (UTC)
| style="width: 32px; height: 32px; background-color: #9CAFF6" |
*'''Support'''. ♫ ] (<small>]</small>) 03:06, 8 December 2024 (UTC)
| style="width: 32px; height: 32px; background-color: #92B0FF" |
| style="width: 32px; height: 32px; background-color: #92B0FF" |
| style="width: 32px; height: 32px; background-color: #47C2D2" |
| style="width: 32px; height: 32px; background-color: #47C2D2" |
|-
| Tropical Storm
| style="width: 32px; height: 32px; background-color: #00FAF4" |
| style="width: 32px; height: 32px; background-color: #00FAF4" |
| style="width: 32px; height: 32px; background-color: #E1DDE3" |
| style="width: 32px; height: 32px; background-color: #E1DDE3" |
| style="width: 32px; height: 32px; background-color: #E7D9FB" |
| style="width: 32px; height: 32px; background-color: #E7D9FB" |
| style="width: 32px; height: 32px; background-color: #84F0FF" |
| style="width: 32px; height: 32px; background-color: #84F0FF" |
|-
| Severe Tropical Storm
| style="width: 32px; height: 32px; background-color: #CCFFFF" |
| style="width: 32px; height: 32px; background-color: #B1FAB1" |
| style="width: 32px; height: 32px; background-color: #F8F3F8" |
| style="width: 32px; height: 32px; background-color: #fae7a8" |
| style="width: 32px; height: 32px; background-color: #FFF1FD" |
| style="width: 32px; height: 32px; background-color: #ffe2cf" |
| style="width: 32px; height: 32px; background-color: #E8F7FF" |
| style="width: 32px; height: 32px; background-color: #c6eeff" |
|-
| Category 1
| style="width: 32px; height: 32px; background-color: #FFFFCC" |
| style="width: 32px; height: 32px; background-color: #FFF795" |
| style="width: 32px; height: 32px; background-color: #FFFCF3" |
| style="width: 32px; height: 32px; background-color: #fff3cb" |
| style="width: 32px; height: 32px; background-color: #FFE2C1" |
| style="width: 32px; height: 32px; background-color: #fff1e4" |
| style="width: 32px; height: 32px; background-color: #FEFBFF" |
| style="width: 32px; height: 32px; background-color: #ffeff7" |
|-
| Category 2
| style="width: 32px; height: 32px; background-color: #FFE775" |
| style="width: 32px; height: 32px; background-color: #FFD821" |
| style="width: 32px; height: 32px; background-color: #FFE775" |
| style="width: 32px; height: 32px; background-color: #f6da27" |
| style="width: 32px; height: 32px; background-color: #FFC140" |
| style="width: 32px; height: 32px; background-color: #ffd393" |
| style="width: 32px; height: 32px; background-color: #FFDEEA" |
| style="width: 32px; height: 32px; background-color: #ffcdd8" |
|-
| Category 3
| style="width: 32px; height: 32px; background-color: #FFC140" |
| style="width: 32px; height: 32px; background-color: #FF8F20" |
| style="width: 32px; height: 32px; background-color: #E4CC43" |
| style="width: 32px; height: 32px; background-color: #c0aa2c" |
| style="width: 32px; height: 32px; background-color: #FFC140" |
| style="width: 32px; height: 32px; background-color: #d9a119" |
| style="width: 32px; height: 32px; background-color: #FFB8C4" |
| style="width: 32px; height: 32px; background-color: #ff8790" |
|-
| Category 4
| style="width: 32px; height: 32px; background-color: #FF8F20" |
| style="width: 32px; height: 32px; background-color: #FF6060" |
| style="width: 32px; height: 32px; background-color: #C0AA2C" |
| style="width: 32px; height: 32px; background-color: #9f9473" |
| style="width: 32px; height: 32px; background-color: #D9A119" |
| style="width: 32px; height: 32px; background-color: #b68e56" |
| style="width: 32px; height: 32px; background-color: #FF8790" |
| style="width: 32px; height: 32px; background-color: #ff6065" |
|-
| Category 5
| style="width: 32px; height: 32px; background-color: #FF6060" |
| style="width: 32px; height: 32px; background-color: #C464D9" |
| style="width: 32px; height: 32px; background-color: #9F9473" |
| style="width: 32px; height: 32px; background-color: #5386f4" |
| style="width: 32px; height: 32px; background-color: #B68E56" |
| style="width: 32px; height: 32px; background-color: #6b89cc" |
| style="width: 32px; height: 32px; background-color: #FF6065" |
| style="width: 32px; height: 32px; background-color: #b57a83" |
|-
| Extratropical
| style="width: 32px; height: 32px; background-color: #CCCCCC" |
| style="width: 32px; height: 32px; background-color: #CCCCCC" |
| style="width: 32px; height: 32px; background-color: #CECACA" |
| style="width: 32px; height: 32px; background-color: #CECACA" |
| style="width: 32px; height: 32px; background-color: #dec4cd" |
| style="width: 32px; height: 32px; background-color: #dec4cd" |
| style="width: 32px; height: 32px; background-color: #cdc9d8" |
| style="width: 32px; height: 32px; background-color: #cdc9d8" |
|}
</div>


:Also '''Support''' --<span style="font-family:Times New Roman;font-size:100%;color:#00008B;background-color:transparent;;CSS">]]</span> 06:12, 9 December 2024 (UTC)
* I decided to be useful, and propose some slight changes. I made the C1 a bit darker to fit with the brightness transition, and the C5 a smoother purple for that reason and to make it easier on the eyes. I plan on adding a Strong TS color soon - it'll be a bit darker to match the new C1. How does this look? (I personally think I like it.) ~ ]] 02:12, 18 November 2021 (UTC)
*'''Support'''. = ] ] 20:57, 9 December 2024 (UTC)
** Postnote: I also kept the TS and TD colors from the old color system. They're good as-is. ~ ]] 02:17, 18 November 2021 (UTC)
* I've now created a rough draft Severe TS color, but I'm not sure it fits. Anyone have any ideas? ~ ]] 02:34, 18 November 2021 (UTC)
* UPDATE 9:58 PM EST - Settled on a STS (Severe Tropical Storm, not to be confused with (if you know, you know)) color. I have it all up with colorblindness effects on . ~ ]] 02:58, 18 November 2021 (UTC)
*<s>'''Weak Support'''</s> '''Comment''' - I think this looks better than the other suggestion, however I think that the TS and STS colours could be confused for each other, and some other colours could be changed. <s>however, other than that, it's easier for colourblind people than the current style, although I don't see the issue with the style we have right now.</s> ] (]) 03:41, 18 November 2021 (UTC)
** Now that I think about it, I liked your STS color suggestion (on HHW Discord). I've put it on there. ~ ]] 21:29, 18 November 2021 (UTC)
*<s>'''Weak Oppose'''</s> This is better then the proposal above, but, per my other comment above, I think shifting the same colors to different categories (Current C5 to C4 and current C4 to C3) would be confusing to people who are accustomed to the current color ramp; more confusing than a completely new color ramp. 18:00, 18 November 2021 (UTC)<!-- Template:Unsigned --><span class="autosigned" style="font-size:85%;">—&nbsp;Preceding ] comment added by ] (] • ]) </span>
** Keeping most of the original colors albeit moving some is the ''point''. I wanted to keep true to the original style but also utilize the new proposed scheme. I'll agree it'll take some getting used to but all-in-all it is worth it. ~ ]] 21:29, 18 November 2021 (UTC)
***Point taken. Compressing the color ramp is probably the best way in increase contrast. ] (]) 03:04, 19 November 2021 (UTC)
* UPDATE - Added the colorblindness conversions for current and proposed directly into the table, à le Noah, and want to reiterate the new STS color courtesy of Solaris. ~ ]] 00:19, 19 November 2021 (UTC)
** Added extratrop (unchanged) and PTC/disturbance (now darker than TD). ~ ]] 00:37, 19 November 2021 (UTC)
*** Brightened PTC color. ~ ]] 13:58, 20 November 2021 (UTC)


:• '''Support''' <span style="background-color: invisible; padding: 2px 3px 1px 3px;">] ]</span> 14:31, 10 December 2024 (UTC)
====LGS's color scheme====
{| class="wikitable" style="text-align: center; margin-top: 0"
|+ Saffir-Simpson Hurricane Wind Scale colors
! rowspan="2" | Category !! colspan="2" | Normal !! colspan="2" | Protanopic !! colspan="2" | Deuteranopic !! colspan="2" | Tritanopic
|-
! <abbr title="Current">C</abbr> !! <abbr title="Proposed">P</abbr> !! <abbr title="Current">C</abbr> !! <abbr title="Proposed">P</abbr> !! <abbr title="Current">C</abbr> !! <abbr title="Proposed">P</abbr> !! <abbr title="Current">C</abbr> !! <abbr title="Proposed">P</abbr>
|-
| Tropical Depression
| style="width: 32px; height: 32px; background-color: #5EBAFF" |
| style="width: 32px; height: 32px; background-color: #5eb9ff" |
| style="width: 32px; height: 32px; background-color: #9CAFF6" |
| style="width: 32px; height: 32px; background-color: #98aef8" |
| style="width: 32px; height: 32px; background-color: #92B0FF" |
| style="width: 32px; height: 32px; background-color: #98aef8" |
| style="width: 32px; height: 32px; background-color: #47C2D2" |
| style="width: 32px; height: 32px; background-color: #41c1d0" |
|-
| Tropical Storm
| style="width: 32px; height: 32px; background-color: #00FAF4" |
| style="width: 32px; height: 32px; background-color: #00faf6" |
| style="width: 32px; height: 32px; background-color: #E1DDE3" |
| style="width: 32px; height: 32px; background-color: #e2dee6" |
| style="width: 32px; height: 32px; background-color: #E7D9FB" |
| style="width: 32px; height: 32px; background-color: #e5dbff" |
| style="width: 32px; height: 32px; background-color: #83F0FF" |
| style="width: 32px; height: 32px; background-color: #85f0ff" |
|-
| Category 1
| style="width: 32px; height: 32px; background-color: #FFFFCC" |
| style="width: 32px; height: 32px; background-color: #ffffdc" |
| style="width: 32px; height: 32px; background-color: #FFFCF3" |
| style="width: 32px; height: 32px; background-color: #fffcf7" |
| style="width: 32px; height: 32px; background-color: #FFE2C1" |
| style="width: 32px; height: 32px; background-color: #fffcfb" |
| style="width: 32px; height: 32px; background-color: #FEFBFF" |
| style="width: 32px; height: 32px; background-color: #fefcff" |
|-
| Category 2
| style="width: 32px; height: 32px; background-color: #FFE775" |
| style="width: 32px; height: 32px; background-color: #ffe205" |
| style="width: 32px; height: 32px; background-color: #FFE775" |
| style="width: 32px; height: 32px; background-color: #ffe10d" |
| style="width: 32px; height: 32px; background-color: #FFC140" |
| style="width: 32px; height: 32px; background-color: #ffdbac" |
| style="width: 32px; height: 32px; background-color: #FFDEEA" |
| style="width: 32px; height: 32px; background-color: #ffd7e1" |
|-
| Category 3
| style="width: 32px; height: 32px; background-color: #FFC140" |
| style="width: 32px; height: 32px; background-color: #ff8800" |
| style="width: 32px; height: 32px; background-color: #E4CC43" |
| style="width: 32px; height: 32px; background-color: #bca614" |
| style="width: 32px; height: 32px; background-color: #FFC140" |
| style="width: 32px; height: 32px; background-color: #d49d00" |
| style="width: 32px; height: 32px; background-color: #FFB8C4" |
| style="width: 32px; height: 32px; background-color: #ff8088" |
|-
| Category 4
| style="width: 32px; height: 32px; background-color: #FF8F20" |
| style="width: 32px; height: 32px; background-color: #db4500" |
| style="width: 32px; height: 32px; background-color: #C1AC28" |
| style="width: 32px; height: 32px; background-color: #897915" |
| style="width: 32px; height: 32px; background-color: #D9A30F" |
| style="width: 32px; height: 32px; background-color: #9a7300" |
| style="width: 32px; height: 32px; background-color: #FF8891" |
| style="width: 32px; height: 32px; background-color: #db4245" |
|-
| Category 5
| style="width: 32px; height: 32px; background-color: #FF6060" |
| style="width: 32px; height: 32px; background-color: #b70f36" |
| style="width: 32px; height: 32px; background-color: #A09676" |
| style="width: 32px; height: 32px; background-color: #615c4f" |
| style="width: 32px; height: 32px; background-color: #B78F58" |
| style="width: 32px; height: 32px; background-color: #72582f" |
| style="width: 32px; height: 32px; background-color: #FF5F65" |
| style="width: 32px; height: 32px; background-color: #b51e1d" |
|}


*'''Support''' — ] (]) 20:14, 10 December 2024 (UTC)
I fiddled around with colors on my own and ended up with this. My main issue with other proposals was that the colors trended toward darker and warmer colors with increasing intensity, and snapped back to a lighter and/or cooler color for C5, so I kept a warmer color for C5 in this chart. It's more intuitive in my mind. ] (]) 03:23, 19 November 2021 (UTC)
*:'''Weak support'''. ]<sup>]</sup> 01:17, 11 December 2024 (UTC)
*::I do think there should be (partial) exceptions for tornado lists pertaining to ] though. ]<sup>]</sup> 01:18, 11 December 2024 (UTC)
*:::These aren't derechos, though. Nor are they severe weather sequences. They're just generic outbreaks. ] (]) 01:41, 11 December 2024 (UTC)
*::::Like I said @]; for generic outbreaks, I am fine with moving them. I’m just saying if it’s something like a derecho (eg: April 2nd), the derecho part should still be mentioned. That’s all. ]<sup>]</sup> 20:05, 13 December 2024 (UTC)
*:::::So, would you support "List of tornadoes in the outbreak and derecho of XY", or would you prefer the status quo "List of tornadoes in the tornado outbreak and derecho of XY"? ] (]) 20:09, 13 December 2024 (UTC)
*::::::It really just depends on the case. But the first option if it’s a generic case. ]<sup>]</sup> 21:48, 13 December 2024 (UTC)
*:::::::I also think there should be exceptions for events like the ] outbreak/derecho. ]<sup>]</sup> 18:52, 14 December 2024 (UTC)
*::::::::If there's an example you can think of that isn't listed above, it's safe to assume it's exempt. ] (]) 19:25, 14 December 2024 (UTC)


<div style="padding-left: 1.6em; font-style: italic; border-top: 1px solid #a2a9b1; margin: 0.5em 0; padding-top: 0.5em">The discussion above is closed. <b style="color: var(--color-error, red);">Please do not modify it.</b> Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.</div><!-- from ] -->
'''Comment''' – Cat 5 pops out on a dark background better if it's lighter. My issue with the original proposal (which has been fixed now) is that the cat 5 color simultaneously stuck out like a sore thumb because of the hue difference but also felt muted compared to cat 4 because it was too dark. Remember that these colors will be displayed on a dark background, so lighter colors will provide more contrast. I think Cat 5 should probably be the "brightest" and center of attention/focus for any map it shows up on. &ndash; ]<span style="line-height: 1.3em;"><span style="font-size:large">𓅊</span></span>] 10:51, 19 November 2021 (UTC)
</div><div style="clear:both;" class=></div>
:{{ping|Atomic7732}} I don't want to go too light, though. As I've said before, a color ramp should be intuitive and internally consistent. (e.g. having colors get darker and redder with increasing intensity). My main issue with the color scheme at the top of this thread is that it is not intuitive that the proposed cat 5 color represents a higher intensity than the cat 4 color. I might go with {{color box|#e00056}} if a lighter cat 5 color is needed, but I think it stands out fine against the ocean background used in the maps , though seeing it now, I might still need to put a bigger color gap between cat 3 and cat 4. ] (]) 21:34, 19 November 2021 (UTC)


== New severe weather terminology drafts ==
====Base map====
Has anyone considered using something other than ] for the base map? I have a feeling creating a linear colour scale would be much less complicated if we didn't have to deal with the existing green, blue, and brown of the blue marble map. ~&nbsp;] <small>{] · ]}</small> 05:28, 20 November 2021 (UTC)
:Do we have any other options for a base map? ] (]) 16:50, 20 November 2021 (UTC)
::There's ], which is in the public domain and probably not too hard to recolour. ~&nbsp;] <small>{] · ]}</small> 06:23, 21 November 2021 (UTC)
:::I do not like the idea of us colouring in the map as I doubt we would not be able to agree on the colours and it would probably count as original research, after all what colour the ocean or a certain point in Africa is? ] (]) 16:46, 21 November 2021 (UTC)
::::], since some colors suggested further on do collide with the Blue Marble background.&nbsp;] ] 15:54, 21 March 2022 (UTC)


I have created two draft articles pertaining to severe weather terminology (in Germany and New Zealand) and I’m about to create a draft for Australia warnings. I encourage anyone who wants to do so to help with the draft. Thank you. ]<sup>]</sup> 01:13, 11 December 2024 (UTC)
===Redux: New RfC (February 2022)===
{{atop
| status =
| result = The proposal in this RFC has been approved by a general consensus of those editors who participated in this discussion. The timetable for enacting changes following the closure of this RfC has yet to be determined and will warrant further discussion. <span style="font-family:Papyrus; color:#800080;">]</span> <sup style="font-family: Times New Roman; color: #006400;">] ]</sup> 20:36, 25 February 2022 (UTC)
}}


:I do invite anyone who wants to to help with these drafts. I think I have the format right on the Germany article but I don’t know for sure.
:Will definitely need help on the rain-related alerts because the units used by the DWD are “l/m2” which I presume is liters per cubic meter but I don’t know for sure. ]<sup>]</sup> 21:52, 13 December 2024 (UTC)


== RFC on tornado lists ==
<!-- ] 00:01, 20 March 2022 (UTC) -->{{User:ClueBot III/DoNotArchiveUntil|1647734485}}
Which color scheme is more accessible?


<!-- ] 15:01, 15 January 2025 (UTC) -->{{User:ClueBot III/DoNotArchiveUntil|1736953276}}
The current colors have been used across weather for the past decade. I believe these colors are hard to distinguish between on track maps for the dots, particularly between the Category 1-4 range. There simply isn't enough contrast between the colors to tell them apart (C1 and C2, C2 and C3, C3 and C4). This has presented a challenge for me as a reader and editor with normal color vision and decent eyesight with glasses. I have to open the full resolution to tell the difference between the colors and even then it can be a challenge for some. This issue would be even worse for color-blind editors. On the grounds of ], I am proposing a change to the below SSHWS colors, which increase the contrast between the hurricane colors. Please place comments in the formal discussion section below. ]<sup>]</sup> 23:33, 12 February 2022 (UTC)
Should weak and unimpactful tornadoes be included in list articles? ] (]) 14:20, 11 December 2024 (UTC)
====Proposed colors====
Given the concern raised by {{re|Asartea}}, I think we should revisit this. I have reopened the discussion which was prematurely archived without closure. I think the history of the discussion should remain intact, however, I do think we should leave the past behind in terms of this discussion. The table below is mostly what AC had proposed, but there was a slight change to some colors. ]<sup>]</sup> 21:54, 6 February 2022 (UTC)


:'''Opening comments''': This all began because of an above discussion, where an editor placed a tag on ] article for "excessive examples", and upon discussion stated that weak tornadoes with little effects were getting too much prose in the lists given their impact and shouldn't be listed in the same manner as other tornadoes. This goes against the status quo of the "List of tornadoes in the XY outbreak" and "List of United States tornadoes from X to Y, YYYY" list articles which have remained largely untouched in policy and unquestioned on notability since their origins. I personally believe that, since other tornadoes in the list are practical, all tornadoes that can be reliably sourced to be included should be listed with a brief summary. Another potential solution which I personally oppose but could be implemented is prose in the articles for EFU/0/1 tornadoes, stating that "X weak tornadoes producing little impact were also observed". I'll also state that this statement will make tallying tornadoes harder, given the lack of specificity that can lead to under or overcounting. Whatever the outcome of this RFC, I merely hope the solution will prevent this issue from producing policy-based stalemate with maintenance tags having no clear and easy solutions as we have at the first article I mentioned. ] (]) 14:27, 11 December 2024 (UTC)
<div style="text-align: center">
{| class="wikitable" style="text-align: center; margin-top: 0"
|+ Proposed colors
! rowspan="2" | Category !! colspan="2" | Normal !! colspan="2" | Protanopic !! colspan="2" | Deuteranopic !! colspan="2" | Tritanopic
|-
! <abbr title="Current">C</abbr> !! <abbr title="Proposed">P</abbr> !! <abbr title="Current">C</abbr> !! <abbr title="Proposed">P</abbr> !! <abbr title="Current">C</abbr> !! <abbr title="Proposed">P</abbr> !! <abbr title="Current">C</abbr> !! <abbr title="Proposed">P</abbr>
|-
| Potential Tropical Cyclone or Disturbance
| style="width: 32px; height: 32px; background-color: #80CCFF" |
| style="width: 32px; height: 32px; background-color: #72A9CD" |
| style="width: 32px; height: 32px; background-color: #B3C0F8" |
| style="width: 32px; height: 32px; background-color: #979fc7" |
| style="width: 32px; height: 32px; background-color: #B2C0FF" |
| style="width: 32px; height: 32px; background-color: #989ecf" |
| style="width: 32px; height: 32px; background-color: #73D0E1" |
| style="width: 32px; height: 32px; background-color: #6babb9" |
|-
| Tropical Depression
| style="width: 32px; height: 32px; background-color: #5EBAFF" |
| style="width: 32px; height: 32px; background-color: #5EBAFF" |
| style="width: 32px; height: 32px; background-color: #9CAFF6" |
| style="width: 32px; height: 32px; background-color: #9CAFF6" |
| style="width: 32px; height: 32px; background-color: #92B0FF" |
| style="width: 32px; height: 32px; background-color: #92B0FF" |
| style="width: 32px; height: 32px; background-color: #47C2D2" |
| style="width: 32px; height: 32px; background-color: #47C2D2" |
|-
| Tropical Storm
| style="width: 32px; height: 32px; background-color: #00FAF4" |
| style="width: 32px; height: 32px; background-color: #00FAF4" |
| style="width: 32px; height: 32px; background-color: #E1DDE3" |
| style="width: 32px; height: 32px; background-color: #E1DDE3" |
| style="width: 32px; height: 32px; background-color: #E7D9FB" |
| style="width: 32px; height: 32px; background-color: #E7D9FB" |
| style="width: 32px; height: 32px; background-color: #84F0FF" |
| style="width: 32px; height: 32px; background-color: #84F0FF" |
|-
| Severe Tropical Storm
| style="width: 32px; height: 32px; background-color: #CCFFFF" |
| style="width: 32px; height: 32px; background-color: #B4FDA8" |
| style="width: 32px; height: 32px; background-color: #F8F3F8" |
| style="width: 32px; height: 32px; background-color: #feea9f" |
| style="width: 32px; height: 32px; background-color: #FFF1FD" |
| style="width: 32px; height: 32px; background-color: #ffe6d2" |
| style="width: 32px; height: 32px; background-color: #E8F7FF" |
| style="width: 32px; height: 32px; background-color: #cef0ff" |
|-
| Category 1
| style="width: 32px; height: 32px; background-color: #FFFFCC" |
| style="width: 32px; height: 32px; background-color: #FFF795" |
| style="width: 32px; height: 32px; background-color: #FFFCF3" |
| style="width: 32px; height: 32px; background-color: #fff3cb" |
| style="width: 32px; height: 32px; background-color: #FFE2C1" |
| style="width: 32px; height: 32px; background-color: #fff1e4" |
| style="width: 32px; height: 32px; background-color: #FEFBFF" |
| style="width: 32px; height: 32px; background-color: #ffeff7" |
|-
| Category 2
| style="width: 32px; height: 32px; background-color: #FFE775" |
| style="width: 32px; height: 32px; background-color: #FFD821" |
| style="width: 32px; height: 32px; background-color: #FFE775" |
| style="width: 32px; height: 32px; background-color: #f6da27" |
| style="width: 32px; height: 32px; background-color: #FFC140" |
| style="width: 32px; height: 32px; background-color: #ffd393" |
| style="width: 32px; height: 32px; background-color: #FFDEEA" |
| style="width: 32px; height: 32px; background-color: #ffcdd8" |
|-
| Category 3
| style="width: 32px; height: 32px; background-color: #FFC140" |
| style="width: 32px; height: 32px; background-color: #FF8F20" |
| style="width: 32px; height: 32px; background-color: #E4CC43" |
| style="width: 32px; height: 32px; background-color: #c0aa2c" |
| style="width: 32px; height: 32px; background-color: #FFC140" |
| style="width: 32px; height: 32px; background-color: #d9a119" |
| style="width: 32px; height: 32px; background-color: #FFB8C4" |
| style="width: 32px; height: 32px; background-color: #ff8790" |
|-
| Category 4
| style="width: 32px; height: 32px; background-color: #FF8F20" |
| style="width: 32px; height: 32px; background-color: #FF6060" |
| style="width: 32px; height: 32px; background-color: #C0AA2C" |
| style="width: 32px; height: 32px; background-color: #9f9473" |
| style="width: 32px; height: 32px; background-color: #D9A119" |
| style="width: 32px; height: 32px; background-color: #b68e56" |
| style="width: 32px; height: 32px; background-color: #FF8790" |
| style="width: 32px; height: 32px; background-color: #ff6065" |
|-
| Category 5
| style="width: 32px; height: 32px; background-color: #FF6060" |
| style="width: 32px; height: 32px; background-color: #C464D9" |
| style="width: 32px; height: 32px; background-color: #9F9473" |
| style="width: 32px; height: 32px; background-color: #5386f4" |
| style="width: 32px; height: 32px; background-color: #B68E56" |
| style="width: 32px; height: 32px; background-color: #6b89cc" |
| style="width: 32px; height: 32px; background-color: #FF6065" |
| style="width: 32px; height: 32px; background-color: #b57a83" |
|}
</div>


*]: "Lists are commonly written to satisfy one of the following sets of objective criteria:" When we apply this to e.g. ], we see that it certainly doesn't meet #1 (not all these tornadoes are independently notable), it doesn't meet #2 (some of them are notable (e.g. ]), and it doesn't meet #3 ("reasonably short (less than 32 KB)": the example article is more than 200K, and is already a random subdivision of US tornadoes of 2023). ] (]) 14:58, 11 December 2024 (UTC)
====Comparison images====
*Cherry picking certain tornadoes to include here would be overly subjective and impossible, so it’s really an all or nothing scenario. I support including all tornadoes as is done currently, with no changes needed to the current core status of the lists. The only way these lists can be totally objective as Fram mentioned above is to include all of them. ] (]) 19:22, 11 December 2024 (UTC)
Original on the left; proposed on the right<br/>
I apologize for the low-quality visuals for the proposed colors. I did the best I could. ]<sup>]</sup> 23:47, 12 February 2022 (UTC)


*:That´s the same kind of argument used for years for sports, everyone who played one game is the only objective measure. Didn´t fly there, doesn´t fly here. Including e.g only tornadoes of, say, EF2 and above is equally objective. Or all rornadoes which have at least one non-local reliable source apart from the curre t database. Or probably other rules, these are just some first thoughts. ] (]) 19:40, 11 December 2024 (UTC)
{{collapse top|Standard vision}}
*::Actually no, there are numerous cases where EF1 and even EF0 tornadoes include more damage description and even media coverage than some EF2s, so then again, it is subjective. You can frame this anyway you want, but your argument here is actually not an improvement and is detrimental to the Wikiproject and the flow of information of Misplaced Pages as a whole. There are actual issues afoot here in this wikiproject, such as mass creation of tornado articles with bad grammar, multiple factual errors, and content-fork creation. The list pages are not a hill to die on for you imo. ] (]) 19:53, 11 December 2024 (UTC)
]]
*I've been following this discussion without really chiming in, so I will offer a ''possible'' solution. Noting, if I was actually choosing, I choose to not alter anything. However, this is a possible compromise to the dispute:
{{collapse bottom}}
::#Monthly U.S. tornadoes articles remain stand-alone list articles (merges to combine additional months open to case-by-case basis).
{{collapse top|Protanopic (red blind)}}
::#Any tornado that has one non-NOAA source is automatically notable for summary details (i.e. summary details as the lists have now).
]]
::#The leader is altered ''slightly'' from the current lead versions to denote this includes notable tornadoes (i.e. at least one non-NOAA source)
{{collapse bottom}}
::#In the lead, any weaker tornadoes are noted without full summaries. For a hypothetical example: "In the month of July, 20 tornadoes occurred across the U.S., with 3 rated EF2, 10 rated EF1, and 22 rated EF0."
{{collapse top|Deuteranopic (green blind)}}
::#The hypothetical example above would be cited by the NOAA database set just to the monthly tornadoes, which is a reliable source.
]]
:As mentioned, I don't necessarily support this at this moment, but I wanted to throw a possible solution into the water. If consensus/compromise would be falling towards allowing this type of solution, I would be for it. '''The ]''' (] 19:54, 11 December 2024 (UTC)
{{collapse bottom}}
::That´s more or less what I intended with my second suggestion, and seems like a good basis for discussion. ] (]) 20:26, 11 December 2024 (UTC)
{{collapse top|Tritanopic (blue blind)}}
:::Almost every single tornado will have a non-NOAA source if you look for them (i.e. local news). So we’d end up excluding maybe 2-5%, so why not just include all of them and be done? ] (]) 21:09, 11 December 2024 (UTC)
]]
::::If almost every single tornado has local news coverage... what's even the point of being selective? Wouldn't they all be considered notable? ] (]) 21:14, 11 December 2024 (UTC)
{{collapse bottom}}
:::::That’s my point. ] (]) 21:18, 11 December 2024 (UTC)
::::::Playing devils advocate for a moment: Then the local news coverage source should also be listed with the NOAA primary source. While those of us (y’all and myself included) generally understand that fact, I’ll be honest, in the example article listed by Fram above, ], there is 0 non-NOAA sources outside of the lead. Out of the entire list article, which has 262 sources, 260 comes from NOAA and 2 come from non-NOAA sources. Part of the overall issue is that WikiProject Weather got in the habit of citing NOAA and then not anyone else since the info was already cited. The topic of “Is NOAA a primary source” has come up multiple times and the answer is yes it is (]). So technically, if we look at Misplaced Pages policy to the letter, that article is basically cited entirely by ] sources, which is actually cautioned against, not ], which is preferred over primary sources. Basically, a possible solution to not even change the list is to just add a secondary reliable sources to the tornadoes. Then, see where it goes from there. Anyone else think that may be a good idea? Actually see how many tornadoes do/do not have secondary sources?
::::::If one or two do not, then the list, bluntly, is fine (once non-NOAA is actually added). If 20+ do not in a monthly list, then we may have a true problem. As I see it, the problem is that primary is being used and secondary is basically being ignored, leading to Fram’s conclusion that most of the tornado may not be notable enough for the list. '''The ]''' (] 21:54, 11 December 2024 (UTC)
::'''Yes''', it should be mentioned in the list as its omission would be misleading (showing less tornadoes than there actually was), less accurate, and less comprehensive. I'm fine with a brief summary, mention, or omission of some of the events outside of the list only if certain details of the tornado would be inappropriate or rule-breaking. <span style="font-family:Times New Roman;font-size:100%;color:#00008B;background-color:transparent;;CSS">]]</span> 05:00, 14 December 2024 (UTC)
*{{sbb}} - Yes, if I understand the question. All tornadoes are sufficiently eventful and concerning that, if there is a list, they should be included in a list. Tornado warnings are disruptive. People who have been disturbed by tornado warnings and have headed for cover when there was no damage would still like to see that event in a list. ] (]) 00:06, 12 December 2024 (UTC)
**Tornado warnings are general, not for a specific tornado. "All tornadoes are sufficiently eventful"? Many tornadoes are likely to remain undetected as they are very minor and shortlived and if no camera or storm chaser is nearby and they happen on unpopulated land they will likely not be noted. Even among the ones listed. Look at e.g. ]; none of these 4 tornadoes were, as far as we know, eventful; we have no idea if tornado warnings were given, and if so where and when. As an aside, I have no idea why this is called the "July 7 event", these were not one event but can perhaps be considered two events (the ND ones and the Texas one have nothing to do with each other). Just labeling it with the date (so here "July 7") would be at least better. ] (]) 12:34, 12 December 2024 (UTC)


There are times when it's useful to list (or attempt to list) every tornado (like ]). I guess the bigger questions comes down to the effort to document every tornado in the United States each year, and how best to do that. The way we do it now, we have the yearly ], plus monthly lists in the US such as ], as well as individual outbreak articles, such as ], and sometimes those outbreak articles have individual lists, such as the ]. While that might seem like a lot of overlap, any single tornado has the potential to be notable. Take the EF2 tornadoes for example: none of the EF2 in the ] get a mention in the main outbreak article. But given the current length of the outbreak article (7,500 articles), it would be too much to include every single EF2. Now most of them weren't that significant, but an EF2 can still destroy a building, so they still deserve mention. Even EF0 and EF1's have the potential to cause significant impacts - the most recent tornadic death in New Jersey was caused by an F0. In the interest in being inclusive, I don't think it makes sense to be unnecessarily restrictive. At the same time, requiring non-NOAA sources could be tricky, since a lot of news sources just regurgitate NWS reports. I realized that while working on ]. I think the way that the severe weather project has been handling tornadoes is honestly pretty impressive. I should also note the importance of digging into each tornado directly, rather than just relying on random NCDC links, as there can be multiple reports for the same tornado if it crossed state/county lines, or if the tornado touched down multiple times. In short, I don't think much needs to change, other than maybe summarizing more here and there, and trying to include non-NOAA sources (when the info doesn't just repeat what's in the NOAA sources). ♫ ] (<small>]</small>) 18:11, 12 December 2024 (UTC)
{{clear}}


:Here’s my opinion: if it’s a list of tornadoes in a specific outbreak: I believe that '''ALL''' tornadoes that occurred in that outbreak, even if their impacts were trivial; need to be included. ]<sup>]</sup> 20:01, 13 December 2024 (UTC)
====Feedback on the proposed scheme====
::If we’re referring to the Tornadoes of YYYY articles and the like, then I think ] should be followed. And only list the more notable ones. But it really depends on the case. But if it’s concerning individual outbreaks; then every tornado needs to be listed. ]<sup>]</sup> 20:03, 13 December 2024 (UTC)
{{archive top|Normal feedback stage closed. ]<sup>]</sup> 23:33, 12 February 2022 (UTC)}}
:::If we're only listing tornadoes notable enough to be mentioned in the yearly article anyway, what's the point of even having the list? In any case, if we make such a move, there will still need to be a list of all tornadoes in project space so we can keep an accurate tally. ] (]) 05:38, 14 December 2024 (UTC)
Please leave any feedback here '''without supporting or opposing (formal discussion to happen at a later time)'''. We need to work together to make a better proposal. We have three things to keep in mind... contrast between colors, contrast between the colors and the map, and contrast between the colors and links. ]<sup>]</sup> 21:54, 6 February 2022 (UTC)
::::Tornadoes of YYYY isn't the same as the "List of tornadoes from M to M YYYY" lists that get created every year. ] (]) 12:54, 14 December 2024 (UTC)
:I never noticed that there was a color difference between disturbance and depression. Can I see what those colors might look like? In the map for Ivan (listed above), the disturbance and TD colors look the same. I'm only wondering based on the background that we use. ♫ ] (<small>]</small>) 22:32, 6 February 2022 (UTC)
:::::What may be more prudent here would be to split those M to M lists into monthly lists rather than omit tornadoes. ]<sup>]</sup> 18:48, 14 December 2024 (UTC)
::I don't think we ever actually had differing colors for tropical depressions and disturbances, since the difference between the two was always denoted by a shape change (triangle for post-trop, circles for tropical depressions and stronger). <span style="background:#ffff55">''''']'''''</span>&nbsp;<small style="font-size:calc(1em - 2pt)">(])</small> 22:37, 6 February 2022 (UTC)
::{{re|Chlod|Hurricanehink}} IIRC The color for disturbance was slightly lighter than tropical depression, almost to the point of being unnoticable. I think a change may be needed for infoboxes (to make it more noticeable), but not for the maps. ]<sup>]</sup> 22:38, 6 February 2022 (UTC) ::::::So, in all honesty '''yes''' even weak and unimpactful tornadoes should be included in these lists. If the lists grow too long; we should instead split the lists. ]<sup>]</sup> 18:50, 14 December 2024 (UTC)
:::::::] is a list focusing on one month and already reaches 118kb in size. This is why I in particular '''beg''' for a <nowiki>{{cite pns}} or {{cite storm events database}}</nowiki> template. I'd wager there's a non-zero chance that the Storm Events Database is the single most used citation across all of Misplaced Pages, and these lists are a big part of that. Cutting down the size in bytes can also be done by cutting summaries of tornadoes from outbreaks and simply including a main article tag with the small table, rather than the excerpt format used today. ] (]) 19:31, 14 December 2024 (UTC)
:::I just color dropped from Harvey's map, and both points for disturbance and depression are {{color box|#5ebaff}}#5ebaff. It's more the matter that this color represents winds below 34 knots, regardless of whether it's a TC, EC, disturbance etc. ] (]) 23:13, 6 February 2022 (UTC)
::::Anyways, the proposal parts for disturbance/PTC and ET are just for infoboxes since there are differences between colors there. ]<sup>]</sup> 23:19, 6 February 2022 (UTC)
:::::Wouldn't the changes also apply to maps? It might be confusing to use two different color schemes for maps and templates. ] (]) 23:25, 6 February 2022 (UTC)
::::::{{re|TornadoLGS}} We already have two different schemes in that regard. ET is gray in infoboxes but colored on maps w/ triangles. PT is a slightly lighter blue in infoboxes currently but same color as TD on maps. If we would want to adopt the regular scheme for ET, it would require some additional changes for templates since they currently do not differentiate between intensity for ET other than <64 kn and ≥64 kn. I would be okay with making disturbance a different color from TD to give a bit more distinction since it's not a cyclone during those stages. ]<sup>]</sup> 23:33, 6 February 2022 (UTC)
:::::::I'd like for all the colors to match up with the Infoboxes. Otherwise, I like and support the proposed changes. One slight note - should we rank the Categories using the same color scheme, such as the ], the ], etc. ♫ ] (<small>]</small>) 00:51, 7 February 2022 (UTC)
::::::::{{replyto|Hurricanehink}} If we gave tornadoes a separate color scheme, that would require changing tens of thousands of entries in tables. So, I'd be opposed to that unless the task could be automated. ] (]) 01:31, 7 February 2022 (UTC)
:::::I believe {{u|Asartea}}'s intention was for us to review the new colors in ], not reintroduce a rehashed version of the previous color scheme (which still has significant issues with links on colored backgrounds). In such a case, the proposed scheme would be (from TD to C5): {{color box|#{{storm colour/sandbox|td}}}}{{color box|#{{storm colour/sandbox|ts}}}}{{color box|#{{storm colour/sandbox|cat1}}}}{{color box|#{{storm colour/sandbox|cat2}}}}{{color box|#{{storm colour/sandbox|cat3}}}}{{color box|#{{storm colour/sandbox|cat4}}}}{{color box|#{{storm colour/sandbox|cat5}}}}.
:::::In any case, this is probably a step in the wrong direction. I'm opposed to using the above colors proposed above for infoboxes. In fact, it would be even more of an ACCESS violation to use the above since {{color box|#c464d9}} purple has an even lower contrast rate with links (2.51) compared to the {{color box|#FF6060}} previous Category 5 color (2.88). <span style="background:#ffff55">''''']'''''</span>&nbsp;<small style="font-size:calc(1em - 2pt)">(])</small> 01:09, 7 February 2022 (UTC)
:Could we simply step around this issue by formatting templates so that linked text is not placed against colored backgrounds? Adding contrast with links on top of other accessibility requirements is just making this more of a headache. The only place I know where linked text regularly appears on a background using these colors is the top of the storm infobox. ] (]) 02:02, 7 February 2022 (UTC)
::Found a solution to both problems and will be adding it in shortly. ]<sup>]</sup> 02:07, 7 February 2022 (UTC)
:::{{re|Chlod|Hurricanehink|TornadoLGS}} I removed the ET color and I modified all the others and believe them to be both colorblind compliant, AA compliant, and maintains a scaling color scheme. Thoughts? ]<sup>]</sup> 02:32, 7 February 2022 (UTC)
{{Clear}}
::::I tested out these colors in photoshop using a screenshot of the sample map given above. When actually put to a map, the colors don't have good contrast, especially between category 4 and category 5. The main issue, I think, is that it leans too heavily on pastels. I also think the scaling breaks down for cat 4 and 5. Ideally, it should be intuitive that, e.g. the category 5 color represents a greater intensity than the category 4 color without the viewer even needing to look at the legend (honestly that is one strength of the current colors). Since the color scheme I proposed earlier never got any support, I would say AC's does the best job of that. I like {{u|LightandDark2000}}'s idea, though, of not putting links in colored parts of templates, though.] (]) 03:35, 7 February 2022 (UTC)
:::::{{re|LightandDark2000|TornadoLGS}} I listed both options above. I readded the previous version to show what we have. Removing the links would definitely lift a large burden off of us in determining colors. ]<sup>]</sup> 03:46, 7 February 2022 (UTC)


I have no more hope of changing anything at this project, which is probably as bad as the former roads project when it comes to closing ranks and not seeing how completely inappropriate their efforts are to duplicate a database in all its excessive detail. ] has more than 500 tornadoes, most of them very ephemeral, and the suggestion to deal with this is ... creating a new cite template to reduce the size of the sources. Try to imagine some other weather phenomenon, say a hurricane or a winter storm or whetever, and having a place by place list describing in place X "damaged some vegetation and fencing", in place Y "damaged a small shed and utility trailer", in place Z "caused no known damage", elsewhere "no damage could be found.", and in many places strong winds were observed but nothing more. And buried among this endless list were the serious, noteworthy instances with deaths or truly massive damage. But hey, congratulations all around, we have repeated every instance from the weather database, good job people! ] (]) 14:45, 10 January 2025 (UTC)
*'''Oppose the color scheme in Astartea's sandbox; Strongly Support AC/Noah's New Color Proposal; Neutral on the current proposal (as of this writing)''', probably '''tilt oppose''' on that one. I agree that the current coloring system can use some changes, even if we don't agree on the exact system to go by. My favorite option so far is the one proposed by AC & Noah. The colors there are easily distinguishable (and definitely distinguishable for colorblind individuals), have a nice color progression, and is similar to the current coloring system. While I understand the WP:ACCESS concerns behind Astartea's proposal, those colors are inconsistent (no clear progression in shading and/or hue), not really aesthetically pleasant, and the lighter hues make it even harder to distinguish the colors. Thus, that system is a no-go for me. While the current proposal is better, I don't like how all of the shades have been lightened in color for a number of reasons. While it does have a clear progression, the lighter shades do make some of the colors appear closer to each other, and the new coloring system just doesn't seem to fit together as well - it seems a little jarring. I do believe that the current coloring system could use some improvements, but I don't believe that the latest proposal is the best possible version. And I will not back a coloring scheme unless I will be comfortable seeing the said system implemented on all of our weather articles and storm maps - as there are thousands of articles and track map images using these colors, we have to get it right the first time. These same colors are used for the tornado intensity scaling (F and EF scales) and winter storms (RSI). So we need a single, unified system. As for those Weather project users who oppose changing the colors just because ], or they feel that redoing all of the maps would be too much of an issue, I have this to say: Your personal opinions do not override project policy. As for the task of redoing the maps, Chlod has discussed ways to redo the maps by bots in a number of discussions off-wiki - all we need is for the track map generator data to be present on the images' Commons pages to do that. A bot can be written to automatically redo the track maps. So changing the colors is doable. ''''']''''' 🌀 (]) 03:12, 7 February 2022 (UTC)
*Regardless of whether or not the coloring system gets changed, '''I propose removing the links entirely from the colored part of the infobox'''. While it's nice to have the links there, I don't think they're necessary. We could link them elsewhere, or have those terms explained elsewhere in the articles using the templates. Given our difficulties in agreeing on a new coloring system, if the links are that much of an WP:ACCESS problem, then let's just remove the links entirely. Then, we can focus on whether or not to change the color system (and which new system we should use) without having to worry about bending over backwards just to accommodate the links. ''''']''''' 🌀 (]) 03:12, 7 February 2022 (UTC)
*:@]: This has already been done with {{T|infobox weather event}}, along with even more fixes that take into consideration much of ACCESS (besides the warnings section for now, because I was not involved in its creation). When we'll be able to transition to this improved infobox style, however, ]. As for ''replacing'' the current infoboxes and templates, I suggest not counting on it, since those boxes are too much of a template hellhole to mess with and ''not'' break anything. <span style="background:#ffff55">''''']'''''</span>&nbsp;<small style="font-size:calc(1em - 2pt)">(])</small> 04:07, 7 February 2022 (UTC)
{{Ping|Chlod}} You can transition to this new infobox style, once there has been an on-wiki discussion (RFC) and consensus to transition to it, since its a MAJOR change. However, I would argue that it's better to be simpler and call upon 1 infobox than call upon 5 separate infoboxes. I would also argue that we need to be careful over which warning centre is shown at the peak, especially with a system in the SHEM, where the peak could have come from a combination of MFR, BMKG, PNG NWS, BoM, MFNC, FMS, NZMS or MSNZ.] (]) 14:33, 7 February 2022 (UTC)


== RfC at ] ==
:@]: There are no "5 seperate infoboxes", there is only one (as looking at the documentation of {{T|infobox weather event}} would have already shown you). Each template is not a new infobox. The reason why it might appear that way is because each template provides a new scale to the box. This easily deals with the fact that we have one infobox with a large amount of parameters (e.g. in {{T|infobox tropical cyclone current}}, where there is <code>category</code>, <code>AUScategory</code>, <code>JMAtype</code>, <code>JMAcategory</code>, <code>IMDtype</code>, <code>IMDcategory</code>, <code>MFRtype</code>, and <code>MFRcategory</code>) with '''no further support''' for other agencies. Additionally, the order of what warning center can easily be changed by simply changing the order of the templates, unlike our existing infoboxes which '''do not''' provide this functionality and is instead fixed to one specific order. In case you want to show the precedence of one specific agency, you can just transclude the correct (or additional) agenc(y/ies), since the new infobox is based on issuing agencies, not specific sections of the world. With Wikidata, I can even compress the box to no longer require ''any'' parameters. ] has had this modular template construction style since at least 2005, and it certainly also fits well with the massively-decentralized storm information centers we have around the world. <span style="background:#ffff55">''''']'''''</span>&nbsp;<small style="font-size:calc(1em - 2pt)">(])</small> 14:50, 7 February 2022 (UTC)
{{archive bottom}}
====Sub-proposal 1: Links in the colored regions of infoboxes and templates====
{{archive top|Closing per ]: consensus exists to remove links from the colored region of weather infoboxes and templates. ]<sup>]</sup> 21:26, 12 February 2022 (UTC)}}
Should links be removed from the colored areas of infoboxes and templates or remain? ]<sup>]</sup> 03:57, 7 February 2022 (UTC)
*'''Support''' – While I would've liked keeping the links, since they seem to be causing so many issues with ], I think we should just remove them entirely. The links can simply be moved elsewhere in the template, or just addressed within the articles themselves. ''''']''''' 🌀 (]) 05:40, 7 February 2022 (UTC)
*'''Support''' Root of the cause.&nbsp;] ] 17:34, 7 February 2022 (UTC)
*'''Support removal''' If we remove links from colored areas, the only ] issue is ensuring that the colors are sufficiently distinct from each other, which we've already come a long way in doing. ] (]) 17:49, 7 February 2022 (UTC)
*<s>'''Oppose''' The status quo has sufficiently different colors, I believe, that ] does not apply. (Feel free to reply if you disagree.) ] (]) 12:08, 8 February 2022 (UTC)</s>
:*{{re|Chicdat}} You realize this subsection is just about removing or keeping links in the colored regions of templates and not about the above color change proposal? Some of the colors do not pass AA compliance when there are links in those areas of the infobox. LightandDark proposed to simply remove the links from the colored regions of infoboxes since that was the root of that problem. ]<sup>]</sup> 12:15, 8 February 2022 (UTC)
:**No, I didn't realize that. But what do you mean by {{tq|removing links from colored areas}}? ] (]) 12:17, 8 February 2022 (UTC)
:::*For example, ] has a link to the scale at the top within the category specific colored region. Most of the current colors fail AA in some manner against either the regular link color or the visited link color. The proposal was simply to remove the links from those areas of all our templates. Articles should have links to the scales and other things in both the lead and body anyways. ]<sup>]</sup> 12:24, 8 February 2022 (UTC)
::::*Oh, I '''support''' that. After all, the links will always be in other parts of the article. ] (]) 12:30, 8 February 2022 (UTC)
*'''Support''' <span style="background:#ffff55">''''']'''''</span>&nbsp;<small style="font-size:calc(1em - 2pt)">(])</small> 23:58, 8 February 2022 (UTC)
{{archive bottom}}
====Formal discussion (RfC)====
Please leave comments related to the RfC here. ]<sup>]</sup> 23:33, 12 February 2022 (UTC)
*'''Support''' as proposer. ]<sup>]</sup> 23:33, 12 February 2022 (UTC)


An RfC has been started to challenge to authenticity of a supposed picture of the Cookeville tornado that was pulled from Reddit and added to the article. ] (]) 19:48, 11 December 2024 (UTC)
:*'''Support''' Accessibility matters and all projects should strive towards it. ] (]) 00:36, 13 February 2022 (UTC)
*'''Strongly Support''' – Per the proposer. This needs to happen. We've already agreed to remove the links from the color bar sections of the various infoboxes we use for the storms and tornadoes, and now, we need to finish the rest of the work. The current colors have ] issues. Some of the colors are difficult to tell apart for readers with normal vision, like me and Noah, and the current color scheme uses multiple colors that have shades too similar to each other for colorblind or disabled readers to tell apart. For the SSHWS scale (the main coloring system used, and the one used for the NATL and EPAC hurricane basins, and the Fujita and Enhanced Fujita scale for tornado articles), the Cat 1–4 colors are simply too close too each other, especially for Cat 1 vs. Cat 2, and Cat 2 vs. Cat 3, where the color contrasting is the worst. I have difficulty telling apart the Cat 1–4 colors at times, especially when the most similar shades are right next to each other (mostly in the cases I outlined earlier). Oftentimes, I find myself having to open up the track map images to their full resolutions just to differentiate some of the specific track points, and even then, I still have issues in some cases. And I consider myself to have very good color vision. If I'm struggling with differentiating the colors with the current system, then a whole multitude of other readers have this issue as well, especially our users with colorblindness or other vision issues. We don't have any of these issues with the new, proposed coloring system. Not only are the new colors much easier to differentiate for people with normal color vision (myself included), but they're also much easier to differentiate for colorblind individuals, as illustrated in the charts and the images above. Additionally, the newer coloring system is largely similar to the current system (so there's that element of familiarity), and the color progression feels natural and easy to follow, making the newer system an excellent solution. As such, I believe that we should replace the current coloring system with the newer one proposed by Noah and AC. For those people who are opposed to changing the current coloring system just because you favor the old system or think that no changes are needed, let me remind you of a couple of things: 1) Just because ] doesn't mean the changes shouldn't go forward, and 2) ]. On the issue of replacing the track maps, Chlod has already proposed a way of dealing with this problem, by coding a bot account to automatically generate new track maps with the new coloring system. This can be done on any track map for which the track map generator data, and the vast majority of track map images do have the track map generator data displayed on Commons. The others can be manually updated. On the issue of people being used to the old system, I would like to repeat what Chlod said earlier, which is that humans can and ''do'' adapt to changes. This is another change that we'll simply have to adapt to. The new coloring system is similar to the old one, so it shouldn't be too jarring for those used to the older system, but at the same time, it makes the colors much easier to differentiate and also more accessible to our colorblind readers, which needs to happen. Also, WP:ACCESS is a site-wide Misplaced Pages policy. Familiarity (or status quo) is not. All things considered, I think this is a good proposal and one that we should implement. ''''']''''' 🌀 (]) 01:53, 13 February 2022 (UTC)
*'''Support''' At this point, I don't think further discussing the color scheme will get us far. While I've voiced my own ideas for colors, I think anything beyond what I've already said would be nitpicking. The proposed colors improve contrast for both normal-sighted and colorblind individuals. ] (]) 02:17, 13 February 2022 (UTC)
*'''Support''' per above. 🌀]]]🏈 |''']''' 05:00, 13 February 2022 (UTC)
*'''Support''' per above. ] (]) 07:30, 13 February 2022 (UTC)
*'''Comment''' What are the proposed colors again? ] (]) 11:14, 13 February 2022 (UTC)
:*{{re|Chicdat}} The colors table under the RfC banner. ]<sup>]</sup> 11:47, 13 February 2022 (UTC)
*'''Support''' This proposal leaves out the bad part of the earlier proposal and keeps the good. ] (]) 11:49, 13 February 2022 (UTC)
*'''Support''', I like it, and it makes sense to change the colors (which were picked decades ago without accessibility concerns). ♫ ] (<small>]</small>) 18:28, 15 February 2022 (UTC)
*'''Neutral''', I still do not feel like a color change is still warranted given the same reasoning I had in the original RfC. The contrast in maps against the blue ocean are strong for the original scheme, land is still hit or miss (that's going to be the case for any proposed scheme), and the contrast between different category colors are close to where I personally see a good compromise between aesthetics and accessibility residing. I do not mind the proposed scheme, however, strongly encourage further experimenting with the Severe TS and C1 colors. They are not great. ] (]) 06:40, 20 February 2022 (UTC)
{{abot}}
===Infobox & Template colors===
{{closed rfc top
| status =
| result = There is consensus to implement the proposed changes to the various colour schemes. No substantive opposition was put forward. ] <small>( ] · ] )</small> 18:47, 18 March 2022 (UTC)
}}
Should the above colors for the maps also be adopted for infoboxes and other weather templates using the same scale? Should the timeline background color be changed for all weather articles?


== Proposal for ] ==
It has been brought to my attention that the above RfC may not have been clear about the entire scope of the changes. Given that consensus was achieved above to remove links from infoboxes for colored regions, that contrast aspect is no longer an issue. However, two issues still remain. Some people have mentioned above that they want to keep consistency between the maps and the infoboxes as it could be confusing if there are differences between the two. Additionally, the color blindness issue still remains for those who use colors to tell apart different statuses as the same contrast issue between colors exists, especially when multiple statuses are in an infobox for different agencies. This proposal increases the contrast between colors in infoboxes and other templates which use the same scale to match the maps which were changed in the above RfC. I recently also discovered a serious breach of MOS:ACCESS on the timelines where the TS color blends in with the background for folks who possess a color blindness. Another header is added below to provide a change that in conjunction with the new colors will fix that issue as well. ]<sup>]</sup> 15:33, 26 February 2022 (UTC)


Per the above comment by ] above, we should probably have template for referencing storm events, since, as the user said, "there's a non-zero chance that the Storm Events Database is the single most used citation across all of Misplaced Pages." Every single URL has the same beginning, so such a template might also need something like ], which shortens the URL for TCR's released by the NHC.
====Proposed colors====
=====SSHWS colors=====
The colors in the first table are the same that were proposed in the RfC above.
<div style="text-align: center">
{| class="wikitable" style="text-align: center; margin-top: 0"
|+ Proposed colors
! rowspan="2" | Category !! colspan="2" | Normal !! colspan="2" | Protanopic !! colspan="2" | Deuteranopic !! colspan="2" | Tritanopic
|-
! <abbr title="Current">C</abbr> !! <abbr title="Proposed">P</abbr> !! <abbr title="Current">C</abbr> !! <abbr title="Proposed">P</abbr> !! <abbr title="Current">C</abbr> !! <abbr title="Proposed">P</abbr> !! <abbr title="Current">C</abbr> !! <abbr title="Proposed">P</abbr>
|-
| Potential Tropical Cyclone or Disturbance
| style="width: 32px; height: 32px; background-color: #80CCFF" |
| style="width: 32px; height: 32px; background-color: #72A9CD" |
| style="width: 32px; height: 32px; background-color: #B3C0F8" |
| style="width: 32px; height: 32px; background-color: #979fc7" |
| style="width: 32px; height: 32px; background-color: #B2C0FF" |
| style="width: 32px; height: 32px; background-color: #989ecf" |
| style="width: 32px; height: 32px; background-color: #73D0E1" |
| style="width: 32px; height: 32px; background-color: #6babb9" |
|-
| Tropical Depression
| style="width: 32px; height: 32px; background-color: #5EBAFF" |
| style="width: 32px; height: 32px; background-color: #5EBAFF" |
| style="width: 32px; height: 32px; background-color: #9CAFF6" |
| style="width: 32px; height: 32px; background-color: #9CAFF6" |
| style="width: 32px; height: 32px; background-color: #92B0FF" |
| style="width: 32px; height: 32px; background-color: #92B0FF" |
| style="width: 32px; height: 32px; background-color: #47C2D2" |
| style="width: 32px; height: 32px; background-color: #47C2D2" |
|-
| Tropical Storm
| style="width: 32px; height: 32px; background-color: #00FAF4" |
| style="width: 32px; height: 32px; background-color: #00FAF4" |
| style="width: 32px; height: 32px; background-color: #E1DDE3" |
| style="width: 32px; height: 32px; background-color: #E1DDE3" |
| style="width: 32px; height: 32px; background-color: #E7D9FB" |
| style="width: 32px; height: 32px; background-color: #E7D9FB" |
| style="width: 32px; height: 32px; background-color: #84F0FF" |
| style="width: 32px; height: 32px; background-color: #84F0FF" |
|-
| Severe Tropical Storm
| style="width: 32px; height: 32px; background-color: #CCFFFF" |
| style="width: 32px; height: 32px; background-color: #B4FDA8" |
| style="width: 32px; height: 32px; background-color: #F8F3F8" |
| style="width: 32px; height: 32px; background-color: #feea9f" |
| style="width: 32px; height: 32px; background-color: #FFF1FD" |
| style="width: 32px; height: 32px; background-color: #ffe6d2" |
| style="width: 32px; height: 32px; background-color: #E8F7FF" |
| style="width: 32px; height: 32px; background-color: #cef0ff" |
|-
| Category 1
| style="width: 32px; height: 32px; background-color: #FFFFCC" |
| style="width: 32px; height: 32px; background-color: #FFF795" |
| style="width: 32px; height: 32px; background-color: #FFFCF3" |
| style="width: 32px; height: 32px; background-color: #fff3cb" |
| style="width: 32px; height: 32px; background-color: #FFE2C1" |
| style="width: 32px; height: 32px; background-color: #fff1e4" |
| style="width: 32px; height: 32px; background-color: #FEFBFF" |
| style="width: 32px; height: 32px; background-color: #ffeff7" |
|-
| Category 2
| style="width: 32px; height: 32px; background-color: #FFE775" |
| style="width: 32px; height: 32px; background-color: #FFD821" |
| style="width: 32px; height: 32px; background-color: #FFE775" |
| style="width: 32px; height: 32px; background-color: #f6da27" |
| style="width: 32px; height: 32px; background-color: #FFC140" |
| style="width: 32px; height: 32px; background-color: #ffd393" |
| style="width: 32px; height: 32px; background-color: #FFDEEA" |
| style="width: 32px; height: 32px; background-color: #ffcdd8" |
|-
| Category 3
| style="width: 32px; height: 32px; background-color: #FFC140" |
| style="width: 32px; height: 32px; background-color: #FF8F20" |
| style="width: 32px; height: 32px; background-color: #E4CC43" |
| style="width: 32px; height: 32px; background-color: #c0aa2c" |
| style="width: 32px; height: 32px; background-color: #FFC140" |
| style="width: 32px; height: 32px; background-color: #d9a119" |
| style="width: 32px; height: 32px; background-color: #FFB8C4" |
| style="width: 32px; height: 32px; background-color: #ff8790" |
|-
| Category 4
| style="width: 32px; height: 32px; background-color: #FF8F20" |
| style="width: 32px; height: 32px; background-color: #FF6060" |
| style="width: 32px; height: 32px; background-color: #C0AA2C" |
| style="width: 32px; height: 32px; background-color: #9f9473" |
| style="width: 32px; height: 32px; background-color: #D9A119" |
| style="width: 32px; height: 32px; background-color: #b68e56" |
| style="width: 32px; height: 32px; background-color: #FF8790" |
| style="width: 32px; height: 32px; background-color: #ff6065" |
|-
| Category 5
| style="width: 32px; height: 32px; background-color: #FF6060" |
| style="width: 32px; height: 32px; background-color: #C464D9" |
| style="width: 32px; height: 32px; background-color: #9F9473" |
| style="width: 32px; height: 32px; background-color: #5386f4" |
| style="width: 32px; height: 32px; background-color: #B68E56" |
| style="width: 32px; height: 32px; background-color: #6b89cc" |
| style="width: 32px; height: 32px; background-color: #FF6065" |
| style="width: 32px; height: 32px; background-color: #b57a83" |
|}
</div>
=====Enhanced Fujita scale (for tornadoes)=====
In the spirit of keeping the scales consistent across Misplaced Pages, I have proposed using the TS and C1-C5 colors above for the EF scale. This is more similar to the scale used by the , however, I think we should try to keep scales somewhat consistent across weather.
<div style="text-align: center">
{| class="wikitable" style="text-align: center; margin-top: 0"
|+ Proposed colors
! rowspan="2" | Category !! colspan="2" | Normal !! colspan="2" | Protanopic !! colspan="2" | Deuteranopic !! colspan="2" | Tritanopic
|-
! <abbr title="Current">C</abbr> !! <abbr title="Proposed">P</abbr> !! <abbr title="Current">C</abbr> !! <abbr title="Proposed">P</abbr> !! <abbr title="Current">C</abbr> !! <abbr title="Proposed">P</abbr> !! <abbr title="Current">C</abbr> !! <abbr title="Proposed">P</abbr>
|-
| EF0
| style="width: 32px; height: 32px; background-color: #00FAF4" |
| style="width: 32px; height: 32px; background-color: #00FAF4" |
| style="width: 32px; height: 32px; background-color: #E1DDE3" |
| style="width: 32px; height: 32px; background-color: #E1DDE3" |
| style="width: 32px; height: 32px; background-color: #E7D9FB" |
| style="width: 32px; height: 32px; background-color: #E7D9FB" |
| style="width: 32px; height: 32px; background-color: #84F0FF" |
| style="width: 32px; height: 32px; background-color: #84F0FF" |
|-
| EF1
| style="width: 32px; height: 32px; background-color: #FFFFCC" |
| style="width: 32px; height: 32px; background-color: #FFF795" |
| style="width: 32px; height: 32px; background-color: #FFFCF3" |
| style="width: 32px; height: 32px; background-color: #fff3cb" |
| style="width: 32px; height: 32px; background-color: #FFE2C1" |
| style="width: 32px; height: 32px; background-color: #fff1e4" |
| style="width: 32px; height: 32px; background-color: #FEFBFF" |
| style="width: 32px; height: 32px; background-color: #ffeff7" |
|-
| EF2
| style="width: 32px; height: 32px; background-color: #FFE775" |
| style="width: 32px; height: 32px; background-color: #FFD821" |
| style="width: 32px; height: 32px; background-color: #FFE775" |
| style="width: 32px; height: 32px; background-color: #f6da27" |
| style="width: 32px; height: 32px; background-color: #FFC140" |
| style="width: 32px; height: 32px; background-color: #ffd393" |
| style="width: 32px; height: 32px; background-color: #FFDEEA" |
| style="width: 32px; height: 32px; background-color: #ffcdd8" |
|-
| EF3
| style="width: 32px; height: 32px; background-color: #FFC140" |
| style="width: 32px; height: 32px; background-color: #FF8F20" |
| style="width: 32px; height: 32px; background-color: #E4CC43" |
| style="width: 32px; height: 32px; background-color: #c0aa2c" |
| style="width: 32px; height: 32px; background-color: #FFC140" |
| style="width: 32px; height: 32px; background-color: #d9a119" |
| style="width: 32px; height: 32px; background-color: #FFB8C4" |
| style="width: 32px; height: 32px; background-color: #ff8790" |
|-
| EF4
| style="width: 32px; height: 32px; background-color: #FF8F20" |
| style="width: 32px; height: 32px; background-color: #FF6060" |
| style="width: 32px; height: 32px; background-color: #C0AA2C" |
| style="width: 32px; height: 32px; background-color: #9f9473" |
| style="width: 32px; height: 32px; background-color: #D9A119" |
| style="width: 32px; height: 32px; background-color: #b68e56" |
| style="width: 32px; height: 32px; background-color: #FF8790" |
| style="width: 32px; height: 32px; background-color: #ff6065" |
|-
| EF5
| style="width: 32px; height: 32px; background-color: #FF6060" |
| style="width: 32px; height: 32px; background-color: #C464D9" |
| style="width: 32px; height: 32px; background-color: #9F9473" |
| style="width: 32px; height: 32px; background-color: #5386f4" |
| style="width: 32px; height: 32px; background-color: #B68E56" |
| style="width: 32px; height: 32px; background-color: #6b89cc" |
| style="width: 32px; height: 32px; background-color: #FF6065" |
| style="width: 32px; height: 32px; background-color: #b57a83" |
|}
</div>
=====Western Pacific (JMA)=====
<div style="text-align: center">
{| class="wikitable" style="text-align: center; margin-top: 0"
|+ Proposed colors (International Scale)
! rowspan="2" | Category !! colspan="2" | Normal !! colspan="2" | Protanopic !! colspan="2" | Deuteranopic !! colspan="2" | Tritanopic
|-
! <abbr title="Current">C</abbr> !! <abbr title="Proposed">P</abbr> !! <abbr title="Current">C</abbr> !! <abbr title="Proposed">P</abbr> !! <abbr title="Current">C</abbr> !! <abbr title="Proposed">P</abbr> !! <abbr title="Current">C</abbr> !! <abbr title="Proposed">P</abbr>
|-
| Tropical Depression
| style="width: 32px; height: 32px; background-color: #5EBAFF" |
| style="width: 32px; height: 32px; background-color: #5EBAFF" |
| style="width: 32px; height: 32px; background-color: #9CAFF6" |
| style="width: 32px; height: 32px; background-color: #9CAFF6" |
| style="width: 32px; height: 32px; background-color: #92B0FF" |
| style="width: 32px; height: 32px; background-color: #92B0FF" |
| style="width: 32px; height: 32px; background-color: #47C2D2" |
| style="width: 32px; height: 32px; background-color: #47C2D2" |
|-
| Tropical Storm
| style="width: 32px; height: 32px; background-color: #00FAF4" |
| style="width: 32px; height: 32px; background-color: #00FAF4" |
| style="width: 32px; height: 32px; background-color: #E1DDE3" |
| style="width: 32px; height: 32px; background-color: #E1DDE3" |
| style="width: 32px; height: 32px; background-color: #E7D9FB" |
| style="width: 32px; height: 32px; background-color: #E7D9FB" |
| style="width: 32px; height: 32px; background-color: #84F0FF" |
| style="width: 32px; height: 32px; background-color: #84F0FF" |
|-
| Severe Tropical Storm
| style="width: 32px; height: 32px; background-color: #CCFFFF" |
| style="width: 32px; height: 32px; background-color: #B4FDA8" |
| style="width: 32px; height: 32px; background-color: #F8F3F8" |
| style="width: 32px; height: 32px; background-color: #feea9f" |
| style="width: 32px; height: 32px; background-color: #FFF1FD" |
| style="width: 32px; height: 32px; background-color: #ffe6d2" |
| style="width: 32px; height: 32px; background-color: #E8F7FF" |
| style="width: 32px; height: 32px; background-color: #cef0ff" |
|-
| Typhoon
| style="width: 32px; height: 32px; background-color: #fdaf9a" |
| style="width: 32px; height: 32px; background-color: #FF6060" |
| style="width: 32px; height: 32px; background-color: #ccc0a1" |
| style="width: 32px; height: 32px; background-color: #9f9473" |
| style="width: 32px; height: 32px; background-color: #e3b997" |
| style="width: 32px; height: 32px; background-color: #b68e56" |
| style="width: 32px; height: 32px; background-color: #ffaab6" |
| style="width: 32px; height: 32px; background-color: #FF8790" |
|}
</div>


There is a little bit of inconsistency over the publisher and author, but since we don't know the people who actually write the event reports (other than the local NWS office), I think the default publisher should be "National Climatic Data Center". Does anybody with template knowledge think they could work on this? I can try tackling it after the new year if no one does it. ♫ ] (<small>]</small>) 20:28, 14 December 2024 (UTC)
=====Southern Hemisphere=====
<div style="text-align: center">
{| class="wikitable" style="text-align: center; margin-top: 0"
|+ Proposed colors
! rowspan="2" | Category !! colspan="2" | Normal !! colspan="2" | Protanopic !! colspan="2" | Deuteranopic !! colspan="2" | Tritanopic
|-
! <abbr title="Current">C</abbr> !! <abbr title="Proposed">P</abbr> !! <abbr title="Current">C</abbr> !! <abbr title="Proposed">P</abbr> !! <abbr title="Current">C</abbr> !! <abbr title="Proposed">P</abbr> !! <abbr title="Current">C</abbr> !! <abbr title="Proposed">P</abbr>
|-
| Disturbance
| style="width: 32px; height: 32px; background-color: #80CCFF" |
| style="width: 32px; height: 32px; background-color: #72A9CD" |
| style="width: 32px; height: 32px; background-color: #B3C0F8" |
| style="width: 32px; height: 32px; background-color: #979fc7" |
| style="width: 32px; height: 32px; background-color: #B2C0FF" |
| style="width: 32px; height: 32px; background-color: #989ecf" |
| style="width: 32px; height: 32px; background-color: #73D0E1" |
| style="width: 32px; height: 32px; background-color: #6babb9" |
|-
| TD/TL
| style="width: 32px; height: 32px; background-color: #5EBAFF" |
| style="width: 32px; height: 32px; background-color: #5EBAFF" |
| style="width: 32px; height: 32px; background-color: #9CAFF6" |
| style="width: 32px; height: 32px; background-color: #9CAFF6" |
| style="width: 32px; height: 32px; background-color: #92B0FF" |
| style="width: 32px; height: 32px; background-color: #92B0FF" |
| style="width: 32px; height: 32px; background-color: #47C2D2" |
| style="width: 32px; height: 32px; background-color: #47C2D2" |
|-
| F1/A1/MTS
| style="width: 32px; height: 32px; background-color: #00FAF4" |
| style="width: 32px; height: 32px; background-color: #00FAF4" |
| style="width: 32px; height: 32px; background-color: #E1DDE3" |
| style="width: 32px; height: 32px; background-color: #E1DDE3" |
| style="width: 32px; height: 32px; background-color: #E7D9FB" |
| style="width: 32px; height: 32px; background-color: #E7D9FB" |
| style="width: 32px; height: 32px; background-color: #84F0FF" |
| style="width: 32px; height: 32px; background-color: #84F0FF" |
|-
| F2/A2/STS
| style="width: 32px; height: 32px; background-color: #CCFFFF" |
| style="width: 32px; height: 32px; background-color: #B4FDA8" |
| style="width: 32px; height: 32px; background-color: #F8F3F8" |
| style="width: 32px; height: 32px; background-color: #feea9f" |
| style="width: 32px; height: 32px; background-color: #FFF1FD" |
| style="width: 32px; height: 32px; background-color: #ffe6d2" |
| style="width: 32px; height: 32px; background-color: #E8F7FF" |
| style="width: 32px; height: 32px; background-color: #cef0ff" |
|-
| F3/A3/TC
| style="width: 32px; height: 32px; background-color: #FFFFCC" |
| style="width: 32px; height: 32px; background-color: #FFD821" |
| style="width: 32px; height: 32px; background-color: #FFFCF3" |
| style="width: 32px; height: 32px; background-color: #f6da27" |
| style="width: 32px; height: 32px; background-color: #FFE2C1" |
| style="width: 32px; height: 32px; background-color: #ffd393" |
| style="width: 32px; height: 32px; background-color: #FEFBFF" |
| style="width: 32px; height: 32px; background-color: #ffcdd8" |
|-
| F4/A4/ITC
| style="width: 32px; height: 32px; background-color: #FFC140" |
| style="width: 32px; height: 32px; background-color: #FF6060" |
| style="width: 32px; height: 32px; background-color: #E4CC43" |
| style="width: 32px; height: 32px; background-color: #9f9473" |
| style="width: 32px; height: 32px; background-color: #FFC140" |
| style="width: 32px; height: 32px; background-color: #b68e56" |
| style="width: 32px; height: 32px; background-color: #FFB8C4" |
| style="width: 32px; height: 32px; background-color: #ff6065" |
|-
| F5/A5/VITC
| style="width: 32px; height: 32px; background-color: #FF6060" |
| style="width: 32px; height: 32px; background-color: #C464D9" |
| style="width: 32px; height: 32px; background-color: #9F9473" |
| style="width: 32px; height: 32px; background-color: #5386f4" |
| style="width: 32px; height: 32px; background-color: #B68E56" |
| style="width: 32px; height: 32px; background-color: #6b89cc" |
| style="width: 32px; height: 32px; background-color: #FF6065" |
| style="width: 32px; height: 32px; background-color: #b57a83" |
|}
</div>
=====North Indian Ocean=====
<div style="text-align: center">
{| class="wikitable" style="text-align: center; margin-top: 0"
|+ Proposed colors
! rowspan="2" | Category !! colspan="2" | Normal !! colspan="2" | Protanopic !! colspan="2" | Deuteranopic !! colspan="2" | Tritanopic
|-
! <abbr title="Current">C</abbr> !! <abbr title="Proposed">P</abbr> !! <abbr title="Current">C</abbr> !! <abbr title="Proposed">P</abbr> !! <abbr title="Current">C</abbr> !! <abbr title="Proposed">P</abbr> !! <abbr title="Current">C</abbr> !! <abbr title="Proposed">P</abbr>
|-
| Land Depression/Depression
| style="width: 32px; height: 32px; background-color: #80CCFF" |
| style="width: 32px; height: 32px; background-color: #72A9CD" |
| style="width: 32px; height: 32px; background-color: #B3C0F8" |
| style="width: 32px; height: 32px; background-color: #979fc7" |
| style="width: 32px; height: 32px; background-color: #B2C0FF" |
| style="width: 32px; height: 32px; background-color: #989ecf" |
| style="width: 32px; height: 32px; background-color: #73D0E1" |
| style="width: 32px; height: 32px; background-color: #6babb9" |
|-
| Deep Depression
| style="width: 32px; height: 32px; background-color: #5EBAFF" |
| style="width: 32px; height: 32px; background-color: #5EBAFF" |
| style="width: 32px; height: 32px; background-color: #9CAFF6" |
| style="width: 32px; height: 32px; background-color: #9CAFF6" |
| style="width: 32px; height: 32px; background-color: #92B0FF" |
| style="width: 32px; height: 32px; background-color: #92B0FF" |
| style="width: 32px; height: 32px; background-color: #47C2D2" |
| style="width: 32px; height: 32px; background-color: #47C2D2" |
|-
| Cyclonic Storm
| style="width: 32px; height: 32px; background-color: #00FAF4" |
| style="width: 32px; height: 32px; background-color: #00FAF4" |
| style="width: 32px; height: 32px; background-color: #E1DDE3" |
| style="width: 32px; height: 32px; background-color: #E1DDE3" |
| style="width: 32px; height: 32px; background-color: #E7D9FB" |
| style="width: 32px; height: 32px; background-color: #E7D9FB" |
| style="width: 32px; height: 32px; background-color: #84F0FF" |
| style="width: 32px; height: 32px; background-color: #84F0FF" |
|-
| Severe Cyclonic Storm
| style="width: 32px; height: 32px; background-color: #CCFFFF" |
| style="width: 32px; height: 32px; background-color: #B4FDA8" |
| style="width: 32px; height: 32px; background-color: #F8F3F8" |
| style="width: 32px; height: 32px; background-color: #feea9f" |
| style="width: 32px; height: 32px; background-color: #FFF1FD" |
| style="width: 32px; height: 32px; background-color: #ffe6d2" |
| style="width: 32px; height: 32px; background-color: #E8F7FF" |
| style="width: 32px; height: 32px; background-color: #cef0ff" |
|-
| Very Severe Cyclonic Storm
| style="width: 32px; height: 32px; background-color: #FFFFCC" |
| style="width: 32px; height: 32px; background-color: #FFD821" |
| style="width: 32px; height: 32px; background-color: #FFFCF3" |
| style="width: 32px; height: 32px; background-color: #f6da27" |
| style="width: 32px; height: 32px; background-color: #FFE2C1" |
| style="width: 32px; height: 32px; background-color: #ffd393" |
| style="width: 32px; height: 32px; background-color: #FEFBFF" |
| style="width: 32px; height: 32px; background-color: #ffcdd8" |
|-
| Extremely Severe Cyclonic Storm
| style="width: 32px; height: 32px; background-color: #FFC140" |
| style="width: 32px; height: 32px; background-color: #FF6060" |
| style="width: 32px; height: 32px; background-color: #E4CC43" |
| style="width: 32px; height: 32px; background-color: #9f9473" |
| style="width: 32px; height: 32px; background-color: #FFC140" |
| style="width: 32px; height: 32px; background-color: #b68e56" |
| style="width: 32px; height: 32px; background-color: #FFB8C4" |
| style="width: 32px; height: 32px; background-color: #ff6065" |
|-
| Super Cyclonic Storm
| style="width: 32px; height: 32px; background-color: #FF6060" |
| style="width: 32px; height: 32px; background-color: #C464D9" |
| style="width: 32px; height: 32px; background-color: #9F9473" |
| style="width: 32px; height: 32px; background-color: #5386f4" |
| style="width: 32px; height: 32px; background-color: #B68E56" |
| style="width: 32px; height: 32px; background-color: #6b89cc" |
| style="width: 32px; height: 32px; background-color: #FF6065" |
| style="width: 32px; height: 32px; background-color: #b57a83" |
|}
</div>
===== North American winter storms (])=====
<div style="text-align: center">
{| class="wikitable" style="text-align: center; margin-top: 0"
|+ Proposed colors
! rowspan="2" | Category !! colspan="2" | Normal !! colspan="2" | Protanopic !! colspan="2" | Deuteranopic !! colspan="2" | Tritanopic
|-
! <abbr title="Current">C</abbr> !! <abbr title="Proposed">P</abbr> !! <abbr title="Current">C</abbr> !! <abbr title="Proposed">P</abbr> !! <abbr title="Current">C</abbr> !! <abbr title="Proposed">P</abbr> !! <abbr title="Current">C</abbr> !! <abbr title="Proposed">P</abbr>
|-
| Category 1
| style="width: 32px; height: 32px; background-color: #FFFFCC" |
| style="width: 32px; height: 32px; background-color: #FFF795" |
| style="width: 32px; height: 32px; background-color: #FFFCF3" |
| style="width: 32px; height: 32px; background-color: #fff3cb" |
| style="width: 32px; height: 32px; background-color: #FFE2C1" |
| style="width: 32px; height: 32px; background-color: #fff1e4" |
| style="width: 32px; height: 32px; background-color: #FEFBFF" |
| style="width: 32px; height: 32px; background-color: #ffeff7" |
|-
| Category 2
| style="width: 32px; height: 32px; background-color: #FFE775" |
| style="width: 32px; height: 32px; background-color: #FFD821" |
| style="width: 32px; height: 32px; background-color: #FFE775" |
| style="width: 32px; height: 32px; background-color: #f6da27" |
| style="width: 32px; height: 32px; background-color: #FFC140" |
| style="width: 32px; height: 32px; background-color: #ffd393" |
| style="width: 32px; height: 32px; background-color: #FFDEEA" |
| style="width: 32px; height: 32px; background-color: #ffcdd8" |
|-
| Category 3
| style="width: 32px; height: 32px; background-color: #FFC140" |
| style="width: 32px; height: 32px; background-color: #FF8F20" |
| style="width: 32px; height: 32px; background-color: #E4CC43" |
| style="width: 32px; height: 32px; background-color: #c0aa2c" |
| style="width: 32px; height: 32px; background-color: #FFC140" |
| style="width: 32px; height: 32px; background-color: #d9a119" |
| style="width: 32px; height: 32px; background-color: #FFB8C4" |
| style="width: 32px; height: 32px; background-color: #ff8790" |
|-
| Category 4
| style="width: 32px; height: 32px; background-color: #FF8F20" |
| style="width: 32px; height: 32px; background-color: #FF6060" |
| style="width: 32px; height: 32px; background-color: #C0AA2C" |
| style="width: 32px; height: 32px; background-color: #9f9473" |
| style="width: 32px; height: 32px; background-color: #D9A119" |
| style="width: 32px; height: 32px; background-color: #b68e56" |
| style="width: 32px; height: 32px; background-color: #FF8790" |
| style="width: 32px; height: 32px; background-color: #ff6065" |
|-
| Category 5
| style="width: 32px; height: 32px; background-color: #FF6060" |
| style="width: 32px; height: 32px; background-color: #C464D9" |
| style="width: 32px; height: 32px; background-color: #9F9473" |
| style="width: 32px; height: 32px; background-color: #5386f4" |
| style="width: 32px; height: 32px; background-color: #B68E56" |
| style="width: 32px; height: 32px; background-color: #6b89cc" |
| style="width: 32px; height: 32px; background-color: #FF6065" |
| style="width: 32px; height: 32px; background-color: #b57a83" |
|}
</div>
====Example====
Here is a rendering of how infobox statuses and timelines may be confused due to the similarities in colors. Certain template text is slightly smaller than prose text and could be harder for some editors to read. If more statuses are added down the road (specifically WPAC) as an example, then the current problem could be amplified.
{{collapse top|Images comparing infobox and timeline status colors}}
;Blue Blindness
]
</br>
]
;Green Blindness
]
</br>
]
;Red Blindness
]
</br>
]
{{collapse bottom}}


:On the database I've been experimenting with a citation that displays as ". I think the WFO and ID are all that are needed, but I'm definitely in support of the begin location or timestamp being alongside the WFO. ] (]) 20:38, 14 December 2024 (UTC)
====Proposed timeline background change====
::I have previously wondered about setting up a template similar to the NHC TCR URL one before now, however, I'm loathed to as I have previously been informed that the URL ID changes from time to time.] (]) 22:09, 14 December 2024 (UTC)
I propose changing the timeline background to {{color box|#fffcf4}} '''#fffcf4''' to alleviate the MOS:ACCESS breach caused between the current background and the longstanding tropical storm color. This assumes that the colors for statues are changed to the new colors. If not, then this background may not work against the current color scale scheme.
:::As long as the time between when the URL is put into the article, and there is an archives of that URL, then it shouldn't matter too much for when it changes. Linkrot is a problem that's avoidable. Data compression is also helpful for articles loading faster, so a template would be useful. As for what ] made, I think it should have the "National Climatic Data Center" as the publisher, but "Storm Events Database" should be the series, if that's possible. The details about the exact time and location is good, but that is ultimately extra coding being added to one of the most common citations. Perhaps a title of just " event report"? The weather type would be whatever is the first entry. That way the NCDC URL could be used all across the weather project. For example - "High wind event report" or "Hurricane event report" or "Tornado event report". If we wanted to be more specific, maybe add location, so you could have "California high wind event report", or even "Monroe County, Florida tornado event report". There are options, but seeing how often the NCDC reports are used, there should be some discussion on it. ♫ ] (<small>]</small>) 01:05, 15 December 2024 (UTC)
*'''Support''' This would just be a part of the proposed color scheme change so the BG color would only change if the other ones do. ] (]) 19:54, 26 February 2022 (UTC)
*I '''Support''' This change as well. ''''']''''' 🌀 (]) 23:38, 26 February 2022 (UTC)
*<s>'''Oppose''' changing the timeline. It ''really'' helps for colorblind people that the timelines have the storm categories right next to their names, so even if they are colorblind, they still know what category the storm is. ] (]) 11:30, 4 March 2022 (UTC)</s>
:*{{re|Chicdat}} The issue is they can't see how long the storm lasted on the timeline. Look at an example of the colorblind one below for the current timeline, particularly red color blindness. ]<sup>]</sup> 12:19, 4 March 2022 (UTC)
::*{{ec}}'''Support''' Seeing the length is very convenient. ] (]) 12:24, 4 March 2022 (UTC)


== List of South America hurricanes nominated for featured list removal ==
=====Examples of proposed change=====
{{collapse top|Images of proposed change}}
;Regular vision
]
;Red blind
]
;Green blind
]
;Green blind
]
{{Collapse bottom}}


I have nominated ] for featured list removal. Please ] on whether this article meets the ]. Articles are typically reviewed for two weeks; editors may declare to "Keep" or "Delist" the article's featured status. The instructions for the review process are ].<!-- Template:FLRCMessage --> ] (]) 16:03, 15 December 2024 (UTC)
=====Current timelines=====
{{collapse top|Images of current timelines}}
;Blue Blindness
]
;Green Blindness
]
;Red Blindness
]
{{collapse bottom}}


== March 31 featured topic ==
====Discussion====
*'''Support''' as proposer. ]<sup>]</sup> 15:09, 26 February 2022 (UTC)
*'''COMMENT:''' Also working on a fix for the current MOS:ACCESS failure for the timeline experienced due to the TS color. ]<sup>]</sup> 15:59, 26 February 2022 (UTC)
*{{Ping|Sennecaster|LightandDark2000|TornadoLGS|CycloneFootball71|Chicdat|Tom94022|Hurricanehink|Supportstorm}} Pinging everyone who participated in the recently closed RfC discussion since it has been brought to my attention that the scope may have been misleading and some may have thought it was just maps and others may have thought it was for everything. The goal was to keep the scales consistent between maps and the on-wiki templates. I am sorry if anyone was confused. The closed RfC above will only apply to the maps as it was pointed out to me that I didn't specifically mention anything else. ]<sup>]</sup> 16:59, 26 February 2022 (UTC)
**Wait a sec. You're saying we're going ahead with changing colors in the maps but not the templates? ] (]) 19:15, 26 February 2022 (UTC)
::* {{re|TornadoLGS}} The maps aren't getting changed right now as a bot has to be coded for that. We would then have to decide a timeline for implementing them once the bot is ready. I was told off-wiki that since templates and other scales were not explicitly mentioned in the original proposal that the consensus for that RfC can't apply to them. Even if it was implied that everything was going to be changed to match up, the consensus only applies to the maps. ]<sup>]</sup> 19:21, 26 February 2022 (UTC)
:::*I figured it was assumed that we wouldn't change one without the other. I think ] applies in this case. ] (]) 19:25, 26 February 2022 (UTC)
::::*I would agree with you, but there are others who may not. I did discover another MOS:ACCESS issue that affects every season article and timeline article as a result of this. That issue is also being considered here and would simply require AWB to implement. This issue would affect hundreds of articles. Keep in mind the timeline background would be altered for all weather articles as well. ]<sup>]</sup> 19:34, 26 February 2022 (UTC)
:So, one thing I've also realized, since we're talking about keeping maps and templates consistent, is that we've started incorporating maps into annual tornado articles, so far only at ] and ]. They currently use the NWS color scheme, or something close to it, but we should include those in this color scheme as well. The may be access issues between the EF1 and EF3 colors . Pinging {{ping|Supportstorm}} since they did both of these maps. ] (]) 19:52, 26 February 2022 (UTC)
:I realize my wording above is ambiguous. I mean we should use the new color scheme for the tornado maps. ] (]) 20:27, 26 February 2022 (UTC)
::Chose the colors since they look well on the map. Personally don't see an issue with the EF1 and EF3 colors, but I'm absolutely done discussing project color changes. I'll change it to whatever is agreed upon. ] (]) 20:56, 26 February 2022 (UTC)


As I'm sure everyone here is aware, this year's off-season hasn't proved to be particularly interesting. So, if you're looking for something to edit, why not work on the March 31, 2023 tornado outbreak topic? Me and {{noping|EF5}} began working on this a while ago, but the goal is to get everything regarding this topic to at least ] status. My personal goal is to see the March 31 outbreak as a ] by March 31 of next year. If you're up for this project, consider contributing to any of the articles below - especially the C class and draft articles.
*'''Strongly Support''' All the proposed changes, per my reasoning in the earlier RfC above. Accessibility is important, and the newer coloring system would clearly work better than the current one. We've already agreed to implement the color changes; this just confirms the color changes in the remaining templates that utilize our storm colors. As for the Timeline background color, accessibility also needs to apply there as well, and the proposed light background color (very light grey) is both more accessible and aesthetically pleasant. ''''']''''' 🌀 (]) 23:38, 26 February 2022 (UTC)
{{Featured topic box |title=Tornado outbreak of March 31 – April 1, 2023 |count=7 |image=Tornado outbreak of March 31 – April 1, 2023.png |imagesize=
*'''Support''' To make my position clear. I agree with keeping keeping tornado colors the same as hurricane colors because 1) It saves the work of reworking thousands of entries in tornado tables and 2) the NWS colors have access issues which I brought up above. ] (]) 01:43, 27 February 2022 (UTC)
|lead= {{icon|C}} ''']'''
{{closed rfc bottom}}
|view=yes
|column1=
:::{{icon|list|}} ]
:::{{icon|C}} ]
|column2=
:::{{icon|FAC}} ]
:::{{icon|draft}} ]
|column3=
:::{{icon|draft}} ]
::: {{icon|B}} ]}}


My personal to-do list is getting the Little Rock article published, adding NCEI references to the List article (and bringing it to FL status), and finishing my FAN of the Belvidere theatre collapse, as well as potentially creating original media for the articles in need of path, etc. photos.
===Timeline for implementation===
Now that the RfC is officially closed with consensus for all the changes, we have to decide on a timeline for implementation. I realize we can't easily implement the past maps immediately as we currently do not have a bot for that. However, I think that we can begin implementing the color changes for the 2022 NIO, WPAC, ATL, and EPAC seasons since they either have not started or their current maps with storms will not change color-wise as a result of this switch. I am going to work to get the timeline changes immediately implemented due to the ACCESS issue it concerns and will work to get the colors for our templates changed as well. There will be a lag any way we do this between templates in articles and the maps, however, I think it's prudent to change as much as we can immediately knowing everything will be the same color-wise in the end. ]<sup>]</sup> 21:54, 18 March 2022 (UTC)


Cheers and happy editing! ] (]) 15:29, 16 December 2024 (UTC)
: will definitely need some changing (namely ) for track map changes. According to some ] I've done a few months back, 466 existing images will require manual regeneration, or at least require a human on the helm to see if the track map being generated is correct and represents the actual cyclone (based on other data on the <nowiki>{{</nowiki>]<nowiki>}}</nowiki> template). 3,051 images have track data embedded, so regeneration wouldn't be hard and would be close to accurate. 1,846 images have command execution input, which can be a bit unreliable if the original data has been deleted/changed, but if particularly problematic, can just be verified by humans (and wouldn't take that long for the humans to scan).
:Of course, the hard part is actually making the bot that will do all this work. Pinging {{u|PurpleLights}}, who I know has some development experience and is still highly active in the project. <span style="background:#ffff55">''''']'''''</span>&nbsp;<small style="font-size:calc(1em - 2pt)">(])</small> 04:04, 19 March 2022 (UTC)
::Now that the color changes have been implemented in the templates, I think that the timeline changes should be implemented, ASAP. This can be done via AutoWikiBrowswer. As for the track map images, they have to be redone, but the vast majority of them can probably be automatically recreated by a bot, since most of them have their track data available on their Commons page. The rest can be manually recreated. We need a new bot to do this, and it's going to take some time, but hopefully, we can get all of the track maps redone within a few months of the bot being set up. I think this summer to the start of next winter is a reasonable time frame when it comes to when to expect this task to be completed. ''''']''''' 🌀 (]) 04:22, 19 March 2022 (UTC)


== RfC: Criteria for individual tornado articles ==
===Comments===
<!-- ] 13:01, 31 January 2025 (UTC) -->{{User:ClueBot III/DoNotArchiveUntil|1738328476}}
This honestly was a very rushed and poorly executed plan. I am pretty sure there was no consensus reached before so this whole sudden 180 seems foul. Barely anyone else had a say in the later phase and it would’ve been much better to alert others to the possible plan instead of just going right at it. Also, the color change is likely to attract more vandals changing borderline C4/5 storms to C5 bc they think the red color is C5. Additionally this is probably gonna provoke a massive backlash in the weather community. I propose to revoke the changes and have a much more discussion about how to move forward with the possible problems from views of all sides, not by just going off 2 or 3 people’s opinions. --''''']''''' (<sup>]</sup>/<sub>]</sub>) 03:40, 19 March 2022 (UTC)
Should we have notability standards for individual tornado articles? We already have informal inclusion criteria for "Tornadoes of YYYY" articles. Below is a preliminary proposal for such criteria, with the hope that it can evolve into a formal guideline that can possibly be referenced in future AfD discussions.
*'''Oppose''' as we would be reintroducing WP:ACCESS issues for the timeline and removing the new scheme for maps which fixes the issues. We have finely tuned this scheme against the map and the colors against each other to have a scale that progresses naturally and is accessible to all. The new scale clearly states colors (see template for scale in articles) and yes, confusion is likely at first, but that will happen with any change. It takes time for people to get used to a change and that isn't a reason to avoid the change. ]<sup>]</sup> 03:43, 19 March 2022 (UTC)
**The problem is that the color scale is not good at all. All it did was make it look even more out of style and purple just does not work at all. This needs to be redrawn from the ground up as other proposals for new colors seem to have been deliberately left out and instead set on one that did not get enough comments on it. Why not just slightly modify the original colors to comply but still retain its faithfulness? Plus, it looks awful on the tornadoes part, especially the higher-end ones. --''''']''''' (<sup>]</sup>/<sub>]</sub>) 03:52, 19 March 2022 (UTC)
***We can't slightly modify all the colors slightly to improve contrast. There isn't much room to go with very similar colors. actually uses purple for EF5, red for EF4, and orange for EF3. This is more inline with what they have. The problem is we have tried many different colors and we have a limited range that works for the maps. People who opposed the first time supported because they felt it was the best option and we had exhausted alternative schemes. I honestly think this is the best option we have. ]<sup>]</sup> 03:59, 19 March 2022 (UTC)
**** But why? Why can’t you give it a chance? We don’t have to be the same as the NWS. It also doesn’t serve to help that Sam’s TCR was released today with no upgrade to C5 - and now this color change is gonna have a lot of people assuming wrongly that it was upped to C5 because the old C5 color was made into the new C4 color. Ditto with Ida. I don’t think you want that on your conscious right? Also ] doesn’t really apply here, since changing the status quo that the entire community has gotten used to even before Twitter was invented is now changed and your probably gonna end up causing a lot of confusion now with this. Plus, some have even said the original colors didn’t really have an ] issue. --''''']''''' (<sup>]</sup>/<sub>]</sub>) 04:06, 19 March 2022 (UTC)
*****We gave it a chance back in November and it ended in a no-consensus track wreck as a result. Discussion fizzled out on it. People could have proposed any alternative back then but they didn't. I tried to get input this time around as a result of the shortcomings of the prior discussion, but nobody checks project pages apparently and I can't ping everyone as it would be canvassing. That's not really my fault. As I have said before, any change will lead to confusion until people get used to it. It just takes time to get over. The ACCESS thing people were referring to was contrast between the map and the colors, which is what got tested way back when. The contrast between the colors themselves was not tested. ]<sup>]</sup> 10:42, 19 March 2022 (UTC)


] '''Previous discussions:''' ], ]
:Just saw the changes, and I'm not too happy to be fair. Personally I find the new colour scheme worse than the old - my eyes hurt when I look at the new one - and I would have preferred that the old one be kept. But this isn't a policy-based reason to oppose the new scheme, so I have no standing to complain, I suppose, especially as I have normal vision; MOS:ACCESS takes precedence over ], after all. '']]'' 03:46, 19 March 2022 (UTC)
:My thoughts on the changes are as follows: simply put my preference is with the old color scheme. This new change has a great purpose, one I’m all for and it is actually well-thought out in a lot of areas (props to AC, who’s actually done well in what he’s set out to do despite the criticisms). My biggest issue lies with the colors themselves. They simply don’t make too much sense to me from a progression standpoint, notably in Categories 3–5. There have also been complaints from others about Categories 1–2. Another thing is execution; the change was sudden and not announced very well. It also could’ve included some (further) thought on the creation of something to allow for those in opposition to have a choice prior to the change. Those concerns aside though, similarly to what Java mentioned, the scheme does accomplish it’s original purpose of being more accessible and I can acknowledge that as a reason against opposing policy-wise. ''']''' ~ 03:59, March 19 2022 (UTC)
* '''Strongly Oppose''' reverting the changes, per the reasons given by Noah. This subject was already discussed in about 3 successive RfCs for the past few months in the sections above, and the relevant WikiProjects were literally notified of the ongoing RfC with banners on their pages. We can't wait forever, and it's not our fault more people weren't paying attention. Also, reversing the changes would reintroduce the old problems we were dealing with. And discussing these issues again really isn't going to produce a different outcome; all we'll get is a similar result, if not a deadlock. I think that retreading this issue would be very counterproductive and a waste of time, so I don't think we should do this. Anyway, it takes time for people to get used to change. And you can't please everyone. This is another one of those cases. While not everyone is pleased with the colors, they're clearly an improvement over the previous system, in terms of accessibility. And we came to a consensus in the said discussions. It's time to implement the results and move on. ''''']''''' 🌀 (]) 04:22, 19 March 2022 (UTC)
*:How is it counterproductive to revisit and come up with a better solution? This feels like you’re trying to exclude those who opposed it and want to go back and have a constructive conversation instead of rushing through changes that many are not gonna be proud of. I really think we need to go back and revisit this because it obviously was not carried through properly. ''''']''''' (<sup>]</sup>/<sub>]</sub>) 04:27, 19 March 2022 (UTC)
*'''Lean Support''' on revisiting this in my view. I understand the use of the Access request and complaints made about the original scale, so alas I understand the need to change it. What I don't understand is the particular scale we changed to. I liked the fact that the previous scale had a solid, strong gradient that made sense- and you could tell that higher up the gradient meant a stronger hurricane. Whereas, the implemented scale uses a bright pinkish/purple for C5, which doesn't make sense and the color implemented does not blend well with the red now being used for C4. Additionally, the fact that C5, C4, and C3 colors were knocked down the scale one could be seen as confusing to viewers. Essentially, one of two things needs to happen in my view:


This has been nagging at me for a while now, and since another editor has talked to me about this issue, I think we bring this up. Since we have a sort of "inclusion criteria" for "Tornadoes of YYYY" articles, I suggest we come up with notability criteria for individual tornadoes as well. See ] for what this may look like.
a) an overhaul from whatever the access issue pointed out as a particular issue with the scale (which seems to be the C1/C2 colors in most proposals) and just overhaul up.
b) just completely overhaul/change the scale entirely, which would be better than just shifting the entire scale one down and adding a new C5 color because of possible confusion for readers/could solve visibility issues while still keeping a scale with reasonable gradients.


In either case I don't believe the current scale to be the fix of our problems. -''''']''''' <!--Template:Undated--><small class="autosigned">—&nbsp;Preceding ] comment added 04:37, 19 March 2022 (UTC)</small> <!--Autosigned by SineBot-->


This is my very primitive way of determining the notability of several tornado articles I've written, and am hoping that it could be integrated into a refined set-in-stone WPW policy that could be used in actual AfDs. I'd assume that the table will be gotten rid of and turned into a list. This has been discussed in the past, but never really came to anything. Maybe it could be... ] (with it's own project page)? Starting an RfC, since obviously community input is needed. Also pinging {{ping|Departure–}}, who suggested this. :) ]<sub>]</sub><sup>]</sup> 18:56, 16 December 2024 (UTC)
* '''Support''' for revisiting the new scale. While changing the scales to comply with WP:ACCESS is a good idea, I believe it has been executed poorly (not AC's fault, by the way). My main problem is that the color progression in the new scale is really odd, especially from category 3 to 5. The old Category 4 color is now the Category 3 color, and the old Category 5 color is the new Category 4 color, and this is likely to lead to confusion. I've also seen people who have said that the Category 1 and Category 2 colors remain to similar. It may be better to have a scale with similar progression to the old one, however slightly more exaggerated differences between categories. However, that's just my opinion. ] (]) 04:46, 19 March 2022 (UTC)
*:This I can '''support'''. But apparently it “can’t work”, which I think it can. It also makes long-trackers like Irma look way more intense then it is in certain areas. Longtime trackers who are used to the old scale but don’t edit here are going to get very confused. I really think we should just go back to the old scale but fix the root of the problem which is the C1/2 colors, not the entire scale. ''''']''''' (<sup>]</sup>/<sub>]</sub>) 05:31, 19 March 2022 (UTC)
*:'''COMMENT:''' {{re|DaneH20|User:SolarisPenguin|HurricaneEdgar}} The contrast between colors has to be enough that they can be distinguished on small dots on a map. Slight adjustments didn't make all that much of a difference when I tested which is why we went with larger adjustments. As I have said before, confusion is likely to be only temporary. Confusion is likely to occur with any change. With all changes, any confusion passes with time as people get used to the changes. That's why we include map keys. As for color progression, it is about as natural as we can get. Dark red is out due to visibility on the map and pink is a no-go for the same reason... that leaves us with purple, which has some blue tint. Even the uses something similar for the tornadoes: Orange for EF3, red for EF4, and purple for EF5. Additionally, we have the timeline accessibility issue to contend with. This new scale is in-line with the background change that fixes the TS color issue for red colorblindness (TS color shows up as gray and it was on a gray background). Our current scale and any minor adjustments does not and will not be appropriate for the background. Our scale needs to be able to be on a different shade of timeline background and have sufficient contrast on the maps. I think we have minimal room for adjustment here as a result. ]<sup>]</sup> 10:23, 19 March 2022 (UTC)
*::{{re|Hurricane Noah}} My main problem with this proposal is how the category colors have been shifted down, and also the large jump between C4 and C5. While the confusion is temporary on WP, it might affect other services that use the now-old versions of WP tracks (Like the JTWC has done in the past). I'm all for changing the colors for ACCESS, however I believe it could've been executed better. C1 and C2, and potentially C3 and C4 are also too similar, while C2 and C3, and C4 and C5 are too different, jumping from light yellow -> orange and red -> purple. I think the C1 and C2 colors are fine, but the C3, C4 and C5 colors should be shifted slightly closer to C2, although not by a significant margin. ] (]) 20:35, 19 March 2022 (UTC)
*::Purple is awful which is why it must be changed. I don’t get why you don’t want to give it a chance and instead are refusing to even do so. The previous colors appeared perfectly fine to me and already I am seeing backlash on WxTwx. The contrasts were perfectly fine as well and all this did was make it even worse. ''''']''''' (<sup>]</sup>/<sub>]</sub>) 13:40, 19 March 2022 (UTC)
*:::{{re|MarioProtIV}} If you want a better solution, the only good option is to ditch the background and go with a political map rather than a terrain one. That will open up many more color possibilities and alleviate the pressure for conforming the scale. The one proposed off wiki doesn’t have enough contrast for small dots. ]<sup>]</sup> 15:29, 19 March 2022 (UTC)
*::::Political maps are just as awful and makes the map itself look very child-ish. Blue Marble background is the better one for all of them. ''''']''''' (<sup>]</sup>/<sub>]</sub>) 18:10, 19 March 2022 (UTC)


:I '''support''' these guidelines, but please see my suggestions on the talk page - the wording around fail-if-pass criteria make this much more difficult to read than it needs to be. Perhaps putting them in their own section separated from the other criteria would resolve this. ] (]) 19:01, 16 December 2024 (UTC)
* ''' Support''' per SolarisPenguin said this new color is confusion in the reader, I would like to kept the old color in the template. <span style="font-family: Georgia; background-color: maroon; padding: 2px 3px 1px 3px;">] ]</span> 04:51, 19 March 2022 (UTC)
{{collapse
:*Specifically to you, this is an all-or-nothing change. People don't want to change one without changing the other so either we change everything to a new scheme or we change nothing at all. Consistency between maps and templates is a requirement for almost everyone here. We really tried to make the best possible scale given the obstacles we had to tackle. If we had a better alternative, it likely would have been proposed by this point and adopted. ]<sup>]</sup> 10:47, 19 March 2022 (UTC)
|1=
{{replyto|EF5}} Please add a ] that does not include a table; this has broken the RfC listing pages. --] &#x1f339; (]) 08:44, 17 December 2024 (UTC)
:How about now? <span style="color:#CD0000">] ★ (])</span> 11:48, 18 December 2024 (UTC)
::{{diff|Misplaced Pages talk:WikiProject Weather|1263749310|1263554971|These two edits}} merely lengthened the existing overlong statement. --] &#x1f339; (]) 19:52, 19 December 2024 (UTC)
:::Ok fix it yourself. <span style="color:#CD0000">] ★ (])</span> 21:34, 19 December 2024 (UTC)
::::I'm pulling this RfC on the grounds that it is invalid. Please read ] before trying again. --] &#x1f339; (]) 22:46, 21 December 2024 (UTC)
:::::{{ping|Redrose64}} Please explain {{em|specifically}} what is invalid about the RfC, preferably quoting from ], as mentioned by you. <span style="color:#CD0000">] ★ (])</span> 11:03, 22 December 2024 (UTC)
::::::Here are the relevant portions of RFCST:
::::::#<li value=4> '''Include a ] of or question about the issue''' in the talk page section, immediately below the {{tlx|rfc}} tag
::::::#'''Sign the statement''' with either ] (name, time and date) or ] (just the time and date). Failing to provide a time and date will cause ] to remove your discussion from the pages that notify interested editors of RfCs.
::::::# '''Publish the talk page'''. Now you're done. Legobot will take care of the rest, including posting the RfC in the proper RfC lists. Whilst Legobot normally runs once an hour, it may take it up to a day to list the RfC, so be patient.
::::::The first link yields three relevant paragraphs:
:::::::{{tq|Keep the RfC statement (and heading) neutrally worded and short.<ref>For clarity: The "statement" is the part that is located between the {{tlx|rfc}} tag (exclusive) and the first valid timestamp (inclusive), and which is copied by bot to various pages. The statement itself needs to be neutrally worded and brief. After that first date stamp, you should follow normal talk page rules, which allow you to be verbose (within reason) and as non-neutral as you want. ...</ref> Statements are often phrased as questions, for example: "Should this article say in the lead that John Smith was a contender for the Pulitzer Prize?"}}
:::::::{{tq|Legobot will copy the markup of your statement (from the end of the {{tlx|rfc}} tag through the first timestamp) to the list of active RfCs, if it is sufficiently brief; a long statement will fail to be copied. For technical reasons, statements may not contain tables or complex formatting, although these may be added after the initial statement (i.e., after the first timestamp). ... If the markup of the RfC statement is too long, Legobot may fail to copy it to the RfC list pages, and will not publicise the RfC via the ].}}
:::::::{{tq|If you have lots to say on the issue, give and sign a brief statement in the initial description and publish the page, then edit the page again and place additional comments ''below'' your first statement and timestamp.}}
::::::The statement was in no way brief. It also included complex formatting (that table). --] &#x1f339; (]) 11:21, 22 December 2024 (UTC)
:::::::Fixed, although I disagree about it being invalid. ]<sub>]</sub><sup>]</sup> 13:27, 27 December 2024 (UTC)
::::::::@] Thank you for your effort. <span style="color:#CD0000">] ★ (])</span> 19:47, 27 December 2024 (UTC)
|2=Resolved discussion regarding the RfC's opening statement.
|bg=#f8f9fa
}}
:'''Support''' <span style="color:#CD0000">] ★ (])</span> 11:50, 18 December 2024 (UTC)


{{reflist-talk}}
* '''Comment''' Many people have an issue with the current C5 color, and while I get the concerns, there's really no alternative color that can be used for C5. A darker red such as {{color box|A71A38}} is the logical progression, however it's A lighter red will become too close to the C4 color, and a dark purple will become too close to the sea color. If purple can't be used, then the background map itself has to change to prevent colors becoming too similar to colorblind people. I would also like to note that the previous colors are not "perfectly fine", imagine trying to discern what color means which in the tiny space ] takes up in an article. ]] 14:21, 19 March 2022 (UTC)


== Good article reassessment for ] ==
* '''Comment''' If the goal was consistency, then can't the track map colors be vibrant and then have a quantitative value be used to brighten the colors for infoboxes (i.e. ]-wise, increase lightness and decrease saturation)? Seems better than having rainbow barf on season effects tables, and I don't think anyone has a problem with that if we just use the same hue. <span style="background:#ffff55">''''']'''''</span>&nbsp;<small style="font-size:calc(1em - 2pt)">(])</small> 14:27, 19 March 2022 (UTC)
] has been nominated for a good article reassessment. If you are interested in the discussion, please participate by adding your comments to the ]. If concerns are not addressed during the review period, the good article status may be removed from the article. ] (]) 17:52, 18 December 2024 (UTC)


== RFC: Rating of the ] ==
* '''Comment''' First, I applaud the thought and cooperation that those involved put into this – huzzah! As some fine-tuning will likely be done, I would like to pass along two observation: the C1 color is a bit difficult to distinguish against the new background shading, and the C5 color makes the hyperlink text difficult to read. I understand and appreciate the complexities involved in developing a workable color scheme, and again say thank you for your work. Cheers. ] (]) 14:58, 19 March 2022 (UTC)
*:@] I removed hyperlinks from info boxes for scales per consensus above as it doesn’t comply with any scale we have had. ]<sup>]</sup> 15:31, 19 March 2022 (UTC)


There is an ongoing RFC to determine which source should be used for the rating of the ]. You can participate in the discussion here: ]. '''The ]''' (] 03:25, 20 December 2024 (UTC)
*'''Comment''' A couple project members have raised the issue in off-wiki communication that implementing the color changes to track maps would also affect other language Wikipedias and force color changes there even though they did not discuss it and which may have different policies on WP:ACCESS etc. This has been presented as a roadblock, but there is a compromise. I think a way around this would be to have bots create new files, instead of updating existing track maps. That way other Wikipedias could implement color changes, or choose not to, at their own pace. ] (]) 17:28, 19 March 2022 (UTC)


== Good article reassessment for ] ==
*'''Comment''' This feels lke we are opening Pandoras Box, which is why I have tried to avoid commenting for now. However, if the track maps are being redone then they should all include data from the RSMC rather than the JTWC.] (]) 20:24, 19 March 2022 (UTC)
] has been nominated for a good article reassessment. If you are interested in the discussion, please participate by adding your comments to the ]. If concerns are not addressed during the review period, the good article status may be removed from the article. ] (]) 02:27, 5 January 2025 (UTC)


== Article Names for Natural Disasters ==
* '''Support''' a better solution that changing the Cat 4 and 5 colors to red and purple. '''Oppose''' the introduction of the purple color. The best solution was to keep something that isn’t broken. Oh but that would offend somebody. ] (]) 20:59, 19 March 2022 (UTC)


'''''tl;dr: climate change is already increasing the number of weather catastrophes, and I don't believe ] provides adequate guidance to name articles when e.g. significant fires share a name.'''''
* '''Oppose''' revoking the changes. The previous discussion sought out to reach consensus on making colors that are more color blind compliant. That consensus was achieved, which is not an easy feat given how many previous discussions there have been on this topic. Do I think there's some combination of colors out in the world that would look and work better than what was proposed here? Yeah, probably. But as it stands, these new colors fulfill the goal that was set and generally match the progression that other websites use as well. "I don't like it" is not a valid excuse in this discussion. ] <small>(] · ])</small> 21:34, 19 March 2022 (UTC)
*I oppose undoing the color change even if the new colors weren’t ideal, because I believe in inclusivity and {{ping|United States Man}} ] can’t be ignored just because “I don’t like it”.—] ] 22:29, 19 March 2022 (UTC)


I was directed here from the teahouse as I'm relatively new. There's currently an going conversation on the talk page for the ] about whether the 2021 Palisades fire or the 2025 Palisades fire is the ].
* I also '''oppose''' reverting the changes per reasons given by Noah, Jasper Deng, L&D2000, and TropicalAnalystwx2013. The original grounds for changing the color scheme was to make it more accessible for users, and to help people with colorblindness and other vision issues differentiate the different colors with higher contrast. Many editors, (myself included) have mentioned how the original colors were difficult to see and tell apart among other things, and how the shades are too close to one another to tell apart for those with colorblindness and other troubles with sight. Per the words of {{ping|LightandDark2000}} from a previous discussion, "{{tq| For those people who are opposed to changing the current coloring system just because you favor the old system or think that no changes are needed, let me remind you of a couple of things: 1) Just because ] doesn't mean the changes shouldn't go forward, and 2) ].}}" And also "{{tq|humans can and ''do'' adapt to changes. This is another change that we'll simply have to adapt to. The new coloring system is similar to the old one, so it shouldn't be too jarring for those used to the older system, but at the same time, it makes the colors much easier to differentiate and also more accessible to our colorblind readers, which needs to happen. Also, WP:ACCESS is a site-wide Misplaced Pages policy. Familiarity (or status quo) is not.}}" I think what LightandDark said here basically sums up why it is futile to try and change back to our old coloring scheme, we are trying to accomodate all of our readers and editors,and that is by making the maps easier to see. I understand that some don't like the coloring scheme, but trying to change it back completely is frankly a bit selfish in the broad scheme of things. I am sure that we will eventually find better colors, but for now, the new ones suffice. 🌀]]]🏈 |''']''' 23:43, 19 March 2022 (UTC)


Without getting into that specific conversation, it occurs to me that as climate change fuels more and more weather catastrophes, it will be helpful to have guidance and/or policy on naming articles. I provided a table below that shows California fire names since 2013 that have been used 10 or more times. I'm, of course, aware that not all named fires meet the ] guidelines. But as more fires occur, there will simply be more notable fires that share the same name.
*I’m not really a fan of the purple but I didn’t feel like battling the access fanatics, which is why I never joined the discussion to begin with. ] (]) 23:45, 19 March 2022 (UTC)
* '''Support''' This is not a complete support for the old color scheme. I would much rather the old colors return with the edits suggested by User SolarisPenguin below. Modifying the category 2 and 3 colors. The less we change the original color scheme while satisfying the accessibility issue caused by those two colors the better resolved this will be. ] (]) 01:27, 20 March 2022 (UTC)
*'''Strongly Oppose''' - It, honestly, hurts to look at, and it may be confusing for people who are familiar with the old scale. ] (]) 17:50, 20 March 2022 (UTC)
*:Wouldn’t this be strongly support if you’re saying the new ones hurt to look at? Just clarifying. ''''']''''' (<sup>]</sup>/<sub>]</sub>) 18:35, 20 March 2022 (UTC)
*::Mixed up the support with oppose. Thought support meant one liked the change. ] (]) 03:46, 22 March 2022 (UTC)
'''Comment''' I've noticed that the EF scale also changed with the Tropical Cyclone scale. It might be an unintended consequence of this change, but still. ] (]) 03:44, 22 March 2022 (UTC)


My understanding is that this is largely due to how fires are named: trying to simplify radio traffic for firefighters. I believe that the <s>]/]</s> ] retires a storm name once a named storm becomes significant.
:{{re|Mobius Gerig}} Do you have any thoughts on the newest proposal below? ]<sup>]</sup> 10:41, 22 March 2022 (UTC)
::It might be better to make some minor changes than to just basically start from scratch. Plus, the ''newer'' one looks good. ] (]) 19:57, 22 March 2022 (UTC)


'''<u>So, some questions (of course feel free to propose your own):</u>'''
====New proposal====
{{ping|SolarisPenguin}} recently made a new scale that is similar to the old one but fixed the issues with the C1/2/3 contrasts and has recently gotten some support off-wiki. (because I’m too lazy to throw this all into actual code to show - I’ll probably get to that later). --''''']''''' (<sup>]</sup>/<sub>]</sub>) 18:33, 19 March 2022 (UTC)
:The one issue with that color scale is, under deuteranopia, there is hardly any contrast between the severe tropical storm and category 2 colors. ] (]) 19:45, 19 March 2022 (UTC)
::STS is not even really used at all on the track maps except for Infobox headers so that’s already taken care of. And rarely do the JMA screw up so bad as to have STS while JTWC has C2. And vice versa. ''''']''''' (<sup>]</sup>/<sub>]</sub>) 19:48, 19 March 2022 (UTC)
::The new scale also has the same problem, as STS and C2 are quite similar as well. ] (]) 20:46, 19 March 2022 (UTC)
:While this is similar to the color scale I proposed, was my actual proposal. ] (]) 20:38, 19 March 2022 (UTC)
:I tried out the proposals here (including one off-wiki) and the colors are still too close to each other. (solar's proposal: , ), (mario's proposal: , ), (off-wiki proposal: ). The only way to create enough contrast between the colors is to, say, shift C4 to C3, etc. I would also like to note that the C1 and TS colors we're currently using are still , so maybe that can be fixed here. ]] 03:09, 20 March 2022 (UTC)
::Shifting colors is not a good idea at all. It creates confusion just like the C3/4 colors were made the old C4/5 colors. ''''']''''' (<sup>]</sup>/<sub>]</sub>) 03:36, 20 March 2022 (UTC)
:::I don't think that's a huge issue. It will take getting used to, but that's true of any change. ] (]) 03:49, 20 March 2022 (UTC)
:::Unfortunately, I don't believe this is avoidable. I originally tried to minorly alter the original colors such as Solaris has done above and it just didn't have enough contrast between colors. The problem is a limited range of color can only have so much contrast between the various shades. That's why I shifted C5 down to C4 and C4 down to C3. It cuts down on the number of shades of yellow/orange between TS color and the strong orange (former C4 one) color to 2 from 3. It's easier to show contrast between two shades of yellow/orange than it is three, and even more so if it were to have been four shades (a hypothetical fourth shade). More colors also increases the number of shades you can have for a scale. I realize you and some others don't like shifting colors and the introduction of purple, but these changes are actually more thought out than you have given us credit for. During the first RfC way back in November, I started off with a pretty poor scheme and tried to implement feedback I got from everyone in order to improve it. I discussed with some people what their thoughts were on a potential scale and took that into consideration as well. AC's scale, which was somewhat different from my final proposal there, got a decent amount of good feedback, so I decided to take it up for the new proposal. I yet again asked for feedback on the proposal during the second RfC, however, people felt it was fine and likely the best outcome we could hope for given all the hours we had spent discussing and formulating color schemes. We had to contend with having enough contrast between colors and the track map background, fixing the timeline background issue for the TS color, and having enough contrast between the colors themselves. I realize you don't like the scale we came up with, but it does accomplish everything it set out to do. ]<sup>]</sup> 12:14, 20 March 2022 (UTC)
::::I get that but you are still opening Pandora’s box to a lot of confusion and misinformation by simply resorting to shifting colors, especially for borderline C4/5 storms like Sam and Jose, as well as EF4/5 tornadoes. I don’t think you want that to happen so the current color scheme needs to be reworked to fix that issue. It’s better to just look at the other proposals. Also FYI, I recall reading from someone saying the old scale didn’t really have any issues and was mostly compliant. ''''']''''' (<sup>]</sup>/<sub>]</sub>) 15:47, 20 March 2022 (UTC)
:::::I think there would be confusion over any change, really, but it will be temporary. I showed the new colors to some non-Wikipedians (including one who does graphic design) who thought they looked fine. ] (]) 21:29, 20 March 2022 (UTC)
:::::It's not misinformation as we are not making anything factually incorrect. While it is leading to some confusion, that's only a temporary issue as people will adapt and become used to the scale with time. I have looked at the other proposals brought up and they don't solve the problem of having enough contrast between colors and being compatible with a new timeline background color. You have to realize with these alt proposals that have come up thus far is either they contrast enough against the timeline background and don't have enough contrast between colors or they contrast enough between colors and don't contrast enough against the timeline background. In regards to the compliancy, that was ACCESS compliance between the colors and the ocean background of the map, not between the colors themselves. ]<sup>]</sup> 22:47, 20 March 2022 (UTC)
::::::Again, you don’t seem to realize this is causing more people to mistake borderline storms and I don’t see how this is a temporary issue as this will mess up a lot of people’s perceptions of higher end storms. You may not think it’s misinformation but it’s damn near close when the old scale (which was in use for over a decade and in the minds of a lot of people) suddenly gets replaced with a new one that merry shifted colors down a scale and made C4 look like it’s actually C5. ''''']''''' (<sup>]</sup>/<sub>]</sub>) 23:10, 20 March 2022 (UTC)
:::::::{{ping|MarioProtIV}} You’ve made this “misinformation” and “confusion” claim numerous times without any, actual, evidence that our readers are actually getting this confused. You’re not defeating the substance of Noah’s argument by saying people will change their perception of higher-end storms, since is bound to happen with any color scheme.—] ] 00:46, 21 March 2022 (UTC)
:::::::Other complaints I have heard off-wiki for the old scale is that orange for EF4/C4 seemed like it insinuated they were a moderate, common event rather than a strong one. They applauded the new scale for making the actual moderate look moderate. They liked seeing C4 be red and C5 as purple because it insinuates severe and very severe. Heck, even covid maps for state gov'ts (California and Ohio I know did this) used yellow, orange, red, purple as the progression. You act as if this came out of nowhere, however, it didn't. The adjustment is likely easier than you think considering people are used to seeing these covid maps showing purple as the next color after red. The main argument against including purple in the scale is ]. This shift could actually be positive for us as it puts colors to the intensities where they match up in this day and age since purple really is the new red across the world. Yes, the old scale was in use for a decade. You made it quite clear in November you wouldn't support any change just because the old scale had been in use for such a long time. A similar thing would be saying racism is okay because it has been done for such a long time in the past. Just because it has been done for a long time doesn't mean it was right for us to have done to begin with. {{u|Hurricanehink}} even said that the colors a decade or so ago were likely picked out without accessibility concerns in mind. If something is displayed to be wrong and treat a group of people unfairly, it is our duty and obligation to fix that issue, making sacrifices if we need to. ] > aesthetics.... It's literally that simple. With these new guidelines (ones that were voted on) likely coming into effect soon, we could get into serious trouble if we take actions either as individuals or as a project that promote discrimination against certain groups of people, such as reverting to a scale that does not support the color blind. Again, I get you and others don't like the idea of shifting colors and using purple, but trying to toss everything out just to get the old scale back is very selfish and dishonorable. I didn't pursue this just for the hell of it. Someone has to fight for the color blind because we don't have very many, if any, with a full color blindness and it is quite clear that a decent chunk of this project just doesn't care. It makes me sick to see people put their own preferences over a group that has a disability. I stand here asking you and others to keep the changes enacted for the sake of the color blind as this fixes serious issues we have with ]. ]<sup>]</sup> 12:03, 21 March 2022 (UTC)
::::::::But why are you refusing to allow other proposals to be discussed such as those discussed off-wiki? Also how could we get into “serious trouble” if nothing happened regarding the old scale '''which was used for over a decade''? The fact that {{ping|SolarisPenguin}}’s and others proposals was thrown out because “it doesn’t meet all of the criteria/fails 1 out of the rest is quite honestly stupid. Also the argument with purple is not ] as you claim. It’s actually a bad color that goes against infoboxes and several people off-wiki have brought up concerns over it. Also, I and others are very aware of the colorblind community and that’s why we took to make proposals that fixed the issue at hand while not straying far from the original scale. Hell, even ] said the only issue with the old scale was the C2/3 transition, so it would seem far better to fix that while leaving the rest of the scale intact. So I’m asking, please consider those other proposals too as at this point it feels very immature to brush them off just because it doesn’t meet 100% of criteria (it should at least meet 75% or more). ''''']''''' (<sup>]</sup>/<sub>]</sub>) 13:10, 21 March 2022 (UTC)
:::::::::Have you not seen where Akbermamps and I have pointed out either A. it does not go well with a new timeline background color or B. it doesn't have enough contrast on the maps? We are allowing discussion of those proposals, but pointing out where they don't measure up to what we need. Both of these are requirements for any new scale. It's not stupid that it was thrown out because it doesn't meet all of the criteria. For example, either something is AA or it isn't. There isn't an "Oh... it meets 90% so it's fine for AA". It's a strict cutoff with no exceptions for a reason. Either we are accessible as possible or if we go with something that fixes 75% of the issues, we are discriminating against people with a disability in order to preserve the old scale. People have brought up both C1/C2 and C2/C3 as confusion areas, which is a large chunk of the scale. Purple is a bad color? It still meets AA on both normal black text and bolded black text. We have consensus above to remove links from every colored region of infoboxes and templates, so I don't see what the issue is here. In terms of getting into trouble, I have no clue, but big brother is likely going to be swinging around its battleaxe to enforce the new guidelines and stop any practices it deems go against the policy. We just have to wait and see what that entails. What is really immature is you reverting the changes three times because you disagree with the consensus. ]<sup>]</sup> 13:58, 21 March 2022 (UTC)


* '''Does the ] policy adequately address article naming for natural disasters?'''
====Alternate proposal for maps====
* '''If yes, please elaborate'''
I made this comment earlier, but I think it got overlooked. The issue was raised, in off-wiki discussion, that the track maps are used on other language Wikipedias in addition to the English Misplaced Pages. The folks there would be affected by this change even though they likely haven't discussed it and may not even be aware of this discussion. I suggest, therefore, that the bots in charge of images create new, separate images with the updated colors rather than update existing files. That way, those on other Wikipedias can choose whether to make the change at their own pace. I don't know to what extent their guidelines on accessibility might differ from the ones here. ] (]) 04:02, 20 March 2022 (UTC)
*'''Support''' having the bots create separate images for the new tracks rather than overriding existing ones. ]<sup>]</sup> 11:59, 20 March 2022 (UTC)
* I'd move to '''snow close''' this as we don't have a choice here but to upload new images per ]. The consensus of the Wikimedia Commons community very clearly overrides the consensus of a WikiProject on just one language of Misplaced Pages. The proposed is automatic, lest we be mass-reverted upon uploading the newly-colored images. Unless, of course, cross-wiki consensus is gathered on Meta, which avoids having to implement a new naming scheme and mass duplication of images based on an extremely minute detail. <span style="background:#ffff55">''''']'''''</span>&nbsp;<small style="font-size:calc(1em - 2pt)">(])</small> 14:48, 20 March 2022 (UTC)


* '''If no, which catastrophes need clarification? Fires only? Hurricanes? Snowstorms? Tornadoes? Derechos? Fire Whirls? Other?'''
====Newest Proposal Yet====
* '''Are you aware of naming schemes for weather catastrophes in countries outside the US that could cause confusion? What are they? It would be helpful to ensure this is not a US-only discussion.'''
<!-- ] 23:01, 25 April 2022 (UTC) -->{{User:ClueBot III/DoNotArchiveUntil|1650927701}}
* '''Does the timing of article creation/title selection affect your decision? e.g. there was a 1981 Hurricane Katrina. At what point did the 2005 Hurricane become the ] Hurricane Katrina?'''
{{Rfc|sci|policy|tech|rfcid=95C238F}}
Which color scheme is more accessible? Which color scheme balances accessibility and aesthetics?


Thanks for taking the time to read this, and I look forward to hearing your thoughts!
The current colors have been used across weather for the past decade. I believe these colors are hard to distinguish between on track maps for the dots, particularly between the Category 1-4 range. There simply isn't enough contrast between the colors to tell them apart (C1 and C2, C2 and C3, C3 and C4). This has presented a challenge for me as a reader and editor with normal color vision and decent eyesight with glasses. I have to open the full resolution to tell the difference between the colors and even then it can be a challenge for some. This issue would be even worse for color-blind editors. We also have issues with the TS color and the timeline background for red color blindness (demonstrated in the above RfC). On the grounds of ], I am proposing a change to the below colors, which increases the contrast between the weather colors. Please place comments in the discussion section below.


<u>''California fire names since 2013 that have been used 10 or more times. (scroll down to Incident Data) .''</u>
As a compromise between keeping the old scale and improving for WP:ACCESS for color blind, I propose the following new scale. I would also like to make it very clear, '''Consensus was reached above to NOT have ANY links on colored backgrounds''' so the below colors only need to have AA contrast against black text. ]<sup>]</sup> 22:08, 21 March 2022 (UTC)


{| class="wikitable"
=====Proposed Colors=====
|Border
{| class="wikitable" style="text-align: center; margin-top: 0"
|31
|+ Proposed colors
! rowspan="2" | Category !! ! rowspan="2" | Color Name </br>(Proposed Colors) !! colspan="3" | Normal !! colspan="3" | Protanopic !! colspan="3" | Deuteranopic !! colspan="3" | Tritanopic
|- |-
|Creek
! <abbr title="Old">O</abbr> !! <abbr title="Previously Approved">PA</abbr> !! <abbr title="Proposed">PR</abbr> !! <abbr title="Old">O</abbr> !! <abbr title="Previously Approved">PA</abbr> !! <abbr title="Proposed">PR</abbr> !! <abbr title="Old">O</abbr> !! <abbr title="Previously Approved">PA</abbr> !! <abbr title="Proposed">PR</abbr> !! <abbr title="Old">O</abbr> !! <abbr title="Previously Approved">PA</abbr> !! <abbr title="Proposed">PR</abbr>
|24
|- |-
|Canyon
| <abbr title="Templates & Infoboxes Only">Potential Tropical Cyclone/Disturbance/Depression</abbr>
|20
|'''True Blue'''
| style="width: 32px; height: 32px; background-color: #80CCFF" |
| style="width: 32px; height: 32px; background-color: #72A9CD" |
| style="width: 32px; height: 32px; background-color: #007FCE" |

| style="width: 32px; height: 32px; background-color: #B3C0F8" |
| style="width: 32px; height: 32px; background-color: #979fc7" |
| style="width: 32px; height: 32px; background-color: #5877c7" |

| style="width: 32px; height: 32px; background-color: #B2C0FF" |
| style="width: 32px; height: 32px; background-color: #989ecf" |
| style="width: 32px; height: 32px; background-color: #377bce" |

| style="width: 32px; height: 32px; background-color: #73D0E1" |
| style="width: 32px; height: 32px; background-color: #6babb9" |
| style="width: 32px; height: 32px; background-color: #018790" |
|- |-
|Oak
| Tropical Depression/Tropical Low/Deep Depression
|18
|'''Brilliant Azure'''
| style="width: 32px; height: 32px; background-color: #5EBAFF" |
| style="width: 32px; height: 32px; background-color: #5EBAFF" |
| style="width: 32px; height: 32px; background-color: #47a1ff" |

| style="width: 32px; height: 32px; background-color: #9CAFF6" |
| style="width: 32px; height: 32px; background-color: #9CAFF6" |
| style="width: 32px; height: 32px; background-color: #759afa" |

| style="width: 32px; height: 32px; background-color: #92B0FF" |
| style="width: 32px; height: 32px; background-color: #92B0FF" |
| style="width: 32px; height: 32px; background-color: #5a9dff" |

| style="width: 32px; height: 32px; background-color: #47C2D2" |
| style="width: 32px; height: 32px; background-color: #47C2D2" |
| style="width: 32px; height: 32px; background-color: #00adba" |
|- |-
|Lake
| Tropical Storm/MTS/CS/A1
|15
|'''Sky Blue'''
| style="width: 32px; height: 32px; background-color: #00FAF4" |
| style="width: 32px; height: 32px; background-color: #00FAF4" |
| style="width: 32px; height: 32px; background-color: #5edbf8" |

| style="width: 32px; height: 32px; background-color: #E1DDE3" |
| style="width: 32px; height: 32px; background-color: #E1DDE3" |
| style="width: 32px; height: 32px; background-color: #c2c8ed" |

| style="width: 32px; height: 32px; background-color: #E7D9FB" |
| style="width: 32px; height: 32px; background-color: #E7D9FB" |
| style="width: 32px; height: 32px; background-color: #c1c6ff" |

| style="width: 32px; height: 32px; background-color: #84F0FF" |
| style="width: 32px; height: 32px; background-color: #84F0FF" |
| style="width: 32px; height: 32px; background-color: #58dced" |
|- |-
|Willow
| <abbr title="Templates & Infoboxes Only">Severe Tropical Storm/SCS/A2/EF0</abbr>
|14
|'''Menthol'''
| style="width: 32px; height: 32px; background-color: #CCFFFF" |
| style="width: 32px; height: 32px; background-color: #B4FDA8" |
| style="width: 32px; height: 32px; background-color: #b1ffa4" |

| style="width: 32px; height: 32px; background-color: #F8F3F8" |
| style="width: 32px; height: 32px; background-color: #feea9f" |
| style="width: 32px; height: 32px; background-color: #ffeba0" |

| style="width: 32px; height: 32px; background-color: #FFF1FD" |
| style="width: 32px; height: 32px; background-color: #ffe6d2" |
| style="width: 32px; height: 32px; background-color: #ffe7d4" |

| style="width: 32px; height: 32px; background-color: #E8F7FF" |
| style="width: 32px; height: 32px; background-color: #cef0ff" |
| style="width: 32px; height: 32px; background-color: #cff1ff" |
|- |-
|Valley
| Category 1/RSI1/EF1
|14
|'''Very Pale Yellow'''
| style="width: 32px; height: 32px; background-color: #FFFFCC" |
| style="width: 32px; height: 32px; background-color: #FFF795" |
| style="width: 32px; height: 32px; background-color: #fffac0" |

| style="width: 32px; height: 32px; background-color: #FFFCF3" |
| style="width: 32px; height: 32px; background-color: #fff3cb" |
| style="width: 32px; height: 32px; background-color: #fff7e1" |

| style="width: 32px; height: 32px; background-color: #FFE2C1" |
| style="width: 32px; height: 32px; background-color: #fff1e4" |
| style="width: 32px; height: 32px; background-color: #fff6f0" |

| style="width: 32px; height: 32px; background-color: #FEFBFF" |
| style="width: 32px; height: 32px; background-color: #ffeff7" |
| style="width: 32px; height: 32px; background-color: #fff4fc" |
|- |-
|Ranch
| Category 2/TY/VSCS/A3/TC/RSI2/EF2
|13
|'''Yellow-Orange'''
| style="width: 32px; height: 32px; background-color: #FFE775" |
| style="width: 32px; height: 32px; background-color: #FFD821" |
| style="width: 32px; height: 32px; background-color: #ffce70" |

| style="width: 32px; height: 32px; background-color: #FFE775" |
| style="width: 32px; height: 32px; background-color: #f6da27" |
| style="width: 32px; height: 32px; background-color: #e9d472" |

| style="width: 32px; height: 32px; background-color: #FFC140" |
| style="width: 32px; height: 32px; background-color: #ffd393" |
| style="width: 32px; height: 32px; background-color: #ffcc86" |

| style="width: 32px; height: 32px; background-color: #FFDEEA" |
| style="width: 32px; height: 32px; background-color: #ffcdd8" |
| style="width: 32px; height: 32px; background-color: #ffc5d2" |
|- |-
|River
| Category 3/RSI3/EF3
|12
|'''Deep Saffron'''
| style="width: 32px; height: 32px; background-color: #FFC140" |
| style="width: 32px; height: 32px; background-color: #FF8F20" |
| style="width: 32px; height: 32px; background-color: #fd963b" |

| style="width: 32px; height: 32px; background-color: #E4CC43" |
| style="width: 32px; height: 32px; background-color: #c0aa2c" |
| style="width: 32px; height: 32px; background-color: #c3ae44" |

| style="width: 32px; height: 32px; background-color: #FFC140" |
| style="width: 32px; height: 32px; background-color: #d9a119" |
| style="width: 32px; height: 32px; background-color: #dca537" |

| style="width: 32px; height: 32px; background-color: #FFB8C4" |
| style="width: 32px; height: 32px; background-color: #ff8790" |
| style="width: 32px; height: 32px; background-color: #ff8d97" |
|- |-
|Coyote
| Category 4/VSTY/ESCS/ITC/A4/RSI4/EF4
|12
|'''Halloween Orange'''
| style="width: 32px; height: 32px; background-color: #FF8F20" |
| style="width: 32px; height: 32px; background-color: #FF6060" |
| style="width: 32px; height: 32px; background-color: #F16523" |

| style="width: 32px; height: 32px; background-color: #C0AA2C" |
| style="width: 32px; height: 32px; background-color: #9f9473" |
| style="width: 32px; height: 32px; background-color: #a19032" |

| style="width: 32px; height: 32px; background-color: #D9A119" |
| style="width: 32px; height: 32px; background-color: #b68e56" |
| style="width: 32px; height: 32px; background-color: #b78818" |

| style="width: 32px; height: 32px; background-color: #FF8790" |
| style="width: 32px; height: 32px; background-color: #ff6065" |
| style="width: 32px; height: 32px; background-color: #f35f65" |
|- |-
|Grant
| Category 5/VITY/SuCS/VITC/A5/RSI5/EF5
|11
|'''Rose Red'''
| style="width: 32px; height: 32px; background-color: #FF6060" |
| style="width: 32px; height: 32px; background-color: #C464D9" |
| style="width: 32px; height: 32px; background-color: #CC2257" |

| style="width: 32px; height: 32px; background-color: #9F9473" |
| style="width: 32px; height: 32px; background-color: #5386f4" |
| style="width: 32px; height: 32px; background-color: #6a6a74" |

| style="width: 32px; height: 32px; background-color: #B68E56" |
| style="width: 32px; height: 32px; background-color: #6b89cc" |
| style="width: 32px; height: 32px; background-color: #7f664d" |

| style="width: 32px; height: 32px; background-color: #FF6065" |
| style="width: 32px; height: 32px; background-color: #b57a83" |
| style="width: 32px; height: 32px; background-color: #c93132" |
|}
</div>
*Keep in mind that I am unable to produce maps on my own so I can't produce visual aids other than the table above. ]<sup>]</sup> 20:21, 21 March 2022 (UTC)
*{{colorbox|#DB2961}} must be used for Category 5 in conjuction with any black text in place of the above in order to pass AA (very slight difference in shading).
*Up-to-date map (normal vision) link

=====Old timelines=====
*These timelines show color blind perception of the timelines using the old scale.
{{collapse top|Images of current timelines}}
;Blue Blindness
]
;Green Blindness
]
;Red Blindness
]
{{collapse bottom}}
=====Current timeline (Normal Vision)=====
<center><timeline>
ImageSize = width:800 height:250
PlotArea = top:10 bottom:80 right:20 left:20
Legend = columns:3 left:30 top:58 columnwidth:270

AlignBars = early
DateFormat = dd/mm/yyyy
Period = from:01/05/2021 till:01/08/2021
TimeAxis = orientation:horizontal
ScaleMinor = grid:black unit:month increment:1 start:01/06/2021

Colors =
id:canvas value:gray(0.88)
id:GP value:red
id:PTC value:rgb(0,0.49,0.80) legend:Potential_Tropical_Cyclone
id:TD value:rgb(0.27,0.64,1) legend:Tropical_Depression
id:TS value:rgb(0.37,0.86,0.97) legend:Tropical_Storm
id:STS value:rgb(0.70,1,0.64) legend:Severe_Tropical_Storm
id:C1 value:rgb(1,0.98,0.75) legend:Category_1
id:C2 value:rgb(1,0.80,0.44) legend:Category_2
id:C3 value:rgb(0.99,0.59,0.39) legend:Category_3
id:C4 value:rgb(0.95,0.40,0.14) legend:Category_4
id:C5 value:rgb(0.80,0.13,0.35) legend:Category_5

Backgroundcolors = canvas:canvas

BarData =
barset:Hurricane
bar:Month

PlotData=
barset:Hurricane width:11 align:left fontsize:S shift:(4,-4) anchor:till
from:01/05/2021 till:10/05/2021 color:PTC text:"Alpha (PTC)"
from:15/05/2021 till:30/05/2021 color:C5 text:"Beta (C5)"
from:01/06/2021 till:10/06/2021 color:TD text:"Gamma (TD)"
from:03/06/2021 till:12/06/2021 color:STS text:"Delta (STS)"
from:15/06/2021 till:23/06/2021 color:C1 text:"Epsilon (C1)"
from:18/06/2021 till:30/06/2021 color:C4 text:"Zeta (C4)"
from:20/06/2021 till:27/06/2021 color:C2 text:"Eta (C2)"
from:22/06/2021 till:04/07/2021 color:C3 text:"Theta (C3)"
from:01/07/2021 till:07/07/2021 color:TS text:"Iota (TS)"


bar:Month width:5 align:center fontsize:S shift:(0,-20) anchor:middle color:canvas
from:01/05/2021 till:01/06/2021 text:May
from:01/06/2021 till:01/07/2021 text:June
from:01/07/2021 till:01/08/2021 text:July

TextData =
pos:(620,30)
text:"(From the"
pos:(667,30)
text:"])"

</timeline>
</center>

=====Provisions=====
;1. The colors above will be adopted in place of the scale which was approved via RfC for maps and will replace the currently used scale for templates and infoboxes.
{{collapse top|Withdrawn provisions}}
<strike>
;2. We recognize that easytimeline is outdated and has technological shortfalls that prevent us from achieving both a viable scale and color blind compatibility.
;3. Therefore, we approve using the scale and background approved in the prior RfC on a temporary basis until such time that we have a viable graphing extension replacement formulated in order to eliminate any issues with color blind compatibility in the meantime. (To clarify, this means creating a timeline using the existing graphing extension, not creating a new extension entirely)
;4. Once a viable replacement for easytimeline has been created, it will be put through an approval process to show it is color blind compliant before being implemented.</strike>
{{collapse bottom}}
;5. Maps on commons will not be overridden but instead will have new files uploaded via bot since this was not discussed on Meta with the support of other Wiki communities. Some files can't be uploaded by a bot and have to be done manually.
;6. Maps will be overridden on commons IF there is a discussion on Meta that has the support of sister wikis (these sister projects must be notified appropriately).
;7. Timeline background will go back to its prior color and the new scheme will be adopted for timelines as well

=====Discussion=====
{{Not a ballot}}
Please state below which provisions you support and/or oppose.
*'''Support 1; Neutral 5; Support 6; Support 7''' provisions as proposer. Hopefully, this makes a solution that everyone can agree on so we can get back to making images and articles. ]<sup>]</sup> 20:18, 21 March 2022 (UTC)
:*{{Ping|MarioProtIV|JavaHurricane|KingLucarius|LightandDark2000&nbsp;|DaneH20|SolarisPenguin|HurricaneEdgar&nbsp;|Akbermamps|Chlod|Drdpw|Jason Rees|United States Man&nbsp;|TropicalAnalystwx13|Jasper Deng|CycloneFootball71|Supportstorm|Mobius Gerig|TornadoLGS}} Pinging everyone who participated thus far in the above discussion for thoughts so we can avoid a repeat of last time. ]<sup>]</sup> 20:33, 21 March 2022 (UTC)
:*{{Ping|ChessEric|Destroyeraa|PurpleLights|Nova Crystallis|CooperScience|Cyclonebiskit}} Pinging some additional project people who may have an opinion on this subject. I would also like to be transparent and state that I collected some feedback on the scale off-wiki before proposing it here so colors could be finetuned and any issues I missed be corrected. ]<sup>]</sup> 23:26, 21 March 2022 (UTC)
* <p>I '''partially support''' the implementation of provision 1. I'm unable to find a reason why we wouldn't be able to apply that color scheme on maps. If the problem comes down to contrast with land, the circle and line (denoting the track and position of the cyclone) should be enough to make the general track distinct with the land. I think something that's been overlooked a lot in all of the proposals so far is that color is not the sole object that conveys information.</p><p>I '''weakly oppose''' provision 2, for the reason that the problem partly lies in our implementation, and should there be a fix it should be implemented in the existing extension and not a new one.</p><p>I '''oppose''' provision 3 for the reason that it suggests the creation of a new extension, which is unrealistic. If the usage of EasyTimeline (i.e. the <code><nowiki><timeline></nowiki></code> tag) itself is what's causing problems, then a better solution would be to use an existing replacement rather than formulate a new one. I will note, having developed a MediaWiki extension before, that extension development is a feat, especially one that requires the use of graphics libraries. The suggestion that we'll be able to develop a replacement extension, have it approved by the entire English Misplaced Pages community, and security-checked by the WMF is far-fetched. The shortfalls likely do not come from ] itself, but our usage of it.</p><p>I automatically '''oppose''' provision 4 as it relies on the implementation of provisions 2 and 3.</p><p>I '''oppose''' provision 5 as it takes the "easy way out" which will only lead us to even more headaches going forward. Starting a discussion on Meta would be more substantial. There's no concrete method of how we're supposed to reupload said images, namely how we'll deal with categorization, what the new filename format would be, etc. With a Meta discussion, we'd be able to gauge how many wikis wish to follow our color scheme, and we'd avoid the mass-reupload of images on Commons and sparking hundreds of unnecessary edits (renames of files, etc.) cross-wiki for a change that would be used by most wikis anyway. The ] has already chosen to follow our newly-proposed (and controversial) color scheme, and since our entire ] and its ] are not that hard to export to other wikis, it wouldn't be hard for other wikis to follow suit. I'd like to finally note that WikiProject Weather is in no way autonomous nor isolated from the entirety of the English Misplaced Pages, nor other-language wikis for that matter. Going with this proposal, and expecting other wikis to either follow or "cope" with the changes would be very selfish of us. Let's try to get other wikis on-board first, shall we?</p><p>I'd also advise the proposer to notify ] and ]. I'd also advise to notify sister wikis, although if this proposal aims to strictly push provision 5 as part of its agenda, I assume that wouldn't be necessary (assuming my comments from above fall on deaf ears). <span style="background:#ffff55">''''']'''''</span>&nbsp;<small style="font-size:calc(1em - 2pt)">(])</small> 21:31, 21 March 2022 (UTC)</p>
*:Forgot to mention why I supported the proposed color scheme in the first place. Put simply, this has the rather unique idea of modifying the ] of colors for categories lower than the SSHWS Categories 1 to 5, and does not have the extremely rough transition from red to purple like our current (recently-applied) scale does (which is a common hate point). I'd suggest the timeline background color be bumped darker to alleviate any contrast issues with Category 1, though. <span style="background:#ffff55">''''']'''''</span>&nbsp;<small style="font-size:calc(1em - 2pt)">(])</small> 21:36, 21 March 2022 (UTC)
*:Clarified what I meant. I didn't mean to create an entirely new extension, but rather to formulate a replacement using the existing extension. I will also add a 6th provision for those in favor to starting a discussion on Meta and notifying sister wiki projects. ]<sup>]</sup> 21:40, 21 March 2022 (UTC)
*::"{{tq|viable graphing extension replacement}}" definitely could have been worded better. In any case, I reiterate my point that our implementation might be what needs fixing. After all, what's the use of switching to a different graphing system if the same issues arise? And in addition, how can we prove that switching to a different way of formulating the timeline will fix the problem? <span style="background:#ffff55">''''']'''''</span>&nbsp;<small style="font-size:calc(1em - 2pt)">(])</small> 21:46, 21 March 2022 (UTC)
*:::Withdrew 2-4 since the original background is compatible with the new colors (including the previously incompatible TS color). I assume you support the new provision 6 per your statement above. I added provisions 6 and 7 above. ]<sup>]</sup> 22:06, 21 March 2022 (UTC)
*'''Comment/Question''' This color scheme does not improve contrast as well as the current one, but I'm willing to get behind it since I'm kind of tired of wheeling around with these and, as I've said before, no color scheme will satisfy everyone. On provision 5, if some of the new files cannot be automatically given update counterparts, can a bot at least tag or categorize them, so we know which ones need to be done manually? ] (]) 21:45, 21 March 2022 (UTC)
*:{{re|TornadoLGS}} As far as I am aware, it would be possible. ]<sup>]</sup> 21:56, 21 March 2022 (UTC)
*'''Support''' provision 1, per the reasons I gave above.
:'''Support''' provision 5, as the one who proposed it. We can decide on categories and title format, but I don't think it will be a big issue.
:'''Neutral''' on provision 6. It's a viable alternative, but I would want provision 5 to be on the table if we hold a discussion on Meta.
:'''Support''' provision 7. If there are no color contrast issues, I see no reason to change the background color from the original. ] (]) 22:48, 21 March 2022 (UTC)

*'''Support''' provision 1 – per TornadoLGS.
:'''Neutral''' on 5 and 6. Whatever works for everyone else works for me.
:'''Support''' provision 7 to keep the original background color.
: ] (]) 00:32, 22 March 2022 (UTC)
*Comment: Slight adjustments were made due to the maps showing an issue with C3 and C4 being a bit too close. No major change overall. ]<sup>]</sup> 00:47, 22 March 2022 (UTC)
*'''Support 1 & 7, Neutral on 5 & 6''' I like the progression of colors in this latest proposal and the retention of a gray background. ] (]) 01:18, 22 March 2022 (UTC)
*'''Strongly Support''' the newest proposal, as well as most of the active provisions (1, 6, and 7). As I've stated multiple times on these discussions, we need colors that are more accessible to colorblind readers. And the 2008–2022 coloring system (the older one that we're all familiar with) had shades for C1, C2, and C3 that were too similar to each other even for some readers with normal color vision. This newest proposal resolves the accessibility issues while also being more similar to the older system, as is clearly more acceptable to our editors. The C1-C4 colors in this proposal are also easier to distinguish than the more familiar scale. As such, I believe that it is a fair compromise, and an excellent proposal. I support starting a discussion on Meta-Wiki and pinging every single Wikimedia site with its own version of WPTC (such as simple wiki, zh.wiki, es.wiki, etc.) to discuss the changes across all the various projects. It would be better if we can have all of the projects in sync, as this would also make it easier to maintain the track maps. In the event that the Meta-Wiki discussions are nowhere near wrapping up by the time we have a bot setup with the capability to redo the maps, I would consider implementing Provision 5, so we can already get started on uploading revised track maps. The discussions should not drag out for months or even years. Concerning the other changes, I think that all of the changes local to en.wiki should be implemented immediately, upon the closure of this discussion. ''''']''''' 🌀 (]) 01:39, 22 March 2022 (UTC)
*'''Support''' provision 1, the colors provide sufficient contrast between each other (see if you want to test).
:'''Wait''' on provision 5, wait for consensus to be reached on Meta/other wikis. If they support the change, override. If they don't, make new files. The track maps can wait.
:'''Support''' provision 6, see above
:'''Support''' provision 7, map provides sufficient contrast. ]] 02:25, 22 March 2022 (UTC)
: '''Partially Support''' provision 1, only thing that really stands out still is the transition from orange to maroon there. Still looks like a duller color than the prior category.] (]) 10:52, 22 March 2022 (UTC)
::{{re|NickWX28}} It's not maroon, but rather rose red. {{colorbox|#CC2257}} for rose red and {{colorbox|#800000}} for maroon. It's not really duller, but maybe it is a factor of it being a darker color. It still contrasts against the map sufficiently; We had to make the colors different and darker (in some cases) in order to provide enough contrast between colors on the map. I believe this is about as close as we can get to the original scale while still fixing all the issues we needed to. ]<sup>]</sup> 11:02, 22 March 2022 (UTC)
:::Ah I see the slight difference in shading there. To be fair though, i referred to it as maroon because it was just a darker red. My own eyes are terrible as well. Retinopathy does that sadly.] (]) 15:39, 22 March 2022 (UTC)
:'''Sorry''' I am not in a position to assist productively in this discussion.] (]) 12:07, 22 March 2022 (UTC)
*'''Support 1, 5, neutral 6, 7'''. As such I have no idea about what the discussion regarding the timeline is about, but I have to say that the new colours are much better than the ones approved above; the new colours cause no eye pain, for my part. '']]'' 15:39, 22 March 2022 (UTC)
* '''Support 1, Neutral/Weak Support 5-6, Support 7''' - These colors are much more friendlier then the previous scheme and are more closely related to the old colors. They satisfy much of the issues and don’t deviate far enough to confuse me as well. In regards to the maps, I '''support''' new maps, if they can’t be globalized then '''create separate files and have a bot replace them in the pages''', if they can be via consensus on Meta, '''upload a new version of the current files''' Timeline looks great as well, so I '''support''' bringing the previous background back for that as well. --''''']''''' (<sup>]</sup>/<sub>]</sub>) 20:09, 22 March 2022 (UTC)
*''' Support Provisions 1, 5 and 7. Oppose Provision 6 ''' - I agree, that this proposal is '''significantly''' better, than the previous ones. The contrast of the colours, slowly change throughout the scale. Unlike, the original proposal, with Category 4 being coded red and Category 5 being coded purple, respectively. The contrast between those two colours were alot darker than the rest of the scale, in that proposal. ] (]) 00:24, 23 March 2022 (UTC)
*'''Support 1&7, Neutral, leaning support on 5&6'''- I like the new color scheme presented here, though I prefer the previous color change with purple cat 5 colors, but I will fully support it if it helps all people who have eyesight troubles. for provision #7, if there were no issues with the previous contrast color, I don't see why we can't change it back to the original color. as for 5&6, I feel more discussion is needed here to see which option is best, however I do think that it only seems fair to have a discussion on meta to get everyone involved and notified of any major changes made for the maps. 🌀]]]🏈 |''']''' 00:30, 23 March 2022 (UTC)
* Cat 4 and Cat 5 are much too close in this new one so I cannot support the new proposal.—] ] 06:01, 23 March 2022 (UTC)
:*{{re|Jasper Deng}} Did a tweaking of the colors. Is better? ]<sup>]</sup> 10:50, 23 March 2022 (UTC)
::This color scheme obviously satisfies everyone else and should stop the arguing. Why not support it? ] (]) 13:34, 23 March 2022 (UTC)
:::Jasper Deng and Cyclonebiskit did make a fair point about the C4 and C5 colors, which has hence been corrected. ]<sup>]</sup> 13:47, 23 March 2022 (UTC)
::::Even better. If their issue has been corrected, they should be able to support it. ] (]) 13:56, 23 March 2022 (UTC)
::::The new revision still does not make them nearly as distinguishable as purple and therefore I remain opposed.—] ] 16:42, 23 March 2022 (UTC)
:::::Oh well. It apparently satisfies a vast majority here, but I guess you can't satisfy everyone. ] (]) 16:46, 23 March 2022 (UTC)

*I see nothing wrong with the currently accepted February 2022 revision. The proposed scale doesn’t improve on what was agreed upon and only adjusts the problem to a muddied C4/5 boundary. I’ve been absent for two months, but I’m post-supporting the Feb 2022 RfC results that have already been implemented and don’t believe further change is warranted as long as it continues to comply with WP:ACCESS. ~ ] (]) 06:17, 23 March 2022 (UTC)
*:The reason why this was reopened was because most of the project despises the color scheme above so we are trying to achieve a balance between accessibility and aesthetics. Otherwise, the debate and ensuing chaos would never see an end. ]<sup>]</sup> 11:03, 23 March 2022 (UTC)
::This color scheme obviously satisfies everyone else and should stop the arguing. Why not support it? It obviously improves on the first one in that the color scheme satisfies both the old way and ACCESS. ] (]) 13:34, 23 March 2022 (UTC)

:::Understood, I remain opposed to this proposed scale tho. The color scheme doesn’t remedy the issue as well as the Feb 2022 version. Part of this whole issue stems from familiarity bias, we’ve been exposed to a particular color scheme for roughly 15 years. Altering it, even for the better, will inherently upset people as it is a departure from something familiar. I remain in support of the current Feb 2022 version. {{ping|Hurricane Noah}} can you add the Feb 2022 version to the proposal table so everyone can easily compare the three versions? I believe this is creating some unclear discussion. ~ ] (]) 16:07, 23 March 2022 (UTC)
::::What is unclear? This is a compromise to both sides. If you can't support that then you aren't really working toward a true solution. ] (]) 16:46, 23 March 2022 (UTC)
:::::{{ping|United States Man}} there’s no reason to be so hostile. I’m asking Noah for a broader comparison image while expressing what I don’t like about the proposed scale and my thoughts on it. ~ ] (]) 16:52, 23 March 2022 (UTC)
::::::@] and @] I updated the table above to include all the colors from the old scale, the previously approved, and this new proposal. ]<sup>]</sup> 17:12, 23 March 2022 (UTC)
:::::::I don't see much improvement with my concerns on the updated colors. I still '''oppose''' these new colors. Other arguments haven't been substantiated outside "I don't like it" which isn't enough to overturn an RfC. There's no problem with a significant color shift, especially when it better highlights the difference in categories, while retaining aesthetic appeal, rather than a gradual shift that can be difficult to differentiate at a glance. I've yet to see any complaints from non-WP:Weather members regarding the new scale...there would be at least a handful of IPs commenting their gripes if it was that much of an issue. Regarding mapping issues, no example has been put forth to convey this. ~ ] (]) 21:48, 23 March 2022 (UTC)
::::::::An issue may be that people simply do not know where to go to complain. I have seen numerous instances of complaints on twitter from non-WP weather people who view our site. See and as examples of external complaints. I'm sure people would be coming here if they knew where to go. ]<sup>]</sup> 21:51, 23 March 2022 (UTC)
*'''Support 1,6, and 7'''- This new scheme is much better than the February revision. I will fully support this reason being it retains the look of the original, satisfies access concerns, and is aesthetically pleasing. As for the bot implementation, I oppose using one. I have the data for all storm that had metadata changes, includes RSMC data, and other custom settings to make sure tracks look proper. A bot would introduce errors. I can run through the most recent data 2000-2021 within a few months if people are patient. ] (]) 14:05, 23 March 2022 (UTC)
*'''Eh'''. I kinda preferred the colors agreed back in February, under the heading ''Infobox & Template colors''. The purple as Cat 5 stands out better than the rose red, and the gradation makes more sense. There isn't enough difference between Cat 4 and Cat 5. ♫ ] (<small>]</small>) 16:35, 23 March 2022 (UTC)
::How does jumping to an entirely different color for Cat 5 make more sense than a red graduation that satisfies ACCESS? ] (]) 16:48, 23 March 2022 (UTC)
:::We're already changing thousands of maps. I think it's easier to see the difference with purple as C5, so the gradations all stand out more. ♫ ] (<small>]</small>) 16:52, 23 March 2022 (UTC)
::::The issue with purple C5 as I see it IIRC from Noah is that the contrast against the map is (Blue Marble) hard to tell. We would probably have to change to a different map style entirely to satisfy ACCESS. He can clarify for me if needed. ''''']''''' (<sup>]</sup>/<sub>]</sub>) 17:00, 23 March 2022 (UTC)
::::The only real issue I see is purple tends to be a bit of an eyesore for people against the background of this map. I'm honestly not seeing any real differences in accessibility looking at the table comparison above. ]<sup>]</sup> 17:28, 23 March 2022 (UTC)
:::::Then I'm fine with the proposed changes. ♫ ] (<small>]</small>) 23:33, 24 March 2022 (UTC)

*'''Strongly Support'''- I support the 1, 5 & 7 options. I feel that they suit my eyes & are similar to the older colors but still help others who do inherently have this condition. Also if there is a bot that can redo the colors then I'm all for it. ] (]) 17:33, 23 March 2022 (UTC)
*'''Oppose''', basically per Hurricanehink. Even with Noah's revision, the new colors don't sufficiently distinguish between Cat 4 and Cat 5. Purple for Cat 5 is distinct and consistent with many external weather sites. No compelling reason has been advanced to overturn the results of the February RfC. – ''']'''&nbsp;&#124;&nbsp;] 21:44, 23 March 2022 (UTC)
*:Did you see the map I had posted under JD's comment above? It shows a decent between the C4 and C5 colors. Im not sure why so many people are still insisting there isn't sufficient contrast. This was meant to be a peace offering/compromise to the other side so we could both get what we wanted and move on. Nothing can be enacted until no more objections are raised here against whatever scale we decide on. ]<sup>]</sup> 22:37, 23 March 2022 (UTC)
*::Yes, which is why I noted that my concerns were in spite of that update. If multiple people are raising the same concern, then maybe there's really a problem beyond just belligerence. – ''']'''&nbsp;&#124;&nbsp;] 23:10, 23 March 2022 (UTC)
*:::{{Re|Cyclonebiskit|Hurricanehink|Juliancolton}} Would you at least be willing to support either provision 5 or provision 6 which are '''independent''' of the color scheme proposed here? They deal with the handling of implementation regarding the map updates on COMMONS regardless of which scale ends up being decided upon here. ]<sup>]</sup> 00:16, 24 March 2022 (UTC)
*::::Yes, provisions 5 and 6 are acceptable regardless of which color scheme is used. ~ ] (]) 00:44, 24 March 2022 (UTC)
*'''Oppose''' (all provisions)&nbsp;– the proposed color scheme, despite satisfying ], gives the appearance of being a ] centered at Category 1 for colorblind users. An intensity color scale should not be presented in that manner. The previously approved scale handles this issue better and offers the best differentiation between categories. —]<sup><small>(] ⬩ ])</small></sup> 22:51, 23 March 2022 (UTC)
*:{{re|TheAustinMan}} I'm just curious, what exactly is the problem with a divergent scale? I looked at the page and it said to have extreme values at both ends. In this case PTC being the least intense category and C5 being the most intense. Also, we need a consensus either way on whether we implement a scale locally only or attempt to implement on a global level, regardless of which scale ends up being implemented. ]<sup>]</sup> 23:08, 23 March 2022 (UTC)
*::Divergent scales give the appearance of a "neutral" position between the extremes, and in this case, that would oddly be the Category 1 rating, which would not make much sense given that there is no "neutral" intensity. We should also be seeking support of sister wikis to ensure presentation of storm intensities is uniform after reaching consensus here. I '''Support provision 6''', and am neutral on provision 7. '''Oppose provisions 1 and 5.''' ]<sup><small>(] ⬩ ])</small></sup> 15:00, 25 March 2022 (UTC)
*'''Oppose''' provision 1, '''Support''' provisions 5-6. I went back and forth on this for a while, hence why it's taken so long to comment. At the end of the day, I think the original colors that were decided upon by consensus should remain. The goal of that endeavour was to eliminate colors looking too similar. In the proposed version here, categories 3-4 are hard to differentiate. This problem does not exist for the colors already rolled out. And while I understand the concern about using recognized colors for different categories compared to the original version, this is something that users can adjust to again with time--something that wasn't given before rushing into yet another lengthy discussion here. If there's widespread and consistent criticism of the color scale by members of the public, then a new discussion can be started down the line. Everything else is just speculation. ] <small>(] · ])</small> 00:39, 24 March 2022 (UTC)
*:I don’t see an issue with telling C3 and C4 apart on the proposed colors. We can only change it so much before it ends up failing ACCESS and one of the colorblind tests and thus becomes an untenable proposal since it doesn’t satisfy one side. Also, despite the claim of getting used to shifted colors, I find that hard to believe as we’ve already seen criticism about this (off-wiki as well), plus purple C5 is quite a bit of an eyesore against the ocean background (which we are most likely not changing). ''''']''''' (<sup>]</sup>/<sub>]</sub>) 01:01, 24 March 2022 (UTC)
*::The Cat 2-4 range has long been an issue with the original scale, which is why these discussions have been occurring for a decade. If you look at your table above, the proposed Cat 3 is darker than the original one, which puts it closer to the Cat 4 colors. This is not an issue in the accepted colors, since the old Cat 5 color/now Cat 4 color is clearly separable. I have no issue with the purple as is. I mentioned time in my post because we have to be cognizant that any change whatsoever, good or bad, will be criticized at the onset for moving past a color scale that has existed a decade. I'm more interested in complaints 3 months from now than I am right now. ] <small>(] · ])</small> 01:20, 24 March 2022 (UTC)
*'''Comment''' I do have a love for the original color scheme, though that is definitely due to it's use for more than 15 years, and I accept that there were accessibility issues that necessitated changes. I am neutral on either color scheme, though I think that we should decide soon (though with proper consideration), and accept the results moving forward. My only concern with the new changes is that the PTC/disturbance color is darker than the tropical depression/tropical storm color — this darkness is which I unconsciously associate with stronger storms, so that is a bit jarring for me. If I have to make a decision, I may want to keep the RfC colors. &mdash; <span style="font-family:Helvetica;Arial; font-size:12px;">]]</span> 00:45, 24 March 2022 (UTC)
*'''Strongly Support''' with the newest proposed color scale, which I did not exactly know was the case until I found out on the Discord server. Nonetheless, it is better than whatever was put into place currently, and I seem to be in the rarer population of those who actually like it better than the old colors. I do see the reasons for changing the colors, and I believe the newest proposed ones are definitely a suitable compromise between the ones who wanted the old colors to stay, and the ones who felt the current ones fit the best. ] | ] </span> 01:35, 24 March 2022 (UTC)
<small>— '''Note''': An editor has expressed a concern that ] (] • ]) has been ] to this discussion. </small>
* '''Neutral''' provision 5, '''Support''' all other provisions — I am in support of the implementation of this color scheme. Not only does it accomplish the original goal of better complying with accessibility standards via being more colorblind-friendly, but it’s also a lot more visually appealing to those not affected by colorblindness, being relatively similar to the former-scheme. The progression also flows a lot more linearly. This scale is a suitable compromise overall and an improvement in a lot of areas over the previous one. As far as provision 5, my neutrality comes at a general lack of a strong opinion there but all other non-withdrawn provisions have my support. ''']''' ~ 02:06, March 24 2022 (UTC)

'''Important!''' 15 '''Supported''' and 5 ''' Opposed''', thus far. ] (]) 14:38, 24 March 2022 (UTC)

:{{re|TropicalCyclone101}} This isn't a vote. It's decided by strength of argument. ]<sup>]</sup> 14:51, 24 March 2022 (UTC)

@Hurricane Noah: My apologies. I'll keep that in mind. ] (]) 15:04, 24 March 2022 (UTC)

* '''Comment''' I don't think the argument that purple does not contrast against the blue ocean background is sustainable:
]
]
*If anything, the preponderance of reddish hues makes the second (right-hand) map much less usable.
*Also, I should add that as per ] we could arguably have to use purple as it is used by the NWS for the EF scale (see and any DAT tool), and (to a lesser extent) by website like Wunderground (e.g. ) and CIMSS (e.g. ). The arguments for the new colors are simply not sustainable, especially on policy and guideline grounds.--] ] 00:35, 25 March 2022 (UTC)
::Nothing says that we have to use the same color scale as the NWS. None of the systems proposed here satisfy that anyway since they use green for EF1. ] (]) 00:45, 25 March 2022 (UTC)
:::Consistency with reliable sources is definitely a reason to use a similar scale to them. We can't use the exact same one, of course, since we have different display needs, but the consistency cannot hurt.--] ] 00:50, 25 March 2022 (UTC)
{{clear}}
* '''Comment'''. I am not a fan of the purple color from the RFC, but I'm afraid that the proposed color scale tries to compress too many classifications within a single ], which was the shortfall of the original scale. While the proposal does address ] concerns, it does ''not'' address the C1-C4 confusion, so I think some sort of purple hue will be needed for C4-C5. ]<sup>(])</sup> 00:54, 25 March 2022 (UTC)
*'''Comment'''. The background on all of these maps could cause accessibility issues so I rather see us replace the base map first before changing the colors.&nbsp;] ] 04:25, 25 March 2022 (UTC)
*:That itself is a tedious process (and was discussed way earlier in this whole thing) so that’s kind of off the table for now. Plus copyright and stuff is different on some of the maps and that is a whole mess we’d not want to get bogged down in. ''''']''''' (<sup>]</sup>/<sub>]</sub>) 04:40, 25 March 2022 (UTC)
*'''Oppose all changes since November 16'''. The map should be on the table first before any of the discussion should have happened. We are already bogged down so I see no reason why we couldn't start from step one.&nbsp;] ] 04:43, 25 March 2022 (UTC)
:{{Reply to|Nova Crystallis}} I could get behind that, if there is the possibility of accessibility issues on the map as well, they definitely need to be addressed along with the colors. Just to clarify, you're proposing to basically restart the discussion from the beginning and find/agree on a better map, and then find colors for the intensity scale and continue to work on from there? 🌀]]]🏈 |''']''' 04:55, 25 March 2022 (UTC)
::Of course.&nbsp;] ] 05:11, 25 March 2022 (UTC)
::: Okay, thank you. 🌀]]]🏈 |''']''' 05:15, 25 March 2022 (UTC)
*'''Comment''' - It may just be me, but I find it difficult to differentiate between the Category 4 and 5 colors in this proposal. They look very similar to me, and I need to zoom in to see the difference, and even then I can only barely see it. It's even worse when I have the blue light filter on. ] (]) 12:43, 26 March 2022 (UTC)
*'''Comment''' - I would like to note that this discussion has been brought up in the WPTC Discord server, and as such, some people commenting may have been notified of the discussion through there or asked to comment by another user off-wiki. For transparency, I am part of the WPTC Discord server and have also discussed the changes there, but I had knowledge of this discussion before it was brought up there. I will also not be making any comment as to my opinion for fairness’ sake; I am merely here to notify about the possibility of stealth canvassing. ]] 22:42, 26 March 2022 (UTC)

*'''Oppose''' - agree with Hink and JC. ]] <sup>]</sup> ] 23:47, 26 March 2022 (UTC)
*'''Support 1 and 7''' "4 is red, 5 is purple?" was what I thought when looking at the recently approved one. This scale, on the other hand, follows the quiet blue-to-intense-red while still meeting ] guidelines. It seems like just the compromise WPWX needs. ] (]) 10:51, 14 April 2022 (UTC)

=== Hybrid proposal ===
{| class="wikitable floatright"
! Color
! Hex
! ]
! ]
! ]
!
! rowspan = 9 | ] in a newly-proposed color scale for English Misplaced Pages]]
|- |-
|Park
| style="width: 32px; height: 32px; background-color: #6699ff" | PT
|11
| #6699ff
| 220
| 60
| 100
| AAA ()
|- |-
|Soda
| style="width: 32px; height: 32px; background-color: #59c8ff" | TD
|10
| #59c8ff
| 205
| 65
| 100
| AAA ()
|- |-
|Point
| style="width: 32px; height: 32px; background-color: #4ffdf6" | TS
|10
| #4dffff
| 180
| 70
| 100
| AAA ()
|- |-
|Pine
| style="width: 32px; height: 32px; background-color: #ffffd9" | C1
|10
| #ffffd9
| 60
| 15
| 100
| AAA ()
|- |-
|Hill
| style="width: 32px; height: 32px; background-color: #ffd98c" | C2
|10
| #ffd98c
| 40
| 45
| 100
| AAA ()
|-
| style="width: 32px; height: 32px; background-color: #ff9e59" | C3
| #ff9e59
| 25
| 65
| 100
| AAA ()
|-
| style="width: 32px; height: 32px; background-color: #ff738a" | C4
| #ff738a
| 350
| 55
| 100
| AAA ()
|-
| style="width: 32px; height: 32px; background-color: #d580ff" | C5
| #d580ff
| 280
| 50
| 100
| AAA ()
|- |-
|Bear
|10
|} |}
Lastly, as an aside, there was also a 2019 Palisades Fire in CA. <s>Good thing we stopped burning fossil fuels!</s> We really need to stop burning fossil fuels!!! ] (]) 05:42, 10 January 2025 (UTC)


:Yes. See ] and ]. No matter the size of the second fire, the first fire with that name will always take the “main” name and the second one will have the “(YYYY)” after it. ]<sub>]</sub><sup>]</sup> 13:06, 10 January 2025 (UTC)
Since I mentioned above that I do think we need to have some sort of purple hue for at least some of the categories to remedy the lack of distinctiveness between the SSHWS Cat 1–Cat 4 colors, I would like to put forward the following color scale for consideration. I based it on the ] for the initial colors, and adjusted to maximize space between C1-C4 while ensuring that the colors maintain ] color contrast guidelines. ]<sup>(])</sup> 03:46, 25 March 2022 (UTC)
::Is this spelled out somewhere? The current conversation about renaming the Palisades fire is looking like it will not be following that convention. ] (]) 18:35, 10 January 2025 (UTC)
:It stands up on the but I think the C5 color could be a bit darker, like in the current color scheme. This is based on an intuitive progression from light to dark colors with increasing intensity. ] (]) 04:01, 25 March 2022 (UTC)
:I'm not seeing how current article title policy is inadequate. If two or more distinct events are similarly named, we disambiguate by year, then by month if necessary (e.g. ] and ]), and a ] is set up (following the same example, ]). If one event is much more significant than others of the same name, we drop the disambiguator, in accordance with ].
::I agree. The lighter colors actually make the C4 (light red) and C3 (orange) colors harder to tell apart from a difference. I'd like to see those categories use a darker shade. ''''']''''' 🌀 (]) 04:39, 25 March 2022 (UTC)
:Determining the primary topic is usually a subjective process, though this can be backed up by objective statistics like pageviews, death tolls, or damage totals. Katrina is probably not a good case study since it existed in a time where content policies were less strict - ] was moved to ] on 27 August 2005, two days before landfall in New Orleans. These days, people prefer to wait for things to settle before making an assessment, like at ]. Faster moves do happen though, like with ] where the gap in usage and long-term significance became quickly apparent, making it easy to reach an early decision (and this is also what's happening with the ongoing Palisades Fire). ~&nbsp;] <small>{] · ]}</small> 14:45, 10 January 2025 (UTC)
:::How are C3 and C4 here difficult to tell apart? They seem rather well-defined both for those who can see all colors on the visible spectrum and for those with the three types of colorblindness (the significant difference in lightness is more than enough to adequately tell them apart and the original proposal that was supported was actually worse in this respect). And I like the lightness, personally, since it makes the scale feel more natural and doesn't have the last one/two colors be jarringly darker than everything else. If you're gonna change the lightness significantly, it should be progressive through the entire scale, not just making the end darker. ]&nbsp;(]) 06:10, 25 March 2022 (UTC)
::I think the example you gave is exactly why it could be helpful to provide guidance. My instinct is to leave the year on both and give it a few months before changing the name.
{{clear}}
::That wasn’t a popular viewpoint, and of course we make decisions by consensus so I don’t pretend that it has to be my way. But it seems to be pretty subjective, at least to me.
:'''Strongly Oppose''' - Much of this rehashes the problems with the current new scale and only makes things lighter (as well as having the shifting color problem as well). --''''']''''' (<sup>]</sup>/<sub>]</sub>) 04:19, 25 March 2022 (UTC)
::Unfortunately, I’d say it’s fairly likely there’s another significant fire (although hopefully not as significant as the current event) in the palisades in the next ten years. What will we do then? ] (]) 18:40, 10 January 2025 (UTC)
*'''Support''' the hybrid proposal (in conjunction with provisions 5 and 6 from Noah in the above discussion). It fixes the issues I had with colors being too similar and makes the category transition feel more natural. A new color is necessary to create an adequate range of colors and purple is the best fit for it. I believe making the purple darker would cause issues blue marble background, as evidenced by the maps provided by Jasper. ~ ] (]) 04:29, 25 March 2022 (UTC)
:::The guidance across Misplaced Pages, per ], is that the most significant event of a name should get the primary topic. Significance should have an objective truth to it, like number of fatalities, or acreage. ♫ ] (<small>]</small>) 19:06, 10 January 2025 (UTC)
*<s>'''Neutral, leaning oppose'''</s> '''Oppose''' – This scale looks okay for the most part, but I'd like to see a darker red color for C4, similar to what we have for the current C4 color (the former C5 color).A darker shade would make it easier to see on the maps. And perhaps a slightly darker shade of orange for C3 as well. Additionally, the lighter colors does make it a bit harder to differentiate the C4 and C3 colors at a smaller resolution. Also, what color are we going to use for the new severe tropical storm color? Menthol green? I don't see this category addressed in this proposal. Also, I feel like we are going to run into the same opposition to those who opposed the coloring system currently in use. ''''']''''' 🌀 (]) 04:39, 25 March 2022 (UTC)
::::I strongly support development of a guideline that spells out how to determine that objective truth. like you said fatalities and acreage are important. I think including other metrics would be important as well. For example:
:* Changing my vote to "oppose" now, in light of the issues identified by Akbermamps. Any viable coloring system has to work for both normal vision and colorblind readers, in templates, the track maps, and the Timeline chart. ''''']''''' 🌀 (]) 06:29, 25 March 2022 (UTC)
::::- people evacuated days (eg # of people * number of days evacuated)
*'''Weak Oppose''' The color scheme is a bit too light and I think it's hard to distinguish C1 and C2 colors on the map. Also, I'm not sure that introducing more color schemes at this point. ] (]) 04:43, 25 March 2022 (UTC)
::::- structures destroyed
**{{ping|TornadoLGS}} As you are probably aware, ] is satirical in nature and in this case, the analogy does not follow. If anything, having colors be brighter is necessary for contrast against the dark blue map. This is more akin to the RfC process of ] than what’s in that strip.—] ] 05:54, 25 March 2022 (UTC)
::::- housing units destroyed
***{{ping|Jasper Deng}} I am aware it is satirical, but I do think that it applies. The more proposed color schemes there are, the more camps there will be in this discussion, and the harder it will be to reach a consensus. An issue, I've found, with too many light colors, is that even if they are easy to distinguish in a chart, they are harder to distinguish from each other if they are all against a dark background, which kind of defeats the purpose of having a color scale. It seems to me that both the current color scheme and the second one under discussion, proposed by Noah, have sufficient contrast from the background. ] (]) 19:07, 25 March 2022 (UTC)
::::- economic damage
* I strongly support this as having the best of both worlds and also being based on sound color science instead of ] like “it looks ugly”.—] ] 05:47, 25 March 2022 (UTC)
::::- firefighters deployed
*'''Oppose''' While pleasant and contrast-compliant, looking on , the colors are either too close to each other or unintuitive. On the red-blind and green-blind simulations, the C1 and TS colors are basically undistinguishable, and on the blue-blind simulation, the C5 color is too close to the C3 color. It's confusing to see the scale getting redder and redder, then when it gets to C5, it suddenly gets lighter. I also want to note that changing the TS/TD color to be farther away from C1 will make the TD color too close to the C5 color for blue-blind people. With some fixes, this could work, but for now I'm opposing. ]] 06:17, 25 March 2022 (UTC)
::::- firefighting equipment deployed
:* In light of these issues, I have no choice but to oppose this proposal. ''''']''''' 🌀 (]) 06:29, 25 March 2022 (UTC)
::::- economic damage
:*I examined the issues you mentioned using that site and for none of the colorblindness types do C1 and TS or C3 and C5 look similar. ]&nbsp;(]) 06:36, 25 March 2022 (UTC)
::::- changes in how future calamities are handled because of learnings
:*To clarify in case there is confusion, I'm inputting the track map provided above into the colorblindness simulator. They are distinguishable on a scale, but when on a map it's very hard to distinguish the difference. ]] 07:52, 25 March 2022 (UTC)
::::All that said, I haven’t a clue how to make all of that objective. ] (]) 20:01, 10 January 2025 (UTC)
*Provided we slightly modify the PTC color to contrast with the C5 shade (and for everything except PTC), I will '''support'''. I like this significantly more than the original proposal that was voted on on the basis that it seems more natural with fewer weird jumps in the colors and makes the scale less oversaturated while still looking good on the colorblindness metrics. ]&nbsp;(]) 06:48, 25 March 2022 (UTC)
:::::I would support a metric based on some these guidelines (structures destroyed, damage $$), but not others -
:Tentatively '''support''' the use of varying hues to allow for clear distinctions in colors, a fairly uniform brightness, and the use of a bright color for cat 5. This is in contrast to the dark color "rose red" in the March 21st proposal which makes cat 4 the most prominent color on the dark blue track map background. I do think the one thing that perhaps hurts it is that it feels a bit too pastel/light, which could affect the color distinction somewhat. Would also like to see the colorblindness scale comparison, though given the similarity to the recently adopted color scale, it is likely quite sufficient in that respect. &ndash; ]<span style="line-height: 1.3em;"><span style="font-size:large">𓅊</span></span>] 07:12, 25 March 2022 (UTC)
:::::* People evacuated days is a good metric but hard to calculate, because evacuation orders are not issued or withdrawn uniformly and good reporting on # of people affected is often hard to find.
::{{re|atomic7732}} here is a color comparison chart. You can use to check the map proposed here if you would like. ]<sup>]</sup> 11:47, 25 March 2022 (UTC)
:::::* Number of personnel or amount of equipment is also tricky because some major fires will have relatively few resources assigned to them if there are a large number of fires burning concurrently (as with this SoCal event).
:'''Oppose''' due to contrast issues between TS and C1 for two types of color blindness, issues between C3 and C5 for one type, and because the top of the scale looks almost the same as the bottom on color blindness simulations. These problems are not apparent on a color table, but they are clear when looking at the map. ]<sup>]</sup> 11:51, 25 March 2022 (UTC)
:::::] (]) 20:21, 10 January 2025 (UTC)
::I would also like to point out that it is still difficult to tell TS from the original timeline background on this proposal, which is what the currently used scheme addressed. If we are looking at the new timeline background, the C1 would be too hard for normal vision and color blind vision. ]<sup>]</sup> 13:08, 25 March 2022 (UTC)
::::::Yes, agreed on both points.
:'''Oppose''' due to the fact the colors are too light and it doesn't fix the issues with the latest color issues. The problem was that many people haven't adjusted from the OG color scheme and are still going to have issues. Hell, how weird this one looks, it makes me want to go to the color scheme we have now. As for the color blind situation, due to its lightness, it would still be a problem per Noah so therefore I reject this. ] (]) 13:05, 25 March 2022 (UTC)
::::::I tried to calculate the people-evacuated-days for a few fires in 2020 during the lockdowns...because I had the time. After 3 or 4 days of maddeningly refreshing facebook posts from rural sheriffs and tracking down nixle alerts...I gave up.
::Why are we arbitrarily deciding this scale is "too light"? The current one, if anything, is oversaturated and too dark. At least this one is rooted in color science. ]&nbsp;(]) 05:26, 26 March 2022 (UTC)
:::::: expressed some interest in studying this in 2020, which is what inspired my effort, although I'm unsure if he ever did so. ] (]) 20:44, 10 January 2025 (UTC)
:::The issue of a scale being too light and/or undersaturated is that it decreases contrast between the colors within it. Increasing saturation and scaling brightness makes the colors more distinguishable from one another, which is the reason for changing the color scale in the first place. On the map, this proposed color scheme doesn't offers little, if any, improvement over the original. ] (]) 18:11, 26 March 2022 (UTC)
:::::::Commendable effort, I'm a fan of Wara's work. Figuring out evacuation timelines and stats is always my very least favorite part of writing wildfire articles. ] (]) 20:47, 10 January 2025 (UTC)
::::That last but is just objectively not true. Every color is decently discernible for all forms of colorblindness save the PTC and C5 colors, which not at all the case for the scale that has been in use for over 10 years. And yes, I did apply the colorblindness filters to the version on the map. Could it be slightly revised? Maybe. But I easily prefer it over the current scale or the original version that was voted on, save the PTC and C5 issue. ]&nbsp;(]) 00:07, 27 March 2022 (UTC)
::::::::Thanks!
::::And I'll add that if undersaturation and darkness really isn't an issue, then we should be using , which was created by an actual color scientist and is consistently perceptually uniform and usable for those who suffer from colorblindness. But aesthetics do in fact matter as well — nobody wants an unattractive scale and it is clear that this scale is too dark and undersaturated for people's liking. ]&nbsp;(]) 00:18, 27 March 2022 (UTC)
::::::::Yeah, he's a very smart guy, and it helps that he's so friendly and available, even to the public.
:::::I experimented a little with different screens. On my two computer monitors at least, I have trouble distinguishing the C1 and C2 colors on the map. They seem less distinct from each other on the map than in a chart. While distinguishing colors from the background is important, I still think this places too much priority on that over distinguishing the colors from each other. There has to be a correct balance. ] (]) 00:45, 27 March 2022 (UTC)
::::::::Evacuation timelines are such a mess -- frankly as are evacuation notifications in the real world. Its too bad that the companies that have 'tried' to solve that...haven't. Emergency alerts have gotten better, and some communities have improved their evacuation policies and procedures. But as a whole, its still a giant mess. ] (]) 22:34, 10 January 2025 (UTC)
:::::I'll add that I wasn't even considering aesthetic arguments since that, I thought, would fall under ]. But I was under the impression that increasing saturation would make the colors more mutually distinguishable, which was the main goal of this discussion. Its value is more than simple aesthetics. For instance I made by simply boosting the saturation from the link you gave. I'm not proposing this as the color scheme, but contrast among those colors is improved across the board. If I am missing something here, please let me know. ] (]) 01:12, 27 March 2022 (UTC)

===Colour for Storm Force===
I don't care what colours are used per say, however, I feel that it is important to remind people that we need a colour for 50 - 65 knots as after all it is a category on every scale bar the SSHWS.] (]) 14:54, 26 March 2022 (UTC)

===Potential off-wiki canvassing===
{{ping|TheresNoTime|Compassionate727|Worm That Turned}} Due to ] and the ongoing Arbcom case that has resulted in the indefinite block of the main nominator here (in which the user said canvassing had gone on in this entire discussion on the AN/I board), should the results of this entire section be nullified and reverted to the system used prior to November 2021? I actually had no knowledge that these off-wiki discussions took place to this extent and feel that if this was discussed extensively off-wiki then it should be nullified. ] (]) 14:01, 27 March 2022 (UTC)
:{{ping|United States Man}} I'm not entirely sure what the best course of action would be right now. While it makes sense to revert to the old scale in light of the canvassing issue, that would be undoing the compliance with WP:ACCESS which isn't ideal. I think for now we should defer to ArbCom and see what their input on how to handle the RfC result is. ~ ] (]) 19:50, 27 March 2022 (UTC)
::Something else that came to mind. I had already thought the implementation of the new colors was a bit hasty, since we didn't have a concrete plan for track maps aside from potentially automating the task. On that subject, I had been under the impression that Noah would be the main one who would make the bots, and his block derails that plan. Would this weigh at all on such a decision and can/should I mention this at the ArbCom discussion? ] (]) 20:20, 27 March 2022 (UTC)
:::It was mentioned earlier (by Support) that he would do the bots thing. I probably would mention it but I’m not so sure. ''''']''''' (<sup>]</sup>/<sub>]</sub>) 20:27, 27 March 2022 (UTC)
:After thinking it over a bit, I believe it's best we leave things at the Feb 2022 RfC and revisit this discussion once the ArbCom case is settled. Many editors involved in the color discussion are involved in the case and we should respect the space for that to be handled. Once the dust settles, we should definitely have a renewed color discussion as we didn't reach a consensus on further changes. We can leave the maps at the legacy colors as there has been no consensus on how to move forward with that. I don't think it's a big deal that the map colors temporarily don't match the infoboxes as they always have a color key attached. Does that sound acceptable? As I'm involved in the color debate I cannot make this decision alone. ~ ] (]) 22:51, 28 March 2022 (UTC)
::Both of the RfCs (including the November 2021 one) was also influenced by canvassing. As much as I hate to say it it probably is best to revert back to the original scale for now until this entire thing is finished. --''''']''''' (<sup>]</sup>/<sub>]</sub>) 23:30, 28 March 2022 (UTC)
:::I'd rather defer this matter to ArbCom and in the meantime maintain the status quo as default as one person being canvassed should not result in a single discussion being nullified IMO. ]] <sup>]</sup> ] 00:42, 29 March 2022 (UTC)

== ] ==

This article on Bill Read, one of the previous director of the ] is ambiguously named. There is a also a famous Canadian indigenous sculptor named Bill Read, a footballer and others of the same name. I had to redirect many link to this article that were for those others and modify the Wikidata. Wouldn't it be better to rename the article "William L. Read", his proper name, in order to avoid this problem in the future?

] (]) 04:38, 25 February 2022 (UTC)

:{{ping|Pierre cb}} ] discourages the use of middle names and initials in titles, except where the middle name or initial is part of the name by which the person is best known, such as Harry S. Truman. If the title for the article ] is proving troublesome, I suggest the title “Bill Read (meteorologist)”. If you look at ] you will see what I mean. ] ''(])'' 23:57, 21 March 2022 (UTC)

== Template:Tropical_cyclone_classification ==

I have nominated for deletion.] (]) 22:36, 19 March 2022 (UTC)

== Requested move at ] ==

] There is a requested move discussion at ] that may be of interest to members of this WikiProject. --] (]) 23:04, 27 March 2022 (UTC)

== ] ==

There is an ArbCom case regarding WikiProject Tropical Cyclones Discord server for which this WikiProject might have been affected. You might be interested in giving statements regarding that case. ''']]]''' 12:27, 28 March 2022 (UTC)

== Does anybody know of some papers / sources? ==

I'm currently rewriting the ] article, and have encountered multiple statements to this effect: " (Mavromatidis & Kallos, 2003). However, I can't seem to find any studies showing the gross warming and/or cooling effects of altostratus clouds. I was able to find significant sources on this topic when I wrote ]. About the only thing I can find for altostratus clouds is paper, but that gets extremely in-depth to the point that I'm hesitant to include its information since it might violate summary style.

Does anybody know of any sources for more gross statistics? Thanks! ] (]) 20:41, 28 March 2022 (UTC)

== Discussion about removing the fatalities section on ] ==

There is an ongoing discussion to remove the fatalities section from the ] article. Feel free to participate in the discussion ]. ] (]) 00:57, 31 March 2022 (UTC)

== Infobox for ] and other such yearly articles ==

There should be some sort of infobox for the yearly weather articles. It would be nice if we had yearly weather deaths, with accompanying citations. That would be amazing to have yearly weather deaths and damage statistics by year for every country, and for every weather type. And then the image would be a gallery of a few images. Any thoughts? ♫ ] (<small>]</small>) 21:16, 8 April 2022 (UTC)
:Sounds like a good idea to me. I think we should find a fairly regular / uniform source for this kind of information, though, since trying to sum them up ourselves could end up with radically-varying totals. Does the WMO or some other organization keep track of these statistics? ]&nbsp;(]) 03:43, 10 April 2022 (UTC)

== Requested move at ] ==
] There is a requested move discussion at ] that may be of interest to members of this WikiProject. ] <sup>(he/him &#124; ])</sup> 06:56, 9 April 2022 (UTC)

== Color issue for people who are monochromatic color blind ==


== Readability of outbreak list articles ==
I know that you guys debated the color change but there's a new issue, the Cat 4/EF4 and Cat 5/EF5 colors (When converted to simulate Monochromatic Blindness) appear as the same shade of gray. I know this because i used a program that changes color to black and white using the new scale color scheme and Colors 4 and 5 are the exact shade of gray. Hope this helps with your finalizing your color choice.
] (]) 20:46, 9 April 2022 (UTC)
:There isn't really much we can do about monochromatic blindness for the colors without redoing the entire scale, which is highly unlikely, given the immense difficulty in even reaching a consensus on this project for changing the colors. The only way that would even become a viable option is if we replaced the Blue Marble background currently used in the track map images, and IMO, such a change is much less likely to gain consensus than any of the color changes. ''''']''''' 🌀 (]) 16:23, 11 April 2022 (UTC)


I recently worked on at least starting the process of getting ] to featured list status. As part of this, I changed the layout of the page (organizing tornadoes by state), however that change was reverted for not being consistent with the standard layout of tornado list articles.
== Restoring old colors for now until the end of ArbCom ==


You can see my take on the style ] and the original ]. I want to get more opinions on whether the new style really is more readable, and whether or not keeping consistency with other project-space articles is more important than readability. Pinging @] as they were the one to revert my edit; bringing this to WPWX because this could easily affect other articles. Cheers! ] (]) 20:52, 11 January 2025 (UTC)
Given the dispute that the colors are involved in at ArbCom with regards to canvassing, I think its best to restore the old colors to the template until the ArbCom case is closed, which won’t happen for another month it seems. Plus, the entire debate was tainted by canvassing as admitted there so I think it’s more harmful to leave it the way it is now with it not matching the maps. I can’t edit it now since it’s fully-template protected. The info boxes not matching the maps is probably the most serious case of this since newcomers within the next few weeks will be confused (and the key does not help since that only appears on individual storm pages). Once the case closes, whatever comes out of it, we can restart the discussion anew. --''''']''''' (<sup>]</sup>/<sub>]</sub>) 12:00, 11 April 2022 (UTC)
:Bearing in mind that {{ping|Chlod}} reverted an attempt to restore the old colours yesterday and put a request for page and the comments above, I personally feel that it is better that we maintain the status quo until the case is over even if it is another month or so. Yes you may ] and people maybe confused by the new scale, but I do feel that those concerns are superseeded by ].] (]) 14:55, 11 April 2022 (UTC)
::I understand the concerns with ] but I don’t think it supersedes the other concerns of misleading information, especially given the fact, as stated above, that multiple people have raised the question. It’s better to create consistency instead of misleading color schemes for the rest of the ArbCom process, even if some think the opposite is true. I also don’t think ] applies here as this is a genuine concern for our readers during this process (since the maps are significantly different from the infoboxes at the moment) and it is far more a better idea to restore consistency between them for the time being. ''''']''''' (<sup>]</sup>/<sub>]</sub>) 15:15, 11 April 2022 (UTC)
:::No, we should keep the changes in place, pending the outcome of the ArbCom case and the RfC here. It is unlikely that the entire RfC will be overturned, and honestly, in the unlikely event that it is overturned, we will literally have to go through the entire discussion again, and you will have to rehash the entire fight with all of the participants, which will set tempers off again and result in more bad blood. Calling for such is counterproductive. As for the template protection, I think that was the best course of action. People need to stop screwing around with the colors, given that color template is highly-visible. We definitely should not have another version of the mid-April color wars at , which was extremely immature and a disgrace (the map is viewed by millions of people each day). Jason Rees is right in saying that ] applies here. And this really is an ] issue, which isn't even a valid reason for overturning the changes. It is not really our problem that so many people don't like change. And either way, there's going to be temporary confusion anyway with whatever new color scheme is implemented, so I see literally zero point in reverting. It's going to be inconsistent for at least a few months anyway, as we can't redo all of the track maps all at once, even if the RfC were immediately concluded. People can get used to the changes, and they will. Also, the correct procedure for RfCs is to keep the status quo pending the outcome of the discussion, not revert back and forth to whatever was the previous version. The fact that you're still suggesting this, and the fact that someone tried to reinstate the old colors in spite of the RfC, convinces me that Chlod was right in requesting the template protection. We should not entertain or even allow the possibility of further color-warring. ''''']''''' 🌀 (]) 16:23, 11 April 2022 (UTC)
::::I would also note that most of the articles and track maps technically are not consistent, since the track maps use data from the JTWC primarily rather than the RSMC's.] (]) 16:41, 11 April 2022 (UTC)
::::Again I really don’t think ] applies here given this is a genuine problem for the entire wiki. The problem is that the color scale is different enough especially at the high end to create confusion for a lot of new readers ESPECIALLY for C4 and C5 compared to the maps and that’s not what Misplaced Pages wants to do right? The result of the ArbCom will in some way likely result in some or a lot of rollback, and given the original November 2021 and subsequent February 2022 RfCs were tainted heavily with off-wiki canvassing, '''it is in the best option and for the project in general''' to at least restore the legacy colors so as to not create confusion and then we can work out whatever comes out of the ArbCom result. I’d argue even a bit that ] applies here given the rigidity. ''''']''''' (<sup>]</sup>/<sub>]</sub>) 16:45, 11 April 2022 (UTC)
:::::The new colors were established by consensus. If the impacts of canvassing were great enough to warrant nullifying that consensus, then that is a decision for ArbCom to make, not us. ] <small>(] · ])</small> 17:12, 11 April 2022 (UTC)
::Back when MarioProtIV first sparked an edit war on ], I thought of having the related pages template-protected but decided against it since modules fail to save if there's a syntax error. But considering the template does ''not'' have this same protection (after Modokai's edit yesterday that likely broke all usages of Beaufort, PAGASA, RSI, WSSI, and other scales that were added in the module), and knowing that an extended-confirmed user can add in a template error that breaks all cyclone pages, I decided to request protection given that there are +4,800 pages that will be affected if that happens. I really don't mind which scale is in use; the protection (and revert, since the template was reverted to a non-module version) was part of my duty as the primary maintainer of that module. <span style="background:#ffff55">''''']'''''</span>&nbsp;<small style="font-size:calc(1em - 2pt)">(])</small> 23:30, 11 April 2022 (UTC)
:{{edit conflict}} I'm maintaining the same position I had when the ArbCom case arose, keep the Feb 2022 RfC results as it meets ACCESS which is the primary concern. Another discussion will begin once the ArbCom case is settled and they, hopefully, provide some input on these discussions and how we proceed and how to balance canvassed opinions. Whether or not people like the colors does not override ACCESS requirements. WP:CCC does not apply here as the root of this renewed debate is a canvassed shift in consensus after a closed discussion. The canvassing is most-evident in the March 2022 RfC, not the other discussions, as there was a sudden increase in dissenting opinions over the accepted RfC results. Why would one think the same canvassing applied to the others when the results were the exact opposite of the canvassed goals? Reverting to the original feels like ] as L&D mentioned. ~ ] (]) 17:17, 11 April 2022 (UTC)
::My point was that this is '''only''' a temporary change until the case is finished and we come back to discussion. I’ve already repeatedly said I don’t think ] applies here as this discrepancy is a genuine concern for newcomers too within the next month. Plus, the current maps and TCR adjustments are still using the old colors for consistency and I think temporarily returning to the old colors fixes this disconnect. I stated numerous times we can come back to this once the ArbCom case closes and eventually come to a new proposal and begin adding it to the tracks, but doing this quick fix for a while can at least not confuse new readers who might not understand the intensity on the track vs the infobox. Regarding the RfC, the first RfC in November 2021 was canvassed almost as much as the March case was, which in turn undermines the Feb 2022 case since it was essentially a revival and given the proposal in the Feb 2022 case was IIRC a canvassed one since numerous discussion happened off-wiki about it in November 2021. ''''']''''' (<sup>]</sup>/<sub>]</sub>) 18:21, 11 April 2022 (UTC)
:Speaking as someone who has supported the color change, I do agree with Mario that the template colors not matching the map colors is a problem and is likely to cause confusion. Honestly, I had assumed that we wouldn't go through with actually changing the colors until we were ready to change the maps, too. Doing so before we had bots ready and whatnot was rather hasty, in my opinion. Admittedly, I felt some implicit pressure not to bring this up, which I alluded to at the ArbCom request. We shouldn't overturn the color change on the grounds of canvassing because that decisionis up to the Arbitration Committee, and they may decided that WP:ACCESS concerns override concerns of canvassing in this instance. Similarly, while I might otherwise support reverting until we are ready address the maps, because ArbCom might overturn any decision made here, I say our best option is to wait. ] (]) 18:48, 11 April 2022 (UTC)
::The problem I see with waiting another month is that opens the doors for confusion as you said. I know the ArbCom will decide the outcome but you also need to consider how this will affect new readers in that time period. I wouldn’t want Misplaced Pages advertising misleading colors for TC intensity between maps and templates as I would not be able to tell which was which. This discrepancy so to speak would prevent any adjustment IMO since the entire thing is in limbo bc of the canvassing issue. ''''']''''' (<sup>]</sup>/<sub>]</sub>) 19:02, 11 April 2022 (UTC)
:::The discrepancy is not much of an issue. The maps still have keys with the old color scheme. In terms of being able to understand them, nothing has changed. ] <small>(] · ])</small> 20:01, 11 April 2022 (UTC)
::::I think it is a big issue because as I’ve said, incoming readers will likely get confused and I honestly don’t think many check the key that is in the image (I know I don’t). The main issue here with the discrepancy is the big difference in C4/5, which can obviously confuse people (and not fixing this doesn’t lead to people adjusting as some might think). ''''']''''' (<sup>]</sup>/<sub>]</sub>) 20:21, 11 April 2022 (UTC)
:::::If readers are confused, they can check the key that is specifically for eliminating confusion. It's not like new visitors to these pages have embedded knowledge of the color scheme either. The color key objectively provides the answer. This argument doesn't hold much weight. ] <small>(] · ])</small> 22:19, 11 April 2022 (UTC)


== Need unified format ==
== Bold titles in article leads for events without formal names ==


We need a unified format for the "Weather of XXXX" articles. For example, ] and ] lists a blurb for each significant weather event (although very incomplete, missing tons of stuff), while ] simply lists Wikilinks, with some info on each type of disaster at the beginning. Thoughts? ] (]) 18:15, 15 January 2025 (UTC)
I've noticed that many of the storm articles we have repeat the article title in bold in the lead. Most of these titles are descriptive rather than actual names for the events, especially those that follow the format (e.g. ]. Reiterating descriptive titles like this is not supported by guidelines per ] and ]. I've mostly seen this in tornado outbreak articles, since I don't often edit non-tropical weather articles outside of those, but it is ]. I'm suggesting the removal of bold titles from articles like this. However, I figured I'd bring it up for discussion here first, since ]ly making changes en masse often doesn't go over well. ] (]) 21:15, 12 April 2022 (UTC)
*'''Support''' – I have been trying to make these changes here and there for a while. I fully support making the change to every article to follow MOS. ] (]) 21:22, 12 April 2022 (UTC)
* '''Strongly oppose''' as this is pretty much superseded by ] which says it can be there if accommodated in a natural way, which can be an easy fix. --''''']''''' (<sup>]</sup>/<sub>]</sub>) 21:53, 12 April 2022 (UTC)
**Restructuring the lead sentence to accommodate the bolded title is not natural, so ] does not apply there. ] (]) 22:34, 12 April 2022 (UTC)
*'''Question'''&nbsp;- I know that its good form to do so but do we have to mention the title in the lead? After all sometimes it is better not to.] (]) 23:04, 12 April 2022 (UTC)
::I agree. It seems unnatural to restate the article title in the first sentence. The reader already knows the title before having to read it again. Apparently it is also against MOS, hence the RfC below. ] (]) 23:06, 12 April 2022 (UTC)
*'''Support''' for any event without a widely accepted name. The article titles we give for the vast majority of outbreaks are just the dates since there is no naming scheme available, giving bold wording in the lead lends to that being an actual title. LGS's and USM's rationales are sound. ~ ] (]) 00:26, 13 April 2022 (UTC)
*'''Support''' - while as {{u|MarioProtIV}} observes, the MOS has a somewhat awkwardly phrased suggestion that we allow the article title to be bolded if it can be accomplished naturally, clearly in many cases this is not the bolded phrases are awkward and per the reasoning in ], I'd prefer that we only bold where there is widespread use of the bolded phrase. &mdash; ] <small>]</small> 10:21, 15 April 2022 (UTC)
*'''Oppose; it should be done on a case-by-case basis'''. There really is no requirement to use or not to use bolded titles in the leads of articles without a formal name. As such, I oppose enforcing a strict set of standards here when instead, we should be looking at each article on a case-by-case basis. Some of them, such as the list articles, shouldn't have their names bolded in the lead. But others can have the title accommodated and bolded in the lead, and I think that in some of those articles, this arrangement would be more appropriate. ''''']''''' 🌀 (]) 19:56, 18 April 2022 (UTC)


:Also note that I support the 2008 and 2009 format. ] (]) 18:15, 15 January 2025 (UTC)
===Request for comment: Bolding article titles in lead===
::] & ] is the best format in my opinion. '''The ]''' (] 18:20, 15 January 2025 (UTC)
<!-- ] 23:01, 17 May 2022 (UTC) -->{{User:ClueBot III/DoNotArchiveUntil|1652828498}}
:::Those seem like the intermediate between the 2008 format and the 2024 format. I could work with that! ] (]) 18:22, 15 January 2025 (UTC)
{{rfc|sci|style|policy|rfcid=FE51D49}}
:::I've begun a rewrite in userspace. ] (]) 21:06, 15 January 2025 (UTC)
An ongoing discussion as to whether bolding the descriptive article title of tornado outbreaks and winter storms is compliant with ] and ] requires comment from others. As it stands now, tornado outbreak articles typically have the event type followed by the date while and winter storm articles have the date preceding the event type: ], ], ], or ].
::::Yea, when the Weather of 2008 was originally written, it was called "Global storm activity of 2008", which was simplified to "Weather of 2008". The overarching articles should include a summary of all of the different weather types, and mention the deadliest events, I think that's a good way of making the article useful. ♫ ] (<small>]</small>) 21:15, 15 January 2025 (UTC)
:Per WP:SBE, bolding these titles in the opening line "{{tq|gives undue weight to the chosen title, implying that it is an official term, commonly accepted name, or the only acceptable title; in actuality, it is just a description and the event or topic is given many different names in common usage.}}"
:::::Elijah and I like the 2021 format like you mentioned, so I'm rewriting it. It looks like it's gonna be a lot of work, as 2008 isn't the only year that has a different format/issues(e.g. somehow Elie 2007 is not mentioned). ] (]) 21:19, 15 January 2025 (UTC)
:Per MOS:BOLDTITLE,
::::::Most "Weather of" articles need a lot of work, so I appreciate you doing that. ♫ ] (<small>]</small>) 21:21, 15 January 2025 (UTC)
:{{tq|If an article's title is a formal or widely accepted name for the subject, display it in bold as early as possible in the first sentence.}}
:These titles are descriptive and not formal names.
:{{tq|Otherwise, include the title if it can be accommodated in a natural way.}}
:These titles require the whole sentence to be written around them, such as {{tq|The '''January 2022 North American blizzard''' was a powerful and disruptive ] that impacted the...}}. This would also fail MOS:BOLDTITLE.


== Cool vs Cold ==
Input from others is requested. ] (]) 22:47, 12 April 2022 (UTC)


In connection with ], I'd like to know whether there is any guideline to distinguish what can be called ''cold'' from what is just ''cool''. I assumed that a Spanish town where 4 months per year have mean daily minima below freezing point could be described as having ''cold winters'' (rather than ''very cold'' or ''freezingly cold''), but there is no consensus. For comparison, I have checked a couple of random articles; for example the one about ] states: ''In winter, ... days are cool, and nights are cold but generally above freezing...'' Furthermore, it seems that it is correct to define winters in the town as ''cold for Spain'', which I would understand if it was a low-latitude country such as Malaysia or Panama, but not for Spain; this makes me think that there is some kind of ''Euro-centric'' or ''Northern-centric'' bias in how climates in the world are described. ] (]) 22:32, 15 January 2025 (UTC)
:An easy fix can be done by stating “The '''January 2022 North American blizzard''' caused widespread and disruptive impacts to the ] coast of ] from ] to ] with as much as {{convert|2.5|ft|in}} of ]fall, blizzard conditions and coastal flooding at the end of January 2022.” I do not see how that fails MOS:BOLDTITLE. ''''']''''' (<sup>]</sup>/<sub>]</sub>) 22:56, 12 April 2022 (UTC)
::This implies that was an official name given to the event when it's merely a descriptor in lieu of an actual title. There's no reason to force bold text when the same information can be conveyed naturally and without undue weight. ~ ] (]) 00:26, 13 April 2022 (UTC)
:::The sample at ] refers to the ] blurb, which is able to use it in a natural way. This can be easily done with these pages too, given some are from a single low pressure area (and thus should follow what tropical cyclones use), and thus doesn’t fail that MOS. The only other option is to use TWC names which have some more recognition (particularly the high impact and most notable ones) but that’s a whole nother can of worms that shouldn’t be opened. Don’t really see how undue weight is given since it states what it did. ''''']''''' (<sup>]</sup>/<sub>]</sub>) 00:53, 13 April 2022 (UTC)
::::{{tq|The only other option is to use TWC names...}} this is only the case if you try to force using bold text in the lead sentence. There's nothing wrong with the current method being used, it's clear, conveys the event, and isn't awkwardly dancing around to avoid repetition. What you're trying here is more of a stylistic choice that you want others to use. USM is correct citing WP:SBE, severe weather events are exactly what that guideline covers. ~ ] (]) 01:02, 13 April 2022 (UTC)
::::The presidential line of succession is well-recognized contingency such that effectively has a name. This is not the case with the date-based title format for storm articles. ] (]) 01:09, 13 April 2022 (UTC)
:I'm just going to say looking at two articles ] & ]. MOS says: {{tq|include the title if it can be accommodated in a natural way}}. The second link I gave incudes it, whereas the first link I gave is a natural lead-in to the topic and doesnt need to be changed. See WP:SBE {{tq|this practice is not mandatory and should be followed only where it lends natural structure}} <small>(brackets added by me)</small>; Basically my not-vote is ]. Both seem fine, and If there are specific articles with lead issues, fix those, otherwise spend your energy on editing other things. WP:AINT: {{tq| don't waste time and energy (yours or anybody else's) trying to fix it}} (that part about anybody else's is NOT a subtle dig at creating an RFC) Happy Editing--''']]''' 03:10, 13 April 2022 (UTC)
::I largely agree; the guidelines currently allow for avoiding long awkward bold titles in the article opening. So, technically, no change is needed. But if editors are ''commonly'' not taking advantage of this allowance, and are insisting on long and descriptive bold titles in the opening as if they were the common name of the subject, some thought can be given to strengthening the guidelines, or maybe just making an essay that other's can readily link when fixing this; it depends on how common this problem is. If the effort to improve the guidelines is less than the effort to correct the title use, then it should be done. --]<sup>(])</sup> 14:58, 14 April 2022 (UTC)
:::I agree with these opinions. This really shouldn't be a big deal at all, as ] doesn't mandate us to go one way or the other in this grey area. I think we should approach these articles on a case-by-case basis. ''''']''''' 🌀 (]) 19:56, 18 April 2022 (UTC)

Latest revision as of 22:32, 15 January 2025

This is the talk page for discussing WikiProject Weather and anything related to its purposes and tasks.
Shortcuts
Archives: 1, 2, 3, 4, 5Auto-archiving period: 50 days 
This project page does not require a rating on Misplaced Pages's content assessment scale.
It is of interest to the following WikiProjects:
WikiProject iconWeather
WikiProject iconThis page is within the scope of WikiProject Weather, which collaborates on weather and related subjects on Misplaced Pages. To participate, help improve this article or visit the project page for details. WeatherWikipedia:WikiProject WeatherTemplate:WikiProject WeatherWeather


2024–25 WikiProject Weather Good Article Reassessment

I would like to announce that a new task force has been created to re-examine the status of every GA in the project. Many good articles have not been reviewed in quite a while (15+ years for some) and notability requirements have changed quite a bit over the years. The goal of this task force is to save as many articles as possible. Anyone not reviewing an article may jump in to help get it up to par if it does not meet the GA requirements. The process will start officially on February 1 and will continue until every article has been checked and either kept or delisted. The task force may be found at Misplaced Pages:WikiProject Weather/2024–25 Good Article Reassessment. Noah, AA 15:22, 26 January 2024 (UTC)

Articles under review

List of tornadoes in XY trivia concerns

A user recently added tags to a lot of articles including List of tornadoes in the tornado outbreak of March 31 – April 1, 2023 stating that the article contained overly trivial content appealing only to a specific audience. I disagree with this assertion, so upon removing these tags and explaining in the edit summary that the article is standard, the user reinstated the tags and stated they're going to stick with this assertion even if it is a project-wide standard. So, I suppose, consider this a heads-up for a future RfC, because I have aspirations of getting the 31 March outbreak to a good / featured topic and these tags are killing those plans in their tracks. Departure– (talk) 20:59, 6 December 2024 (UTC)

It would probably be good to ping this user in the article's talk page and ask for specific details on what they mean before escalating further. DJ Cane (he/him) (Talk) 21:47, 6 December 2024 (UTC)
The specific diff is here and the edit summary back-and-forth went as such:
  • 2 December: Added {{Excessive examples}} and {{Overly detailed}} tags
  • 6 December: Undid revision 1260738230 by Fram (talk) remove tags - this is a standard "list of tornadoes in xy outbreak" page and this one shouldn't be singled out, if there's a problem with these page's notability it'd be better to take it to Wikiproject Weather instead of this page
  • 6 December: Undid revision 1261573129 by Departure– (talk) If the issues xith this page are standard with this project, then geel free to alert the project thzt they will have to cleanup the other articles as well. This is a list with way too much trivia
I understand their assertion and think that it would have been made inevitably. @Fram, could you please clarify your specific concerns regarding the "list of tornadoes in xyz" page format? I understand your position is that these pages consist entirely of trivia outside the scope of Misplaced Pages. I don't agree with that position but if you have any further comments please do share. Departure– (talk) 22:38, 6 December 2024 (UTC)
Thank you for raising this and pinging me. I´ll have more time to answer on Monday probably. I don´t consider the whole list to be trivia, but way too many if the minor tornadoes and their (lack of) damage and so on is of no importance at all. Fram (talk) 22:51, 6 December 2024 (UTC)
That's a fair assessment to make, but consider also that the list of tornadoes is usually included in the outbreak's article itself, and is usually only split off once it reaches 100 entries or so. If you want a really extreme example of this, see List of tornadoes in the 2011 Super Outbreak or List of tornadoes in the tornado outbreak sequence of May 2019 - these both have nearly double what the 31 March outbreak article has, and having them as separate from the outbreak's article seems obvious. I should also state that the list articles can be useful in illustrating the widespread nature of any given tornado outbreak, and remember that even a "weak" EF1 tornado can change lives, as we saw at the Apollo Theatre on 31 March. Even EF2 / EF3 tornadoes can fail the notability test for article sections, even if they have plenty of coverage and do deserve at least a mention in reference to the outbreak, and the list articles do just that. Once you have those, it's clear that including even the weak tornadoes that caused no human cost should be included. I'll compare it here to American Dad! season 20 which has a list and brief description of each episode - as a whole, these episodes have enough information to comprise a list, even those with bare-bones notability and importance. Their absence would be detrimental to the list as a whole. Departure– (talk) 23:03, 6 December 2024 (UTC)
An episode seen by 300,000 people in the US alone, shown in other countries, repeated, perhaps a DVD, ... vs. a tornado which caused little or no damage or is only seen by some security camera or one or two people. More on monday! Fram (talk) 23:13, 6 December 2024 (UTC)

This list (and many similar ones) want to describe every single tornado, no matter how minor. I see no reason why we would want to have so much unimportant, minute details, taking away the attention of the actual more major tornadoes by putting every little thing down. We don't do this for other events or accidents, we wouldn't list every car accident or building fire because some of them are important, notable, deadly, and we also don't list every damaged property, affected village, uprooted tree in the case of non-tornado storms. ... In the example list, we have 146 tornadoes, 12 of them major (EF3/4), 32 average, and 103 minor or unknown. Some of these minor ones are more notable than others, due to where or when they happened, but the vast majority are really of very passing interest only. Briefly mentioning the minor ones as groups (genre "14 EF0 en EF1 tornadoes occurred in Wisconsin, causing damage to properties and uprooting trees") and only giving more attention to the more notable ones would solve WP:UNDUE issues, not inundating the reader in countless details where minor and major stuff is given equal weight. Fram (talk) 13:34, 9 December 2024 (UTC)

I get that they may not all be inherently notable, but the main reason I'm willing to die on this hill is I'm trying to get the March 31, 2023 tornado outbreak to featured topic status, which will require to get this article to featured list status. The criteria for featured list has the following:
  • Comprehensiveness.
    • (a) It comprehensively covers the defined scope, providing at least all of the major items and, where practical, a complete set of items; where appropriate, it has annotations that provide useful and appropriate information about the items.
    • (b) statements are sourced where they appear, and they provide inline citations if they contain any of the four kinds of material absolutely required to have citations.
    • (c) In length and/or topic, it meets all of the requirements for stand-alone lists and includes at minimum eight items; does not violate the content-forking guideline, does not largely duplicate material from another article, and could not reasonably be included as part of a related article.
There's no reason in my eyes not to list every tornado, but a significant amount of the tornadoes were weak EF0 and EF1 tornadoes and including at the very least a one sentence summary for them would be preferred to increase the quality of the article. I'm not aware of any list where entries deemed minor or unimportant are stripped of their right to a summary, especially when there are reliable sources to put descriptions of said entries. Departure– (talk) 13:42, 9 December 2024 (UTC)
I'll also say that this is a much more specific and inclusive page than the parent outbreak's article, Tornado outbreak of March 31 – April 1, 2023. That, in fact, does have descriptions of six individual tornadoes that day under the section #Confirmed tornadoes, and each is given around 6000 words of prose. I agree that it would be absurd to give that to each tornado in the outbreak - hence why the list is used for less notable tornadoes. Departure– (talk) 13:45, 9 December 2024 (UTC)
But the same is done when there is no main article, or when the tornadoes are just a more or less random grouping, as in List of United States tornadoes from July to August 2023. This is not an outbreak but an arbitrary period, with at first glance one tornado which caused considerable damage plus deaths and will have plenty of sources, but of the 250+ other tornadoes, probably 10 or so will have received local coverage, and the others are just entries in the NCEI database. Fram (talk) 14:12, 9 December 2024 (UTC)
We have been doing monthly tornado lists like this for a while. We usually merge months together unless there are more than about 150 tornadoes in a given month. One thing worth mentioning is that yearly tornado articles keep a tally on the number of tornadoes by rating, which would be quite difficult without some kind of list. TornadoLGS (talk) 02:57, 10 December 2024 (UTC)
We should hardly keep articles in the mainspace just for the sake of a yearly tally. I see that e.g. 2017 had 1418 tornadoes in the US, so hardly a rare event. Apart from counting them, what is the purpose of listing and describing all of them, no matter how minor? Fram (talk) 15:43, 10 December 2024 (UTC)
What would be the appropriate namespace then? TornadoLGS (talk) 18:51, 10 December 2024 (UTC)
If the project needs this, then projectspace. Fram (talk) 08:32, 11 December 2024 (UTC)
I have serious doubts that putting these pages in project space would fix the problem, and also doubt the problem exists nearly to the point of removing a significant amount of projectspace pages. There just aren't many reasons to make an article on, say, Hurricane Milton's tornado outbreak, despite producing multiple significant tornadoes responsible for multiple deaths, when it's summary at List of United States tornadoes from August to October 2024 fits that just fine. A lot of more minor outbreaks aren't good fits for pages but are still clearly fits for Misplaced Pages. It's entirely practical to list every tornado in the country. These articles pass WP:NLIST, as the 2024 tornado season has been discussed independently in reliable sources (a list of tornadoes in 2024 would be too long, so splitting it into smaller articles is practical). It's by no means of little interest to the general public and still gets an average of 89 page views per day over the last month. Even barring that, the fact is that most tornadoes nowadays have their best summaries on Misplaced Pages and choosing to not have these summaries on the grounds of "not being of interest to the general public and being too similar to other outbreaks, and giving too much details to unimportant events" strike me as nonsensical.
Tornadoes, even weak ones, can and do change lives, and enough of them happen each year to establish their notability; we're describing and listing them as a group, whether or not they hit anyone, because we recognize their importance and agree that it is indeed practical to list every tornado in a season / outbreak / part of a year. Departure– (talk) 13:23, 11 December 2024 (UTC)
But the vast majority of these tornadoes don't change lives, and "enough of them happen each year to establish their notability" doesn't make any sense: the fact that there are notable X doesn't mean that every X is notable. The same arguments can be made about car crashes, house fires, ... some of them are notable, change lives, have lasting importance: but that doesn't mean that we would list every car crash if we had some public database of them. What makes extremely minor tornadoes different from extremely minor car crashes? Fram (talk) 13:44, 11 December 2024 (UTC)
Your point is understandable and I acknowledge we wouldn't be having this discussion if there was a proper policy setting in stone the procedure for individual weak tornadoes. But I will say that you are the first to state that you believe these pages have notability issues; the consensus in the weatherspace of Misplaced Pages is, from what I can tell, that these articles do belong in mainspace as they are. I don't feel like discussing this further as i believe we've reached deadlock with both sides raising valid objections, so expect an RFC to be opened later today regarding this topic, where you will be welcome to argue your position on this matter in a more formal consensus-building setting. I'll admit I'm not a die-hard on keeping the tornadoes, but the alternative requires changing the status quo and gutting articles that have been untouched for years, including a few featured lists (List of California tornadoes, List of Connecticut tornadoes, Hurricane Katrina tornado outbreak, List of tornadoes in the 1999 Oklahoma tornado outbreak, List of tornadoes in the tornado outbreak of May 4–6, 2007). Good day to you. Departure– (talk) 13:52, 11 December 2024 (UTC)
Just a P.S. for Fram: Referencing car accidents isn't a good argument since over 36,000 car crashes happen per day in just the U.S., which means more car crashes happen in 1 day in just the U.S. than tornadoes worldwide in just the 21st century (roughly 1,600-ish tornadoes a year worldwide). Honestly, the list of tornadoes is closest to something like the Lists of shipwrecks, where it goes year-by-year, month-by-month, and even in the List of shipwrecks in 2024, Day-by-day. The Weather Event Writer (Talk Page) 14:13, 11 December 2024 (UTC)
Then replace car crashes with bus crashes. As for the shipwrecks, most of these are at least a lot more substantial than "two storm chasers drove through this short-lived tornado which did no damage" and similar entries. They are also referenced to actual major news sources in many cases, not a government database, so they have clearly received independent attention. Fram (talk) 14:22, 11 December 2024 (UTC)
rther comments should be discussed in the RFC at the bottom of this page. Departure– (talk) 14:33, 11 December 2024 (UTC)u

Requested move 8 December 2024

The following is a closed discussion of a requested move. Please do not modify it. Subsequent comments should be made in a new section on the talk page. Editors desiring to contest the closing decision should consider a move review after discussing it on the closer's talk page. No further edits should be made to this discussion.

The result of the move request was: moved as proposed. If any of these need further changes, feel free to start a separate RM (or just move them BOLDly). Extraordinary Writ (talk) 04:08, 15 December 2024 (UTC)

– Literally any article entitled "List of tornadoes in the tornado outbreak / tornado outbreak sequence of XY" renamed to drop the second "tornado" in the title. It lets each article have a shorter title, and the fact that it's a tornado outbreak is obvious given that it's a list of tornadoes, established in the title. The only exception is for named outbreaks like the 2011 Super Outbreak - this is for genericly named outbreaks only. Departure– (talk) 03:02, 8 December 2024 (UTC) Departure– (talk) 03:02, 8 December 2024 (UTC)

Also Support --ZZ'S 06:12, 9 December 2024 (UTC)
• Support ModdiWX (You Got Mail!) 14:31, 10 December 2024 (UTC)
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

New severe weather terminology drafts

I have created two draft articles pertaining to severe weather terminology (in Germany and New Zealand) and I’m about to create a draft for Australia warnings. I encourage anyone who wants to do so to help with the draft. Thank you. Hurricane Clyde 🌀 01:13, 11 December 2024 (UTC)

I do invite anyone who wants to to help with these drafts. I think I have the format right on the Germany article but I don’t know for sure.
Will definitely need help on the rain-related alerts because the units used by the DWD are “l/m2” which I presume is liters per cubic meter but I don’t know for sure. Hurricane Clyde 🌀 21:52, 13 December 2024 (UTC)

RFC on tornado lists

Should weak and unimpactful tornadoes be included in list articles? Departure– (talk) 14:20, 11 December 2024 (UTC)

Opening comments: This all began because of an above discussion, where an editor placed a tag on List of tornadoes in the tornado outbreak of March 31 – April 1, 2023 article for "excessive examples", and upon discussion stated that weak tornadoes with little effects were getting too much prose in the lists given their impact and shouldn't be listed in the same manner as other tornadoes. This goes against the status quo of the "List of tornadoes in the XY outbreak" and "List of United States tornadoes from X to Y, YYYY" list articles which have remained largely untouched in policy and unquestioned on notability since their origins. I personally believe that, since other tornadoes in the list are practical, all tornadoes that can be reliably sourced to be included should be listed with a brief summary. Another potential solution which I personally oppose but could be implemented is prose in the articles for EFU/0/1 tornadoes, stating that "X weak tornadoes producing little impact were also observed". I'll also state that this statement will make tallying tornadoes harder, given the lack of specificity that can lead to under or overcounting. Whatever the outcome of this RFC, I merely hope the solution will prevent this issue from producing policy-based stalemate with maintenance tags having no clear and easy solutions as we have at the first article I mentioned. Departure– (talk) 14:27, 11 December 2024 (UTC)
  • WP:CSC: "Lists are commonly written to satisfy one of the following sets of objective criteria:" When we apply this to e.g. List of United States tornadoes from July to August 2023, we see that it certainly doesn't meet #1 (not all these tornadoes are independently notable), it doesn't meet #2 (some of them are notable (e.g. Tornado outbreak sequence of August 4–8, 2023), and it doesn't meet #3 ("reasonably short (less than 32 KB)": the example article is more than 200K, and is already a random subdivision of US tornadoes of 2023). Fram (talk) 14:58, 11 December 2024 (UTC)
  • Cherry picking certain tornadoes to include here would be overly subjective and impossible, so it’s really an all or nothing scenario. I support including all tornadoes as is done currently, with no changes needed to the current core status of the lists. The only way these lists can be totally objective as Fram mentioned above is to include all of them. United States Man (talk) 19:22, 11 December 2024 (UTC)
  • That´s the same kind of argument used for years for sports, everyone who played one game is the only objective measure. Didn´t fly there, doesn´t fly here. Including e.g only tornadoes of, say, EF2 and above is equally objective. Or all rornadoes which have at least one non-local reliable source apart from the curre t database. Or probably other rules, these are just some first thoughts. Fram (talk) 19:40, 11 December 2024 (UTC)
    Actually no, there are numerous cases where EF1 and even EF0 tornadoes include more damage description and even media coverage than some EF2s, so then again, it is subjective. You can frame this anyway you want, but your argument here is actually not an improvement and is detrimental to the Wikiproject and the flow of information of Misplaced Pages as a whole. There are actual issues afoot here in this wikiproject, such as mass creation of tornado articles with bad grammar, multiple factual errors, and content-fork creation. The list pages are not a hill to die on for you imo. United States Man (talk) 19:53, 11 December 2024 (UTC)
  • I've been following this discussion without really chiming in, so I will offer a possible solution. Noting, if I was actually choosing, I choose to not alter anything. However, this is a possible compromise to the dispute:
  1. Monthly U.S. tornadoes articles remain stand-alone list articles (merges to combine additional months open to case-by-case basis).
  2. Any tornado that has one non-NOAA source is automatically notable for summary details (i.e. summary details as the lists have now).
  3. The leader is altered slightly from the current lead versions to denote this includes notable tornadoes (i.e. at least one non-NOAA source)
  4. In the lead, any weaker tornadoes are noted without full summaries. For a hypothetical example: "In the month of July, 20 tornadoes occurred across the U.S., with 3 rated EF2, 10 rated EF1, and 22 rated EF0."
  5. The hypothetical example above would be cited by the NOAA database set just to the monthly tornadoes, which is a reliable source.
As mentioned, I don't necessarily support this at this moment, but I wanted to throw a possible solution into the water. If consensus/compromise would be falling towards allowing this type of solution, I would be for it. The Weather Event Writer (Talk Page) 19:54, 11 December 2024 (UTC)
That´s more or less what I intended with my second suggestion, and seems like a good basis for discussion. Fram (talk) 20:26, 11 December 2024 (UTC)
Almost every single tornado will have a non-NOAA source if you look for them (i.e. local news). So we’d end up excluding maybe 2-5%, so why not just include all of them and be done? United States Man (talk) 21:09, 11 December 2024 (UTC)
If almost every single tornado has local news coverage... what's even the point of being selective? Wouldn't they all be considered notable? Departure– (talk) 21:14, 11 December 2024 (UTC)
That’s my point. United States Man (talk) 21:18, 11 December 2024 (UTC)
Playing devils advocate for a moment: Then the local news coverage source should also be listed with the NOAA primary source. While those of us (y’all and myself included) generally understand that fact, I’ll be honest, in the example article listed by Fram above, List of United States tornadoes from July to August 2023, there is 0 non-NOAA sources outside of the lead. Out of the entire list article, which has 262 sources, 260 comes from NOAA and 2 come from non-NOAA sources. Part of the overall issue is that WikiProject Weather got in the habit of citing NOAA and then not anyone else since the info was already cited. The topic of “Is NOAA a primary source” has come up multiple times and the answer is yes it is (WP:VNTIA). So technically, if we look at Misplaced Pages policy to the letter, that article is basically cited entirely by WP:PRIMARY sources, which is actually cautioned against, not secondary reliable sources, which is preferred over primary sources. Basically, a possible solution to not even change the list is to just add a secondary reliable sources to the tornadoes. Then, see where it goes from there. Anyone else think that may be a good idea? Actually see how many tornadoes do/do not have secondary sources?
If one or two do not, then the list, bluntly, is fine (once non-NOAA is actually added). If 20+ do not in a monthly list, then we may have a true problem. As I see it, the problem is that primary is being used and secondary is basically being ignored, leading to Fram’s conclusion that most of the tornado may not be notable enough for the list. The Weather Event Writer (Talk Page) 21:54, 11 December 2024 (UTC)
Yes, it should be mentioned in the list as its omission would be misleading (showing less tornadoes than there actually was), less accurate, and less comprehensive. I'm fine with a brief summary, mention, or omission of some of the events outside of the list only if certain details of the tornado would be inappropriate or rule-breaking. ZZ'S 05:00, 14 December 2024 (UTC)
  • (Summoned by bot) - Yes, if I understand the question. All tornadoes are sufficiently eventful and concerning that, if there is a list, they should be included in a list. Tornado warnings are disruptive. People who have been disturbed by tornado warnings and have headed for cover when there was no damage would still like to see that event in a list. Robert McClenon (talk) 00:06, 12 December 2024 (UTC)
    • Tornado warnings are general, not for a specific tornado. "All tornadoes are sufficiently eventful"? Many tornadoes are likely to remain undetected as they are very minor and shortlived and if no camera or storm chaser is nearby and they happen on unpopulated land they will likely not be noted. Even among the ones listed. Look at e.g. List of United States tornadoes from July to August 2023#July 7 event; none of these 4 tornadoes were, as far as we know, eventful; we have no idea if tornado warnings were given, and if so where and when. As an aside, I have no idea why this is called the "July 7 event", these were not one event but can perhaps be considered two events (the ND ones and the Texas one have nothing to do with each other). Just labeling it with the date (so here "July 7") would be at least better. Fram (talk) 12:34, 12 December 2024 (UTC)

There are times when it's useful to list (or attempt to list) every tornado (like List of Australia tornadoes). I guess the bigger questions comes down to the effort to document every tornado in the United States each year, and how best to do that. The way we do it now, we have the yearly Tornadoes of 2024, plus monthly lists in the US such as List of United States tornadoes in May 2024, as well as individual outbreak articles, such as Tornado outbreak sequence of May 19–27, 2024, and sometimes those outbreak articles have individual lists, such as the List of tornadoes in the tornado outbreak sequence of May 19–27, 2024. While that might seem like a lot of overlap, any single tornado has the potential to be notable. Take the EF2 tornadoes for example: none of the EF2 in the List of tornadoes in the tornado outbreak sequence of May 19–27, 2024 get a mention in the main outbreak article. But given the current length of the outbreak article (7,500 articles), it would be too much to include every single EF2. Now most of them weren't that significant, but an EF2 can still destroy a building, so they still deserve mention. Even EF0 and EF1's have the potential to cause significant impacts - the most recent tornadic death in New Jersey was caused by an F0. In the interest in being inclusive, I don't think it makes sense to be unnecessarily restrictive. At the same time, requiring non-NOAA sources could be tricky, since a lot of news sources just regurgitate NWS reports. I realized that while working on List of California tornadoes. I think the way that the severe weather project has been handling tornadoes is honestly pretty impressive. I should also note the importance of digging into each tornado directly, rather than just relying on random NCDC links, as there can be multiple reports for the same tornado if it crossed state/county lines, or if the tornado touched down multiple times. In short, I don't think much needs to change, other than maybe summarizing more here and there, and trying to include non-NOAA sources (when the info doesn't just repeat what's in the NOAA sources). ♫ Hurricanehink (talk) 18:11, 12 December 2024 (UTC)

Here’s my opinion: if it’s a list of tornadoes in a specific outbreak: I believe that ALL tornadoes that occurred in that outbreak, even if their impacts were trivial; need to be included. Hurricane Clyde 🌀 20:01, 13 December 2024 (UTC)
If we’re referring to the Tornadoes of YYYY articles and the like, then I think WP:TornadoCriteria should be followed. And only list the more notable ones. But it really depends on the case. But if it’s concerning individual outbreaks; then every tornado needs to be listed. Hurricane Clyde 🌀 20:03, 13 December 2024 (UTC)
If we're only listing tornadoes notable enough to be mentioned in the yearly article anyway, what's the point of even having the list? In any case, if we make such a move, there will still need to be a list of all tornadoes in project space so we can keep an accurate tally. TornadoLGS (talk) 05:38, 14 December 2024 (UTC)
Tornadoes of YYYY isn't the same as the "List of tornadoes from M to M YYYY" lists that get created every year. Departure– (talk) 12:54, 14 December 2024 (UTC)
What may be more prudent here would be to split those M to M lists into monthly lists rather than omit tornadoes. Hurricane Clyde 🌀 18:48, 14 December 2024 (UTC)
So, in all honesty yes even weak and unimpactful tornadoes should be included in these lists. If the lists grow too long; we should instead split the lists. Hurricane Clyde 🌀 18:50, 14 December 2024 (UTC)
List of United States tornadoes in May 2024 is a list focusing on one month and already reaches 118kb in size. This is why I in particular beg for a {{cite pns}} or {{cite storm events database}} template. I'd wager there's a non-zero chance that the Storm Events Database is the single most used citation across all of Misplaced Pages, and these lists are a big part of that. Cutting down the size in bytes can also be done by cutting summaries of tornadoes from outbreaks and simply including a main article tag with the small table, rather than the excerpt format used today. Departure– (talk) 19:31, 14 December 2024 (UTC)

I have no more hope of changing anything at this project, which is probably as bad as the former roads project when it comes to closing ranks and not seeing how completely inappropriate their efforts are to duplicate a database in all its excessive detail. List of United States tornadoes in May 2024 has more than 500 tornadoes, most of them very ephemeral, and the suggestion to deal with this is ... creating a new cite template to reduce the size of the sources. Try to imagine some other weather phenomenon, say a hurricane or a winter storm or whetever, and having a place by place list describing in place X "damaged some vegetation and fencing", in place Y "damaged a small shed and utility trailer", in place Z "caused no known damage", elsewhere "no damage could be found.", and in many places strong winds were observed but nothing more. And buried among this endless list were the serious, noteworthy instances with deaths or truly massive damage. But hey, congratulations all around, we have repeated every instance from the weather database, good job people! Fram (talk) 14:45, 10 January 2025 (UTC)

RfC at Talk:2020 Cookeville tornado

An RfC has been started to challenge to authenticity of a supposed picture of the Cookeville tornado that was pulled from Reddit and added to the article. United States Man (talk) 19:48, 11 December 2024 (UTC)

Proposal for Template:Cite storm events database

Per the above comment by User:Departure– above, we should probably have template for referencing storm events, since, as the user said, "there's a non-zero chance that the Storm Events Database is the single most used citation across all of Misplaced Pages." Every single URL has the same beginning, so such a template might also need something like Template:NHC TCR url, which shortens the URL for TCR's released by the NHC.

There is a little bit of inconsistency over the publisher and author, but since we don't know the people who actually write the event reports (other than the local NWS office), I think the default publisher should be "National Climatic Data Center". Does anybody with template knowledge think they could work on this? I can try tackling it after the new year if no one does it. ♫ Hurricanehink (talk) 20:28, 14 December 2024 (UTC)

On the database I've been experimenting with a citation that displays as "Storm Events Database (LWX survey BALTIMORE MARTIN ST, 2024-06-05 20:27 EST-5). I think the WFO and ID are all that are needed, but I'm definitely in support of the begin location or timestamp being alongside the WFO. Departure– (talk) 20:38, 14 December 2024 (UTC)
I have previously wondered about setting up a template similar to the NHC TCR URL one before now, however, I'm loathed to as I have previously been informed that the URL ID changes from time to time.Jason Rees (talk) 22:09, 14 December 2024 (UTC)
As long as the time between when the URL is put into the article, and there is an archives of that URL, then it shouldn't matter too much for when it changes. Linkrot is a problem that's avoidable. Data compression is also helpful for articles loading faster, so a template would be useful. As for what User:Departure– made, I think it should have the "National Climatic Data Center" as the publisher, but "Storm Events Database" should be the series, if that's possible. The details about the exact time and location is good, but that is ultimately extra coding being added to one of the most common citations. Perhaps a title of just " event report"? The weather type would be whatever is the first entry. That way the NCDC URL could be used all across the weather project. For example - "High wind event report" or "Hurricane event report" or "Tornado event report". If we wanted to be more specific, maybe add location, so you could have "California high wind event report", or even "Monroe County, Florida tornado event report". There are options, but seeing how often the NCDC reports are used, there should be some discussion on it. ♫ Hurricanehink (talk) 01:05, 15 December 2024 (UTC)

List of South America hurricanes nominated for featured list removal

I have nominated List of South America hurricanes for featured list removal. Please join the discussion on whether this article meets the featured list criteria. Articles are typically reviewed for two weeks; editors may declare to "Keep" or "Delist" the article's featured status. The instructions for the review process are here. Yilku1 (talk) 16:03, 15 December 2024 (UTC)

March 31 featured topic

As I'm sure everyone here is aware, this year's off-season hasn't proved to be particularly interesting. So, if you're looking for something to edit, why not work on the March 31, 2023 tornado outbreak topic? Me and EF5 began working on this a while ago, but the goal is to get everything regarding this topic to at least good article status. My personal goal is to see the March 31 outbreak as a featured topic by March 31 of next year. If you're up for this project, consider contributing to any of the articles below - especially the C class and draft articles.

view | edit | discuss Tornado outbreak of March 31 – April 1, 2023 7 articles
List of tornadoes in the outbreak of March 31 – April 1, 2023
2023 Wynne–Parkin tornado
Belvidere Apollo Theatre collapse
2023 Covington tornado
2023 Little Rock tornado
2023 Robinson–Sullivan tornado

My personal to-do list is getting the Little Rock article published, adding NCEI references to the List article (and bringing it to FL status), and finishing my FAN of the Belvidere theatre collapse, as well as potentially creating original media for the articles in need of path, etc. photos.

Cheers and happy editing! Departure– (talk) 15:29, 16 December 2024 (UTC)

RfC: Criteria for individual tornado articles

Should we have notability standards for individual tornado articles? We already have informal inclusion criteria for "Tornadoes of YYYY" articles. Below is a preliminary proposal for such criteria, with the hope that it can evolve into a formal guideline that can possibly be referenced in future AfD discussions.

recycle Previous discussions: New tornado articles and the news, Proposal - Criteria for inclusion on Tornadoes of XXXX articles

This has been nagging at me for a while now, and since another editor has talked to me about this issue, I think we bring this up. Since we have a sort of "inclusion criteria" for "Tornadoes of YYYY" articles, I suggest we come up with notability criteria for individual tornadoes as well. See User:EF5/My tornado criteria for what this may look like.


This is my very primitive way of determining the notability of several tornado articles I've written, and am hoping that it could be integrated into a refined set-in-stone WPW policy that could be used in actual AfDs. I'd assume that the table will be gotten rid of and turned into a list. This has been discussed in the past, but never really came to anything. Maybe it could be... WP:NTORNADO (with it's own project page)? Starting an RfC, since obviously community input is needed. Also pinging @Departure–:, who suggested this. :) EF 18:56, 16 December 2024 (UTC)

I support these guidelines, but please see my suggestions on the talk page - the wording around fail-if-pass criteria make this much more difficult to read than it needs to be. Perhaps putting them in their own section separated from the other criteria would resolve this. Departure– (talk) 19:01, 16 December 2024 (UTC)
Resolved discussion regarding the RfC's opening statement.
@EF5: Please add a brief and neutral opening statement that does not include a table; this has broken the RfC listing pages. --Redrose64 🌹 (talk) 08:44, 17 December 2024 (UTC)
How about now? waddie96 ★ (talk) 11:48, 18 December 2024 (UTC)
These two edits merely lengthened the existing overlong statement. --Redrose64 🌹 (talk) 19:52, 19 December 2024 (UTC)
Ok fix it yourself. waddie96 ★ (talk) 21:34, 19 December 2024 (UTC)
I'm pulling this RfC on the grounds that it is invalid. Please read WP:RFCST before trying again. --Redrose64 🌹 (talk) 22:46, 21 December 2024 (UTC)
@Redrose64: Please explain specifically what is invalid about the RfC, preferably quoting from WP:RFCST, as mentioned by you. waddie96 ★ (talk) 11:03, 22 December 2024 (UTC)
Here are the relevant portions of RFCST:
  2. Include a brief, neutral statement of or question about the issue in the talk page section, immediately below the {{rfc}} tag
  3. Sign the statement with either ~~~~ (name, time and date) or ~~~~~ (just the time and date). Failing to provide a time and date will cause Legobot to remove your discussion from the pages that notify interested editors of RfCs.
  4. Publish the talk page. Now you're done. Legobot will take care of the rest, including posting the RfC in the proper RfC lists. Whilst Legobot normally runs once an hour, it may take it up to a day to list the RfC, so be patient.
The first link yields three relevant paragraphs:
Keep the RfC statement (and heading) neutrally worded and short. Statements are often phrased as questions, for example: "Should this article say in the lead that John Smith was a contender for the Pulitzer Prize?"
Legobot will copy the markup of your statement (from the end of the {{rfc}} tag through the first timestamp) to the list of active RfCs, if it is sufficiently brief; a long statement will fail to be copied. For technical reasons, statements may not contain tables or complex formatting, although these may be added after the initial statement (i.e., after the first timestamp). ... If the markup of the RfC statement is too long, Legobot may fail to copy it to the RfC list pages, and will not publicise the RfC via the feedback request service.
If you have lots to say on the issue, give and sign a brief statement in the initial description and publish the page, then edit the page again and place additional comments below your first statement and timestamp.
The statement was in no way brief. It also included complex formatting (that table). --Redrose64 🌹 (talk) 11:21, 22 December 2024 (UTC)
Fixed, although I disagree about it being invalid. EF 13:27, 27 December 2024 (UTC)
@EF5 Thank you for your effort. waddie96 ★ (talk) 19:47, 27 December 2024 (UTC)
Support waddie96 ★ (talk) 11:50, 18 December 2024 (UTC)

References

  1. For clarity: The "statement" is the part that is located between the {{rfc}} tag (exclusive) and the first valid timestamp (inclusive), and which is copied by bot to various pages. The statement itself needs to be neutrally worded and brief. After that first date stamp, you should follow normal talk page rules, which allow you to be verbose (within reason) and as non-neutral as you want. ...

Good article reassessment for Noctilucent cloud

Noctilucent cloud 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) 17:52, 18 December 2024 (UTC)

RFC: Rating of the 2005 Birmingham tornado

There is an ongoing RFC to determine which source should be used for the rating of the 2005 Birmingham tornado. You can participate in the discussion here: Talk:2005 Birmingham tornado#Should the article’s infobox indicate EF2/T4 or F3/T5-6?. The Weather Event Writer (Talk Page) 03:25, 20 December 2024 (UTC)

Good article reassessment for Precipitation

Precipitation 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) 02:27, 5 January 2025 (UTC)

Article Names for Natural Disasters

tl;dr: climate change is already increasing the number of weather catastrophes, and I don't believe WP:Disambiguation provides adequate guidance to name articles when e.g. significant fires share a name.

I was directed here from the teahouse as I'm relatively new. There's currently an going conversation on the talk page for the Palisades Fire about whether the 2021 Palisades fire or the 2025 Palisades fire is the WP:PRIMARYTOPIC.

Without getting into that specific conversation, it occurs to me that as climate change fuels more and more weather catastrophes, it will be helpful to have guidance and/or policy on naming articles. I provided a table below that shows California fire names since 2013 that have been used 10 or more times. I'm, of course, aware that not all named fires meet the WP:N guidelines. But as more fires occur, there will simply be more notable fires that share the same name.

My understanding is that this is largely due to how fires are named: often by dispatchers trying to simplify radio traffic for firefighters. I believe that the NWS/NOAA World Meteorological Organization retires a storm name once a named storm becomes significant.

So, some questions (of course feel free to propose your own):

  • If no, which catastrophes need clarification? Fires only? Hurricanes? Snowstorms? Tornadoes? Derechos? Fire Whirls? Other?
  • Are you aware of naming schemes for weather catastrophes in countries outside the US that could cause confusion? What are they? It would be helpful to ensure this is not a US-only discussion.
  • Does the timing of article creation/title selection affect your decision? e.g. there was a 1981 Hurricane Katrina. At what point did the 2005 Hurricane become the WP:PRIMARYTOPIC Hurricane Katrina?

Thanks for taking the time to read this, and I look forward to hearing your thoughts!

California fire names since 2013 that have been used 10 or more times. From this dataset(scroll down to Incident Data) .

Border 31
Creek 24
Canyon 20
Oak 18
Lake 15
Willow 14
Valley 14
Ranch 13
River 12
Coyote 12
Grant 11
Park 11
Soda 10
Point 10
Pine 10
Hill 10
Bear 10

Lastly, as an aside, there was also a 2019 Palisades Fire in CA. Good thing we stopped burning fossil fuels! We really need to stop burning fossil fuels!!! Delectopierre (talk) 05:42, 10 January 2025 (UTC)

Yes. See Lake Fire and Lake Fire (2024). No matter the size of the second fire, the first fire with that name will always take the “main” name and the second one will have the “(YYYY)” after it. EF 13:06, 10 January 2025 (UTC)
Is this spelled out somewhere? The current conversation about renaming the Palisades fire is looking like it will not be following that convention. Delectopierre (talk) 18:35, 10 January 2025 (UTC)
I'm not seeing how current article title policy is inadequate. If two or more distinct events are similarly named, we disambiguate by year, then by month if necessary (e.g. Hurricane Alice (June 1954) and Hurricane Alice (December 1954)), and a set index article is set up (following the same example, List of storms named Alice). If one event is much more significant than others of the same name, we drop the disambiguator, in accordance with WP:PRIMARYTOPIC.
Determining the primary topic is usually a subjective process, though this can be backed up by objective statistics like pageviews, death tolls, or damage totals. Katrina is probably not a good case study since it existed in a time where content policies were less strict - Hurricane Katrina (2005) was moved to Hurricane Katrina on 27 August 2005, two days before landfall in New Orleans. These days, people prefer to wait for things to settle before making an assessment, like at Talk:Typhoon Doksuri#Requested move 15 August 2023. Faster moves do happen though, like with Talk:Hurricane Beryl/Archive 1#Requested move 1 July 2024 where the gap in usage and long-term significance became quickly apparent, making it easy to reach an early decision (and this is also what's happening with the ongoing Palisades Fire). ~ KN2731 {talk · contribs} 14:45, 10 January 2025 (UTC)
I think the example you gave is exactly why it could be helpful to provide guidance. My instinct is to leave the year on both and give it a few months before changing the name.
That wasn’t a popular viewpoint, and of course we make decisions by consensus so I don’t pretend that it has to be my way. But it seems to be pretty subjective, at least to me.
Unfortunately, I’d say it’s fairly likely there’s another significant fire (although hopefully not as significant as the current event) in the palisades in the next ten years. What will we do then? Delectopierre (talk) 18:40, 10 January 2025 (UTC)
The guidance across Misplaced Pages, per WP:COMMONNAME, is that the most significant event of a name should get the primary topic. Significance should have an objective truth to it, like number of fatalities, or acreage. ♫ Hurricanehink (talk) 19:06, 10 January 2025 (UTC)
I strongly support development of a guideline that spells out how to determine that objective truth. like you said fatalities and acreage are important. I think including other metrics would be important as well. For example:
- people evacuated days (eg # of people * number of days evacuated)
- structures destroyed
- housing units destroyed
- economic damage
- firefighters deployed
- firefighting equipment deployed
- economic damage
- changes in how future calamities are handled because of learnings
All that said, I haven’t a clue how to make all of that objective. Delectopierre (talk) 20:01, 10 January 2025 (UTC)
I would support a metric based on some these guidelines (structures destroyed, damage $$), but not others -
  • People evacuated days is a good metric but hard to calculate, because evacuation orders are not issued or withdrawn uniformly and good reporting on # of people affected is often hard to find.
  • Number of personnel or amount of equipment is also tricky because some major fires will have relatively few resources assigned to them if there are a large number of fires burning concurrently (as with this SoCal event).
Penitentes (talk) 20:21, 10 January 2025 (UTC)
Yes, agreed on both points.
I tried to calculate the people-evacuated-days for a few fires in 2020 during the lockdowns...because I had the time. After 3 or 4 days of maddeningly refreshing facebook posts from rural sheriffs and tracking down nixle alerts...I gave up.
Michael Wara expressed some interest in studying this in 2020, which is what inspired my effort, although I'm unsure if he ever did so. Delectopierre (talk) 20:44, 10 January 2025 (UTC)
Commendable effort, I'm a fan of Wara's work. Figuring out evacuation timelines and stats is always my very least favorite part of writing wildfire articles. Penitentes (talk) 20:47, 10 January 2025 (UTC)
Thanks!
Yeah, he's a very smart guy, and it helps that he's so friendly and available, even to the public.
Evacuation timelines are such a mess -- frankly as are evacuation notifications in the real world. Its too bad that the companies that have 'tried' to solve that...haven't. Emergency alerts have gotten better, and some communities have improved their evacuation policies and procedures. But as a whole, its still a giant mess. Delectopierre (talk) 22:34, 10 January 2025 (UTC)

Readability of outbreak list articles

I recently worked on at least starting the process of getting List of tornadoes in the outbreak of March 31 – April 1, 2023 to featured list status. As part of this, I changed the layout of the page (organizing tornadoes by state), however that change was reverted for not being consistent with the standard layout of tornado list articles.

You can see my take on the style here and the original here. I want to get more opinions on whether the new style really is more readable, and whether or not keeping consistency with other project-space articles is more important than readability. Pinging @TornadoInformation12 as they were the one to revert my edit; bringing this to WPWX because this could easily affect other articles. Cheers! Departure– (talk) 20:52, 11 January 2025 (UTC)

Need unified format

We need a unified format for the "Weather of XXXX" articles. For example, Weather of 2008 and Weather of 2009 lists a blurb for each significant weather event (although very incomplete, missing tons of stuff), while Weather of 2024 simply lists Wikilinks, with some info on each type of disaster at the beginning. Thoughts? Wildfireupdateman :) (talk) 18:15, 15 January 2025 (UTC)

Also note that I support the 2008 and 2009 format. Wildfireupdateman :) (talk) 18:15, 15 January 2025 (UTC)
Weather of 2021 & Weather of 2022 is the best format in my opinion. The Weather Event Writer (Talk Page) 18:20, 15 January 2025 (UTC)
Those seem like the intermediate between the 2008 format and the 2024 format. I could work with that! Wildfireupdateman :) (talk) 18:22, 15 January 2025 (UTC)
I've begun a rewrite in userspace. Wildfireupdateman :) (talk) 21:06, 15 January 2025 (UTC)
Yea, when the Weather of 2008 was originally written, it was called "Global storm activity of 2008", which was simplified to "Weather of 2008". The overarching articles should include a summary of all of the different weather types, and mention the deadliest events, I think that's a good way of making the article useful. ♫ Hurricanehink (talk) 21:15, 15 January 2025 (UTC)
Elijah and I like the 2021 format like you mentioned, so I'm rewriting it. It looks like it's gonna be a lot of work, as 2008 isn't the only year that has a different format/issues(e.g. somehow Elie 2007 is not mentioned). Wildfireupdateman :) (talk) 21:19, 15 January 2025 (UTC)
Most "Weather of" articles need a lot of work, so I appreciate you doing that. ♫ Hurricanehink (talk) 21:21, 15 January 2025 (UTC)

Cool vs Cold

In connection with this discussion, I'd like to know whether there is any guideline to distinguish what can be called cold from what is just cool. I assumed that a Spanish town where 4 months per year have mean daily minima below freezing point could be described as having cold winters (rather than very cold or freezingly cold), but there is no consensus. For comparison, I have checked a couple of random articles; for example the one about Paris states: In winter, ... days are cool, and nights are cold but generally above freezing... Furthermore, it seems that it is correct to define winters in the town as cold for Spain, which I would understand if it was a low-latitude country such as Malaysia or Panama, but not for Spain; this makes me think that there is some kind of Euro-centric or Northern-centric bias in how climates in the world are described. Jotamar (talk) 22:32, 15 January 2025 (UTC)

Categories: