Ontologia

Rivière· 68 segments

Swan River

Crosses 3 administrative regions : Flathead, Lake, Missoula

rivière

Total length

1 046km

Max discharge

34,1m³/s

Max Strahler

4

Segments matched

68

River geography3 admin regions · 0 communes

Parent watershed

hybas-70803313501943 km²

3 administrative regions crossed (GADM L2)

  • Lake
    Montana · United States
    110.6 km
    in this dpt
  • Missoula
    Montana · United States
    91.3 km
    in this dpt
  • Flathead
    Montana · United States
    24.4 km
    in this dpt

11 intersecting protected areas

2 more protected areas

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

Species present

160 distinct species · 297 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 45 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 Swan River : 38 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 69 interactions GloBI sur 4 types (connectance 7.0%, filtre Serrano α=0.2). 7 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
45
Interactions affichées
69
Connectance
0.070
Patrimoniales
1
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

1 046km

Max discharge

34,1m³/s

Max Strahler

4

Segments matched

68

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