Talk:Oroville Dam

Flood protection cost savings

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)

GA Review

This review is transcluded from Talk:Oroville Dam/GA1. The edit link for this section can be used to add comments to the review.

Reviewer: MathewTownsend (talk · contribs) 00:20, 31 August 2012 (UTC)

This is a very nice, well-written article. I've only a few minor comments:

• "it is the tallest dam in the U.S." - I added " as of 2012" - is this correct?
• NealthNewsDigest.com - is this a reliable source for damage prevented?
• "Groundbreaking on the dam site occurred in May 1957 with the relocation of the Western Pacific Railroad tracks that ran through the Feather River canyon." - the relocation of the railroad tracks was the groundbreaking?
• I've made a few edits that you're free to correct.[1]

GA review-see WP:WIAGA for criteria (and here for what they are not)

1. Is it reasonably well written?

   a. prose: clear and concise, respects copyright laws, correct spelling and grammar:

   b. complies with MoS for lead, layout, words to watch, fiction, and list incorporation:

2. Is it factually accurate and verifiable?

   a. provides references to all sources in the section(s) dedicated to footnotes/citations according to the guide to layout:

   b. provides in-line citations from reliable sources where necessary:

   c. no original research:

3. Is it broad in its coverage?

   a. it addresses the main aspects of the topic:

   b. it remains focused and does not go into unnecessary detail (see summary style):

4. Does it follow the neutral point of view policy.

   fair representation without bias:

5. Is it stable?

   no edit wars, etc:

6. Does it contain images to illustrate the topic?

   a. images are copyright tagged, and non-free images have fair use rationales:

   b. images are provided where possible and appropriate, with suitable captions:

7. Overall:

   Pass or Fail:

• The few comments I made above are not enough to hold up the passing of this article. Congratulations! MathewTownsend (talk) 21:35, 2 September 2012 (UTC)

Damage in February 2017

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)

Currently there are no photos available with a permit-able license. We will probably see one in a few weeks of the spillway damage. That should be uploaded. Seeing something to scale (people besides or in) will show a lot more than just saying how big it is. Also the damage after use when this is over will greatly increase the size of the hole. It'd probably be good to add the emergency spillway and a photo of the water, and the damage later on. Currently the damage and cost is all just speculation so its good that it isn't put in. Citations will need to be gone through though to be certain that everything is reliable as this is a current event. Rocka1994 (talk) 22:58, 11 February 2017 (UTC)

Semi-protected edit request on 13 February 2017

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 100,000 cubic feet per second (2,800 m³/s) 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 100,000 cubic feet per second (2,800 m³/s) 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)

Partly done: I have added the requested changes. However, I have changed some of the wording and grammar (to put things in the past tense), and omitted potentially contentious changes not supported by the sources. Please resubmit your request if you would like additional changes. --Vandraedha (talk) 08:55, 13 February 2017 (UTC)

References

Semi-protected edit request on 13 February 2017

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)

2017 Spillway incident

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)

• I suggest the spillways incidents could be mentioned in the lede. -DePiep (talk) 12:15, 13 February 2017 (UTC)

• 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)

• 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)

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)

@Vandraedha and Prevalence: 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 Prevalence noted, I think "emergency" is the best term to use. 71.41.210.146 (talk) 20:33, 14 February 2017 (UTC)

2017 Oroville Dam crisis

The following is a closed discussion of the proposal. Please do not modify it. Subsequent comments should be made in a new section on the talk page. No further edits should be made to this section.

The result of the proposal was no consensus for the proposed change.

Yellowdesk (talk) 00:03, 18 February 2017 (UTC)

---

The content of the 2017 Oroville Dam crisis article is described in more detail in the Oroville Dam article. I suggest splitting in the future, but right now the 2017 Oroville Dam crisis article doesn't have any content that is not duplicated in the other article. epicgenius (talk) 17:48, 13 February 2017 (UTC) Should it be merged or split? epicgenius (talk) 18:19, 13 February 2017 (UTC)

