Lythrum salicaria
Lythrum salicaria
(purple loosestrife)
Plants
Exotic

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
1677621 ORLane[No locality description provided]2016 17090002 Coast Fork Willamette 
856632 ORLaneCottage Grove Lake2001 17090002 Coast Fork Willametteestablished
856633 ORLaneCottage Grove Lake2005 17090002 Coast Fork Willametteestablished
854726 ORLaneCreswell1973 17090002 Coast Fork Willametteestablished
854522 ORLaneCreswell1973 17090002 Coast Fork Willametteestablished
854529 ORLaneJasper1973 17090002 Coast Fork Willametteestablished
855069 ORLaneJasper1973 17090002 Coast Fork Willametteestablished
850951 ORLaneJasper1974 17090002 Coast Fork Willametteestablished

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.


Disclaimer:

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/23/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.