Taphromysis louisianae
(Possum shrimp)
Crustaceans-Mysids
Native Transplant

6 results for Taphromysis louisianae (Possum shrimp)
Download Data

Specimen IDStateCountyLocalityYear HUC Number What's this? Drainage nameStatus
541998 KYBrackenOhio River at RM 438.3, ORSANCO survey site OH438.3LDB2009 05090201 Ohio Brush-Whiteoakunknown
541991 KYLewisOhio River at RM 395.1, ORSANCO survey site OH395.1LDB2007 05090201 Ohio Brush-Whiteoakunknown
541980 KYMasonOhio River at RM 410.6, ORSANCO survey site OH410.6LDB2007 05090201 Ohio Brush-Whiteoakunknown
541981 OHBrownOhio River at RM 423.5, ORSANCO survey site OH423.5RDB2007 05090201 Ohio Brush-Whiteoakunknown
284806 OHClermontCrooked Run State Nature Preserve wetland [Ohio River Mile 434]1990 05090201 Ohio Brush-Whiteoakestablished
541982 OHClermontOhio River at RM 431.2, ORSANCO survey site OH431.2RDB2007 05090201 Ohio Brush-Whiteoakunknown

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 [4/19/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.