Ludwigia peploides
Ludwigia peploides
(floating primrose-willow)
Plants
Native Transplant

4 results for Ludwigia peploides (floating primrose-willow)
Download Data

Specimen IDCommon NameStateCountyLocalityYear HUC Number What's this? Drainage nameStatus
1634028 floating primrose-willowCAMontereyAt edge of slough below Ohlone Loop trial2019 18060005 Salinasestablished
1634172 floating primrose-willowCAMontereyFort Hunter Liggett; San Antonio River, ca. 2.2 km NW of Quail Top, ca. 0.2 rd km SE of jct of Tule and Sam Jones Rds; Ft Hunter Liggett1994 18060005 Salinasestablished
1634173 floating primrosewillowCAMontereyFort Ord National Monument; Region H1; Salinas River2014 18060005 Salinasestablished
1634174 floating primrosewillowCAMontereyFort Ord National Monument; Region H1; Salinas River2014 18060005 Salinasestablished

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 [5/6/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.