Oswego Lake

From Infogalactic: the planetary knowledge core
Jump to: navigation, search

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Oswego Lake
Lakewood Bay Oswego Lake.jpg
Lakewood Bay (connected to the main lake in 1928)
Location Lake Oswego, Clackamas County, Oregon
Coordinates Lua error in package.lua at line 80: module 'strict' not found.
Type Kolk depression/Reservoir
Primary inflows Tualatin River, Springbrook Creek
Primary outflows Willamette River (via Oswego Creek)
Catchment area 6.6 sq mi (17 km2)[1]
Basin countries United States
Max. length 2.5 mi (4.0 km)
Max. width 0.3 mi (0.48 km)
Surface area 420 acres (1.7 km2)[2]
Average depth 26 ft (7.9 m)[1]
Max. depth 55 ft (17 m)[1]
Water volume 10,055 acre·ft (12,403,000 m3)[1]
Residence time 2 months[1]
Shore length1 11.95 mi (19.23 km)[2]
Surface elevation 99 ft (30 m)[1]
Islands Jantzen Island
Settlements Lake Oswego
1 Shore length is not a well-defined measure.

Oswego Lake is a lake in Clackamas County, Oregon that is completely surrounded by the city of Lake Oswego. Though the lake is naturally occurring (a former channel of the Tualatin River), it has been significantly altered because of the concrete dam that has increased its size to 395 acres (1.60 km2). Officially, the United States Geological Survey records the official name as Lake Oswego and classifies it as a reservoir (due to its artificially increased size).[3] To distinguish it from the city, however, the lake is usually called Oswego Lake.[4]

Geologic history

The lake is a former channel of the Tualatin River, carved in basalt to the Willamette River. Eventually, the river changed course and abandoned the Oswego route.[1][2]

About 13,000 to 15,000 years ago, the ice dam that contained Glacial Lake Missoula ruptured, resulting in the Missoula Floods, which backed the Columbia River up the Willamette River. The flooding created an underwater vortex called a kolk, which scoured out and enlarged the old Oswego channel, creating a natural lake.[5] The rocks and boulders were flung by the kolk up to a mile away to present-day Durham and Tualatin, where they were quarried for many years before the site was converted to the Bridgeport Village shopping center.[1][6]

Early human habitation

The lake was known to the native Clackamas Indians as Waluga ("wild swan"), for the birds they hunted there. With the arrival of European settlers in the mid-19th century, the lake was called Sucker Lake for a type of fish that was abundant in its waters.[7] In 1847, Albert Alonzo Durham built a sawmill on Sucker Creek, the lake's outlet to the Willamette River. In 1850, he made the first Donation Land Claim in the area, which he named Oswego after Oswego, New York.[8]

Iron industry

Remains of the Oregon Iron Company Furnace in Lake Oswego's George Rogers Park

In 1865, the Oregon Iron Company was incorporated with the goal of making the town of Oswego an industrial center for the smelting of the abundant iron ore in the area. The company purchased the entire town of Oswego, including the lake and surrounding hills, which were rich in not only iron ore, but trees that would be turned into charcoal to feed the furnaces.[9] Population in the town boomed, aided by the opening of a narrow gauge railroad from Portland in 1886. The Oregon iron industry peaked in 1890, but with the availability of cheaper coke-fired iron and steel mills, by the early 20th century it had nearly collapsed.[8]

Lake expansion

The Lake Oswego Canal was built in 1872 to connect then-Sucker Lake to the Tualatin River.

In 1871, the Tualatin River Navigation & Manufacturing Company began work to build a continuous waterway that would connect the Tualatin River to the Willamette. The company planned to build two canals: one to connect the Tualatin to the lake to provide access to the iron smelter, and a second with locks that would connect the lake to the Willamette via Sucker Creek.[10] The first canal was finished in 1872, but due to low water, was not passed through until January 21, 1873, when the sternwheeler Onward made the first trip.[11] In 1873, the completion of the Willamette Falls Locks made traffic past Willamette Falls possible without portage; since the Tualatin was more difficult to navigate anyway, the idea of a second canal was abandoned.[10][11]

