Ontologia

Ruisseau· 3 segments

Stanley Creek

Crosses 4 administrative regions : Benzie, Lake, Lanark, Saint Louis

ruisseau

Total length

269km

Max discharge

0,4m³/s

Max Strahler

1

Segments matched

3

River geography4 admin regions · 0 communes

Parent watershed

hybas-70804104501148 km²

4 administrative regions crossed (GADM L2)

  • Saint Louis
    Minnesota · United States
    6.5 km
    in this dpt
  • Lanark
    Ontario · Canada
    2.6 km
    in this dpt
  • Benzie
    Michigan · United States
    2.1 km
    in this dpt
  • Lake
    Minnesota · United States
    0.7 km
    in this dpt

2 intersecting protected areas

1 page = 1 named river (aggregation of 3 HydroRIVERS v10 segments). Spatial join cached after first hit.

Species present

169 distinct species · 440 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).

RègnesAnimalPlanteChampignonBacterie
RelationsPredationParasitismeSymbiosePollinisation
StatutEn dangerVulnérableProtégéeEndémique

Indicateurs du tissu écologique

Tissu écologique de Stanley Creek : 32 espèces reliées par 80 interactions GloBI sur 6 types (connectance 7.7%, filtre Serrano α=0.2). 14 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
46
Interactions affichées
80
Connectance
0.077
Patrimoniales
0
Plus dense que (national)0 %(top 100%)

Comparaison sur la connectance du réseau local complet vs distribution nationale (toutes les communes françaises).

Hydrology (HydroRIVERS v10)

Total length

269km

Max discharge

0,4m³/s

Max Strahler

1

Segments matched

3

HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.