Ontologia

Ruisseau· 6 segments

South Creek

Crosses 5 administrative regions : Algoma, Elgin, Lake Erie, Ottawa, Sandusky

ruisseau

Total length

651km

Max discharge

3,6m³/s

Max Strahler

3

Segments matched

6

River geography5 admin regions · 0 communes

Parent watershed

hybas-70804989101396 km²

5 administrative regions crossed (GADM L2)

  • Sandusky
    Ohio · United States
    27.6 km
    in this dpt
  • Algoma
    Ontario · Canada
    10.0 km
    in this dpt
  • Elgin
    Ontario · Canada
    7.1 km
    in this dpt
  • Lake Erie
    Ohio · United States
    1.4 km
    in this dpt
  • Ottawa
    Ohio · United States
    0.0 km
    in this dpt

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

Species present

141 distinct species · 3 107 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 42 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 South Creek : 31 espèces reliées par 116 interactions GloBI sur 4 types (connectance 13.5%, filtre Serrano α=0.2). 11 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
42
Interactions affichées
116
Connectance
0.135
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

651km

Max discharge

3,6m³/s

Max Strahler

3

Segments matched

6

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