Ontologia

Rivière· 21 segments

Little Spokane River

Crosses 3 administrative regions : Pend Oreille, Spokane, Stevens

rivière

Total length

89km

Max discharge

26,6m³/s

Max Strahler

4

Segments matched

21

River geography3 admin regions · 0 communes

Parent watershed

hybas-70803378202208 km²

3 administrative regions crossed (GADM L2)

  • Spokane
    Washington · United States
    57.3 km
    in this dpt
  • Pend Oreille
    Washington · United States
    27.9 km
    in this dpt
  • Stevens
    Washington · United States
    0.0 km
    in this dpt

1 intersecting protected areas

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

Species present

152 distinct species · 555 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 40 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 Little Spokane River : 28 espèces reliées par 104 interactions GloBI sur 4 types (connectance 12.1%, filtre Serrano α=0.2). 14 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
42
Interactions affichées
104
Connectance
0.121
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

89km

Max discharge

26,6m³/s

Max Strahler

4

Segments matched

21

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