Ontologia

Rivière· 67 segments

Quinault River

Crosses 3 administrative regions : Grays Harbor, Jefferson, Mason

rivière

Total length

117km

Max discharge

89,7m³/s

Max Strahler

4

Segments matched

67

River geography3 admin regions · 0 communes

Parent watershed

hybas-70800151801140 km²

3 administrative regions crossed (GADM L2)

  • Grays Harbor
    Washington · United States
    79.6 km
    in this dpt
  • Jefferson
    Washington · United States
    42.6 km
    in this dpt
  • Mason
    Washington · United States
    3.1 km
    in this dpt

9 intersecting protected areas

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

Species present

1 113 distinct species · 19 490 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 48 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 Quinault River : 36 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 103 interactions GloBI sur 5 types (connectance 9.1%, filtre Serrano α=0.2). 12 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
48
Interactions affichées
103
Connectance
0.091
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

117km

Max discharge

89,7m³/s

Max Strahler

4

Segments matched

67

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