Ontologia

Ruisseau· 10 segments

Running Creek

Crosses 5 administrative regions : Arapahoe, Chippewa, Dunn, Elbert, Newton

ruisseau

Total length

601km

Max discharge

0,8m³/s

Max Strahler

2

Segments matched

10

River geography5 admin regions · 0 communes

Parent watershed

hybas-70805314001241 km²

5 administrative regions crossed (GADM L2)

  • Elbert
    Colorado · United States
    53.8 km
    in this dpt
  • Arapahoe
    Colorado · United States
    15.0 km
    in this dpt
  • Dunn
    Wisconsin · United States
    10.7 km
    in this dpt
  • Newton
    Arkansas · United States
    1.9 km
    in this dpt
  • Chippewa
    Wisconsin · United States
    0.0 km
    in this dpt

3 intersecting protected areas

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

Species present

5 distinct species · 17 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 4 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 Running Creek : 4 espèces reliées par 3 interactions GloBI sur 2 types (connectance 50.0%, filtre Serrano α=0.2).

Espèces affichées
4
Interactions affichées
3
Connectance
0.500
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

601km

Max discharge

0,8m³/s

Max Strahler

2

Segments matched

10

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