Ontologia

Ruisseau· 25 segments

Finley Creek

Crosses 4 administrative regions : Christian, Macon, Stone, Webster

ruisseau

Total length

155km

Max discharge

10,2m³/s

Max Strahler

3

Segments matched

25

River geography4 admin regions · 0 communes

Parent watershed

hybas-7080613420672 km²

4 administrative regions crossed (GADM L2)

  • Christian
    Missouri · United States
    61.5 km
    in this dpt
  • Webster
    Missouri · United States
    15.9 km
    in this dpt
  • Macon
    Illinois · United States
    10.8 km
    in this dpt
  • Stone
    Missouri · United States
    3.9 km
    in this dpt

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

Species present

64 distinct species · 92 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

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

Espèces affichées
41
Interactions affichées
57
Connectance
0.070
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

155km

Max discharge

10,2m³/s

Max Strahler

3

Segments matched

25

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