Reference Viewer


Cut-and-Paste Reference:
McIvor, C. 2011. Unpublished data on distribution of pike killifish (Belonesox belizanus) in Everglades National Park. Provided on 7/5/2011.
Reference Details:
Reference Number: 20902
Type: Database
Author: McIvor, C.
Date (year): 2011
Title:Unpublished data on distribution of pike killifish (Belonesox belizanus) in Everglades National Park. Provided on 7/5/2011.
Publisher:
Publisher Location:
URL:
Accessed on:
Created on:
Keywords:
Species Profiles and Specimens that use this Reference:

Belonesox belizanus

    FL - Tarpon Bay, on Shark River ~22.5 km from Gulf of Mexico in upper 1/3 of Tarpon Bay.
    FL - Tarpon Bay, on Shark River ~22.5 km from Gulf of Mexico in upper 1/3 of Tarpon Bay.
    FL - Tarpon Bay, ~22.5 km from the Gulf on Shark River in upper 1/3 of Tarpon Bay
    FL - Tarpon Bay, ~22.5 km from Gulf on Shark River, in upper 1/3 of Tarpon Bay
    FL - Tarpon Bay, ~22.5 km from Gulf on Shark River, in upper 1/3 of Tarpon Bay
    FL - Harney River, midway along river ~11.4 km from Gulf.
    FL - Harney River, midway along river ~11.4 km from Gulf.
    FL - Harney River, midway along river ~11.4 km from Gulf.
    FL - Harney River, midway along river ~11.4 km from Gulf.
    FL - Shark River, 6.1 km upstream from mouth.
    FL - Big Sable Creek, ~6.6 km south of the mouth of Shark River.
    FL - Watson's River.


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