Lythrum salicaria
Lythrum salicaria
(purple loosestrife)

8 results for Lythrum salicaria (purple loosestrife)
Download Data
Click here for listing in all states

Specimen IDStateCountyLocalityYear HUC Number What's this? Drainage nameStatus
1527815 WAKittitasFreeway Pond2002 17030001 Upper Yakimaestablished
1526619 WAKittitasMattoon Lake2010 17030001 Upper Yakimaestablished
1525413 WAKittitasMattoon Lake2016 17030001 Upper Yakimaestablished
1529022 WAKittitasUnnamed Pond (17N-19E-02)1994 17030001 Upper Yakimaestablished
231422 WAKittitasUnnamed pond in Kittitas County1994 17030001 Upper Yakimaestablished
1526093 WAYakimaEast Selah Pit2002 17030001 Upper Yakimaestablished
1526143 WAYakimaWenas Lake2001 17030001 Upper Yakimaestablished
1524938 WAYakimaYakima River - Yakima Co1994 17030001 Upper Yakimaestablished

Data Disclaimer: Number of records does not imply species abundance. This summary represent collection records only and may not reflect the actual distribution of established populations. These data are preliminary or provisional and are subject to revision. They are being provided to meet the need for timely best science. The data have not received final approval by the U.S. Geological Survey (USGS) and are provided on the condition that neither the USGS nor the U.S. Government shall be held liable for any damages resulting from the authorized or unauthorized use of the data.


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. [2022]. Nonindigenous Aquatic Species Database. Gainesville, Florida. Accessed [5/19/2022].

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.