Knowledge (XXG) talk:WikiProject Tropical cyclones/Archive 38

2030:(except with the exact winds). I will switch the winds in the tables to a km/h (mph) format this evening and make a mini Australian scale (just like the mini SSHWS) to go along with the tables. I will fill in the first few months tomorrow. Any named storm at category 1 strength will be mentioned in the text as will the few significant TDs. All other TDs will have no mention in the text, but appear in the table. There shall not be any monthly timelines to save space unless decided otherwise by consensus. The yearly timeline has been fixed... I made it somewhat taller and added 50% more cyclones to each column in order to fix the overlapping names and bars. It now looks great and shows an accurate picture of the cyclone activity throughout the year without the issues of having 10 storms per column. I would appreciate it if someone could add some text to go alongside that table I made with the number of cyclones. The table contains TDs, C1s, C2s, C3s, C4s, and C5s. It is based upon the timeline. Let me know how that sounds. 1208:. No individual systems are listed in the table. For the systems section, Im only adding a brief, much abbreviated segment about each storm of notability. The segment is much smaller than what would appear in any season article. The main content is saved for the season article/storm article. Every storm that I mentioned caused many deaths, damages, and/or had a large impact with the exception of Celia which simply set records. I didn't really mention any fish storms. However, one sentence isn't enough to cover a system of notability. I would rather have nothing at all about any of the systems than do a single sentence saying it was notable for this. If we were to remove the content related to the 2010 systems, we would need a consensus to do so because otherwise it is vandalism. 1323:

it by month. To be honest, if someone were looking for storms that impacted their area in a specific year, they would search 'Hurricanes in the Atlantic Ocean in 2009' or 'Hurricanes in the Pacific in 2012' which would take them to a season article. We could talk about how many systems formed in the month total and then say how many formed in each basin (I don't know exactly how detailed we should go here). We could have a section highlighting the global tropical cyclone activity. That would include what areas had high, above average, average, below average, and low activity. We could possibly have an image displaying that too.

1574:

sub-sections for every storm, and for notable storms, those sub-sections function essentially as the lead of individual storm articles. Think of it the same way for a global tropical cyclone summary. You're just giving the barest taste of each storm. I don't think individual tropical depressions should be mentioned in prose unless they were destructive or deadly, but they should still be in the table. I'm torn on short-lived fish storms, like Gaston 2010, but I think all named storms should at least be mentioned. It's a good metric for comparing activity by years. Eventually we can have an article for

1632:. I would personally prefer to see the Australian scale used on the timeline image as the SSHWS since it's only officially used in the Atlantic and Northern Pacific to the east of the dateline. Yes you can argue that the Australian scale is only officially used in the Australian and SPAC basins (90E-120W), but the winds supplied by the JMA (WPAC) and Reunion (SWIO) can be applied to it without resorting to converting any winds or using unofficial windspeeds which is why i think it is better for an article like this. 2305:... I know some people felt the article was jumping the gun/rushed, but we have a decent article developed at this point which required several people working on it. As it currently stands, it will be primarily a meteorological history article as there is a lot of content for this system since it has been active for 9 days. Also, I have a question about the storm... As it appears Hector will cross the international date line on Monday, would it simply become Typhoon Hector with the JMA wind classification? 3176:, it is difficult to maintain the season articles well as two or three tropical cyclones often develop simultaneously in the Northwest Pacific Ocean. This situation always results in outdated information that the efforts from editors to maintain become useless, completely discouraging editors to participate. It also leaves sections blank as editors have no time to write seriously at all. Moreover, outdated information could mislead readers, which may cause a potential life-threatening risk to them. 1715:, I had the table as "Tropical cyclones", "Named storms", and "≥64 knots" and convert it in a special note for the laymen. All basins have a special designation for storms of 64 kt winds, with varying scales and categories above that strength. Likewise, there is uniformity for when TC's are named (sustained winds of 35 knots), with some exceptions. In the monthly table for each basin, just remove the "retired" names category, and change "Notes" to "References". ♫ 3503:, it implies that the system was named by an unofficial agency in the basin. In WPAC, PAGASA names are put into parentheses as the agency is unofficial. We can't have names in parentheses mean two different things. It needs to have one set meaning. Otherwise, it is confusing for unfamiliar editors and readers. My recommendation is to have a note in the infobox or something above the text stating it was named in another basin if the clarification is needed. 31: 559:, I'd recommend if for instance we could not find an image that is around its peak strength time, then I'd suggest to use an image that is literally a Category below its peak. For example, no images found when the storm is at Cat4 intensity, so instead use an image that is at Cat3. Moreover, I don't know if it's just me, but I'd prefer the storm to be in the center of the image as it looks more neat and tidy. 2486: 1793:

well. Personally, I think the SSHWS is better for the timeline because it is highlights the strength of the storms with winds higher than 157 mph. If we were to do the Australian scale, a lot more storms would show up as C5 which would make them a lot less rare. Additionally, a lot of other storms would be bumped up to higher categories which would make them appear to be stronger when they really aren't.

3413: 3354: 3105: 3046: 2795: 3169:

cyclone, and South Pacific cyclone season articles. As the template is implemented to them when a tropical cyclone is active, those editors, who have already been extremely few comparing to editors of Atlantic/Pacific hurricane seasons, must spend more time on maintaining current information that is soon to be replaced and removed in the end.

520:

single-band imagery on stock backgrounds. Stock backgrounds may not be the most photographically up to par but they can provide clear geographic context (viz encyclopedic value), which on an encyclopedia should be given higher precedence over aesthetics in my opinion. Day-night band images are included in the envelope of visible imagery.

2773:. The issue is about whether or not individual storms will be in the see also section of the article. As we have no official consensus on this matter, the outcome of this could have a ripple effect and result in the removal of individual storms from EVERY see also section of cyclone articles if the argument passes. 750:- I really don't think it matters what type of imagery is used for peak (whether it's IR or vis), if the storm's peak was at night IR should be able to be used as it shows the storm at peak. I've also been seeing lots of ugly Vis crops lately and I think that's a problem. Regardless, I support this idea. - 2558:

