Ontologia

Ruisseau· 18 segments

Limestone Creek

Crosses 4 administrative regions : Halton, Madison, Onondaga, Thunder Bay

ruisseau

Total length

1 218km

Max discharge

11,7m³/s

Max Strahler

3

Segments matched

18

River geography4 admin regions · 0 communes

Parent watershed

hybas-70804543206325 km²

4 administrative regions crossed (GADM L2)

  • Onondaga
    New York · United States
    33.8 km
    in this dpt
  • Thunder Bay
    Ontario · Canada
    7.4 km
    in this dpt
  • Halton
    Ontario · Canada
    6.6 km
    in this dpt
  • Madison
    New York · United States
    4.7 km
    in this dpt

2 intersecting protected areas

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

Species present

404 distinct species · 6 499 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 36 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 Limestone Creek : 24 espèces reliées par 77 interactions GloBI sur 4 types (connectance 12.2%, filtre Serrano α=0.2). 12 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
36
Interactions affichées
77
Connectance
0.122
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

1 218km

Max discharge

11,7m³/s

Max Strahler

3

Segments matched

18

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