Specimen Information

Trachemys scripta elegans
Trachemys scripta elegans
(Red-eared Slider)
Reptiles-Turtles
Native Transplant

Specimen ID1658098
GroupReptiles-Turtles
GenusTrachemys
Speciesscripta
Subspecieselegans
Common NameRed-eared Slider
StateIN
CountyMarion
LocalityCentral Canal, Indianapolis
Mapping AccuracyAccurate
HUC8 NameUpper White
HUC8 Number05120201
HUC10 NamePleasant Run-White River
HUC10 Number0512020112
HUC12 NamePogues Run-White River
HUC12 Number051202011201
Map
+
Collection Year2002
Year AccuracyActual
Potential Pathwayreleased pet | escaped captivity pond
Statusunknown
Reference 1
Ref. Number:36141
Author:Conner, C. A., B. A. Douthitt, and T. J. Ryan.
Date:2005
Title:Descriptive ecology of a turtle assemblage in an urban landscape
Journal:The American Midland Naturalist
Volume:153
Issue:2
Pages:428-435
Reference 2
Ref. Number:35920
Author:Kikillus, K., K. M. Hare, and S. Hartley.
Date:2010
Title:Minimizing false-negatives when predicting the potential distribution of an invasive species: a bioclimatic envelope for the red-eared slider at global and regional scales
Journal:Animal Conservation
Volume:13
Pages:5-15
Reference 3
Ref. Number:31353
Author:Spear, M.J., A.K. Elgin, and E.K. Grey.
Date:2018
Title:Current and Projected Distribution of the Red-Eared Slider Turtle, Trachemys scripta elegans, in the Great Lakes Basin
Journal:American Midland Naturalist
Volume:179
Issue:2
Pages:191-221
Record TypeLiterature
Freshwater/MarineFreshwater


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 [7/1/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.