Forever since I am editing hurricane season articles – what, in case of the German WP, would be 2006 – I am wondering for which case we defined "GP" in plain red, and it is still in, for example in this year's PHS article. I remember that in the German WP we used it once to mark a storm which still

1322:

I think it would be better to list it by month than by basin. In my opinion, a chronological order would be better as this is a global summary. It shouldn't be organized by each basin as that is what the season articles are for. When talking about something happening globally, it is much easier to do

1305:

Agreed, and to echo TheAustinMan, compare the summary with a season article. Come to think of it, should the article be by month, or by basin? If it's by basin, you can literally copy the lead from those season articles (until you come up with something flashier). That could be of more service to the

1188:

My problem is that it’s too long. Make it as concise as possible. No need to mention fish storms when the table already lists status, deaths, damage, and name. Make the article 50 kb, otherwise it doesn’t serve a purpose. One sentence for every storm of note, generally every named storm that affected

673:

IR in any way regardless of peak", I now have some doubts over this. Firstly, IR easily trumps VIS images if the storm in question has a significantly improved intensity or structure. Secondly, IR images are satellite images too, they provide imagery of overnight passes through infrared. As a result,

3557:

could work as a solution to the issue... could be added to season storm sections so that way people aren't assuming the system was assigned the name in that basin. It will still let people know that they are the same system without causing any confusion in regards to the naming of the system. We can

3517:

The way we apply names to systems that are named after they have moved out of their original basin is a tricky one, especially since the BoM/PNG are technically official for the SPAC and visa versa for Nadi/Wellington. I would personally prefer to keep the names as it allows the reader to be able to

2533:

It's worth remembering that we update track maps and article text (among many other things) after post-season reanalysis, so that shouldn't be a huge issue. I'm just not sure the charts are of broad enough interest to be useful for general readership. As a weather editor I like it, but it might just

2519:

For your graph, I really have no preference either way right now. I don't have much to do with that article. Others may be more passionate as to whether or not it should be included. Be warned, it will be meaningless if the tropical cyclone report makes changes. You probably should make redirects to

1815:

I disagree that a lot more systems would show up as Category 5 if we used the AUS scale, in fact for 2010, I can only see one system as a Cat 5 in the Western Pacific that would be classified as a Cat 5, which is after all the main region for TC formation. Also I feel that most of the basins provide

1696:

I do not see why we should use the SSHWS when it is only officially used by RSMC's in 2 main basins and can only be applied to 2 main basins, when we have a scale that the majority of TC's can use without having to adapt their official windspeeds or use unofficial windspeeds from the JTWC which most

1336:

True, a global monthly track map would be nice, but more work for the track map editors. Ok, so if it was monthly, I’d still prefer minimal info for each storm (1-2 sentences max), listed individually. It would be interesting to see the longest period of time each year without any tropical cyclones,

1286:

I agree with the general points outlined by Hurricanehink. The monthly recap should exercise brevity. Not all storms need to be mentioned in prose; that's for the individual season articles. Even the most impactful systems can be noted in 1–2 sentences. In my opinion the article should be treated as

1203:

Im sorry you feel it is long, but it really isn't that long compared to many other pages. Even quite a few season articles are much larger. Size really has nothing to do with serving its purpose. Once fully developed, I would imagine an article like this would be between 90 and 100k bytes once it is

1034:

article. It was never properly developed back in 2010 and 2011 when it was created, but it is definitely worth exploring. I have been adding content to it over the last few days. It would be nice to discuss the development here. I am interested to see what content everyone would want in the article.

287:

If no satellite imagery can be found at or near peak intensity, satellite imagery at some point of significance (such as landfall, closest approach to land) or meteorological significance (secondary peak) should be used, following the order of precedence above. Satellite imagery from other points in

131:

over which images should be used as the image of choice in storm infoboxes over the past few months, I am proposing the following protocol that may aid in a more objective assessment of what image should be used. The following users have been pinged as they have been frequently involved with editing

2720:

I agree it's worth developing them, and global atmospheric conditions (such as El Niño or volcanic winter) would be mentioned here. Having a global article for tropical cyclone activity can help reference stats such as the number of storms per year, named storms per year, damage/deaths. It's a good

2696:

Personally I strongly feel that it is worth developing them as we would be able to cover bits and bobs that the season articles cannot. As for concerns over sourcing, I personally believe that they are unfounded as most of the RSMC's produce reports on the seasons that go into details over why a TC

2464:

1) It isn't all incorrect but is still in the development stages. 2) It uses the Aussie scale rather than the SSHWS, since it can be applied using official data rather than unofficial data. 3) It should in theory when its developed further contain more information about what was going on during the

