Phragmites australis australis
Phragmites australis australis
(common reed)
Plants
Exotic
Collection Info
Point Map
Species Profile
Animated Map
Impacts

4 results for Phragmites australis australis (common reed)

Impact ID Scientific Name Impact Type Study Type Study Location Impact Description Reference
4224 Phragmites australis australis Food Web Observational Field The replacement of Spartima by Phragmites australis in marshes of southern New... 20315
4225 Phragmites australis australis Food Web Anecdotal Field The replacement of Spartima by Phragmites australis in marshes of southern New... 20315
4227 Phragmites australis australis Food Web Observational Field Phragmites australis traps sediment at high rates, magnifying a reduction in trophic... 35915
4256 Phragmites australis australis Food Web Observational Field Phragmites australis seeds are eaten by sparrows and bobolinks, and their vegetation is... 27608

View all impact types for Phragmites australis australis
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.

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. [2022]. Nonindigenous Aquatic Species Database. Gainesville, Florida. Accessed [5/26/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.