Talk:Oroville Dam

message: This article needs sources. It makes allegations regarding the cost savings from flood protection but does not provide a source.  —Preceding unsigned comment added by 76.200.154.96 (talk) 07:01, 24 August 2008 (UTC)
thread_title: Flood protection cost savings

message: http://sacramento.cbslocal.com/2017/02/07/damage-reported-at-oroville-dam-spillway-after-officials-increase-water-releases/  — Preceding unsigned comment added by 46.22.104.168 (talk) 12:54, 10 February 2017 (UTC)
thread_title:  Damage in February 2017 

message: : Update the final paragraph of the "2017 spillway failure" section:
On February 12, 2017, evacuation was ordered for those in low-lying levels of Oroville, due to an anticipated failure of the auxiliary spillway. A failure of the concrete top of the spillway would allow up to 30 vertical feet of Lake Oroville through the gap in an uncontrolled deluge. The flow over the main spillway was increased to  to try to slow the erosion of the emergency spillway.
: as follows:
On February 12, 2017, evacuation was ordered for those in low-lying levels of Oroville, due to an anticipated failure of the auxiliary spillway. Specifically, erosion on the hillside was growing uphill toward the concrete lip of the auxilliary spillway, leading to the fear that it would collapse.  A failure of the concrete top of the spillway would allow up to 30 vertical feet of Lake Oroville through the gap in an uncontrolled deluge. The flow over the main spillway was increased to  to try to slow the erosion of the emergency spillway.
By the evening of the 12th, the increased flow had successfully lowered the water level to below the emergency spillway, allowing the erosion there to be inspected and hastily stabilized with boulders.  The danger is that the damage is transferred to the main spillway.  Not only does this make future repair more expensive, but the damage to the main spillway could grow uphill to the point that it endangered the main spillway gates, leaving no safe way to release water.  The extent of such damage is currently unknown, hidden by water spray and darkness; it will be assessed on the morning of the 13th.
: Thank you!  71.41.210.146 (talk) 06:37, 13 February 2017 (UTC)
thread_title:  Semi-protected edit request on 13 February 2017 

message: : Fix the dead (possibly malicious) link in the Operations section at the end of the paragraph involving the 1997 flood
|url=http://cepsym.info/Sympro1997/roos.pdf
: Should be this:
|url=http://cepsym.org/Sympro1997/Roos.pdf
— Preceding unsigned comment added by Tduff (talk • contribs) 2017-02-13T00:23:18 (UTC)
 Done --Vandraedha (talk) 09:02, 13 February 2017 (UTC)
thread_title:  Semi-protected edit request on 13 February 2017 

message: I've attempted to reorganize the existing text of the incident into a logical progression and coherent narrative. I've added sub-headers in an attempt to clarify the timeline and avoid confusion between the failure of the primary spillway and the use of and failure of the auxiliary (emergency) spillway. These subheadings may not be the best solution long term, and they but I hope that they will help keep things organized temporarily until the incident evolves further.
I have also changed several mentions of emergency spillway to auxiliary spillway. Although most of the locals and many news sources use the term emergency spillway, I believe that using auxiliary spillway is a more clear and accurate description. AFAIK, this is also the term being used by the California DWR. Although it may be more correct, I think that emergency auxiliary spillway is just too long and potentially confusing to type repetitively. I'm not really concerned with the exact term used for the secondary spillway, as much as having a consistent name. --Vandraedha (talk) 10:49, 13 February 2017 (UTC)
replies: text: *We may want to hold off on adding too much detail about the spillway incident to the lede, lest we run afoul of WP:RECENT. Yes, it probably should be mentioned, but the exact wording for the mention will most likely change repeatedly over the next few days/weeks/months. At this time, nobody knows exactly how big of an event this is going to be and there is a high degree of speculation and uncertainty involved in all aspects of it. --Vandraedha (talk) 12:39, 13 February 2017 (UTC)
replies: text: *The failure of or substantial damage to of any supporting structure of a dam should be in the lead, particularly if it leads to evacuations.--NortyNort  (Holla) 13:58, 13 February 2017 (UTC)