1924:

Just on first mention in the prose, when applicable. I'd rather see the lead covered with global stats. As of right now, the timeline graph in the article is a mess. At minimum, the timeline graph itself probably should be made taller, if possible, so the text on the table is illegible, but in your

1221:

It isn’t vandalism if it’s methodical. I stand by the article being too long, and I don’t buy that you cant summarize in a single sentence. For most of these important storms, there is a season article in the basin, a storm sub-article, and maybe even effects articles. A storm as big as Katrina can

1165:

Finally, I made a 2010 Storm Effects section that has a table with the columns 'Season Name', Areas Affected', 'Damages (USD)', and 'Deaths'. Rather than having something with individual storms in it, I felt it would be better to simply have the totals from each season in the table. The seasons are

733:

That creates a problem with storms that undergo explosive intensification. For example, you could have a tropical cyclone ranking as a Category 1 hurricane on a day pass, but overnight it undergoes explosive intensification into a Category 3 hurricane, and it then quickly weakens the following day.

3282:

Meow, you make a really good point. I think the bigger issue is that users are spending more time updating the infobox than writing content. I’m sure much of the infobox can be automated once it gets regular advisories. I know the NHC has a fixed link for active storms. Do other basins have a link

2911:

Yes, I think if a reliable source has an independent reanalysis, we should include it, but for official purposes (infobox and discussing peak intensity in the MH), the official RSMC data should be included. Say something like "Although RSMC X estimated peak winds of Y, an independent analysis by Z

2029:

Well... I am going to do work tomorrow on the article now that I am invigorated once again. I needed a couple days reprieve as I was getting burned out on this after many hours of constant work. The storm intensity on the tables will be based on the Australian scale so it is just like the timeline

2850:

I have a question that I think I know the answer to but is worth revisiting to see where the land lies. If we have someone do a reanalysis on a system by an independent author, a good few years after a system existed and was warned on and BT'd by the warning centres. Whose data do we go with? The

2701:

on an annual basis with a slight bias towards their territories. I would also hope that we wouldn't be regurgitate everything from the seasonal summaries and would help our readers understand why TC's developed, where they developed or not and why not etc. I would also hope that we could use news

1792:

How about we have a yearly timeline in the summary section and then have a blown up version of each month in the monthly sections? I think we should keep the timeline for the whole year since it shows the differences in activity throughout the year. We could do a table of storms for each month as

506:

Items 1 and 3 show that the proposer does not really understand how to choose better images for tropical cyclones. For Item 1, images from ISS are unique but not very clear at all, so they are unsuitable for the box. For Item 3, we should not encourge people using a stock background which means a

3498:

I would like to propose either changing or eliminating a practice that has been going on with SHEM articles for some time. In SHEM, people have been adding parentheses with a name to tropical disturbances and depressions that formed in a basin and were named in another. This practice is entirely

3298:

JMA does provide advisories with a fixed format. Advisories from others are not that fixed, especially IMD. For hurricane season articles, the template is okay to maintain, but it really devours too much time for editors of other basins. In the typhoon season article, many people provide invalid

1856:

The same can be said for using SSHWS over in basins where the SSHWS is not officially used, especially if you take the JTWC estimates over the RSMC for the basin. It is also worth noting that the Aus scale can be directly applied to systems in 4 out of the 7 basins where as the SSHWS can only be

1646:

Only issue with that is multiple scales being used would be confusing for readers. I have noticed with a lot of cyclones in other basins, a SSHWS classification is shown below the official one for the basin. If we add the Australian scale, we would need to add all of them. To be honest, it would

1155:

In addition to that timeline, I made a 2010 systems section that contains a paragraph discussing every system of notability around the world (based on damages, deaths, impact, and/or records set). The paragraph about a system is a much abbreviated meteorological history along with an abbreviated

2069:

After going through the list of page ratings, I was quite alarmed to see 840 pages or 19.3% of our content either at or below start class. As most of the current task forces work on creating new articles and improving higher priority articles, I would like to propose the creation of the Article

1894:

