Ontologia

Fleuve· 4 segments

Kings Creek

Crosses 4 administrative regions : Hancock, Haskell, Jefferson, Muskogee

fleuve

Total length

546km

Max discharge

1 150m³/s

Max Strahler

7

Segments matched

4

River geography4 admin regions · 0 communes

Parent watershed

hybas-70806499001019 km²

4 administrative regions crossed (GADM L2)

  • Haskell
    Oklahoma · United States
    9.5 km
    in this dpt
  • Hancock
    West Virginia · United States
    8.8 km
    in this dpt
  • Muskogee
    Oklahoma · United States
    2.4 km
    in this dpt
  • Jefferson
    Ohio · United States
    0.0 km
    in this dpt

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

Species present

375 distinct species · 571 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 54 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 Kings Creek : 44 espèces dont 2 patrimoniales (LR IUCN CR/EN/VU) reliées par 99 interactions GloBI sur 5 types (connectance 6.7%, filtre Serrano α=0.2). 11 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
55
Interactions affichées
99
Connectance
0.067
Patrimoniales
2
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

546km

Max discharge

1 150,0m³/s

Max Strahler

7

Segments matched

4

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