Landoltia punctata
Landoltia punctata
(dotted duckweed)

6 results for Landoltia punctata (dotted duckweed)

Impact ID Scientific Name Impact Type Study Type Study Location Impact Description Reference
3120 Landoltia punctata Competition Anecdotal Field Landoltia punctata fills in open gaps on the water surface when other floating vegetation... 15944
4343 Landoltia punctata Water Quality Experimental Laboratory Landoltia punctata take up nitrogen in roots and fronds; it prefers ammonium to nitrate 36290
4344 Landoltia punctata Water Quality Anecdotal N/A has been used to clean waste water 36291
4345 Landoltia punctata Competition Anecdotal N/A light availabilty is decreased due to dense mats of Landoltia punctata shading out native... 36298
4346 Landoltia punctata Water Quality Anecdotal N/A used in waste water remediation to eliminate high levels of nutrients 36298
4347 Landoltia punctata Harvest Anecdotal N/A plant is harvested as a substitute for alfalfa for farm animals 36298

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. [2024]. Nonindigenous Aquatic Species Database. Gainesville, Florida. Accessed [6/20/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.