Ontologia

Rivière· 18 segments

South Fork Skokomish River

Crosses 3 administrative regions : Grays Harbor, Jefferson, Mason

rivière

Total length

50km

Max discharge

33,9m³/s

Max Strahler

4

Segments matched

18

River geography3 admin regions · 0 communes

Parent watershed

hybas-7080015600620 km²

3 administrative regions crossed (GADM L2)

  • Mason
    Washington · United States
    38.5 km
    in this dpt
  • Grays Harbor
    Washington · United States
    0.0 km
    in this dpt
  • Jefferson
    Washington · United States
    0.0 km
    in this dpt

7 intersecting protected areas

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

Species present

277 distinct species · 480 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 51 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 South Fork Skokomish River : 37 espèces reliées par 92 interactions GloBI sur 6 types (connectance 7.2%, filtre Serrano α=0.2). 14 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
51
Interactions affichées
92
Connectance
0.072
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

50km

Max discharge

33,9m³/s

Max Strahler

4

Segments matched

18

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