Specimen Information

Pomacea maculata
Pomacea maculata
(giant applesnail)
Mollusks-Gastropods
Exotic

Specimen ID879958
GroupMollusks-Gastropods
GenusPomacea
Speciesmaculata
Common Namegiant applesnail
StateSC
CountyCharleston
Localitypond in Village Green community (just outside SW bend of Fieldstone Cir)
Mapping AccuracyAccurate
HUC8 NameCooper
HUC8 Number03050201
HUC10 NameAshley River
HUC10 Number0305020106
HUC12 NameLower Ashley River
HUC12 Number030502010605
Map
+
Collection Month9
Collection Year2015
Year AccuracyActual
Potential Pathwayreleased aquarium
Statusestablished
Reference 1
Ref. Number:28081
Author:Kingsley-Smith, P., A. Fowler, E. Gooding, and D. Knott.
Date:2015
Title:SCDNR Marine Resources Research Institute Report to GSARP.
Publisher:South Carolina Marine Resource Research Institute
Pages:7
Reference 2
Ref. Number:32245
Author:Gooding, E.L., A.E. Fowler, D. Knott, R.T Dillon, Jr., T. Brown, M.R. Kendrick, and P.R. Kingsley-Smith
Date:2018
Title:Life History and Phenological Characteristics of the Invasive Island Apple Snail Pomacea maculata (Perry, 1810) in Stormwater Retention Ponds in Coastal South Carolina, USA
Journal:Journal of Shellfish Research
Volume:37
Issue:1
Pages:229-238
Commentspart of survey expanded to all ponds with 0.5 mile radius of original site of known introduction
Record TypePersonal communication
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. [2024]. Nonindigenous Aquatic Species Database. Gainesville, Florida. Accessed [11/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.