• Oppose @Epicgenius: In my opinion, that is putting the cart before the horse. I think there is too much content in the dam's article on the current crisis (overall slanting the article towards recent events) and splitting it off is a good thing. We should be trimming what the dam article says, not undoing the split.--Jasper Deng (talk) 18:06, 13 February 2017 (UTC)
  • Well, it could go either way. I am proposing either a split or a merge. I'll amend it. epicgenius (talk) 18:19, 13 February 2017 (UTC)
• Merge Current events articles get too much hype. - Frankie1969 (talk) 18:59, 13 February 2017 (UTC)
  • @Frankie1969: Not in general. Notability is irrevocable - once reliable sources have covered it in great depth, which has happened, notability is not in question. And since this is going to be ongoing for a while ($200 million spillway repair at the very least) rather than just an isolated incident, of course it deserves an article. --Jasper Deng (talk) 19:32, 13 February 2017 (UTC)
• Oppose for the same reason as Frankie1969: current events articles get too much hype, so let the original article, strictly on the dam, stand on its own. The crisis article should bear the brunt of the crisis.— Preceding unsigned comment added by Civil Engineer 3 (talk • contribs)
• Wait If there is NOT a catastrophic failure of either the main or emergency spillways, then this should just be an interesting section merged into the MAIN article. Sure, it's a little bigger than the sections on "2005 dam re-licensing" and "Spillway cracking and inspections", but it is still JUST a part of the evolving history of the dam. Only if the worst should happen (hope not!!), THEN this should stay as a standalone article. Jmg38 (talk) 19:42, 13 February 2017 (UTC)
  • @Jmg38: Uhm no. That's not how notability works, either. We all know now that the spillway is no longer in imminent danger of failing, but this coming week's storms will test that. by the way, please don't use all-caps--Jasper Deng (talk) 19:48, 13 February 2017 (UTC)
• Merge - There's no reason to separate it out from the main body article. Most of this stuff is just a product of recentism; when merged into the main article, we won't need to break down the specific timeline in great detail as is presently the case. Titanium Dragon (talk) 21:12, 13 February 2017 (UTC)
• Wait - The dam might collapse soon. If something doesn't happen, we'll merge and if something does happen, we keep this as a standalone article. UNSC Luke 1021 (talk) 21:31, 13 February 2017 (UTC)'
  • @UNSC Luke 1021: Surely you don't actually mean the dam will collapse. The dam itself is in absolutely no danger of failing. It's all about he spillways.--Jasper Deng (talk) 21:52, 13 February 2017 (UTC)
    • @Jasper Deng: But if the spillways fail, this could be almost as serious as a direct dam failure. Water could erode around the spillway until the gate would collapse, leading to a catastrophic situation. Another reason to keep this article. Glacier2009 (talk) 23:21, 13 February 2017 (UTC)
      • @Glacier2009: Yes, but it's not like a dam break where the entire 3.75-odd million acre-feet will all come out at once, since bedrock would at some point halt the erosion.--Jasper Deng (talk) 02:08, 14 February 2017 (UTC)
• Oppose Already, this is a major story. Topic deserves its own article. Issue is not if the dam fails, but that failure was seriously possible. Glacier2009 (talk) 21:38, 13 February 2017 (UTC)
• Oppose This is such a major issue, the 2017 Oroville Dam crisis page will be needed for all the follow up info also. The Oroville Dam will only have a summary in the future. The two pages should be used as such, one for summary and one for details.Telecine Guy (talk) 22:04, 13 February 2017 (UTC)
• Oppose The Dam article doesn't need the clutter; it can contain a summary and point here. Whatever happens to the dam, there will be fallout and long-time major repair efforts to cover here. Twang (talk) 23:53, 13 February 2017 (UTC)
• Wait and merge - Agree with the others who say wait—however, I would add, check out St. Francis Dam, an article about a dam in the past tense, because it failed and is gone. Most of the article deals with the history of the dam, its design flaws, and how those led to its failure. That's what the main article on Oroville Dam would turn into if this dam bites the big one. And if it doesn't, it's a merge as this will become a footnote in the history books. But, first and foremost, wait. Wikipedia is NOTNEWS. Darkest Tree Talk 23:54, 13 February 2017 (UTC)
  • @Darkest tree: If you read NOTNEWS, you'll notice that "enduring notability" is the main question for an article of this type, and you will surely agree with me that this subject will not lose notability anytime soon, given the massive repairs that will be needed regardless of what events occur. So NOTNEWS is not a valid reason to merge here.--Jasper Deng (talk) 02:08, 14 February 2017 (UTC)
