Ontologia

Ruisseau· 19 segments

Stoner Creek

Crosses 3 administrative regions : Bourbon, Clark, Montgomery

ruisseau

Total length

134km

Max discharge

9,9m³/s

Max Strahler

3

Segments matched

19

River geography3 admin regions · 0 communes

Parent watershed

hybas-70805727902395 km²

3 administrative regions crossed (GADM L2)

  • Bourbon
    Kentucky · United States
    62.7 km
    in this dpt
  • Clark
    Kentucky · United States
    10.8 km
    in this dpt
  • Montgomery
    Kentucky · United States
    0.0 km
    in this dpt

1 intersecting protected areas

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

Species present

120 distinct species · 818 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

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

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

134km

Max discharge

9,9m³/s

Max Strahler

3

Segments matched

19

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