Just to clarify one thing, SSHWS has no formal use in the SHEM so there is no point in using them when it comes to prose. Just be sure to be clear what scale you are using (for instance, clarify you're referring to the SSHWS for an ATL storm and AUS scale for an SPAC storm), when necessary, and

519:

Point 1 does restrict low Earth orbit photography to those that only show the storm completely, but understandably they are at a rather oblique angle and I would be fine with removing them from the order of precedence. Item 3 also covers some material from NESDIS which has historically overlaid

3606:

I'd say just remove the parentheses. It's the same storm, so you could just call it Tropical Low Bouchra. BoM and TCWC Jakarta are certain to recognize the name because if the storm were to move into the Australian region it would retain the name. The current (11/12 18z) GFS run re-strengthens

3168:

Although the template is suitable for Atlantic/Pacific hurricane season articles, it brings troubles to other season articles. The primary reason is simple: We do not have enough editors to maintain Pacific typhoon, North Indian Ocean cyclone, South-West Indian Ocean cyclone, Australian region

2246:

Since technically I can't self-assess and I think this can allow some younger editors to familiarize thereselves with my work and what to do past WPTC articles in general, I'm gonna make a list of articles that I've written recently I'm going through that need to have a {{WikiProject Weather |

1838:

198 km/h is category 5... Danielle, Earl, Igor, Julia, and Karl would become Category 5 for the Atlantic. Karl is a category 3! The scale would shift for storms in other categories too. Category 2s could become Cat 4s and Cat 1s could become cat 2 or cat 3. Also, weak TSs would become tropical

1573:

Same table for the season article, but separated by month, and including every storm worldwide. At least, that's how I think it should go, and I am open to outside opinion. I just think it would be good to model it as closely to the current format of articles that we have. Season articles have

1145:

I have already added a summary section which contains a timeline with EVERY cyclone formed during the 2010 year (excludes storms formed in 2009 and 2011). Also in that section is a table that shows the number of TDs, TSs, C1s, C2s, C3s, C4s, and C5s (other classifications were converted to the

1291:

is a venue to synthesize information across basins and broach global weather patterns that aren't as applicable on basin pages to present them collectively, so picking and choosing storms already presented in similar formats on their seasonal pages should not be the article's focus.

370:- I think it's a great idea! However, I would like to make a change. If the intensity difference between a VIS image and an IR image is great, and/or the structure is much better in IR, as such is the case for storms like Wilma 2005, I would put the IR images as the higher priority. 1125:

Do the same for every month, have a section for retirements, make sure everything is referenced. It could be a nicely developed article without being too long (leave the content for the season article), and does a good job summarizing global tropical cyclone activity. Thoughts? ♫

3204:. I'd rather cut down on the information in the infobox; in my humble opinion, position vectors are excessive information (not to mention being nontrivial to manually calculate). The long-term solution is to use a bot, which has been a wish of WPTC for something like a decade.-- 1075:, so you don't have to mention deaths or damage in prose (unless relevant). Write out (briefly) any storms that caused deaths (where they passed by), damage. Summarize in each basin, if possible. For example - "In the Atlantic basin, a record 7 named storms developed, tied with 887:), which follows the protocol suggested here. However, I think the original image was better (which is more defined and shows Florida). This policy doesn't take into consideration images where we might have a better visible image within a few hours of the peak. Can we clarify 3571:

I don’t think we should make the rules more complicated. Brackets could be enough to indicate that name is not officially recognised in the basin. Besides, some officially named systems are downgraded to tropical lows in post-analysis, but they should not be added with

1494:

True, but you don't need to mention the minimum pressure and the exact dates, since each month will have a table of storms, correct? Also, since you're going worldwide, you have to go with the RSMC intensity, not what JTWC says. Here's a two sentence version of Edzani:

2953:. There have been ramblings on Twitter and other avenues from NWS meteorologists who believe the center line unnecessarily contributes to certainty in track when uncertainty almost always exists, and I don't believe Knowledge (XXG) should be adding to that confusion. 3216:

What is your short-term solution? We still have to manually update everything which gives us high pressure to maintain. You should give us some solid solutions before a simple oppose. That is why I propose a temporal suspension as we currently do not have any proper

850:

Since this proposal is still in discussion, what's been written up here does not constitute project policy at the moment and should not be currently used as the rationale for changing images. In the meantime, if you are changing an image please consider using the

3591:

This wouldn't really complicate things. All the template would do is put it right in front of them that is was named elsewhere and have the link to the other season. If we do that, it should clear up confusion easily. We wouldn't have to change the parentheses.

2188:

Hi all, just wondering how I can become a member of this project. I honestly find it to be a little bit insulting that after nine years of dedication and hard work that I have put into articles in this domain, I still haven't been invited to join this project.

3324:

blurbs, and I'd like to try to tie up all the loose ends at once by presenting a list of examples tomorrow and asking for feedback. I'm rewriting a lot of these so that people can't tell which articles they come from ... but one of my examples is "The

1757:

My apologies. Perhaps have the timeline for each month, and just have the yearly table? I think some sort of demonstration for the monthly activity would be useful for the readers, beyond just a textual summary. As for the intensity in the timeline,

1543:

I figured you'd have a giant table somewhere in the article. It would be more useful having that table in each month than to have it at the end of the article. This way, you can see stats like death and damage without having to have it in prose. ♫

2582:

we didn't do it either. We usually indicate it in the "Storm names" section, which I think is rather redundant and should be merged with a "season summary" section (where the timeline is usually located). But that's for a different discussion. ♫

165:" articles. However, where possible, images without latitude-longitude grids are preferred. In addition, if a satellite image used for an infobox has labels, those labels should be clear enough to be at least somewhat discernible in a thumbnail. 802:: Finally a protocool. I edit and translate TC articles for Spanish Knowledge (XXG) and occassionally upload TC images. My question is: should be formalize tropical cyclone images naming on this proposal or was it established before? --🌀 2721:

way to cross-reference between the season articles and individual storm articles, particularly in regards to death and damage totals. The yearly article would be a parent article to all of the seasonal basin articles, along the lines of

193:, for example. Although these images have highest precedence, they need to feature the storm clearly in full or nearly in full. However, the images used should be free of spacecraft components like modules or structural components. 3469: 1742:

Firstly, we were talking about the scale used on the timeline. Secondly, we shouldn't have a monthly table for each basin. That would be too many tables and very odd. I might as well remove the intensity column from the table.

3187:

section should also be simplified to the links of meteorological agencies only, so readers can still get the updates immediately. These two proposals mentioned above should be effective until there are enough editors in the

3335:", which comes right out of the article. (I actually have no idea how people will vote on this one ... it's fine in a Featured Article, I think.) If there are any objections, I'll remove this example from my list. - Dank ( 2043:

I must apologize... I had some stuff come up that prevented me from doing any editing on this page. I made the template for the Australian scale, but was unable to get any further. I will work on this page some tomorrow.

2070:

Improvement task force. The purpose of this task force would be to improve all lowly rated articles (as possible) that have been neglected due to age or others getting precedent and get them to a higher quality rating.

1306:

readers. If they're looking for a storm that affected their area in a particular year, they're more likely to know the basin (general geography) than the exact month (especially as many storms existed in two months). ♫

1878:

Fine... I will convert them right now and end any debate over which we will use for the 2010 timeline. However, we still have the issue of whether or not we will have a blown up version of the timeline for each month.

1857:

applied to 2 out of the 7 basins. Also Danielle, Earl and Karl would just be cat 4s on the Aus scale since we would not directly apply the windspeeds that NHC/IMD gives without converting them using WMO standards.

2424:

This was created after I noticed that I was unable to PM non-registered users on IRC (making stuff like fixing GAN comments more difficult). Hopefully this helps revive the project somewhat. Come on in everyone!

1712: 1682:

are already adapted to SSHWS. Almost all other articles are adapted. I just don't see why it is necessary to go through the pain and suffering of changing every single item on that table to the Australian scale.

1575: 3532:

Could we change the system to be less confusing? I'm not saying to remove all mention of it, just do something different than the name in parentheses so people don't assume it was named by an unofficial agency.

1363:

What storms do you want to be mentioned? I obviously know that most of the TDs were insignificant, but some were of significance. Were you thinking of all the ones that impacted land, all named storms, or both?

288:

a storm's lifetime can be used, so long as they are still somewhat representative of the storm (for example, an image of a super typhoon as a tropical depression should probably not be used). Otherwise, either

1156:

statement about the impact the storm had. These paragraphs are generally 2-3k bytes with citations which is pretty good considering some of them have articles over 100k bytes that go into much greater detail.

1980: 2357:

Good in coverage of the areas primarily impacted by Beryl (Lesser Antilles, Puerto Rico, Dominican Republic), but mentions nothing about other listed areas such as the Bahamas, Bermuda, and Atlantic Canada.

162: 3499:

incorrect and should not have even happened to begin with. Firstly, the lows and TDs were never assigned that name before or during their existence in that basin. Also, by having a title like the one seen

2381:

Article is pretty understandable. There is no over usage of technical terms that would lead to confusion. Where there are technical terms, they are internally linked so one could find out what it means.

2133:

Todaym Subtropical Storm Debby formed 38.9 N and I was wandering " Is that the record?" So, my question is what (sub)tropical cyclone formed the farthest north? If so, what latitude did it form at?

1660:

I'm not suggesting to use multiple scales, I'm proposing to use just the Australian scale for the reasons I outlined above. SSHWS is only offically used in two basins and we have to say that its

2684:(as I'm not sure long-term synoptic/climatic summaries are produced in other basins), while the "global effects" sections would be a nightmare to maintain at an adequate level of referencing. 1911:

Should we simply add which basins use what scales in the introduction? Elsewhere? We will have the season articles linked in the prose. Also, you feel we should remove the timeline altogether?

2949:

Unless there is disagreement within the project, I would suggest that from now on, when uploading the NHC's forecast track for ongoing tropical cyclones, we leave the center line track turned

94: 86: 81: 69: 64: 59: 980:

The folks at ITN/C don't like incomplete articles (especially the fact it doesn't even have impact in the article), so you should've worked on it before sending it to be an candidate.

2084:

Interesting proposal but I would note that some of the 20% would be season articles which may need splitting off before being improved. Especially in the Southern Hemisphere basins.

2605:

I figured we needed to have a discussion here about what content should be included in yearly tropical cyclone articles. As it stands right now, we have the following structure...

855:

to explain reasons for changing those images. There have been way too many unexplained image changes without any edit summaries, which just makes fertile grounds for edit warring.

177:. "Near peak intensity" refers to any point where a storm has winds within 5 percent of peak intensity (in knots). The following indicates the order of precedence for these images. 2741:

We simply need to get people working on this and it won't take long at all to get individual articles filled out. I do like the idea of having an article with the all-time stats.

3283:

that automatically refreshes? If so, then creating the bot should be easy. If the links to the advisories change every time, then I don’t think a bot would work for that basin.

1778:

My suggestion was to use the Australian scale rather than SSHWS, since we are using RSMC intensity in the article and most TC's can be rated on it without resorting to JTWC.

1679: 1504: 1442: 1003:

Don't worry about the ITN/C people. I have some experience there. I will make sure it gets a fair hearing. Can you help me get the article to meet your standards here.---

2205: 674:

I would propose to make an exception to this rule. When a storm peaks overnight, and/or its structure is signficiantly improved overnight, the IR image holds priority.

257:

This includes any grayscale visible or infrared imagery that has been superimposed on a Blue Marble or similar basemap. Images of this variety may also be generated by

2166:

In December 1975, a subtropical storm formed at 41.5N while it was diving southward. Debby isn’t that unusual. Plus, it’s track will likely be extended back by a day.

2990:

Maybe we should just upload the 34 knot wind speed probabilities? There are problems with the forecast track as well given it deson't take into account storm size.

924:

Leaving this message to stop the bot from archiving this since it's been nearly 12 days since the last comment but the discussion here doesn't appear to be over. ~

47: 17: 1603:

Are we just going to use the Saffir Simpson scale for all the storms in the table? I think it would be very time consuming and confusing to have multiple scales.

1530:

Yeah, I see what you mean. However, I don't really see the need for each month to have a table of storms. If you feel it is needed, please elaborate as to why.

538:- finally someone is listing out all the order of importance of the images used on tropical cyclone articles. Now all is clear and no more pointless edit wars! 3500: 1982: 1500: 1438: 159:

High-resolution satellite images with political borders or nearby landmasses visible are preferred over the same images without borders or landmasses visible

1248:

I'm going to ask a few more people in the project before going ahead with any big changes like that. Changes will probably be made later today or tomorrow.

2148:

It looks like an excessive statistic to me, it can be mentioned in the article though if there is some third party coverage that isn't just a tweet from a

3607:

Bouchra to a TC as it returns to the Australian region. If that plays out, they won't rename it, and this instance of the issue would be resolved anyway.

298:

If there are no image of the storm or its impacts, its track should be used as the infobox image. This will typically be track images generated using the

1895:

please wikilink the relevant scales on their first instance. Honestly, I have reservations that a timeline graph entirely, largely due to lack of space.

174: 2965: 701: 583:

This person is new to the project and has recently been uploading beautiful images. So this is to let that person know on this discussion. Along with

3263:

You were not providing any proper solution at all. The only solution is not to use the template until that so-called bot is officially introduced.--

2698: 2000:

At first glance, this looks still quite messy. Maybe just do two timeline graphs? One for the first six months and one for the second sixth months?

468:

but this is the first good faith proposal to at least give some order to the arguement-less image wars I see on my watchlist like all the time now.

173:

Where possible, the picture of the storm used should be a satellite image at or near its official peak intensity as determined by their respective

1234:

Essentially, leave the details for the other article, and make this one a worldwide summary. The more info you have, the less effective it is.

2520:

the discussion on article talk pages more clear in the future because I thought it was spam before asking for a second opinion on the matter.

1035:

I would appreciate it if others could help with expanding the article. If this article goes well, we can make similar articles in the future.

1010: 969: 2866:

We should always follow RSMCs and TCWCs for the official values but we could mention something else in an article if that is trustworthy.--

2534:

be an overly technical data dump to everyone outside that tiny subset. I'd definitely like to solicit some input from non-weather people. –

3373: 2222:

Oh, just add your name to the bottom. It's an informal thing so there probably wasn't an incentive to invite an already recognized editor.

1839:

depressions/tropical lows which conflicts completely with the status of the storm. That is why I don't like the idea of using this scale.

3432: 3065: 1472:

Some people are also saying 2-3 sentences. 3 shouldn't be that big of a deal though. It is much shorter than what was previously there.

884: 464:

seven or eight years ago I started staying out of image wars on grounds that any argument for or against a certain type of imagine was

169:; images that show more of the storm and its surroundings are preferred over those that are more zoomed-in and consequently show less. 3180: 3157: 1816:

a divider at 50 kts, which i feel is nicer than having one at 115 kts, since 50 kts is the divider between gale and storm force winds.

650:

with the caveat that Jasper Deng had raised, that visible imagery should be preferred over IR imagery regardless of time from peak. —

2997: 2432: 2286: 2231: 2009: 1934: 1904: 477: 1272:

I just wiped the whole section and will start over. Im not even going to try and work with shortening any of the existing content.

302:, but may also be unofficial tracks from studies such as those associated with tropical cyclones outside official track databases. 3613: 117: 2814: 3365: 3346: 2672:

Are these articles even a good idea? I am concerned that "global atmospheric and hydrological conditions" would violate either

3424: 3405: 3327: 3288: 3234: 3057: 3038: 2213: 2171: 2016:

The big timeline doesn't even look messy anymore. None of the bars or names are touching and it can be easily distinguished.

1463: 1354: 1239: 1194: 1080: 1076: 1072: 336: 2806: 2787: 2961: 1112: 1084: 697: 2316:

Ello Figfires, thx for the invite earlier, and yes it would be renamed typhoon hector. One example of this happening is

1386:

Might as well mention every named storm, since that's a useful metric for comparing global season activity, plus global

1229:

became the costliest United States hurricane when it struck southern Florida, Louisiana, and Mississippi in August 2005.

1116: 1049:

Yea, I'm wondering, what would be an ideal structure for this type of article? It should be similar to a season article:

936: 305:

If there is no picture of the storm or its impacts, a relevant map of an affected area can be used as the infobox image.

3618: 3600: 3579: 3566: 3541: 3527: 3511: 3488: 3439: 3420: 3380: 3361: 3340: 3306: 3292: 3270: 3258: 3238: 3224: 3211: 3195: 3131: 3112: 3072: 3053: 3032: 2999: 2985: 2970: 2939: 2923: 2901: 2887: 2873: 2860: 2821: 2802: 2781: 2749: 2736: 2715: 2691: 2666: 2594: 2568: 2545: 2528: 2506: 2474: 2458: 2434: 2418: 2393: 2334: 2313: 2288: 2233: 2217: 2198: 2175: 2161: 2142: 2120: 2106: 2093: 2078: 2052: 2038: 2024: 2011: 1994: 1968: 1936: 1919: 1906: 1887: 1866: 1847: 1825: 1801: 1787: 1773: 1751: 1726: 1706: 1691: 1669: 1655: 1641: 1611: 1589: 1568: 1555: 1538: 1522: 1480: 1467: 1453: 1417: 1401: 1372: 1358: 1331: 1317: 1300: 1280: 1256: 1243: 1216: 1198: 1183: 1137: 1043: 1015: 991: 974: 941: 916: 902: 863: 842: 828: 792: 759: 738: 724: 706: 678: 665: 640: 602: 570: 547: 528: 514: 498: 479: 454: 431: 391: 374: 360: 340: 317: 3476:(FAC) so that source reviews would need to occur prior to any other reviews for FAC. Your comments are appreciated. -- 557:("If satellite imagery cannot be found, surface analyses of the system at or near peak or its impacts should be used") 190: 3455: 3396: 3147: 3088: 2878:

I second Meow's comment. The primary info we show will always be RSMC/TCWC but we can mention reanalyses in prose. ~

2837: 1175:

That was what I did. I don't know how you feel about that, but that was my idea for initial development of the page.

1119:

caused extensive flooding in Jamaica. The other storms – Gaston and Lisa – were short-lived and did not affect land.

2722: 2637:(seasonal effects for X year added together for a worldwide total & discussion of TC impacts in a global view) 2138: 1499:

Very Intense Tropical Cyclone Edzani – the first cyclone to form worldwide in 2010 – developed on January 1 in the

1425:"Edzani was the first cyclone to form worldwide in 2010. Edzani was a powerful cyclone, reaching category 4 on the 1387: 295:

If satellite imagery cannot be found, surface analyses of the system at or near peak or its impacts should be used.

107: 38: 3332: 3284: 3230: 2655: 2441: 2413: 2209: 2204:

You’re already a member of the project! Even if you aren’t one officially :) All you have to do is add your name

2167: 1459: 1350: 1288: 1235: 1190: 1031: 1024: 1004: 986: 963: 755: 449: 332: 240: 3431:. This page is of interest to this WikiProject and interested members may want to participate in the discussion 3372:. This page is of interest to this WikiProject and interested members may want to participate in the discussion 3123:. This page is of interest to this WikiProject and interested members may want to participate in the discussion 3064:. This page is of interest to this WikiProject and interested members may want to participate in the discussion 2813:. This page is of interest to this WikiProject and interested members may want to participate in the discussion 1511:

This is short and sweet. Streamline your sentence writing, and try and sum it up in two sentences if you can. ♫

1426: 3124: 2954: 2157: 1955: 690: 289: 3558:

still have the name in parentheses if you want. Just want this set apart from everything else to clear it up.

833:

I dont think the naming of images has ever been formalised and it could be an interesting discussion to have.

629:

This is the software I use for satellite image production. So where can I share it? On this page, or others?

3428: 3061: 2981: 2918: 2883: 2770: 2731: 2589: 2494: 2302: 2295: 1768: 1721: 1584: 1550: 1517: 1396: 1312: 1132: 955: 948: 907:

We have to remember though Hink that peak intensity isn't at 12z when the NHC/JMA/JTWC issue their advisory.

897: 878: 387: 355: 3554: 3017: 2543: 2330: 1675: 788: 2928:

Like Hurricanehink said, use the official RSMC data, and notice any discrepancies that can be sourced to

637: 409: 3369: 3255: 3208: 3021: 2994: 2502: 2429: 2281: 2226: 2194: 2134: 2004: 1929: 1899: 1104: 1096: 599: 567: 495: 472: 3314: 1507:

since 2005, reaching 10 minute sustained winds of 220 km/h (140 mph), before dissipating on January 19.

128: 775:. I support it because I always want to have a clean peak intensity regardless of any reasons, but as 382:– Desperately needed to stop the silly image editing wars. Points are clear and easy to understand. ~ 3608: 3523: 2897: 2856: 2810: 2711: 2654:

I would like your opinion on what should be in articles of this type. You may find an example of one

2470: 2408: 2261: 2256: 2116: 2089: 1862: 1821: 1783: 1702: 1665: 1637: 998: 981: 912: 838: 751: 444: 427: 147: 3320:

Hi guys. There have been some questions recently about what does and doesn't count as redundancy in

1287:

an overview of tropical cyclone activity in 2010 rather than a highlight reel of individual storms.

465: 154:

In general, consider whether or not the image used is representative of the storm and its impacts.

3116: 3097: 2564: 2268: 2153: 507:

fake background. The proposer also misses images from the day-night band that I feel very pitiful.

299: 2977: 2913: 2879: 2763: 2726: 2629:(monthly break down of TCs and impacts worldwide with notable TCs getting a brief prose mention) 2584: 1763: 1716: 1619: 1579: 1545: 1512: 1391: 1307: 1127: 892: 874: 820: 735: 675: 383: 371: 350: 139: 2111:

Yeah I kinda meant season articles into storm articles. Always happy to see work on SHEM though.

959: 491:. We want to show the storm as it would have looked to an astronaut. Reality is always better.-- 2702:

articles and other sources where appropriate, especially since BoM provide weekly notes on the

2536: 2326: 1346: 1294: 1226: 857: 852: 784: 778: 624: 586: 543: 522: 311: 212: 2673: 2320:

in 1996. As it crossed the prime meridian, it had to be renamed Typhoon John, as questioned.

440: 3252: 3246: 3205: 3013: 2991: 2703: 2514: 2498: 2426: 2278: 2223: 2190: 2001: 1926: 1896: 1338: 932: 770: 720: 617: 609: 592: 560: 492: 469: 402: 208: 3473: 3321: 2149: 3519: 3480: 2893: 2852: 2707: 2466: 2340: 2112: 2085: 1873: 1858: 1832: 1817: 1779: 1759: 1698: 1661: 1633: 1429:

with 1 minute sustained winds of 220 km/h (140 mph) and a minimum central pressure of 910

1342: 1100: 1092: 908: 834: 423: 184: 2929: 2681: 1560:

Okay... basically have the same table that a season article has? Or make a custom table?

3576: 3484: 3336: 3303: 3267: 3221: 3192: 2870: 2575: 2560: 2559:

is active but this fell out of use several years ago. Any veterans remembering this? --

2455: 2317: 2274: 1088: 657: 630: 578: 511: 247:

include simulated true-color images created by overlaying grayscale visible data on a

3593: 3559: 3534: 3504: 3449: 3436: 3390: 3377: 3141: 3128: 3082: 3069: 3025: 2831: 2818: 2774: 2742: 2659: 2521: 2386: 2306: 2099: 2071: 2045: 2031: 2017: 1987: 1961: 1912: 1880: 1840: 1810: 1794: 1744: 1684: 1648: 1627: 1604: 1561: 1531: 1473: 1446: 1430: 1410: 1365: 1324: 1273: 1249: 1209: 1176: 1036: 804: 3120: 958:. I am not experienced with storm articles but have nominated it to be included in 539: 487:

unless it is made explicit that visual images are to take precedence over infrared

198: 143: 2485: 1674:

A lot of articles are already adapted with converted wind speeds. For example...

2933: 2685: 2385:

Basically, from what I saw, B2 needs work in order for Beryl to become B-Class.

926: 716: 248: 167:

Clarity of the storm and its context should be emphasized over closeness to peak

135: 46:

If you wish to start a new discussion or revive an old one, please do so on the

2578:, I don't ever remember indicating in the timeline that storms are active, and 1434: 1058: 228: 1624:

Strange I was just about to post the following argument about the scale used

1071:

Here is where I believe we should have an effects table, like the one linked

3573: 3548: 3477: 3300: 3264: 3218: 3189: 2867: 2452: 652: 508: 417: 220: 3183:

for those season articles that do not have enough editors to maintain. The

1087:

caused flooding rains from Central America to Texas. Category 4 hurricanes

3229:

Let’s formally apply for that bot. It shouldn’t be difficult to automate.

1680:

2009–10_South-West_Indian_Ocean_cyclone_season#Subtropical_Depression_Joël

2351:

Decent number of citations/references throughout the body of the article.

2284: 2229: 2007: 1932: 1902: 1108: 555:- I simply support the proposal. Although in terms of Bullet-point no.3, 475: 258: 3412: 3353: 3104: 3045: 2794: 3251:. Also, "temporal" is not the correct word for what I think you mean.-- 3243:

Frankly, if you are complaining about the infoboxes not being updated,

2725:. I think it's a good idea, and it'll fill a gap on Knowledge (XXG). ♫ 2489:

Maximum sustained wind speed and minimum pressure of Hurricane Florence

1713:

Knowledge (XXG):WikiProject Tropical cyclones/Tropical cyclones by year

232: 224: 3299:

information that editors have to take more time to check the facts.--

2697:

developed etc. I also note that France develop seasonal summaries for

1925:

defense, I'm well aware these things aren't the easiest to work with.

1390:

each year, if anyone does that and we have a good citation for it. ♫

282:

This includes any infrared data that has been mapped to a color ramp.

236: 132:

in or out infoboxes; if I did not include others, please notify them

2465:

season in the atmosphere than the season articles like the PTS can.

1409:

Alright... I will get started on it later today and some tomorrow.

1337:

or of continuous activity. Just some thoughts. I’d be curious what

1054:

General forecasts for global activity (if that exists for the year)

2484: 2098:

The task force could work on cyclone articles until that happens.

1974:

A blown up version of the timeline could look something like this:

268: 216: 204: 157:

Geographic context is important for storms if they are near land.

614:

Appreciate it! I'm planning on a simple tutorial of polar2grid.

189:

These include images of storms taken from personnel onboard the

2892:

Would the same rule apply for 1-min winds from the JTWC/NPMOC?

734:

In those cases, the overnight (IR) images would be preferable.

1979: 1095:

existed simultaneously in the Atlantic Ocean while Category 3

25: 2404: 255:

Infrared or visible imagery overlaid on a true-color basemap.

3411: 3352: 3103: 3044: 2793: 2247:

tropical-cyclones-project=yes}} banner with a rating on it.

1960:

back in early 2011. As for making the graph taller, can do.

1647:

probably be best to stick with SSHWS to prevent confusion.

292:

of the system at or near peak or its impacts should be used

2676:(i.e. we regurgitate everything from the RSMC Miami basin 331:- it’s about time we have some standardization on images. 1107:, and Hurricane Karl caused flooding and heavy damage in 231:, and the true-color approximations of the ABI sensor on 3446: