Ruisseau· 9 segments
Pickerel Creek
Crosses 7 administrative regions : Algoma, Benzie, Forest, Grand Traverse, Langlade +2
Total length
143km
Max discharge
7,8m³/s
Max Strahler
3
Segments matched
9
River geography7 admin regions · 0 communes
7 administrative regions crossed (GADM L2)
- AlgomaOntario · Canada18.7 kmin this dpt
- ShawanoWisconsin · United States14.9 kmin this dpt
- LangladeWisconsin · United States10.1 kmin this dpt
- SaginawMichigan · United States9.0 kmin this dpt
- BenzieMichigan · United States6.9 kmin this dpt
- Grand TraverseMichigan · United States0.9 kmin this dpt
- ForestWisconsin · United States0.0 kmin this dpt
7 intersecting protected areas
State Forest
Provincial Park
MNRTF Parcel
IUCN VConservation Area
Statewide Habitat Areas
IUCN VHabitat Area
Conservation Reserve
MNRTF Parcel 50
IUCN VConservation Area
MNRTF Parcel 139
IUCN VConservation Area
1 page = 1 named river (aggregation of 9 HydroRIVERS v10 segments). Spatial join cached after first hit.
Species present
480 distinct species · 1 670 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 41 species (selected proportionally per kingdom among those with at least one documented interaction here) to keep the graph readable. Hover for details, click to explore the full ecosystem of a species.
ℹ️ The territory contains many more species than displayed and all their documented interactions: the graph is intentionally the structural skeleton (top-N species by composite local score, edges filtered by Serrano 2009 disparity filter α=0.2).
Indicateurs du tissu écologique
Tissu écologique de Pickerel Creek : 28 espèces dont 2 patrimoniales (LR IUCN CR/EN/VU) reliées par 107 interactions GloBI sur 4 types (connectance 12.4%, filtre Serrano α=0.2). 14 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).
Comparaison sur la connectance du réseau local complet vs distribution nationale (toutes les communes françaises).
Hydrology (HydroRIVERS v10)
Total length
143km
Max discharge
7,8m³/s
Max Strahler
3
Segments matched
9
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.