Ontologia

Ruisseau· 13 segments

Lobster Creek

Crosses 3 administrative regions : Benton, Lane, Lincoln

ruisseau

Total length

89km

Max discharge

7,3m³/s

Max Strahler

3

Segments matched

13

River geography3 admin regions · 0 communes

Parent watershed

hybas-70800146301167 km²

3 administrative regions crossed (GADM L2)

  • Benton
    Oregon · United States
    17.0 km
    in this dpt
  • Lane
    Oregon · United States
    5.3 km
    in this dpt
  • Lincoln
    Oregon · United States
    1.7 km
    in this dpt

1 intersecting protected areas

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

Species present

243 distinct species · 1 147 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

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

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

89km

Max discharge

7,3m³/s

Max Strahler

3

Segments matched

13

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