• Merge The history plays a major part in the crisis, when split, there would be redundancy on the construction (info on how deep the foundation of the emergency spillway wall is is still missing, but may be available soon), the 2005 consideration whether the emergency spillway ridge should have been reinforced, the 2013 cracks etc. The crisis section may eventually make up the most part of the article, but it also is the most notable part of the dam itself (e.g. being the reason why interational audiences hear of that dam at all), so that would be justified. Regardless if the situation worsens or not, it is already bad enough to determine the whole "life" of the dam project so far, in other words, there is no point in splitting the small dam article off the important main article about the 2017 crisis. And when the dam is rebuilt and (likely) heavily modified over the next years because of what happens now, will you write it in the crisis article as outcome or in the dam article as next construction step? Makes really no sense to have two articles that tell the same with only different detail focus.--79.194.224.239 (talk) 00:27, 14 February 2017 (UTC)
• Oppose - Plenty of sources for this, and it's notable for a standalone article -- at least it is at this time. Octoberwoodland (talk) 00:44, 14 February 2017 (UTC)
• Oppose It's unlikely to become a full blown disaster (also no unnecessary fear mongering on Wikipedia please), but the Feb 2017 "incident" is notable enough for its own page. Shannon 01:12, 14 February 2017 (UTC)
• Wait and merge The dam does not yet seem to have any issues. The spillway is where the issue lies. I would suggest that if there is some damage to the dam itself, that would be when the two should be merged. jwhouk 02:07, 14 February 2017 (UTC)
• Oppose Major event. --Deansfa (talk) 02:45, 14 February 2017 (UTC)
• Split - too much detail would make the article way big. plus enough detail to make the split off data not too light Dave Rave (talk) 05:28, 14 February 2017 (UTC)
• Oppose Merge - That article is detailing a notable event without any fluff very nicely while this article should cover just the overall summary of the dam and other important details about it. --Super Goku V (talk) 06:46, 14 February 2017 (UTC)
• Merge - Makes sense. K.I.S.S. Pcvcolin (talk)
• Split. This is already a major crisis which could easily surpass Hurricane Katrina's damage and flooding area if either of the spillways fail. I live an hour away, and we have another week of heavy rain projected. --Light show (talk) 07:28, 14 February 2017 (UTC)
• Oppose Merge - The ongoing crisis is most certainly a notable incident, and thus quite arguably merits its own dedicated article.!
  SecretName101 (talk) 10:47, 14 February 2017 (UTC)

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)

