Basically, this is just a random project idea I had. The title mostly explains it all. But here is a more in depth explanation. So the WPac and CPac naming lists work like this: At the final name of the season, instead of restarting at A and rotating lists, they just keep going with the list. EX: The final name to be used in the CPac was Oho in 2015. For 2016, instead of starting with Akoni, it started with Pali. In the Atlantic, it doesn't work like that. But I'm gonna see what would have happened if it did work like that! So lets begin!
Attributes | Values |
---|
rdfs:label
| - If the naming in the Atlantic worked like the naming in the WPac and CPac.
|
rdfs:comment
| - Basically, this is just a random project idea I had. The title mostly explains it all. But here is a more in depth explanation. So the WPac and CPac naming lists work like this: At the final name of the season, instead of restarting at A and rotating lists, they just keep going with the list. EX: The final name to be used in the CPac was Oho in 2015. For 2016, instead of starting with Akoni, it started with Pali. In the Atlantic, it doesn't work like that. But I'm gonna see what would have happened if it did work like that! So lets begin!
|
dcterms:subject
| |
abstract
| - Basically, this is just a random project idea I had. The title mostly explains it all. But here is a more in depth explanation. So the WPac and CPac naming lists work like this: At the final name of the season, instead of restarting at A and rotating lists, they just keep going with the list. EX: The final name to be used in the CPac was Oho in 2015. For 2016, instead of starting with Akoni, it started with Pali. In the Atlantic, it doesn't work like that. But I'm gonna see what would have happened if it did work like that! So lets begin! Btw, if this gets popular, I might do this with the EPac as well (Or someone else can do it if they like.)
|