Specimen Information

Drosera filiformis
(threadleaf sundew)
Plants
Native Transplant

Specimen ID1467266
GroupPlants
GenusDrosera
Speciesfiliformis
Common Namethreadleaf sundew
StateVA
CountySpotsylvania
LocalityS of Frederisksburg, exit ramp from I-95 S to Rt. 1 and 17, W side of ramp between green directional sign and "Stop" sign.
Mapping AccuracyAccurate
HUC8 NameLower Rappahannock
HUC8 Number02080104
HUC10 NameMassaponax Creek-Rappahannock River
HUC10 Number0208010401
HUC12 NameMassaponax Creek
HUC12 Number020801040103
Map
+
Collection Day20
Collection Month8
Collection Year1986
Year AccuracyActual
Potential Pathwayplanted ornamental
Statusfailed
Reference 1
Ref. Number:31305
Author:Hayden, W. (curator).
Date:2018
Title:University of Richmond Herbarium (URV)
Publisher:University of Richmond
Reference 2
Ref. Number:28331
Author:SEINet Portal Network.
Date:2021
Title:Southwest Environmental Information Network
Publisher:Symbiota Software Project, Arizona State University
Reference 3
Ref. Number:31557
Author:Rice, B.A.
Date:2011
Title:The thread-leaf sundews Drosera filiformis and Drosera tracyi
Publisher:Carnivorous Plant Newsletter
Volume:40
Pages:4-16
CommentsWith Sarracenia purpurea, S. rubra, S. minor, and Drosera intermedia, all planted by P. Sheridan ca. 1980.
Record TypeSpecimen
Earliest Recorddrainage
DisposalURV
Museum Cat Number6695
Freshwater/MarineFreshwater
Photo
Drosera filiformis


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