Ontologia

Ruisseau· 5 segments

Henry Creek

Crosses 4 administrative regions : Central Kootenay, Clackamas, Marion, Wheeler

ruisseau

Total length

216km

Max discharge

0,2m³/s

Max Strahler

1

Segments matched

5

River geography4 admin regions · 0 communes

Parent watershed

hybas-70804207101585 km²

4 administrative regions crossed (GADM L2)

  • Wheeler
    Oregon · United States
    6.0 km
    in this dpt
  • Clackamas
    Oregon · United States
    2.9 km
    in this dpt
  • Central Kootenay
    British Columbia · Canada
    1.2 km
    in this dpt
  • Marion
    Oregon · United States
    0.9 km
    in this dpt

4 intersecting protected areas

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

Species present

438 distinct species · 14 225 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 37 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 Henry Creek : 29 espèces reliées par 99 interactions GloBI sur 4 types (connectance 14.1%, filtre Serrano α=0.2). 9 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
38
Interactions affichées
99
Connectance
0.141
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

216km

Max discharge

0,2m³/s

Max Strahler

1

Segments matched

5

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