Coleto Creek Reservoir

Coleto Creek Reservoir is a reservoir on Coleto Creek and Perdido Creek located in Fannin, Texas, 15 miles (24 km) southwest of Victoria, Texas. The surface of the lake extends into Victoria and Goliad counties. The reservoir was formed in 1980 by the construction of a dam by the Guadalupe-Blanco River Authority to provide a power station cooling pond for electric power generation. Coleto Creek Reservoir is a venue for outdoor recreation, including fishing and boating.

Coleto Creek Reservoir
LocationGoliad / Victoria counties, Texas, United States
Coordinates28°43.63′N 97°10.22′W
TypePower station cooling reservoir
Primary inflowsColeto Creek and Perdido Creek
Basin countriesUnited States
Surface area3,100 acres (1,300 ha)
Max. depth46 ft (14 m)
Surface elevation98 ft (30 m)

Fish and plant life

Coleto Creek Reservoir has been stocked with species of fish intended to improve the utility of the reservoir for recreational fishing. Fish present in the reservoir include white bass, hybrid striped bass, catfish, crappie, sunfish, bluegill, and largemouth bass. Vegetation in the lake includes cattail, pondweed, American lotus, rushes, and hydrilla.

Recreational uses

View from the pier

The Guadalupe-Blanco River Authority maintains a public park at the reservoir with recreational facilities for boating and fishing.

The reservoir has camp sites, picnic areas, cabins, a boat ramp for access to the water, a 200 feet (60 m) long lighted fishing pier, a 1.5 miles (2.4 km) hiking path, and restroom facilities.

gollark: If enough people come up with interesting non-stupid uses for this sort of thing, I *can* put together a centralized version.
gollark: You *could* sort of do that, in a kristaceous centralized fashion, by having some server just connect to KristQL and run user-submitted bits of JS code to validate things.
gollark: Hmm, if krist supports postgres I could turn my Redis instance back on and pointlessly run a node.
gollark: As you control the instance, you can MAKE it lower.
gollark: No, the history was fine, the block value function for new instances was wrong.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.