Ontologia

Ruisseau· 2 segments

Sourdough Creek

Crosses 4 administrative regions : Ellis, Ochiltree, Roberts, Roger Mills

ruisseau

Total length

116km

Max discharge

0m³/s

Max Strahler

1

Segments matched

2

River geography4 admin regions · 0 communes

Parent watershed

hybas-70806388802756 km²

4 administrative regions crossed (GADM L2)

  • Roberts
    Texas · United States
    10.5 km
    in this dpt
  • Ochiltree
    Texas · United States
    1.5 km
    in this dpt
  • Roger Mills
    Oklahoma · United States
    1.3 km
    in this dpt
  • Ellis
    Oklahoma · United States
    0.5 km
    in this dpt

1 intersecting protected areas

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

Species present

56 distinct species · 57 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 31 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 Sourdough Creek : 27 espèces reliées par 49 interactions GloBI sur 3 types (connectance 10.5%, filtre Serrano α=0.2). 4 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
31
Interactions affichées
49
Connectance
0.105
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

116km

Max discharge

0,0m³/s

Max Strahler

1

Segments matched

2

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