Ontologia

Ruisseau· 10 segments

Upper South Branch Thunder Bay River

Crosses 3 administrative regions : Alpena, Montmorency, Oscoda

ruisseau

Total length

59km

Max discharge

2,6m³/s

Max Strahler

3

Segments matched

10

River geography3 admin regions · 0 communes

Parent watershed

hybas-7080411120450 km²

3 administrative regions crossed (GADM L2)

  • Oscoda
    Michigan · United States
    26.7 km
    in this dpt
  • Alpena
    Michigan · United States
    16.4 km
    in this dpt
  • Montmorency
    Michigan · United States
    10.1 km
    in this dpt

4 intersecting protected areas

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

Species present

98 distinct species · 247 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 35 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 Upper South Branch Thunder Bay River : 25 espèces reliées par 62 interactions GloBI sur 3 types (connectance 10.4%, filtre Serrano α=0.2). 10 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
35
Interactions affichées
62
Connectance
0.104
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

59km

Max discharge

2,6m³/s

Max Strahler

3

Segments matched

10

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