Ontologia

Ruisseau· 6 segments

Hanson Creek

Crosses 4 administrative regions : Alger, Bayfield, Lake Superior, Nipissing

ruisseau

Total length

106km

Max discharge

0,4m³/s

Max Strahler

2

Segments matched

6

River geography4 admin regions · 0 communes

Parent watershed

hybas-70803496202676 km²

4 administrative regions crossed (GADM L2)

  • Bayfield
    Wisconsin · United States
    5.9 km
    in this dpt
  • Nipissing
    Ontario · Canada
    5.4 km
    in this dpt
  • Alger
    Michigan · United States
    3.4 km
    in this dpt
  • Lake Superior
    Michigan · United States
    0.0 km
    in this dpt

4 intersecting protected areas

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

Species present

56 distinct species · 161 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 32 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 Hanson Creek : 29 espèces reliées par 31 interactions GloBI sur 5 types (connectance 6.2%, filtre Serrano α=0.2). 3 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
32
Interactions affichées
31
Connectance
0.063
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

106km

Max discharge

0,4m³/s

Max Strahler

2

Segments matched

6

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