Rivière· 7 segments
Ryan Creek
Crosses 7 administrative regions : Mecosta, Milwaukee, Missaukee, Nipissing, Osceola +2
Total length
250km
Max discharge
37,6m³/s
Max Strahler
4
Segments matched
7
River geography7 admin regions · 0 communes
7 administrative regions crossed (GADM L2)
- OsceolaMichigan · United States16.1 kmin this dpt
- MecostaMichigan · United States13.2 kmin this dpt
- MilwaukeeWisconsin · United States8.0 kmin this dpt
- MissaukeeMichigan · United States6.2 kmin this dpt
- RenfrewOntario · Canada4.1 kmin this dpt
- NipissingOntario · Canada1.2 kmin this dpt
- RacineWisconsin · United States0.0 kmin this dpt
8 intersecting protected areas
Provincial Park
Haymarsh Lake State Game
IUCN VLake
Farm Service Agency Interest Of Mi
IUCN Not AssignedConservation Easement
Game Area
Bush
IUCN Not AssignedEasement
Osceola Woods
IUCN VNature Preserve
Conservation Easement
Jacobson
IUCN Not AssignedEasement
1 page = 1 named river (aggregation of 7 HydroRIVERS v10 segments). Spatial join cached after first hit.
Species present
140 distinct species · 378 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 45 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 Ryan Creek : 35 espèces reliées par 83 interactions GloBI sur 4 types (connectance 8.4%, filtre Serrano α=0.2). 10 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
250km
Max discharge
37,6m³/s
Max Strahler
4
Segments matched
7
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.