Cotula coronopifolia
Cotula coronopifolia
(common brassbuttons)
Plants
Exotic
Collection Info
Point Map
Species Profile
Animated Map

8 results for Cotula coronopifolia (common brassbuttons)
Download Data

Specimen IDStateCountyLocalityYear HUC Number What's this? Drainage nameStatus
852245 ORLaneMercer Lake OE W1978 17100205 Alseaestablished
1677744 ORLincoln[No locality description provided]2017 17100205 Alsea 
1678195 ORLincoln[No locality description provided]2018 17100205 Alsea 
1671943 ORLincoln[No locality description provided]2018 17100205 Alsea 
1672493 ORLincoln[No locality description provided]2018 17100205 Alsea 
1673411 ORLincoln[No locality description provided]2019 17100205 Alsea 
852243 ORLincolnNewport South1918 17100205 Alseaestablished
852248 ORLincolnWaldport1971 17100205 Alseaestablished

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/23/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.