Ontologia

Ruisseau· 7 segments

Little Badger Creek

Crosses 4 administrative regions : Faribault, Fremont, Glacier, Martin

ruisseau

Total length

76km

Max discharge

1,4m³/s

Max Strahler

2

Segments matched

7

River geography4 admin regions · 0 communes

Parent watershed

hybas-70805774301974 km²

4 administrative regions crossed (GADM L2)

  • Glacier
    Montana · United States
    19.2 km
    in this dpt
  • Faribault
    Minnesota · United States
    10.6 km
    in this dpt
  • Fremont
    Colorado · United States
    7.8 km
    in this dpt
  • Martin
    Minnesota · United States
    7.1 km
    in this dpt

2 intersecting protected areas

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

Species present

77 distinct species · 282 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 29 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 Little Badger Creek : 20 espèces reliées par 61 interactions GloBI sur 4 types (connectance 15.0%, filtre Serrano α=0.2). 9 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
29
Interactions affichées
61
Connectance
0.150
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

76km

Max discharge

1,4m³/s

Max Strahler

2

Segments matched

7

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