• Wait and merge I agree with several of the other editors, this is an ongoing current event. There is a lot of recentism going on. I think that after this event resolves itself the actually notable portions of the incident will fit into a reasonably sized section of this article. The information about the aftermath (either repair, rebuild, dismantling, or whatever end of lifespan) should balance out the article so that it isn't too much emphasis on the current events. --Vandraedha (talk) 11:37, 14 February 2017 (UTC)
• Keep split - the amount of details is disproportionate for the main article about the dam. The crisis is notable enough for the separate article. Dr Bug (Vladimir V. Medeyko) 13:51, 14 February 2017 (UTC)
• Oppose Merge - We don't want to make the Oroville Dam article slanted towards current events any more than it already is. I agree with other editors here who say that this event is notable enough for its own article. - Knowledgekid87 (talk) 14:35, 14 February 2017 (UTC)
• Split - It's looking like a consensus for the short term. A month from now when it's old news and everyone's bored someone can decide to merge. Meanwhile let's trim the subsection. No need for a sub-subsection or many paragraphs. Jim.henderson (talk) 14:51, 14 February 2017 (UTC)
• Wait then merge I agree with many of the sentiments above regarding recentism and news hysteria. I have worked many dam articles on this encyclopedia and this is barely notable compared to what can happen and what has happened with other dams. The difference is we are in the now and flooded with information. See Category:Dam_failures or an article like Howard A. Hanson Dam for a major structural issue that was controlled by engineers. If the spillway holds, which I suspect it will (pending another act of God), this incident rates just a section in the dam's history.--NortyNort (Holla) 16:02, 14 February 2017 (UTC)
• Comment If nobody else has any more dam comments, then we should close this dam discussion. - Knowledgekid87 (talk) 16:05, 14 February 2017 (UTC)
• Oppose Merge Oppose at this time, revisit in a few months.MeropeRiddle (talk) 16:53, 14 February 2017 (UTC)
• Oppose, maybe merge later There's clearly enough material that a separate article is reasonable, even if not yet obviously preferable, but there's more appearing each day, and the end is not in sight. Let the crisis article get the churn, then consider for merging once it's clear what the scope is. 71.41.210.146 (talk) 20:41, 14 February 2017 (UTC)
• Comment (on my Wait and Merge position): Just to be clear, I don't think that anybody on the wait/merge side is saying that this isn't notable, just that it would work better as part of the main dam article. But in the meantime, there isn't any reason to rush to a decision on this dam issue, and I believe we should all should just wait to see how this dam situation plays out and exercise a little dam patience. The dam story, as it were, could be very different in a few days. Agree with the above that the crisis article is the best place for the churn. Darkest Tree Talk 21:46, 14 February 2017 (UTC)
• Oppose merge wait until a couple of months after the crisis has past to see if we should merge or not, and not now, since it is ongoing, churning, and notable. If it is sufficient to stand on its own, or not, does not mean that the traffic and editing will make this article unstable if merged. When the churn dies down we can determine if it should be merged or not, but right now, it's better to have all the rapid editing and conflicts on that page. -- 65.94.168.229 (talk) 23:05, 14 February 2017 (UTC)
• Oppose merge: The crisis article is probably more related to the unusual 2016-17 California wet season than to the Oroville Dam, and if anything should be merged into an article regarding that (or expanded into such an article if we don't already have one) rather than the Oroville Dam history. This is assuming the spillway tops hold; if one fails, it should remain its own article independent of anything else as it will be a bigger disaster than 2001 September 11 action. 207.47.199.18 (talk) 01:23, 15 February 2017 (UTC) P.S.: Curious if any of Wikipedia's host or CDN hardware is in the basin downstream of Oroville?
• Merge the [File:Oroville_dam_infographic_feb_14.png|phased-stage infographic] added [2] by Alfred Twe ( talk) isn't on the separated incident page so link to specific useful Wikimedia content missed, thus better merged. The parking-lot design flaw noted here lot edit by MeropeRiddle (talk) is inherent to the dam itself and will threaten the edifice always not just for the duration of the incident and this fact would be lost - or need to be duplicated - if split MrsKrishan (talk) 09:13, 15 February 2017 (UTC)
• Oppose Crisis and aftermath can make for a very long article, well in excess of 50K bytes. forgot to sign.L3X1 My Complaint Desk 20:04, 15 February 2017 (UTC)

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)

• Split to keep the main article on the Dam, and not the crisis.
• Oppose merge We stopped printing on paper decades ago ... prokaryotes (talk) 20:04, 15 February 2017 (UTC)

That is brilliant! L3X1 My Complaint Desk 21:00, 15 February 2017 (UTC)

• Oppose merge Major event with sufficient notability and coverage to deserve of its own article. —Lowellian (reply) 11:11, 16 February 2017 (UTC)
• Oppose merge. ---Another Believer _(Talk) 20:59, 16 February 2017 (UTC)

The above discussion is preserved as an archive of the proposal. Please do not modify it. Subsequent comments should be made in a new section on this talk page. No further edits should be made to this section.

2009 accident involving river valves

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)

External links modified

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.

This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template {{source check}} (last update: 5 June 2024).

• If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
• If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—InternetArchiveBot (Report bug) 05:21, 23 March 2017 (UTC)

External links modified

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 {{dead link}} 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.

This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template {{source check}} (last update: 5 June 2024).

• If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
• If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—InternetArchiveBot (Report bug) 18:45, 9 September 2017 (UTC)

External links modified

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.

This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template {{source check}} (last update: 5 June 2024).

• If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
• If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—InternetArchiveBot (Report bug) 23:15, 21 December 2017 (UTC)