Ludwigia grandiflora
Ludwigia grandiflora
(large-flower primrose-willow)

5 results for Ludwigia grandiflora (large-flower primrose-willow)

Impact ID Scientific Name Impact Type Study Type Study Location Impact Description Reference
3488 Ludwigia grandiflora Food Web Experimental Field Ludwigia grandiflora increased pollinator visits to Lythrum salicaria in mixed... 32944
3503 Ludwigia grandiflora Food Web Observational Field Invertebrate richness and abundance declined in ponds with high abundance of Ludwigia... 32943
4163 Ludwigia grandiflora Food Web Experimental Field When Ludwigia grandiflora was present in high abundance, pollinator densities increased by... 32944
4164 Ludwigia grandiflora Food Web Experimental Field High cover of Ludwigia grandiflora increased visitation from Syrphidae species and... 32944
4165 Ludwigia grandiflora Food Web Experimental Field Ludwigia grandiflora is highly attractive to and visited frequently by honeybees to... 32944

View all impact types for Ludwigia grandiflora
Data Disclaimer: 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 [12/1/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.