text: In DWR's press release of Feb 9 ( http://www.water.ca.gov/news/newsreleases/2017/020917spillwayflow.pdf ) only the term "emergency spillway" is used (4 times). In licensee and ACE Reservoir Regulation Manual documentation, it's referred to as "emergency spillway". The role as auxiliary spillway was supposed to be temporary, until the Marysville Dam (which was never built) became operational. They never meant to use it as such, and must have known it wasn't suitable for that purpose (according to regulations, they're supposed to limit releases to 150,000 cfs "until 10 feet of surcharge above the ungated spillway lip is achieved"; look at the damage the spillway sustained after just 1.5 feet).  Prevalence  06:37, 14 February 2017 (UTC)
replies: text:   Indeed, the naming is a significant issue, and was at the heart of the 2005 lawsuit.  The terms "emergency spillway" and "auxilliary spillway" are defined in the Federal Energy Regulatory Commission rules, and they're defined differently.  An emergency spillway is designed for emergency (unanticipated) use only, and not in any reasonably anticipated case.  It's okay if the spillway suffers substantial damage if used.  An auxiliary spillway is intended for infrequent but anticipated use, and may suffer minor damage.  The lawsuit was that the spillway was not up to auxiliary standards but should be (because procedures, intended to be temporary until the never-built Marysville dam entered service, called for its planned use in some cases).  The result of the lawsuit was that it was okay to leave it at emergency standards.  Significantly, both parties agreed that the current spillway met "emergency" standards but not "auxiliary" ones; the dispute was about which it should meet.  So, combined with what  noted, I think "emergency" is the best term to use. 71.41.210.146 (talk) 20:33, 14 February 2017 (UTC)
thread_title:  2017 Spillway incident 

message: no consensus for the proposed change.
Yellowdesk (talk) 00:03, 18 February 2017 (UTC)
replies: text: We can perhaps revisit a potential merge at a later date, but it is currently my opinion that a merge at this point would be a poor idea.SecretName101 (talk) 10:49, 14 February 2017 (UTC)
replies: text: Comment Holding an RfC may brign more people, I only came because my weather service had an article on the side for 3 days, and I decided to check it out. Currently the consensus is like 27-7 Oppose. L3X1 My Complaint Desk 21:00, 15 February 2017 (UTC)

text: That is brilliant! L3X1 My Complaint Desk 21:00, 15 February 2017 (UTC)
thread_title:  {{anchor|Proposed merge with 2017 Oroville Dam crisis}} 2017 Oroville Dam crisis 

message: On July 22, 2009, there was an accident at the Orovile Dam involving the "river valves", meant to discharge water during low-flow seasons. Refs: 
* http://www.orovillemr.com/general-news/20120912/dwr-planning-study-on-worrisome-river-valves-blamed-in-2009-oroville-dam-accident
* http://www.chicoer.com/article/zz/20100223/NEWS/100227917
* http://www.sfchronicle.com/bayarea/article/Releasing-water-at-Oroville-Dam-a-lingering-10941922.php
-- Dan Griscom (talk) 23:50, 18 February 2017 (UTC)
thread_title:  2009 accident involving river valves 

message: Hello fellow Wikipedians,
I have just modified 2 external links on Oroville Dam. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
*Added archive https://web.archive.org/web/20120325153036/http://www.ussdams.org/uscold_s.html to http://www.ussdams.org/uscold_s.html
*Added archive https://web.archive.org/web/20120407054356/http://www.water.ca.gov/swp/facilities/Oroville/hyatt.cfm to http://www.water.ca.gov/swp/facilities/Oroville/hyatt.cfm
When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.
Cheers.—InternetArchiveBot (Report bug) 05:21, 23 March 2017 (UTC)
thread_title:  External links modified 

message: Hello fellow Wikipedians,
I have just modified 3 external links on Oroville Dam. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
*Added  tag to http://npdp.stanford.edu/DamDirectory/DamDetail.jsp?npdp_id=CA00035
*Added archive https://web.archive.org/web/20150128112059/http://www.energyalmanac.ca.gov/renewables/hydro/ to http://www.energyalmanac.ca.gov/renewables/hydro/
*Added archive https://web.archive.org/web/20120205223601/http://cee.engr.ucdavis.edu/faculty/lund/dams/DamList.htm to http://cee.engr.ucdavis.edu/faculty/lund/dams/DamList.htm
*Added archive https://web.archive.org/web/20170210163002/http://abcnews.go.com/Technology/wireStory/latest-emergency-spillway-oroville-dam-45401080 to http://abcnews.go.com/Technology/wireStory/latest-emergency-spillway-oroville-dam-45401080
When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.
Cheers.—InternetArchiveBot (Report bug) 18:45, 9 September 2017 (UTC)
thread_title:  External links modified 

message: Hello fellow Wikipedians,
I have just modified 4 external links on Oroville Dam. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
*Added archive https://web.archive.org/web/20121001040007/http://ussdams.org/ben_9903.html to http://ussdams.org/ben_9903.html
*Added archive https://web.archive.org/web/20130515142259/http://www.pcl.org/projects/2011symposium/proceedings/Keats8.pdf to http://www.pcl.org/projects/2011symposium/proceedings/Keats8.pdf
*Added archive https://web.archive.org/web/20130516093200/http://library.thinkquest.org/trio/TTQ06035/History.html to http://library.thinkquest.org/trio/TTQ06035/History.html
*Added archive https://web.archive.org/web/20120405052816/http://www.water.ca.gov/swpao/docs/bulletin/95/view/text/cha11.html to http://www.water.ca.gov/swpao/docs/bulletin/95/view/text/cha11.html
When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.
Cheers.—InternetArchiveBot (Report bug) 23:15, 21 December 2017 (UTC)
thread_title:  External links modified