NAS - Nonindigenous Aquatic Species
U.S. Fish and Wildlife Service. 1994. White River spinedace, Lepidomeda albivallis, recovery plan. U.S. Fish and Wildlife Service, Portland, OR.
Reference Number: 881 Type: Report Author: U.S. Fish and Wildlife Service. Date (year): 1994 Report TitleWhite River spinedace, Lepidomeda albivallis, recovery plan. Publisher:U.S. Fish and Wildlife Service, Portland, OR. Publisher Location: Pages: 45 pp URL: Keywords: White River spinedace, Lepidomeda albivallis, E&T, recovery
Carassius auratus NV - Lund Spring, northern White River Valley, on Rt 318 just south of I-6
Gambusia affinis NV - Lund Spring, northern White River Valley, on Rt 318 just south of I-6
Lepidomeda albivallis CO - state non-specific NV - Railroad Valley
Micropterus salmoides NV - Flag Springs, northern White River Valley
Oncorhynchus clarkii NV - White River drainage
Oncorhynchus mykiss NV - White River drainage NV - Flag Springs complex, White River drainage
Poecilia reticulata NV - Lund Spring, northern White River Valley, on Rt 318 just south of I-6 NV - Indian Spring, northern White River Valley NV - Cold Spring, northern White River Valley, part of Preston Springs complex NV - Nicholas Spring (a.k.a. Preston Town Spring), northern White River Valley NV - Arnoldson Spring, northern White River Valley
Salmo trutta NV - White River drainage
Salvelinus fontinalis NV - White River drainage
The data represented on this site vary in accuracy, scale, completeness, extent of coverage and origin. It is the user's responsibility to use these data consistent with their intended purpose and within stated limitations. We highly recommend reviewing metadata files prior to interpreting these data.
Citation information: U.S. Geological Survey. [2024]. Nonindigenous Aquatic Species Database. Gainesville, Florida. Accessed [11/21/2024].
Contact us if you are using data from this site for a publication to make sure the data are being used appropriately and for potential co-authorship if warranted.
For general information and questions about the database, contact Wesley Daniel. For problems and technical issues, contact Matthew Neilson.
