Ontologia

Ruisseau· 4 segments

Twin Falls Creek

Crosses 4 administrative regions : Columbia-Shuswap, Lewis, Pierce, Skamania

ruisseau

Total length

32km

Max discharge

0,6m³/s

Max Strahler

2

Segments matched

4

River geography4 admin regions · 0 communes

Parent watershed

hybas-70802459301815 km²

4 administrative regions crossed (GADM L2)

  • Columbia-Shuswap
    British Columbia · Canada
    6.4 km
    in this dpt
  • Lewis
    Washington · United States
    3.2 km
    in this dpt
  • Skamania
    Washington · United States
    2.1 km
    in this dpt
  • Pierce
    Washington · United States
    1.2 km
    in this dpt

4 intersecting protected areas

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

Species present

34 distinct species · 45 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 14 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 Twin Falls Creek : 10 espèces reliées par 18 interactions GloBI sur 1 type (connectance 19.8%, filtre Serrano α=0.2). 4 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
14
Interactions affichées
18
Connectance
0.198
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

32km

Max discharge

0,6m³/s

Max Strahler

2

Segments matched

4

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