Specimen Information

Phyllanthus fluitans
(red root floater)
Plants
Exotic

Specimen ID1322777
GroupPlants
GenusPhyllanthus
Speciesfluitans
Common Namered root floater
StateFL
CountyDeSoto
LocalityMorgan Park, ca. 0.5 mi. E and 0.1 mi. N of the FL 70 and FL 72 junction; Peace River floodplain
Mapping AccuracyAccurate
HUC8 NamePeace
HUC8 Number03100101
HUC10 NameJoshua Creek-Peace River
HUC10 Number0310010109
HUC12 NameJohnson Lake-Peace River
HUC12 Number031001010905
Map
+
Collection Day5
Collection Month1
Collection Year2016
Year AccuracyActual
Potential Pathwayescaped captivity pond | released aquarium
Statusestablished
Reference 1
Ref. Number:10661
Author:Farid, A. (curator).
Date:2018
Title:University of South Florida Herbarium (USF)
Publisher:University of South Florida
Reference 2
Ref. Number:29179
Author:Franck, A.R., L.C. Anderson, J.R. Burkhalter, and S. Dickman.
Date:2016
Title:Additions to the flora of Florida, U.S.A. (2010-2015)
Journal:Journal of Botanical Research Institute of Texas
Volume:10
Issue:1
Pages:175-190
CommentsStagnant pool, permanently flooded depression; soil mucky over sandy substratum; subcanopy of Cephalanthus and Fraxinus caroliniana; with Salvinia minima.
Record TypeSpecimen
DisposalUniversity of South Florida
Museum Cat NumberUSF 282778
Freshwater/MarineFreshwater
Photo
Phyllanthus fluitans


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