Ontologia

Rivière· 25 segments

East Fork Salmon River

Crosses 3 administrative regions : Clackamas, Custer, Hood River

rivière

Total length

80km

Max discharge

30,3m³/s

Max Strahler

5

Segments matched

25

River geography3 admin regions · 0 communes

Parent watershed

hybas-70804331001410 km²

3 administrative regions crossed (GADM L2)

  • Custer
    Idaho · United States
    92.0 km
    in this dpt
  • Clackamas
    Oregon · United States
    2.4 km
    in this dpt
  • Hood River
    Oregon · United States
    0.0 km
    in this dpt

8 intersecting protected areas

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

Species present

329 distinct species · 1 112 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 46 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 East Fork Salmon River : 33 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 89 interactions GloBI sur 4 types (connectance 8.2%, filtre Serrano α=0.2). 14 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
47
Interactions affichées
89
Connectance
0.082
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

80km

Max discharge

30,3m³/s

Max Strahler

5

Segments matched

25

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