Lythrum salicaria
Lythrum salicaria
(purple loosestrife)
Plants
Exotic
Collection Info
Point Map
Species Profile
Animated Map
Impacts

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

Specimen IDStateCountyLocalityYear HUC Number What's this? Drainage nameStatus
233278 MIBarryBarry County1985 04050000 Southeastern Lake Michiganestablished
233282 MICalhounCalhoun County1985 04050000 Southeastern Lake Michiganestablished
233275 MIClintonClinton County1985 04050000 Southeastern Lake Michiganestablished
233279 MIEatonEaton County1985 04050000 Southeastern Lake Michiganestablished
233302 MIKalamazooKalamazoo County1985 04050000 Southeastern Lake Michiganestablished
233276 MIOttawaOttawa County1985 04050000 Southeastern Lake Michiganestablished

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