Ontologia

Ruisseau· 6 segments

Negro Creek

Crosses 3 administrative regions : Adams, Lincoln, Spokane

ruisseau

Total length

275km

Max discharge

3,1m³/s

Max Strahler

3

Segments matched

6

River geography3 admin regions · 0 communes

Parent watershed

hybas-70803638801737 km²

3 administrative regions crossed (GADM L2)

  • Lincoln
    Washington · United States
    32.6 km
    in this dpt
  • Adams
    Washington · United States
    4.8 km
    in this dpt
  • Spokane
    Washington · United States
    1.8 km
    in this dpt

2 intersecting protected areas

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

Species present

396 distinct species · 15 942 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 34 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 Negro Creek : 22 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 128 interactions GloBI sur 4 types (connectance 21.5%, filtre Serrano α=0.2). 13 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
35
Interactions affichées
128
Connectance
0.215
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

275km

Max discharge

3,1m³/s

Max Strahler

3

Segments matched

6

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