Ontologia

Ruisseau· 11 segments

West Fork Beaver Creek

Crosses 3 administrative regions : Gallatin, Madison, Renville

ruisseau

Total length

91km

Max discharge

1,9m³/s

Max Strahler

2

Segments matched

11

River geography3 admin regions · 0 communes

Parent watershed

hybas-7080425260644 km²

3 administrative regions crossed (GADM L2)

  • Renville
    Minnesota · United States
    55.7 km
    in this dpt
  • Madison
    Montana · United States
    3.3 km
    in this dpt
  • Gallatin
    Montana · United States
    0.7 km
    in this dpt

12 intersecting protected areas

3 more protected areas

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

Species present

51 distinct species · 133 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 23 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 West Fork Beaver Creek : 19 espèces reliées par 43 interactions GloBI sur 3 types (connectance 17.0%, filtre Serrano α=0.2). 4 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
23
Interactions affichées
43
Connectance
0.170
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

91km

Max discharge

1,9m³/s

Max Strahler

2

Segments matched

11

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