Panicum repens
Panicum repens
(torpedo grass)
Plants
Exotic
Collection Info
Point Map
Species Profile
Animated Map
Impacts

7 results for Panicum repens (torpedo grass)
Download Data
Click here for listing in all states

Specimen IDStateCountyLocalityYear HUC Number What's this? Drainage nameStatus
215390 FLOkeechobeeLake Okeechobee1982 03090201 Lake Okeechobeeestablished
216444 FLOkeechobeeLake Okeechobee1983 03090201 Lake Okeechobeeestablished
217771 FLOkeechobeeLake Okeechobee1984 03090201 Lake Okeechobeeestablished
219331 FLOkeechobeeLake Okeechobee1986 03090201 Lake Okeechobeeestablished
222868 FLOkeechobeeLake Okeechobee1989 03090201 Lake Okeechobeeestablished
225062 FLOkeechobeeLake Okeechobee1990 03090201 Lake Okeechobeeestablished
227804 FLOkeechobeeLake Okeechobee1992 03090201 Lake Okeechobeeestablished

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 [4/19/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.