Ontologia

Rivière· 6 segments

Redhorse Creek

Crosses 4 administrative regions : Burnett, Pine, Woods, Woodward

rivière

Total length

36km

Max discharge

96,3m³/s

Max Strahler

5

Segments matched

6

River geography4 admin regions · 0 communes

Parent watershed

hybas-7080625010988 km²

4 administrative regions crossed (GADM L2)

  • Woods
    Oklahoma · United States
    24.4 km
    in this dpt
  • Pine
    Minnesota · United States
    9.9 km
    in this dpt
  • Burnett
    Wisconsin · United States
    0.5 km
    in this dpt
  • Woodward
    Oklahoma · United States
    0.0 km
    in this dpt

5 intersecting protected areas

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

Species present

31 distinct species · 38 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

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

Espèces affichées
16
Interactions affichées
26
Connectance
0.217
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

36km

Max discharge

96,3m³/s

Max Strahler

5

Segments matched

6

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