A series of wooden dams had been built at the outlet to Sucker Creek beginning in 1860 to provide water power; but since winter floods would wash out these dams within a few years, in 1921 a concrete dam was built, which not only provided a more reliable power source, but also allowed the lake level to be precisely controlled. The level was allowed to rise several feet to cover the unsightly stumps left over from logging and create a more visually appealing shoreline.[12]

With the name Sucker Lake considered unappealing to potential residents, the community decided to rename the lake. While "Lake Tualatin" was considered, in 1913 the United States Board on Geographic Names officially renamed it Oswego Lake.[13] In 1961, the USGS officially changed the name to "Lake Oswego," though the old name is usually used to avoid confusion with the name of the city.[3][4]

In 1928, a marshy area known as the Duck Pond adjacent to the lake was flooded, and a canal dug to it to connect to the main lake to create Lakewood Bay, which allowed more shoreline homes to be built next to the newly completed Pacific Highway (now part of Oregon Route 43).[14]

Land development

The Lake Grove Swim Park on the north shore of Oswego Lake, one of several swim parks

With the demise of the iron industry, the now-renamed Oregon Iron & Steel Company turned to development of its approximately 23,000 acres (93 km2) of land surrounding the lake. The company built a power plant in 1909, just before the incorporation of the City of Oswego in 1910. Headed by Oregon Iron & Steel president William M. Ladd (son of former Portland mayor William S. Ladd, who was one of the original investors in the Oregon Iron Company), the Ladd Estate Company converted the iron town into a prestigious lakeside retreat.[9]

In 1924, Paul Murphy developed the Oswego Lake Country Club to promote Oswego as a place to "live where you play."[8] The Paul Murphy Company replaced Ladd's company as developer of Oregon Iron and Steel's property in 1940, and the following year, Oregon Iron and Steel created the Lake Oswego Corporation, which still owns the lake as a private corporation of lakefront property owners.[13] In 1960, shortly before ending its existence, Oregon Iron & Steel was disbanding deeded the powerhouse and dams to the corporation.[13]

With the relative scarcity of building easements, lakefront property remains prestigious, and a number of architecturally significant homes have been built along its shores, including the Carl C. Jantzen Estate, a Tudor-style estate on the National Register of Historic Places, built on an island on the lake's north shore by the founder of the Jantzen swimwear company in 1930. In addition, the lakeshore features homes by noted Portland architects such as Richard Sundeleaf and Van Evera Bailey.[15]

Ownership and access

Sign in Millennium Plaza Park in Lake Oswego, asserting private status of the lake

Despite a decades-old status quo in which the Lake Oswego Corporation maintains that it owns the lake and has the authority to restrict access to it, state and local law enforcement have recently indicated that they consider the lake to be public and that they will not pursue charges against anyone for using it.[16] As of 2012, local law enforcement was on the record saying the water is public property and that it was more likely to charge the corporation's security patrols with unlawful arrest than to cite swimmers or boaters for enjoying the water.[16]

Nonetheless, the corporation has successfully cultivated an air of authority to control the waters, posting "no trespassing" signs and issuing permits to select individuals who overcome various administrative hurdles.[16] The corporation also seeks to regulate boat and operator licensing, water safety, and water quality,[17] but those regulations may not be actually binding.[16] With most land around the lake privately owned, and following a unanimous vote by the Lake Oswego City Council to bar entry to the lake from several lakefront parks,[18] few people have been able to test the authority of the corporation to enforce those regulations.[16]

The ability of the corporation to restrict access to the water has been questioned on numerous occasions.[19][20] According to recent independent assessments of the legal situation, including a 2005 Oregon Attorney General opinion regarding the public's right to use navigable waterways in Oregon,[21] the waters are publicly owned, though the ground beneath the lake is owned by the shareholders of the corporation, including 690 lakefront property owners and another 515 families who belong to one of 20 waterfront easement associations.[16][22][23][24]

The corporation argues that the federal Water Resources Development Act of 1976 specifically classified the lake as non-navigable; therefore, the Attorney General opinion—which states that waterways over private land are only public if they are "navigable-for-public-use"—does not apply.[21][24][25] The corporation also asserts that the lake is an artificially-expanded power reservoir and not a natural body of water.[19][26]

