Ontologia

Ruisseau· 3 segments

Snag Creek

Crosses 4 administrative regions : Bracken, Clermont, Marshall, Woodford

ruisseau

Total length

250km

Max discharge

1m³/s

Max Strahler

2

Segments matched

3

River geography4 admin regions · 0 communes

Parent watershed

hybas-70805240802438 km²

4 administrative regions crossed (GADM L2)

  • Woodford
    Illinois · United States
    15.2 km
    in this dpt
  • Marshall
    Illinois · United States
    9.9 km
    in this dpt
  • Bracken
    Kentucky · United States
    5.6 km
    in this dpt
  • Clermont
    Ohio · United States
    0.0 km
    in this dpt

3 intersecting protected areas

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

Species present

59 distinct species · 109 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

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

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

250km

Max discharge

1,0m³/s

Max Strahler

2

Segments matched

3

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