Ontologia

Rivière· 6 segments

Ontonagon River

Crosses 4 administrative regions : Gogebic, Lake Superior, Ontonagon, Vilas

rivière

Total length

53km

Max discharge

75,8m³/s

Max Strahler

5

Segments matched

6

River geography4 admin regions · 0 communes

Parent watershed

hybas-7080343660772 km²

4 administrative regions crossed (GADM L2)

  • Ontonagon
    Michigan · United States
    22.4 km
    in this dpt
  • Vilas
    Wisconsin · United States
    10.8 km
    in this dpt
  • Lake Superior
    Michigan · United States
    1.7 km
    in this dpt
  • Gogebic
    Michigan · United States
    0.0 km
    in this dpt

3 intersecting protected areas

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

Species present

114 distinct species · 255 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 38 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 Ontonagon River : 28 espèces reliées par 86 interactions GloBI sur 3 types (connectance 12.2%, filtre Serrano α=0.2). 10 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
38
Interactions affichées
86
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

53km

Max discharge

75,8m³/s

Max Strahler

5

Segments matched

6

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