In May 2012, a federal lawsuit was filed against the city of Lake Oswego to prevent it from limiting public access to the lake.[27] The case was dismissed from federal court in October, with the judge indicating that the state of Oregon, due to its presumed ownership interest, should be able to weigh in on the case.[28] The plaintiffs refiled in state court in November 2012,[29] and in early 2014, the judge ruled that the city had the right to block access.[30] The plaintiffs appealed, and the case will be heard by the Oregon Court of Appeals in late 2014. Citing their interest in the impact of the case to public trust doctrine, 36 law professors from around the nation have filed amici curiae briefs for the plaintiffs.[31][32]

Lake health

Lakewood Bay during 2010–2011 drawdown.

Periodically, the corporation lowers the water level in the lake by opening the dam to enable lakefront property owners to conduct repairs on docks and boathouses.[33] In September 2010, the lake was drawn down approximately 24 feet (7.3 m) to allow replacement of an aging sewer pipe that traverses the lake, the lowest lake level since 1962 when the original sewer line was installed. The lake was refilled to its usual level in the summer of 2011.[34][35] In recent years, the lake has experienced explosive algae growth in the lake, due in part to runoff from lawn fertilizer, which is rich in phosphorus.[22]

See also

Notes

  1. 1.0 1.1 1.2 1.3 1.4 1.5 1.6 1.7 Lua error in package.lua at line 80: module 'strict' not found.
  2. 2.0 2.1 2.2 Lua error in package.lua at line 80: module 'strict' not found.
  3. 3.0 3.1 Lua error in package.lua at line 80: module 'strict' not found.
  4. 4.0 4.1 Lua error in package.lua at line 80: module 'strict' not found.
  5. Lua error in package.lua at line 80: module 'strict' not found.
  6. Lua error in package.lua at line 80: module 'strict' not found.
  7. Fulton, p. 15
  8. 8.0 8.1 8.2 Lua error in package.lua at line 80: module 'strict' not found.
  9. 9.0 9.1 Lua error in package.lua at line 80: module 'strict' not found.
  10. 10.0 10.1 Fulton, p. 33
  11. 11.0 11.1 Lua error in package.lua at line 80: module 'strict' not found.
  12. Fulton, p. 80
  13. 13.0 13.1 13.2 Lua error in package.lua at line 80: module 'strict' not found.
  14. Fulton, p. 83
  15. Lua error in package.lua at line 80: module 'strict' not found.
  16. 16.0 16.1 16.2 16.3 16.4 16.5 Lua error in package.lua at line 80: module 'strict' not found.
  17. Lua error in package.lua at line 80: module 'strict' not found.
  18. Lua error in package.lua at line 80: module 'strict' not found.
  19. 19.0 19.1 Lua error in package.lua at line 80: module 'strict' not found.
  20. Lua error in package.lua at line 80: module 'strict' not found.
  21. 21.0 21.1 Lua error in package.lua at line 80: module 'strict' not found.
  22. 22.0 22.1 Lua error in package.lua at line 80: module 'strict' not found.
  23. Lua error in package.lua at line 80: module 'strict' not found.
  24. 24.0 24.1 Lua error in package.lua at line 80: module 'strict' not found.
  25. Lua error in package.lua at line 80: module 'strict' not found.
  26. Lua error in package.lua at line 80: module 'strict' not found.
  27. Lua error in package.lua at line 80: module 'strict' not found.
  28. Lua error in package.lua at line 80: module 'strict' not found.
  29. Lua error in package.lua at line 80: module 'strict' not found.
  30. Lua error in package.lua at line 80: module 'strict' not found.
  31. Lua error in package.lua at line 80: module 'strict' not found.
  32. Lua error in package.lua at line 80: module 'strict' not found.
  33. Lua error in package.lua at line 80: module 'strict' not found.
  34. Lua error in package.lua at line 80: module 'strict' not found.
  35. Lua error in package.lua at line 80: module 'strict' not found.

References

Lua error in package.lua at line 80: module 'strict' not found.

External links