Ontologia

Ruisseau· 3 segments

Kimball Creek

Crosses 4 administrative regions : Cook, Forest, Haliburton, Lake Superior

ruisseau

Total length

115km

Max discharge

0,8m³/s

Max Strahler

1

Segments matched

3

River geography4 admin regions · 0 communes

Parent watershed

hybas-70803893501428 km²

4 administrative regions crossed (GADM L2)

  • Cook
    Minnesota · United States
    12.6 km
    in this dpt
  • Haliburton
    Ontario · Canada
    7.1 km
    in this dpt
  • Lake Superior
    Minnesota · United States
    1.5 km
    in this dpt
  • Forest
    Wisconsin · United States
    1.3 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

26 distinct species · 40 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 12 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 Kimball Creek : 11 espèces reliées par 9 interactions GloBI sur 4 types (connectance 13.6%, filtre Serrano α=0.2). 1 bulle taxonomique (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
12
Interactions affichées
9
Connectance
0.136
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

115km

Max discharge

0,8m³/s

Max Strahler

1

Segments matched

3

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