Palaemonetes kadiakensis
Palaemonetes kadiakensis
(Mississippi Grass Shrimp)
Crustaceans-Shrimp
Native Transplant
Collection Info
Point Map
Species Profile
Animated Map

4 results for Palaemonetes kadiakensis (Mississippi Grass Shrimp)
Download Data
Click here for listing in all states

Specimen IDStateCountyLocalityYear HUC Number What's this? Drainage nameStatus
541946 WVJacksonOhio River at RM 218.1, ORSANCO survey site OH218.1LDB2010 05030202 Upper Ohio-Shadeestablished
541947 WVJacksonOhio River at RM 218.5, ORSANCO survey site OH218.5LDB2010 05030202 Upper Ohio-Shadeestablished
541948 WVJacksonOhio River at RM 222.7, ORSANCO survey site OH222.7LDB2010 05030202 Upper Ohio-Shadeestablished
541957 WVJacksonOhio River at RM 231.7, ORSANCO survey site OH231.7RDB2010 05030202 Upper Ohio-Shadeestablished

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